From: Alan <alan@lxorguk.ukuu.org.uk>
Cc: Liang Yang <multisyncfe991@hotmail.com>,
"Petersson, Mats" <Mats.Petersson@amd.com>,
xen-devel@lists.xensource.com, tim.post@netkinetics.net,
Keir Fraser <keir@xensource.com>,
xen-users@lists.xensource.com
Subject: Re: Re: logs attached. Re: [Xen-users] Can not findthe cdrom device in /dev/ afterbooted into xen(3.0.3)
Date: Fri, 1 Dec 2006 19:58:36 +0000 [thread overview]
Message-ID: <20061201195836.439e5ca1@localhost.localdomain> (raw)
In-Reply-To: <C19631F1.53B5%keir@xensource.com>
On Fri, 01 Dec 2006 19:24:33 +0000
Keir Fraser <keir@xensource.com> wrote:
> Looks like the I/O ports are allocated correctly to the device in both cases
> (both Xen and native). So I have no idea why the IDE PCI probing code isn't
> picking up on this. At this point I'd be adding tracing to the two kernels
> to find out where their probing paths diverge.
Looking over the current kernel code it is known to work in the non-Xen
case. The native mode on the ESB2 has other problems recently reported
but they would cause hangs later with stuck interrupts. Since I've got
bugs filed on this I know the detection works outside of Xen.
The old IDE probe code predates PCI so conveniently the PCI side of the
scan logic is all in setup-pci.c. Modules registering with ide during
init are added to a list and all run post init, modules added later get
their setup methods run immediately. Thus you can trace loading the piix
module pretty directly through idepci_register_driver and
ide_setup_pci_device, beyond that you are pretty much out of PCI territory
next prev parent reply other threads:[~2006-12-01 19:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 6:17 Can not find the cdrom device in /dev/ on xen 3.0.3 Liang Yang
2006-12-01 16:12 ` Can not find the cdrom device in /dev/ after booted into xen(3.0.3) Liang Yang
2006-12-01 16:22 ` [Xen-users] " Petersson, Mats
2006-12-01 16:38 ` Liang Yang
2006-12-01 16:44 ` Keir Fraser
2006-12-01 16:52 ` [Xen-devel] " Petersson, Mats
2006-12-01 17:23 ` Liang Yang
2006-12-01 17:33 ` Re: [Xen-users] " Keir Fraser
2006-12-01 18:05 ` Tim Post
2006-12-01 18:27 ` logs attached. Re: [Xen-users] Can not find the cdrom device in /dev/ afterbooted " Liang Yang
2006-12-01 18:34 ` Keir Fraser
2006-12-01 18:48 ` [Xen-devel] Re: logs attached. " Liang Yang
2006-12-01 18:56 ` Re: logs attached. Re: [Xen-users] " Keir Fraser
2006-12-01 18:58 ` Keir Fraser
2006-12-01 19:19 ` Re: logs attached. Re: [Xen-users] Can not findthe " Liang Yang
2006-12-01 19:24 ` Keir Fraser
2006-12-01 19:58 ` Alan [this message]
2006-12-01 19:39 ` [Xen-devel] Re: logs attached. " Tim Post
2006-12-01 19:10 ` Re: logs attached. Re: [Xen-users] Can not find the " Alan
2006-12-01 19:10 ` Keir Fraser
2006-12-01 19:00 ` [Xen-devel] Re: logs attached. " Tim Post
2006-12-01 18:28 ` Can not find the cdrom device in /dev/ after booted " Tim Post
2006-12-01 18:34 ` [Xen-users] Can not find the cdrom device in /dev/ afterbooted " Liang Yang
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-all 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=20061201195836.439e5ca1@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Mats.Petersson@amd.com \
--cc=keir@xensource.com \
--cc=multisyncfe991@hotmail.com \
--cc=tim.post@netkinetics.net \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.