Return-path: Received: from charlotte.tuxdriver.com ([70.61.120.58]:49366 "EHLO smtp.tuxdriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753127AbZDUOAx (ORCPT ); Tue, 21 Apr 2009 10:00:53 -0400 Date: Tue, 21 Apr 2009 09:52:57 -0400 From: "John W. Linville" To: Ivo Van Doorn Cc: Greg KH , Xose Vazquez Perez , dcbw@redhat.com, linux-wireless Subject: Re: [PATCH] Add vt6656 driver to drivers/staging. Message-ID: <20090421135257.GG17805@tuxdriver.com> (sfid-20090421_160057_838422_D2DF5F2A) References: <49E632A1.1050605@gmail.com> <20090415212103.GA5202@kroah.com> <200904182318.56512.IvDoorn@gmail.com> <20090420135940.GB3369@tuxdriver.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 In-Reply-To: Sender: linux-wireless-owner@vger.kernel.org List-ID: On Tue, Apr 21, 2009 at 12:30:16PM +0200, Ivo Van Doorn wrote: > On Mon, Apr 20, 2009 at 3:59 PM, John W. Linville > wrote: > > On Sat, Apr 18, 2009 at 11:18:56PM +0200, Ivo van Doorn wrote: > >> Hi, > >> > >> > > I hope rt2800pci/usb to be included *ASAP*, because rt2800usb = supports > >> > > more than 1oo USB devices and rt2800pci is included in a lot o= f > >> > > laptops(ask Torvalds [1] [2]) > >> > > > >> > > [1] http://marc.info/?l=3Dlinux-netdev&m=3D121799144422863&w=3D= 2 > >> > > [2] http://marc.info/?l=3Dlinux-kernel&m=3D123187052023831&w=3D= 2 > >> > > >> > That would be great to have in, what's keeping it from happening= ? > >> > >> In short: A stable workable driver. > >> > >> The rt2800usb driver is pretty far (at least on my testsetup), but > >> still has problems with transmitting frames immediately after > >> association. > > > > I read this as "it works, but some frames are lost immediately afte= r > > association" -- is that right? >=20 > It is not "Some frames" it is "All frames" you can't get a DHCP lease= , > or use a static IP and try to do anything. Is this permanent? Or does it start working at some point? > Also 11n APs are not detected at all, which for a 11n client sounds > very problematic. If 11g works then I think that is good enough to merge. > > FWIW, this sounds good enough to me > > to get it into the mainline kernel. =A0_Please_ submit the rt2800us= b > > driver for wireless-testing/linux-next ASAP! >=20 > If the above 2 problems aren't critical for merge, then I'll send the > patches as soon as possible. If there is no traffic at all then I guess it can still wait -- ping seems like a reasonable requirement. But 11n is not a requirement for merge. John --=20 John W. Linville Someday the world will need a hero, and you linville@tuxdriver.com might be all we have. Be ready. -- To unsubscribe from this list: send the line "unsubscribe linux-wireles= s" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html