OF bug of the week

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

Hello,

just for the records. I put a RealTek 8029 card ( cheap PCI
NE2k 
compatible ) into my Beige G3 only to find out that OF (
2.0f1 ) must 
be completely on drugs or something - it mapped both the
8029's and the 
onboard graphics controller's I/O registers to 0x1000. So
when ne tries 
to attach it messes up the video output.
Is that just me or can anyone reproduce this?

The obvious workaround would be to disable I/O accesses in
machfb since 
neither machfb nor XFree's atimisc driver actually care
about the I/O 
range - both prefer the memory-mapped registers.

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

iQEVAwUBRTQUH8pnzkX8Yg2nAQLj8Qf/aVleX9ePFOL/vpnzQe0fdoljwfPS
ocme
9n052co5pcKXV2/X2qcPc48kD/NAdqe8S7dMyHVObHY4ZOoMSVieoBX2C0gs
8WOG
xjAeiihadaYujS7oBvEodkf+CsP2eIArJ7mnCy9ElfNgrh13ZZzZXJCHDYQF
dEvU
mCzWc4mcQ3NDDRsgeXfq2ykN0J4Usys3YB4/wFFotuLlocNJ5DdvWf8rzzyK
zavs
dVG5aVvZQUUEUuu72NKX4sBhXDYAoJPv4+HMkEGxqdTiTzB3ttfqFzyeHfLr
vnWl
lFrPbIIlUgYk7ljB2htM3Nl4PU3b9Zr2DU3BHmW3CTANqMXt1MUCbw==
=HKsn
-----END PGP SIGNATURE-----

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

Hello,

On Oct 16, 2006, at 19:22, Michael Lorenz wrote:

> just for the records. I put a RealTek 8029 card ( cheap
PCI NE2k 
> compatible ) into my Beige G3 only to find out that OF
( 2.0f1 ) must 
> be completely on drugs or something - it mapped both
the 8029's and 
> the onboard graphics controller's I/O registers to
0x1000. So when ne 
> tries to attach it messes up the video output.
> Is that just me or can anyone reproduce this?

Turns out it's not OF - the graphics controller's OF
properties only 
ever mention the aperture's address and don't say anything
about the IO 
range. No idea how the 0x1000 got there, probably the ATI
firmware.

> The obvious workaround would be to disable I/O accesses
in machfb 
> since neither machfb nor XFree's atimisc driver
actually care about 
> the I/O range - both prefer the memory-mapped
registers.

Turns out machfb doesn't even try to map it so I just
disabled IO 
accesses and the problem went away.

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

iQEVAwUBRTUWscpnzkX8Yg2nAQJkQggAiivKhkUSGGywz0IwvgTxDqe1v3SR
e1OX
uXrACKzYNZyVQh/B5y/P8BwkF0xTbCqRiGZ+jRdhTuuCnBULIMq6w36FB2O4
kqQ3
NfYZ4qAOFcdN3iX5GhhxpU6Lv2YFcuTcnMv+kTFvek51MDbLoAdd4oS0tuXh
b0UI
upLL7ncGcTkWD1kHNiOFJeKOHCZe2T6sussXjqtjDB4gArMSZCTD6fwTqITr
oY+P
hvs+P6mQ1KTYNyGM7kHNWPozzD/l+OieoJYujBHVHtychHfaAhMr1yl+ZpxW
R4H2
6R5BZzRpQNJm8JiP0GENdH1He008z9l3bg1c+sv7sEKO4h8R0qBMgA==
=afyb
-----END PGP SIGNATURE-----

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


On Oct 17, 2006, at 1:45 PM, Michael wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello,
>
> On Oct 16, 2006, at 19:22, Michael Lorenz wrote:
>
>> just for the records. I put a RealTek 8029 card (
cheap PCI NE2k  
>> compatible ) into my Beige G3 only to find out that
OF ( 2.0f1 )  
>> must be completely on drugs or something - it
mapped both the  
>> 8029's and the onboard graphics controller's I/O
registers to  
>> 0x1000. So when ne tries to attach it messes up the
video output.
>> Is that just me or can anyone reproduce this?
>
> Turns out it's not OF - the graphics controller's OF
properties  
> only ever mention the aperture's address and don't say
anything  
> about the IO range. No idea how the 0x1000 got there,
probably the  
> ATI firmware.
>
>> The obvious workaround would be to disable I/O
accesses in machfb  
>> since neither machfb nor XFree's atimisc driver
actually care  
>> about the I/O range - both prefer the memory-mapped
registers.
>
> Turns out machfb doesn't even try to map it so I just
disabled IO  
> accesses and the problem went away.
>

Maybe that'll fix the Rage LT Pro?


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)

iD8DBQFFNTFUBZaZ8/mXbSkRAgYmAJwOCMnIX2fd6ZrQrvz1+qAW36FApwCf
TQic
AVmoGWX1CjbSOctP24qLx58=
=eWca
-----END PGP SIGNATURE-----

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

Hello,

On Oct 17, 2006, at 15:38, Chris Tribo wrote:

> On Oct 17, 2006, at 1:45 PM, Michael wrote:
>
>> Hello,
>>
>> On Oct 16, 2006, at 19:22, Michael Lorenz wrote:
>>
>>> just for the records. I put a RealTek 8029 card
( cheap PCI NE2k 
>>> compatible ) into my Beige G3 only to find out
that OF ( 2.0f1 ) 
>>> must be completely on drugs or something - it
mapped both the 8029's 
>>> and the onboard graphics controller's I/O
registers to 0x1000. So 
>>> when ne tries to attach it messes up the video
output.
>>> Is that just me or can anyone reproduce this?
>>
>> Turns out it's not OF - the graphics controller's
OF properties only 
>> ever mention the aperture's address and don't say
anything about the 
>> IO range. No idea how the 0x1000 got there,
probably the ATI 
>> firmware.
>>
>>> The obvious workaround would be to disable I/O
accesses in machfb 
>>> since neither machfb nor XFree's atimisc driver
actually care about 
>>> the I/O range - both prefer the memory-mapped
registers.
>>
>> Turns out machfb doesn't even try to map it so I
just disabled IO 
>> accesses and the problem went away.
>>
>
> Maybe that'll fix the Rage LT Pro?

Maybe - if something else keeps hammering the LT's IO
registers. That 
should be easy to check though.

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

iQEVAwUBRTVsd8pnzkX8Yg2nAQIZyAf8CoMvQOezpJJxIWGuo3iyRMkzXVGC
1DkV
PIh2ilMNiPqXCQ1n0fVySdZO9a6teQ+zoD7IpvED+VXaQyEeJcnKlSO4VIrF
2dP9
j89XPX+IRsGZdVl90zVLeljYi85dERc43hYglQVXZnQC5D7J13zClZryFuqm
Vttu
yyVz29OH1WW+zUYpp7Zb7qdU2oBq1W2ef4pLo6g9TAlDLNYJ94mAFVm4qlfH
uiyI
YPVJgsnRZWvTdKdJtUZW930bBTFeHIhVaTem19cdcJqLoDsYMVb5aUhEX76t
sPxp
kec2+C7sosfs4CfB7u+DSt9Imv1UJCIWWVCO5vALTF1kzZo21UtGVQ==
=gRYn
-----END PGP SIGNATURE-----