From owner-freebsd-hackers Thu Feb 20 7: 0: 0 2003 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 DCBF337B401 for ; Thu, 20 Feb 2003 06:59:58 -0800 (PST) Received: from troncalo.cs.poste.it (troncalo.cs.poste.it [62.241.4.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FD4043FA3 for ; Thu, 20 Feb 2003 06:59:57 -0800 (PST) (envelope-from andrea.franceschini@postecom.it) Received: from knute.cs.poste.it (192.168.44.146) by troncalo.cs.poste.it (5.5.053.1) id 3E36CD9F00037A91 for freebsd-hackers@FreeBSD.ORG; Thu, 20 Feb 2003 15:59:55 +0100 Received: (from andrea@localhost) by knute.cs.poste.it (8.12.6/8.12.6) id h1KEuDP5003285 for freebsd-hackers@FreeBSD.ORG; Thu, 20 Feb 2003 15:56:13 +0100 (CET) (envelope-from andrea.franceschini@postecom.it) X-Authentication-Warning: knute.cs.poste.it: andrea set sender to andrea.franceschini@postecom.it using -f Date: Thu, 20 Feb 2003 15:56:12 +0100 From: Andrea Franceschini To: freebsd-hackers@FreeBSD.ORG Subject: Wireless PCI card Message-ID: <20030220145612.GA3042@postecom.it> Mail-Followup-To: freebsd-hackers@FreeBSD.ORG References: <5.2.0.9.0.20030217091242.05b184b0@marble.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5.2.0.9.0.20030217091242.05b184b0@marble.sentex.ca> User-Agent: Mutt/1.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi All! Browsing trough the mailing-list archive i've found a thread about a problem really similar to mine ( actually it was the same). But, as often happen, that thread didn't have any follow-up. This is part of the thread: Alfred Perlstein wrote: >* Chad David [011227 21:39] wrote: >> On Thu, Dec 27, 2001 at 11:31:43AM -0800, Brooks Davis wrote: >> > On Thu, Dec 27, 2001 at 12:10:32PM -0700, Chad David wrote: >> > >> > What you'll want to do is edit src/sys/dev/wi/if_wi.c, add an appropriate >> > entry to the definition of pci_ids for your card, and recompile your >> > kernel. If that works, you're all set. >> > >> >> I took the advice, and now the attach is failing because the card doesn't >> appear to have any I/O Space (WI_PCI_IORES). Both the local registers and >> attribute memory are in the resource list, but no IO space. I've debugged >> it to the limits of my ability, and now any advice on how to continue would >> be welcome. >> >> hacked dmesg out: >> >> wi0: port 0xa400-0xa43f,0xa800-0xa80f irq 10 at device 11.0 on pci0 >> wi0: about to call wi_alloc(dev, WI_PCI_IORES) >> wi0: type=1 rid=0 >> wi0: type=4 rid=24 >> wi0: type=4 rid=20 >> wi0: type = 4, rid = 28 >> wi0: No I/O space?! >> device_probe_and_attach: wi0 attach returned 6 >> >> Brooks is probably at home with his family, and not reading his email like >> a sensible person, so I thought I would toss this out to the members at >> large again, and see if anybody had any ideas... Alfred? you are the last >> person to touch if_wi.c, doesn't that make it yours ;-). > >hahaha, no. > >Uh, it looks like you don't have the standard PCI card that people >are getting, mine looks like this: >wi0: port 0xff00-0xff3f,0xfc00-0xfc7f mem 0xffbee000-0xffbeefff irq 11 at device 13.0 on pci0 > >The fact that your card doesn't have a memory map concerns me that >it's not what we're expecting. Where is the vendor's website? >Can you ask them for more info? I'm wondering if, by now, someone resolved this issue and how. The thing really strange about all this ,is that the card is among those declared as supported by 'wi' driver. I tried troubleshooting the problem on my own ,but i miss the very basilar knowledge about the PCI addressing... so if you cannot help me with problem i would appreciate any hints/links about PCI programming.. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message