Re: NetBSD 4.0.1 on 7300 with G3 card

[Michael <macallan%netbsd.org@localhost>]

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

Hello,

On Feb 8, 2009, at 7:10 PM, Georg Schwarz wrote:

> - The Sonnect Crescendo CPU seems to work fine. Now I am wondering  
> how to enable the L2 cache.
>
> cpu0 at mainbus0: 750 (Revision 3.0), ID 0 (primary)
> cpu0: HID0 8290c0a4<EMCP,ECLK,DOZE,DPM,ICE,DCE,SGE,BTIC,BHT>,  
> powersave: 1
> cpu0: 500.00 MHz L2 cache present but not enabled
>
> I came across http://mail-index.netbsd.org/port-macppc/2001/01/05/0000.html 
>  and http://mail-index.netbsd.org/port-macppc/2001/01/05/0007.html
> How do I figure out which L2RAM option is appropriate?
>
> According to the sticker on the card I have a 500 MHz G3 with 1 MB  
> L2. I assume the L2 is running at only half the 500 MHz, or is it  
> really using the full 500 MHz?
> I think it is this card:
> http://www.sonnettech.com/product/crescendo_pci.html

With cards like this it's always half or less. I'd start with half  
speed / write back.

> There's another strange thing. I've added a UF200 PCI firewire/USB  
> combo card. This is how it is detected:
>
> fwohci0 at pci1 dev 0 function 0: Lucent Technologies FW322/323 IEEE  
> 1394 Host Controller (rev. 0x04)
> fwohci0: interrupting at irq 25
> fwohci0: OHCI version 1.0 (ROM=1)
> fwohci0: No. of Isochronous channels is 8.
> fwohci0: EUI64 00:60:1d:00:00:00:00:dd
> fwohci0: Phy 1394a available S400, 3 ports.
> fwohci0: Link S400, max_rec 2048 bytes.
> ieee1394if0 at fwohci0: IEEE1394 bus
> fwip0 at ieee1394if0: IP over IEEE1394
> fwohci0: Initiate bus reset
> ohci0 at pci1 dev 9 function 0: Lucent Technologies Sierra Wireless  
> AirCard 580 (rev. 0x10)
> ohci0: interrupting at irq 25
> ohci0: OHCI version 1.0, legacy support
> usb0 at ohci0: USB revision 1.0
> uhub0 at usb0
> uhub0: Lucent Technolo OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> uhub0: 2 ports with 2 removable, self powered
>
> why on earth is NetBSD talking about a Lucent Sierra Wireless mobile  
> adapter??? Is this a PCI ID mismatch in the kernel?

Yes and no. My guess is that the 'Sierra Wireless AirCard' is just  
another USB controller and a EVDO modem hooked up to it crammed into a  
cardbus card, which just happened to use the exact same PCI ID for the  
USB part.

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

iQEVAwUBSY/AlspnzkX8Yg2nAQIKnAf+POy1zPBFANTd6HGuyYUb+QoH4gKM16Ao
lGCZV0MM2sd98/QV56fBxlGaPXC6Yg5B9LRytpMKE3vFQdloVo/XadP4Vxw49JHL
6BF3lhPNVpQRTe0gpHE2qnQKzB2pnDhAMil+LnMbfY1HZVsX1lRps+z9FnSPxKIT
y+r5lFfKWNQRoq0tFiUqnUnxaNNXOFbVB2i+mP+fXvgvwhBw/B9M0fy7PM6vUJ/K
yMVT4ZNuYNxttgvOvai1ZAJRmH79S+XpN8BD3hf4hYAZjMjs39qqu4A6hiLjn0Io
Q3GSdtGAC/LU4UvNUc3j7F8YeeZSzE9dPTNoyndReY0yGBxkP0BH9Q==
=otLg
-----END PGP SIGNATURE-----