Date: Wed, 11 Aug 1999 20:04:48 -0600 From: Warner Losh <imp@village.org> To: Dan Janowski <danj@3skel.com> Cc: freebsd-mobile@FreeBSD.ORG, Dan Janowski <danj@netcom.com> Subject: Re: Linksys Etherfast 10/100+56K Message-ID: <199908120204.UAA01005@harmony.village.org> In-Reply-To: Your message of "Mon, 09 Aug 1999 09:21:12 EDT." <Pine.BSF.4.05.9908090831560.34004-100000@fnur.3skel.com> References: <Pine.BSF.4.05.9908090831560.34004-100000@fnur.3skel.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <Pine.BSF.4.05.9908090831560.34004-100000@fnur.3skel.com> Dan Janowski writes: : I am running PAO3 under 3.1. I should upgrade ... Yes. You should. : 1. This is a multi-function card. I can get the modem to : work with no problem, both via pccardd and pccardc enabler. : The LAN is the second I/O block in each configuration : tuple, so I can't/don't know how to specify a /etc/pccard.conf : that will use the second. You lose. There is insufficient support in FreeBSD 3.x to do this. There is no way to specify this. : 2. After playing around with pccardd.c, and getting access to the : second IO block, the card fails to pass the driver init. : So, afer discovering pccardc enabler... : : 3. I have tried to use: pccardc enabler 0 ed0 -a 300 -i 5 : I assume that I need to tell the card something so it : knows what to expect? If so, is there a way to do this? You need to enable the second I/O window for the pcic bridge. Last time I was looking at the old pcccard code, I recall that this didn't happen. That may just be in the pccardd <-> kernel interface. : I am assuming that I can use the enabler to confirm that all : the kernel level stuff is working. Then dealing with the pccardd : stuff to get it to happen automatically. True or False? False. Pccard stuff is about the hardest to debug in FreeBSD. : It does get through the pccard.c, up to 'err=drv->enable(devi)'. : but the return is an error "Device not configured". This means that the driver's enable routine was not able to enable the card. : What code gets called for the enable? I see templates in skel.c : but what is really getting called. I assume that at some point it : has to get passed to ed_attach, but I don't see the path. For the ed driver, you will want to look for the code inside of if NCARD > 0. edinit is what you are looking for. However, if you want to support both functions of the card in the current pccard system, you'll likely need to write some kind of wrapper driver that deals with the multiple I/O windows. : 4. Is there a simple way to confirm the signature for the ethernet chip? Don't know what you are asking here. : I am assuming that it is ed compatible. Why? :-) : I did however see some : referenced to it being tulip based. the FreeBSD tulip driver : is PCI, no? That would make it a cardbus card, and unsupported as we have no cardbus implementation right now. : Any help or recommendations are welcomed. I may just go and buy : a regular EtherFast card, but I'd at least like to try to get this : to work. I not done any kernel level coding to date, and this may : or may not be a good way to start ;) It is likely to be frustrating :-). I'm not sure what to recommend as a fast, supported ethernet card. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199908120204.UAA01005>