Am Mittwoch 30 August 2006 18:34 schrieb David Reimer:
> Sorry, it's taken so long for me to reply about my driver problem, but had
> to understand a little about the card I'm using before I responded. Also,
> kind of new to mailing lists so please forgive my poor netiquette (I am
> willing to learn).
>
> The card I'm using is not a pci card, and have been informed by the
> manufacture that it will not be listed by using "lspci". They told me to
> use ''pccardctl info" (see table below for output).

This was before 2.6.17 (or earlier). 
pcmcia_cs is the old PCMCIA stuff, the whole pcmcia-stuff was reworked. You 
should have the pcmciautils installed for newer kernels. Then you have
# lspcmcia -v
Socket 0 Bridge:        [yenta_cardbus]         (bus ID: 0000:01:02.0)
        Configuration:  state: on       ready: yes
Socket 1 Bridge:        [yenta_cardbus]         (bus ID: 0000:01:02.1)
        Configuration:  state: on       ready: yes
                        Voltage: 3.3V Vcc: 3.3V Vpp: 3.3V
  CardBus card -- see "lspci" for more information

lspci is then used for all 32bit cards (PCMCIA is kind of a PCI-Bridge), 
lcpcmcia for 16bit cards (you need drivers with special pcmcia support to use 
those).
# lspci -v -d 14e4:
06:00.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless 
LAN Controller (rev 03)
        Subsystem: Tekram Technology Co.,Ltd. Unknown device 1604
        Flags: bus master, fast devsel, latency 64, IRQ 10
        Memory at 26000000 (32-bit, non-prefetchable) [size=8K]
        Capabilities: [40] Power Management version 2

Note that I had to use "pci=assign-busses" on the kernel command line to see 
this.
If the vendor of you card has set itself as primary vendor instead of 
secondary vendor (like above): bad style and you'd manually have to tell the 
bcm43xx driver in source the IDs of the card.

> The 05:06.X device is the card bus bridge that the BroadCom card is
> connetcted to. Basically, it the pcmcia slot.

Mine, too, and if it is a 32bit card, it will show up with lspci on newer 
kernels. I think that for bcm43xx, this is necessary.

HS
_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to