From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 25 09:12:42 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D05316A4CE for ; Thu, 25 Mar 2004 09:12:42 -0800 (PST) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id F418543D46 for ; Thu, 25 Mar 2004 09:12:40 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (sccrmhc13) with ESMTP id <2004032517123901600qpegue>; Thu, 25 Mar 2004 17:12:40 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id JAA76898; Thu, 25 Mar 2004 09:16:54 -0800 (PST) Date: Thu, 25 Mar 2004 09:16:53 -0800 (PST) From: Julian Elischer To: Fred Clift In-Reply-To: <20040324152527.R60652@irfcn.qzm.berz.irevb.arg> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org Subject: Re: Diagnosing unrecognized hardware X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Mar 2004 17:12:42 -0000 On Wed, 24 Mar 2004, Fred Clift wrote: > On Mon, 22 Mar 2004, M. Warner Losh wrote: > > > : pccard0: (manufacturer=0x000b, product=0x7110) at function 0 > > : pccard0: CIS info: D-Link, DWL-650 Wireless PC Card RevP, ISL37101P-10 > > > > Looks like this isn't a supported card. You can add it to > > if_wi_pccard.c and see if that helps. Changes are good that this > > isn't a wi card, but I could be wrong. > > > I'm just making the switch to 5.X from 4.7 on my laptop and this is the > first time I've had to deal with the NEWCARD stuff. > > My question is is there any easy way to experiment with unknown > pcmcia/cardbus cards to get them to work without rebuilding the whole > kernel, or at least modules? No, this is not yet done though I imagine it is on the to-do list. The newcard code only handles cards it has intrinsic knowledge of at this time (unfortunatly). > > In 4.x, I can tweak a few lines in pccardd.conf and have unknown cards use > different drivers, different options etc. I believe that _some_ of that > info can be set in devd.conf, but it doesn't appear that all of it can. > In particular, I have an unrecognized prisim2 card (known working with > 4.7's wi driver) that I could previously just drop in to /etc/pccardd.conf > but which now seems to require at least rebuilding a kernel module. Isn't > this a functionality regression? or do I just not understand what I'm > doing (be kind!)? > > Fred > > > -- > Fred Clift - fclift@verio.net -- Remember: If brute > force doesn't work, you're just not using enough. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >