Subject: Re: wscons support for various framebuffers (questions from NetBSD sparc newbie)
To: der Mouse <mouse@Rodents.Montreal.QC.CA>
From: Michael Lorenz <firstname.lastname@example.org>
Date: 03/05/2007 10:51:46
-----BEGIN PGP SIGNED MESSAGE-----
On Mar 5, 2007, at 04:04, der Mouse wrote:
>>> If it's doing bus enumeration (SBus in this case), [...]
>> And what makes you think it's doing that?
> Greg Woods's post, of course.
>> Just read the source.
> Okay, I have.
> It certainly is trying to do something very much like SBus enumeration;
> see the call sparcPromInit() and the loop that follows in xf86SbusProbe
> and the implementations of those functions in os-support/bus/*SBus.c.
> (Though this is actually just walking the device tree set up by the
> PROM at POST time, it's close enough to SBus enumeration to trip my
> "this is something the X server has no business doing" reaction.)
As far as I remember that's for X -configure. When you actually run the
Xserver you point it at whatever fb devices you want it to use and
> It also seems to think that bwtwos exist only at sbus, which is simply
> wrong (bwtwos exist on machines that don't even *have* sbus), and is
> yet another layer violation (it shouldn't care where the bwtwo is
> attached; that's what kernel drivers are for).
You fell for their confusing naming scheme.
Their 'SBus support' really doesn't know anything about actual SBus -
it's talking to whatever it finds behind /dev/fb* - even FFBs.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
-----END PGP SIGNATURE-----