On Mon, 14 Aug 2000, Chris wrote:

>     Last I remember, the hang up with BootX is that a mechanism had to be
> worked out for passing down a device tree into the NetBSD kernel. (Which
> would likely be a non-OFW ppc solution. But couldn't one just hardcode
> enough information into the kernel so that when (OFW Version==NULL) or some
> such, we assume a NuBus based system and default ROM locations, etc.; enough
> to pull the Gestault ID and go from there? We're not talking about a whole
> lot of info to add, it's just the 61xx, 71xx, 81xx and a few variations of
> those models that we're talking about. And with any luck, they'll probably
> use most of the same parameters.

I think the thing is that we would only get the OF version from calling
OF, which we can't do w/o OF. :-)

Probably the best thing to do is ask the bootX author what it provides the
kernel, and see if there's a way we can tell if we were loaded by OF or
bootX. :-)

>     It would be nice though, to get an MI NuBus framework going, though not
> necessary at this point. That way 68k and PPC could get NuBus things working
> with minimum fuss. I also think that the Data General AViiON [Motorola 88k
> based] systems use NuBus, so that would be a kick start for the 88k port as
> well (though they may be proprietary like everything else in them)

That would be cool!

Take care,

Bill