<html><head/><body><html><head></head><body>My favorite move is to get a mini-pci to pci adapter and reuse cards from dead laptops.<br>
I see the chip, most are BRCM or Atheros, then plug it all together. Cheap move IMO.<br>
<br>
Mike--<br><br><div class="gmail_quote">Brian Callahan <bcallah@devio.us> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre style="white-space: pre-wrap; word-wrap:break-word; font-family: sans-serif; margin-top: 0px">On 2/2/2013 1:42 PM, George Rosamond wrote:<br />*snip*<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;">I've found the Realtek stuff never changes the chipset on a product. A<br />different chipset will have a different product name/number. Plus they<br />tend to advertise the chipset openly and directly. Much different from<br />some of the big-name vendors, indeed!</blockquote><br /><br />The nice thing is that with the declining margins/cheaper production, a<br />la carte components aren't the monopoly of the big manufacturers that<br />you have to wait on them for "niceties" like documentation.<br />AFAIK/remember, it was the Taiwanese manufacturers who the OpenBSD<br />people ha
d an
easier time accessing, not the bcms of the world.</blockquote><br /><br />Yup. For this reason, I make sure to buy Realtek wireless stuff. As an <br />added benefit, urtw(4) doesn't require any firmware, so it's perfectly <br />usable in bsd.rd (in fact, I use wireless all the time to install new <br />snapshots to my yeeloongs).<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;">The manpages usually have a list of hardware known to work with each<br />driver. Admittedly, it's sometimes non-exhaustive.</blockquote><br />Which</blockquote><br /><br />ath(4) comes to mind...<br /><br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left:
1px
solid #ad7fa8; padding-left: 1ex;">Of course, if you have something you know has a good chipset and it<br />comes up unidentified, write up a patch or let a dev know<br />(me/okan/others? for OpenBSD, I'm sure there are devs for other BSDs<br />lurking here) so we can write up a patch.<br /><br />I wonder if there's a way we can take the dmesgd entries, pull out the<br />networking info, and keep that in its own separate database? Just a<br />thought :)</blockquote><br />You mean dynamically? Like queries across all the files based on<br />categories? hmmm.. . . good idea. the problem is there a way to<br />indicate network stuff across all the dmesg types?<br /><br />OTOH, I'm sure we could just do a dump of the contents if you wanted...</blockquote><br /><br />I do mean dynamically. I'm sure there are plenty of people in the <br />"hoping the right chip is inside the plastic" camp as Jesse pointed out.<br /><br />Even a dump would be useful for people looking to buy wirel
ess
cards.<br /><br />~Brian<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">g<br /><br /><hr /><br />talk mailing list<br />talk@lists.nycbug.org<br /><a href="http://lists.nycbug.org/mailman/listinfo/talk">http://lists.nycbug.org/mailman/listinfo/talk</a></blockquote><br /><hr /><br />talk mailing list<br />talk@lists.nycbug.org<br /><a href="http://lists.nycbug.org/mailman/listinfo/talk">http://lists.nycbug.org/mailman/listinfo/talk</a><br /></pre></blockquote></div><br>
-- <br>
Sent from my Android phone with K-9 Mail. Please excuse my brevity.</body></html></body></html>