Date: Tue, 16 May 2006 09:20:32 +0200 From: Milan Obuch <current@dino.sk> To: freebsd-current@freebsd.org Subject: Weird thing - pciconf reading differs in two systems Message-ID: <200605160920.33323.current@dino.sk>
next in thread | raw e-mail | index | archive | help
Hi,
I was trying to test miniPCI atheros-based card in wrap, using 7-CURRENT. S=
ome=20
time ago, it attached as ath0, I did some configuration and it looked OK.=20
Yesterday, I tested it again with system built from sources cvsupped at May=
=20
12. No attachment, pciconf -lv said (relevant device)
none0@pci0:13:0: class=3D0x020000 card=3D0x00000000 chip=3D0xff16168c rev=
=3D0x01=20
hdr=3D0x00
vendor =3D 'Atheros Communications Inc.'
class =3D network
subclass =3D ethernet
=46rom some earlier conversation I got chips with ID beginning 0xFF are=20
pre-production and should not be used.
Just out of curiosity I put this card in my tablet TC1000, with system buil=
t=20
from sources cvsupped at May 15 and got
ath0@pci0:10:0: class=3D0x020000 card=3D0x000d17f9 chip=3D0x001b168c rev=3D=
0x01=20
hdr=3D0x00
This makes me wonder - how could the same card be identified as two differe=
nt=20
devices? I tested the same card, then another one and the result is the sam=
e.=20
Working in my tablet, not working in WRAP. There is one difference, however=
-=20
kernel in WRAP has ath built-in, in my tablet I am kldloading it.
If it were the other way round, I would be happier - I can use those cards =
for=20
some radio links, but it would not be less surprising.
Any ideas?
Regards,
Milan
=2D-=20
No need to mail me directly. Just reply to mailing list, please.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200605160920.33323.current>