[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 944628] [NEW] Documentation for mtdblock, option-rom,
From: |
Brian Vandenberg |
Subject: |
[Qemu-devel] [Bug 944628] [NEW] Documentation for mtdblock, option-rom, and pflash is non-existent |
Date: |
Fri, 02 Mar 2012 08:22:52 -0000 |
Public bug reported:
The options -mtdblock, -option-rom, and -pflash are severely under-
documented. For example:
-mtdblock -- It isn't at all clear what this does from --help or the
documentation, and it's especially not clear that it's only implemented
for ARM right now
-option-rom is only implemented for a handful of architectures,
including palm, pc, pci, and one or two others
-pflash looks to be implemented for most if not all architectures, but
there's nothing informing the user that it replaces the bios if -bios
isn't used in tandem with -pflash, and it isn't clear whether the user
could add multiple pflash roms
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/944628
Title:
Documentation for mtdblock, option-rom, and pflash is non-existent
Status in QEMU:
New
Bug description:
The options -mtdblock, -option-rom, and -pflash are severely under-
documented. For example:
-mtdblock -- It isn't at all clear what this does from --help or the
documentation, and it's especially not clear that it's only
implemented for ARM right now
-option-rom is only implemented for a handful of architectures,
including palm, pc, pci, and one or two others
-pflash looks to be implemented for most if not all architectures, but
there's nothing informing the user that it replaces the bios if -bios
isn't used in tandem with -pflash, and it isn't clear whether the user
could add multiple pflash roms
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/944628/+subscriptions