Re: 8. Current and Intel 5100 AGN wifi

2009-08-14 Thread Sam Fourman Jr.
On Fri, Aug 14, 2009 at 7:45 PM, Weongyo Jeong wrote: > On Sun, Aug 09, 2009 at 02:41:20PM +0100, Alireza Torabi wrote: >> folks, >> >> Can anyone please shet any lights on this. are iwn & iwnfw  going to >> support 5100 agn wifi? >> I've updated mine to 8. Current with iwn & iwnfw and still not go

Re: 8. Current and Intel 5100 AGN wifi

2009-08-14 Thread Alireza Torabi
thanks so i gathered by the lack of response i must say... On 8/15/09, Weongyo Jeong wrote: > On Sun, Aug 09, 2009 at 02:41:20PM +0100, Alireza Torabi wrote: >> folks, >> >> Can anyone please shet any lights on this. are iwn & iwnfw going to >> support 5100 agn wifi? >> I've updated mine to 8.

Re: 8. Current and Intel 5100 AGN wifi

2009-08-14 Thread Weongyo Jeong
On Sun, Aug 09, 2009 at 02:41:20PM +0100, Alireza Torabi wrote: > folks, > > Can anyone please shet any lights on this. are iwn & iwnfw going to > support 5100 agn wifi? > I've updated mine to 8. Current with iwn & iwnfw and still not going > anywhere with the card. AFAIK no one working on it.

[Take 2] Re: RFC: interface description

2009-08-14 Thread Xin LI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, guys, Here is a patch that implements the functionality in userland (as setifdescription/getifdescription functions in libutil); with this I think we can also provide an option that some kernel feature (like Qing Li said it might be useful for emb

Re: kern/137775: [netgraph] [patch] Add XMIT_FAILOVER to ng_one2many

2009-08-14 Thread linimon
Old Synopsis: [patch] Add XMIT_FAILOVER to ng_one2many New Synopsis: [netgraph] [patch] Add XMIT_FAILOVER to ng_one2many Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Fri Aug 14 20:20:55 UTC 2009 Responsible-Changed-Why: Over to m

Re: RFC: interface description

2009-08-14 Thread Brooks Davis
On Fri, Aug 14, 2009 at 10:49:24AM -0700, Li, Qing wrote: > > > > My point has always been - if I have to add/do an ioctl I can always > > also use a library call that will read it from a .txt, .xml, .db file > > or whatever and I don't have to go to the kernel, handle all the > > string length pr

RE: RFC: interface description

2009-08-14 Thread Li, Qing
> > My point has always been - if I have to add/do an ioctl I can always > also use a library call that will read it from a .txt, .xml, .db file > or whatever and I don't have to go to the kernel, handle all the > string length problems there, ... especially as the kernel cannot do > anything with

Re: RFC: interface description

2009-08-14 Thread Louis Mamakos
On Aug 14, 2009, at 3:58 AM, Bjoern A. Zeeb wrote: On Fri, 14 Aug 2009, Andrey V. Elsukov wrote: Hi, Xin LI wrote: The only question I have would be, that is it possible to uniquely identify a NIC without assistance from kernel? For instance, one can change an interface from being called

Re: RFC: interface description

2009-08-14 Thread Bjoern A. Zeeb
On Fri, 14 Aug 2009, Andrey V. Elsukov wrote: Hi, Xin LI wrote: The only question I have would be, that is it possible to uniquely identify a NIC without assistance from kernel? For instance, one can change an interface from being called "em0" to "eth0" and from "bge0" to "em0". It's easy to