From mboxrd@z Thu Jan  1 00:00:00 1970
From: Miles Lane <miles@megapathdsl.net>
Date: Thu, 08 Feb 2001 07:22:38 +0000
Subject: Re: Adding PCMCIA support to the kernel tree -- developers needed.
Message-Id: <marc-linux-hotplug-98161688116927@msgid-missing>
List-Id: <linux-hotplug.vger.kernel.org>
References: <marc-linux-hotplug-98118528107653@msgid-missing>
In-Reply-To: <marc-linux-hotplug-98118528107653@msgid-missing>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: linux-hotplug@vger.kernel.org

David Hinds wrote:

> On Sun, Feb 04, 2001 at 10:02:36AM -0800, Miles Lane wrote:
> 
>>> 1. The yenta driver can't handle CardBus adapter cards for desktop
>>>    systems.  Many require explicit overrides for the default interrupt
>>>    delivery settings, and a few require other special bridge settings.
>> 
>> Huh?  You mean that the driver can't handle _some_ Cardbus adapter
>> cards, right?  Mine work fine.
> 
> 
> What ones do you have?  Are you using 16-bit cards or only CardBus
> cards?

I have a "3Com PCI 3CCFE575BT Cyclone CardBus" (lspci lists
this device as a "3Com Corporation 3c575 [Megahertz] 10/100 
LAN CardBus [rev 01]") and a "Belkin BusPort Mobile" (lspci
gives "OPTi Inc. 82C861 [rev 10] [prog-if 10 [OHCI]]" for 
this device).

The full lspci output for them is:

01:00.0 Ethernet controller: 3Com Corporation 3c575 
[Megahertz] 10/100 LAN CardBus (rev 01)
        Subsystem: 3Com Corporation: Unknown device 5b57
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- 
	VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- 
	DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- 
	<PERR-
        Latency: 10 min, 5 max, 64 set
        Interrupt: pin A routed to IRQ 11
        Region 0: I/O ports at 1000 [size8]
        Region 1: Memory at 10800000 (32-bit, non-prefetchable) 
		[size8]
        Region 2: Memory at 10800080 (32-bit, non-prefetchable) 
		[size8]
        Expansion ROM at 10400000 [size8K]
        Capabilities: [50] Power Management version 1
                Flags: PMEClk- AuxPwr- DSI- D1+ D2+ PME-
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00: b7 10 57 51 07 00 10 02 01 00 00 02 00 40 00 00
10: 01 10 00 00 00 00 80 10 80 00 80 10 00 00 00 00
20: 00 00 00 00 00 00 00 00 90 00 00 00 b7 10 57 5b
30: 01 00 40 10 50 00 00 00 00 00 00 00 0b 01 0a 05
40: 00 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00
50: 01 00 01 76 00 00 00 00 00 00 00 00 00 00 00 00
60: 10 00 7c 4b 9d 9d 57 51 c9 c4 36 00 4e 56 50 6d
70: 00 30 09 00 10 00 7c 4b 9d 9d 10 20 00 00 06 00
80: a6 32 70 15 00 00 60 00 07 00 00 00 00 00 81 00
90: 13 03 43 49 53 20 04 01 01 57 51 04 06 03 01 00
a0: 00 00 00 05 0c 41 9a 01 b5 1e 01 55 02 30 ff ff
b0: 01 07 06 11 00 40 00 00 00 15 34 05 00 33 43 6f
c0: 6d 20 43 6f 72 70 6f 72 61 74 69 6f 6e 00 33 43
d0: 43 46 45 35 37 35 42 54 00 4c 41 4e 20 43 61 72
e0: 64 62 75 73 20 43 61 72 64 00 30 30 31 00 ff 21
f0: 02 06 01 05 06 00 80 80 80 80 19 ff ff ff ff ff

and

05:00.0 USB Controller: OPTi Inc. 82C861 (rev 10) 
	(prog-if 10 [OHCI])
        Subsystem: OPTi Inc.: Unknown device c861
        Control: I/O- Mem+ BusMaster- SpecCycle- 
	MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- 
	DEVSEL=medium >TAbort- <TAbort- <MAbort- 
	>SERR- <PERR-
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at 11000000 (32-bit, non-prefetchable) 
		[size=4K]
00: 45 10 61 c8 02 00 80 02 10 10 03 0c 00 00 00 00
10: 00 00 00 11 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 45 10 61 c8
30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 01 00 00
40: 00 00 0f 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 01 26 00 30 33 33 33 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Now, I do have a couple of bugs I am currently 
documenting.  One where, if I insert a card into
a slot that was empty at boot time, an OOPS occurs
and the PCMCIA/Cardbus slots become unusable.
The other has to do with using these two cardbus
cards simultaneously.  Linus thinks this is related
to my latency_timer settings, but I haven't been
able to confirm this, yet.

I should note that for at least the 3c575, I have
been using this card for about half a year with 
the yenta driver and it's worked great.  The problems
I mention only started showing up in the later 
kernels from the 2.4.0-test series.

Anyhow, I have used both of these cards without
other trouble.  If I have one of these cards
inserted at boot time, I can load either 3c59x
or usb-ohci and use the corresponding card.  

>> As for the issue of many drivers
>> requiring overrides and special settings, could you please give us
>> a few examples? 
> 
> 
> The PCMCIA-HOWTO has a list.  Some adapters do not power up in the
> correct interrupt delivery mode and the yenta driver doesn't have a
> way to tell it that a bridge must be put in PCI interrupt mode.

Thanks.  We'll refer to it.

	Miles


_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel