Return-path: Received: from bues.ch ([80.190.117.144]:38305 "EHLO bues.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752943Ab2AAVjb (ORCPT ); Sun, 1 Jan 2012 16:39:31 -0500 Date: Sun, 1 Jan 2012 22:39:13 +0100 From: Michael =?UTF-8?B?QsO8c2No?= To: Oliver Neukum Cc: Linus Torvalds , Alan Stern , Matthew Garrett , Dave Jones , Linux Kernel , Larry Finger , Chaoming Li , "John W. Linville" , "Greg Kroah-Hartman" , USB list , Linux Wireless List Subject: Re: loading firmware while usermodehelper disabled. Message-ID: <20120101223913.3ff57d0f@milhouse> (sfid-20120101_223958_238432_1FDE2BB2) In-Reply-To: <201201012227.56568.oliver@neukum.org> References: <201201011322.34483.oliver@neukum.org> <201201012227.56568.oliver@neukum.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-wireless-owner@vger.kernel.org List-ID: On Sun, 1 Jan 2012 22:27:56 +0100 Oliver Neukum wrote: > Ideally usbcore would deal with such devices, but at present the USB layer > is unable to cleanly resume devices that change their IDs during > resume. > Solving this would mean putting all firmware loaders into kernel space. > And the mode switching logic as well. I don't get it. Why would a device enter a state after resume, that it was not in at _any_ time before the machine was suspended? These change-id-on-bootstrap devices usually work like this, as far as I know: probe bootstrap device (switches hw to real device) probe real device (firmware is loaded) Suspend machine Resume machine usb detects that the device is "gone" probe/resume bootstrap device (switches hw to real device) probe/resume real device (No need to fetch fw from userspace. It's already cached) What did I get wrong? -- Greetings, Michael.