Return-path: Received: from smtp-out002.kontent.com ([81.88.40.216]:51085 "EHLO smtp-out002.kontent.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757110AbZLQNC2 (ORCPT ); Thu, 17 Dec 2009 08:02:28 -0500 From: Oliver Neukum To: Matthew Dharm Subject: Re: [PATCH] move eject code from zd1211rw to usb-storage Date: Thu, 17 Dec 2009 14:02:41 +0100 Cc: Dan Williams , Josua Dietze , Stefan Seyfried , linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org, usb-storage@lists.one-eyed-alien.net, Stefan Seyfried References: <1260878800-14691-1-git-send-email-stefan.seyfried@googlemail.com> <1260993048.2179.68.camel@localhost.localdomain> <20091216195258.GJ16426@one-eyed-alien.net> In-Reply-To: <20091216195258.GJ16426@one-eyed-alien.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Message-Id: <200912171402.42168.oliver@neukum.org> Sender: linux-wireless-owner@vger.kernel.org List-ID: Am Mittwoch, 16. Dezember 2009 20:52:58 schrieb Matthew Dharm: > > > If this is the case, then the only reasonable answer to is to push the > > > modeswitch code for both into udev and out of the kernel. It will take > > > > you mean usb_modeswitch, not udev actually. > > That is correct; I had mis-typed. Tho, the actual implementation is udev > calling usb_modeswitch and/or eject. Can storage tell the devices apart so that it knows which ones to leave to the kernel solution and which devices to accept so that udev can issue an eject command? Regards Oliver