[ros-kernel] Re: RE: Re: Gcc and binutils release

[Robert C. <rob...@it...>]

----- Original Message -----
From: "Brian Palmer" <br...@sg...>
>
> About ReactOS being multiboot compliant -- I don't see how we can
accomplish
> this without an intermediate boot loader. ReactOS will need to have
hardware
> & registry information passed in from the boot loader, and the list of
> modules to load is specified in the registry. All this doesn't fit
very well
> into the multiboot spec.

Oh. Uhmm, lets see now, in most free os's hardware is detected by the
kernel and config data is determined by the root partition.

So for ReactOS (please correct me if I'm wrong)
hardware is detected _pre_ kernel loading and config data is determined
by the SYSTEMROOT.

hardware: how will ReactOS deal with plugnplay and the like? I would
have thought that the kernel (or a module) will need to be able to
detect and categorise new hardware at runtime - think USB. Win2k
certainly does this. This implies to me that the HKCC hive is maintained
bythe kernel under NT, not the boot loader? 'course you folk are the
gurus, and wrote ROS, so I'll just listen now :]. Anyway, I'd guess that
from the Grub point of view arbitrary h/w detection is a kernel
responsibility, so whatever Grub is told is the kernel is what needs to
perform that detection. Chain loading here we come.

SYSTEMROOT: well thats simply a root partition + path specifier.

So the only thing I see is that the _initial_ h/w detection is done
outside the kernel today.

*shrug* it's not going to worry me much one way or another though :}. I
only asked in case time migrating freeloader could be saved...

Rob


====================================================
= To remove yourself from this mailing list, go to =
= http://www.reactos.com/home/mailing.html         =
====================================================