From owner-freebsd-mobile Mon Oct 23 7:36:24 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from toyland.drapple.com (toyland.drapple.com [204.200.26.114]) by hub.freebsd.org (Postfix) with ESMTP id 9D4D637B479 for ; Mon, 23 Oct 2000 07:36:17 -0700 (PDT) Received: from freebsd.org (bet-su5-23.itg.discovery.com [198.147.13.23]) by toyland.drapple.com (8.9.3/8.9.3) with ESMTP id HAA32621; Mon, 23 Oct 2000 07:36:09 -0700 (PDT) (envelope-from patrick@freebsd.org) Message-ID: <39F44CD7.8EF143A@freebsd.org> Date: Mon, 23 Oct 2000 14:36:07 +0000 From: Patrick Gardella Organization: FreeBSD X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: mobile@freebsd.org Subject: Re: Cardbus status References: <200010220509.XAA44604@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What devices need to be activated in the kernel to support cardbus? I've tried to use what was in NEWCARD, but those don't seem to work: device PCCARD device CARDBUS device PCIC #device PCCBB On one of my reboots, my "3CCFE575CT" (what CardBus detects it as), was identified as an xl0, which it should be, but then I had some warnings about unable to attach to pccbb bus, so I rebuilt the kernel as above. Now it says: pccbb0: card inserted: event=0x00000000, state=30000820 pccbb0: pccbb_power: CARD_VCC_3V and CARD_VPP_UC[1] cardbus0: reading CIS data from configuration space Manufacturer ID: 01015752 TUPLE: CONFIG_CB [6]: 03 01 00 00 00 00 TUPLE: CFTABLE_ENTRY_CB [13]: 41 9a 01 b5 1e 01 b5 ie 02 30 ff ff 01 cardbus0: Opening BAR: type=MEM, bar=10, len=0040 Product version: 5.0 Product name: 3Com Corporation | 3CCFE575CT | LAN Cardbus Card | 004 | Functions: Network Adaptor, Memory cardbus0: (vendor 0x10b7, dev=0x5257) at 0.0 irq 0 pccbb0: card activation failed I'm thinking I have the kernel configged wrong. Patrick Warner Losh wrote: > > OK. It looks like we have cardbus working on most laptops. I'm > currently coming in via the 3C575BT card. At BSDcon we found that the > following cards worked: > 3C575[CB][CT] > Xircom cards (and clones: IBM and Intel) > 3c656 (no modem) > Dlink generic card > > There are no modems working right now. Most of them are win modems, > but there are some drivers out there for them of unknown quality that > haven't been ported to FreeBSD. > > Some laptops don't work. There are resource allocation issues that > need to be addressed. The Dell 5000e is one of the bad ones, iirc. I > may need to go buy one of those bad boys. We don't have a list of > working/broken laptops at this time. > > 16-bit cards don't work yet. I've not had time to debug this > completely yet. I've cleaned it up, but still need to dig deeper. > > scsi cards don't work yet. I talked to Justin about this. He has > access to code that brings the chips out of power saving mode so that > the SBCs are available. > > Generally speaking, to port to cardbus, you need to add 1 line to most > pci drivers since our card bus code emulates a pci bus very well. > Many drivers need to be taught to cope with detaching properly as > well. In addition, many drivers will need to have some chip specific > tweaking due to errata that apply only to cardbus silicon or the > manner that the cardbus implementation differs slightly from other > cards supported by the driver. > > A big thanks to Jonathan Chen for his excellent work. The code is > mostly stable, but there are still issues. It should be considered > advanced alpha or early beta until we get more experience with this > code and fix the issues that invariably come up when laptop hardware > gets into the loop. > > It will not be available in -stable for some time, if ever. My palns > are to get the 16-bit code working, firm up the issues between now and > then and then throw the switch over from OLDCARD to NEWCARD by > default. We need an devd infrastructure in place as well. No clue > how long all this will take :-) > > Warner > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message