From: "Gerd Hoffmann" <kraxel@redhat.com>
To: devel@edk2.groups.io, James.Bottomley@hansenpartnership.com
Cc: chris.willing@linux.com, ardb+tianocore@kernel.org, jiewen.yao@intel.com
Subject: Re: [edk2-devel] [PATCH 1/1] OvmfPkg PlatformBootManagerLib: Move TryRunningQemuKernel()
Date: Wed, 11 Aug 2021 08:08:14 +0200 [thread overview]
Message-ID: <20210811060814.vnxegcrny72enjmt@sirius.home.kraxel.org> (raw)
In-Reply-To: <5c85a3f963d1ab7d20e177db9a07a73e82a0eed0.camel@HansenPartnership.com>
Hi,
> > -drive file=disk.img,format=raw,cache=none,index=0,media=disk \
> > -cdrom
> > /storage/iso/slackware/slackware64-15.0/slackware64-15.0-20210807.iso
>
> There's no definition of a disk device in here.
First line is disk, second is cdrom. Both are attached to the piix4 ide
controller.
Linux finds the controller just fine in both cases (see bugzilla for
the logs):
ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc040 irq 14
ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc048 irq 15
But only in one case it finds disk and cdrom:
ata1.00: ATA-7: QEMU HARDDISK, 2.5+, max UDMA/100
ata1.00: 41943040 sectors, multi 16: LBA48
ata2.00: ATAPI: QEMU DVD-ROM, 2.5+, max UDMA/100
[ ... ]
Not obvious why. There isn't an error message in the non-working case.
Does ovmf talk to the ide controller in case the order of the two calls
is changed? Maybe that does some initialization which the linux driver
depends on.
take care,
Gerd
prev parent reply other threads:[~2021-08-11 6:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 2:02 [PATCH 0/1] OvmfPkg PlatformBootManagerLib: Move TryRunningQemuKernel() Christoph Willing
2021-07-28 2:02 ` [PATCH 1/1] " Christoph Willing
2021-08-09 13:08 ` [edk2-devel] " Ard Biesheuvel
[not found] ` <1695D2E15A92C8E7.3876@groups.io>
2021-08-09 12:53 ` Christoph Willing
2021-08-09 14:52 ` James Bottomley
2021-08-10 0:10 ` Christoph Willing
2021-08-10 6:01 ` Gerd Hoffmann
2021-08-10 12:10 ` Christoph Willing
2021-08-10 14:26 ` James Bottomley
2021-08-10 23:04 ` Christoph Willing
2021-08-10 23:24 ` James Bottomley
2021-08-11 0:34 ` Christoph Willing
2021-08-11 6:12 ` Gerd Hoffmann
2021-08-11 9:55 ` Christoph Willing
2021-08-11 10:30 ` Ard Biesheuvel
2021-08-12 12:41 ` Christoph Willing
2021-08-12 13:36 ` Gerd Hoffmann
2021-08-12 14:07 ` Christoph Willing
2021-08-11 6:08 ` Gerd Hoffmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210811060814.vnxegcrny72enjmt@sirius.home.kraxel.org \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox