Date: Mon, 26 Apr 2010 07:29:32 -0700 From: Chip Camden <sterling@camdensoftware.com> To: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Wireless networking question Message-ID: <20100426142932.GD72082@libertas.local.camdensoftware.com> In-Reply-To: <4BD50547.1070705@daleco.biz> References: <20100424203946.GA1542@libertas.local.camdensoftware.com> <20100424210029.GA6139@libertas.local.camdensoftware.com> <20100424220732.00000f67@unknown> <20100424220034.GC6139@libertas.local.camdensoftware.com> <20100424235156.00007de8@unknown> <20100425191040.GA12460@libertas.local.camdensoftware.com> <20100425212630.00001bd4@unknown> <20100425231840.GB72082@libertas.local.camdensoftware.com> <20100425234127.GC72082@libertas.local.camdensoftware.com> <4BD50547.1070705@daleco.biz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 25 2010 22:15, Kevin Kinsey wrote: > > Let me preface my commentary with "I'm way out of my league", so #include > disclaimer.h and all that ... > > For starters, in re: above, didn't someone suggest "libpciaccess" as the > source for "scanpci"? I can't tell if you are misunderstanding what S > Roberts suggested, or I am misunderstanding what you are responding. > > I'm pretty sure there's some misunderstanding here, though. Thanks for your response, Kevin. I did try rebuilding libpciaccess, to no avail. I also searched elsewhere. > > I thought we had pciconf output that stated it was an Atheros chipset? > In that case, it would be the Azurewave, right? I'd suspect it might > be supported under ath(4), but you'd wanna read the manpage and possibly > even the source for any kind of confirmation on that; the manpage does > specifically say that adapters based on the AR5005VL aren't supported. > However, the manpage might be slightly out-of-date, also. Yes, pciconf says Atheros. I guess that does rule out Intel, and I see from a little searching that at least some Azurewave devices use an Atheros chipset. I, too, am a little out of my depth in this region, as is probably obvious from my posts. > > The other thing I recall seeing is that a new variant of a supported > chipset comes out, and the driver code doesn't recognize it even though > it might work well. Used to be something like a VENDOR_ID string in > the source files; I don't know if it's still the case, but if it was, > some people have been able to hack their own device support in rare > cases simply by adding the new info to the driver file and recompiling > it, but you'd want someone with a lot more $OS_foo than I have to help > out with that (or tell you if it's even possible). This is open-source > stuff; you might even get sam@ 's attention and get help from the writer > himself if you're wearing your lucky sneakers. > Yes, I've seen that done with video drivers. Perhaps I'll give it a go with the ath or uath driver, neither of which work for me out of the box (so to speak). Thanks again. -- Sterling (Chip) Camden | camdensoftware.com | chipstips.com | chipsquips.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100426142932.GD72082>