From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761435AbZLKWhP (ORCPT ); Fri, 11 Dec 2009 17:37:15 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1761345AbZLKWhK (ORCPT ); Fri, 11 Dec 2009 17:37:10 -0500 Received: from mail-bw0-f227.google.com ([209.85.218.227]:34314 "EHLO mail-bw0-f227.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761309AbZLKWhI (ORCPT ); Fri, 11 Dec 2009 17:37:08 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type:content-transfer-encoding; b=gibqH9t9yEAnMtQxay1ZSQ9UobWMcwuScP6RhsKxR0YWgBeJQWKcqlmMEDSdg07qCJ zHhO+TOEZTZCAEMtTYKuF2ATiY2r/bQBA3zTIWHJDFY94/9HfR28Wd2MHhSYXvJ1t9re B5yYYBFJPfUSn8E5che24LW/RPF9puGQwuA8c= Date: Fri, 11 Dec 2009 23:37:09 +0100 From: Stefan Seyfried To: Dan Williams Cc: "John W. Linville" , linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/2] Add support for Sphairon Homelink 1202 USB WLAN Message-ID: <20091211233709.29fc5312@strolchi.home.s3e.de> In-Reply-To: <1260559270.6254.2.camel@localhost.localdomain> References: <1260282095-17042-1-git-send-email-stefan.seyfried@googlemail.com> <20091211133603.46bec686@strolchi.home.s3e.de> <20091211144221.GA6663@tuxdriver.com> <20091211160124.4db2da76@strolchi.home.s3e.de> <1260559270.6254.2.camel@localhost.localdomain> X-Mailer: Claws Mail 3.7.3 (GTK+ 2.18.1; i586-suse-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 11 Dec 2009 11:21:10 -0800 Dan Williams wrote: > On Fri, 2009-12-11 at 16:01 +0100, Stefan Seyfried wrote: > > Maybe a separate driver that is ejecting all those fake storage > > devices, be it 3G modems or wireless LAN might be a good idea, but I am > > probably not the right one to code that ;) > > Or maybe we decide that userspace should handle it for all devices... > > If the device actually changes USB IDs after the switch, then the right Yes, it does. > place to put this code is probably unusual_devs instead of > touching /two/ drivers. I'd say extract the code from zd1211rw and put > the new code that works for both zd1211rw/ar9170 into unusual_devs. In > fact, people might be happier if you posted two patches, (1) move the > code to unusual_devs unchanged, and (2) fix up the moved code to support > the new device's behavior. Ok, I'll do this next week (might take some time, since I need to get familiar with the usb / unusual_devs code). I guess this will mostly go through Greg then? John, please take the patch 1, that adds the USB ID to ar9170usb. It is useful on its own since the device can also be switched with usb_modeswitch from userspace, and it is really trivial. Thanks, Stefan -- Stefan Seyfried "Any ideas, John?" "Well, surrounding them's out."