David, > Socket 0 Device 0: [-- no driver --] (bus ID: 0.0) > Configuration: state: on > Product Name: SummitDC 802.11g SC CF 4.0 > Identification: manf_id: 0x02d0 card_id: 0x0448 > function: 6 (network) > prod_id(1): "SummitDC" (0xde2746ff) > prod_id(2): "802.11g SC CF" (0xdbe5c59c) > prod_id(3): "4.0" (0x0ebc74cc) > prod_id(4): --- (---)
It's good to see that at least that shows up :) > pccard outputs: > pccardctl ls returns: same as lspcmcia btw with the new tools :) > I guess my first questions is what mechanism is used to bind a device to a > driver, and secondly where is a good source for me to read to start to > understand the Linux Device Driver system? The mechanism is just like for PCI, it's some table with valid IDs. But, I suggest you don't bother. We haven't speced how to bring up the PCMCIA core this card must have. Once I can get my hands on one I'll try to bring it up and spec the remaining things so that we can at least talk to the wireless chip. It being a 4318 might mean it won't work too well initially though. johannes _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
