From owner-freebsd-mobile@FreeBSD.ORG Tue Sep 28 20:09:19 2004 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E55816A4CE for ; Tue, 28 Sep 2004 20:09:19 +0000 (GMT) Received: from o2.hostbaby.com (o2.hostbaby.com [208.187.29.121]) by mx1.FreeBSD.org (Postfix) with SMTP id 0940F43D75 for ; Tue, 28 Sep 2004 20:09:18 +0000 (GMT) (envelope-from ceo@l-i-e.com) Received: (qmail 89057 invoked by uid 1001); 28 Sep 2004 19:53:22 -0000 Received: from 66.243.5.202 (SquirrelMail authenticated user ceo@l-i-e.com); by www.l-i-e.com with HTTP; Tue, 28 Sep 2004 12:53:22 -0700 (PDT) Message-ID: <33523.66.243.5.202.1096401202.squirrel@www.l-i-e.com> Date: Tue, 28 Sep 2004 12:53:22 -0700 (PDT) From: "Richard Lynch" To: freebsd-mobile@freebsd.org User-Agent: Hostbaby Webmail X-Mailer: Hostbaby Webmail MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal cc: freebsd-questions@freebsd.org Subject: NIC Driver Hacking X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ceo@l-i-e.com List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Sep 2004 20:09:19 -0000 Since so many people gave me on -mobile and -questions gave me so much help, I'd like to *TRY* to continue working on adding support for the Broadcom 4401-B0 to FreeBSD. Here's where I came from: None of my CardBus, NIC, WiFi, etc devices were getting register memory: http://phpbootcamp.com/articles/inspiron700m/dmesg_verbose.txt All hardware worked fine under Windows. Well, as fine as anything works under Windows. :-) Here's where I am: I can use "allow_unsupported_io_range" and all my devices get identified and assigned what look like valid memory ranges: http://www.phpbootcamp.com/articles/inspiron700m/hw.pci.allow_unsupported_io_range/dmesg.txt Attempting to configure the NIC using ifconfig or the sysinstall GUI locks up the machine completely. So, which of the following most likely describes my current status: A) The unsupported_io_range is fine, but the driver source needs hacking B) I really haven't solved the device register memory issues -- they just *SEEM* to be okay. If it's A) I can start mucking with C code and hopefully not damage my hard drive too much in the process... If it's B) I'm still at a complete loss how to compute valid io_range... Use the Windows numbers, since they work? Use the Linux numbers, since they work? Some kind of tool/monitor to compute a base offset? If it's A) I can also start playing with the CardBus and WiFi with some hope of it working. If it's B) there's not much point in my buying a PCM/CIA WiFi card, now is there, as the Cardbus io_range ain't gonna be any good either, is it?... -- Like Music? http://l-i-e.com/artists.htm