-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

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 
that's it.

> 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.

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iQEVAwUBRew8kspnzkX8Yg2nAQIS7Af/VMkx8SEkhNKouUryP3py5WjIfqYZm8rs
s5wNx2ZEYR3qSmNMAgEI2Q7N0DzAasSV0O2CtcLy51rwgdOKeXi505i4W/9tL4xa
x6E5CYjDIvvzBfehjYljsaeYVODmqqscJ3sw+nEorUFcoeo+hExKG6tUo88JIQPV
CobLS6WE7QjmRmOmn4Cp40WcPJyosD3dPriVao2J9OfiHiZxM+i9rAIBX6mynDyD
24otwDwRl50G+V4jUHLXyUBWAL2CYPagQ9bM5Q62BIt09/Ie/34eyKYIMZ8yxv04
o6G+CltahAemCxGbsi+rBNiYLPLhHq0M+K7Fdk+KdGau4zLJ11FxQQ==
=6i2I
-----END PGP SIGNATURE-----