From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomas Szepe Subject: Re: ipw2100 wireless driver Date: Wed, 11 Aug 2004 18:33:33 +0200 Sender: netdev-bounce@oss.sgi.com Message-ID: <20040811163333.GE10100@louise.pinerecords.com> References: <20040714115523.GC2269@elf.ucw.cz> <20040809201556.GB9677@louise.pinerecords.com> <20040810075558.A14154@infradead.org> <20040810101640.GF9034@atrey.karlin.mff.cuni.cz> <4119F203.1070009@linux.intel.com> <20040811114437.A27439@infradead.org> <411A478E.1080101@linux.intel.com> <20040811093043.522cc5a0@dell_ss3.pdx.osdl.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: James Ketrenos , Christoph Hellwig , Pavel Machek , Jeff Chua , netdev@oss.sgi.com, kernel list Return-path: To: Stephen Hemminger Content-Disposition: inline In-Reply-To: <20040811093043.522cc5a0@dell_ss3.pdx.osdl.net> Errors-to: netdev-bounce@oss.sgi.com List-Id: netdev.vger.kernel.org On Aug-11 2004, Wed, 09:30 -0700 Stephen Hemminger wrote: > > The driver supports (and defaults to) using firmware_class for loading the > > firmware. The driver also supports a legacy loading approach for folks that > > have problems with using hotplug to load the firmware (which represents a fair > > number of users). > When and if you submit it into mainline, please remove the legacy loading > approach. Let's get to the cause of the problem and fix it, not bandaid > around it. Or better yet, let's not! There are many people who don't want to mess around with hotplug just to get a single driver to load. -- Tomas Szepe