On Thu, Jun 14, 2007 at 11:11:10PM +0200, Christoph Badura wrote:
> On Thu, Jun 14, 2007 at 08:17:29PM +0200, Manuel Bouyer wrote:
> > On Thu, Jun 14, 2007 at 06:05:57PM +0200, Christoph Badura wrote:
> > > No, obviously it doesn't.  That begs the question what all the code
> > > is supposed to do that relies on Xen getting the bootinfo from the
> > > bios?
> > I suspect it's an heritage from i386. What code are you talking about ?
> 
> The code in matchbiosdisks(), findroot(), cpu_rootconf() in
> sys/arch/xen/i386/autoconf.c for example.

I think it's mostly unused or useless. I think the only important thing is
the call to xen_parse_cmdline(XEN_PARSE_BOOTDEV, &xcp) in findroot().
This needs cleanup, but whenever it's possible to get some information from
grub via Xen needs to be investicated. 

> 
> > > > > This is to be expected, because grub(1) first probes the IDE/ATA disks and
> > > > > then the SCSI disks.  (I believe it fails to probe the ld(4) disks on NetBSD.)
> > > > works for me ...
> > > What works for your?
> > It properly probes ld(4)
> 
> So, you invoke just plain "grub --no-floppy" and it probes the ld(4) disks
> that the kernel knows about?  I don't believe you.  Because there is no
> code in lib/device.c that opens an ld(4) device.

Hum, maybe I added the ld entry myself in device.map, I can't remember.
But booting a ld device from grub definitively works :)

-- 
Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
     NetBSD: 26 ans d'experience feront toujours la difference
--