Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1763231AbYGOUai (ORCPT ); Tue, 15 Jul 2008 16:30:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1761674AbYGOUaQ (ORCPT ); Tue, 15 Jul 2008 16:30:16 -0400 Received: from senator.holtmann.net ([87.106.208.187]:46804 "EHLO mail.holtmann.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760959AbYGOUaP (ORCPT ); Tue, 15 Jul 2008 16:30:15 -0400 Subject: Re: [GIT *] Allow request_firmware() to be satisfied from in-kernel, use it in more drivers. From: Marcel Holtmann To: David Woodhouse Cc: Linus Torvalds , Jeff Garzik , david@lang.hm, Arjan van de Ven , Andrew Morton , alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org In-Reply-To: <1216152377.26991.10.camel@shinybook.infradead.org> References: <1216077806.27455.85.camel@shinybook.infradead.org> <20080714164119.99c33d5b.akpm@linux-foundation.org> <20080714165956.7fe2d4ee@infradead.org> <487C585C.2060002@garzik.org> <487CD7FE.9010209@garzik.org> <487CDEC0.3090004@garzik.org> <487CEA73.9000408@garzik.org> <1216146651.27455.336.camel@shinybook.infradead.org> <1216152021.27242.94.camel@violet.holtmann.net> <1216152377.26991.10.camel@shinybook.infradead.org> Content-Type: text/plain Date: Tue, 15 Jul 2008 22:30:23 +0200 Message-Id: <1216153823.27242.121.camel@violet.holtmann.net> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2006 Lines: 48 Hi David, > > I really think we should use /lib/firmware/`uname -r`/. I do see the > > point here that I don't wanna overwrite existing firmware from other > > installed kernels. Especially if modules_install will install the > > firmware files. > > > > So in case of non-Ubuntu distros we have to push a fix to udev, but that > > is not a big deal. It should be a one-line change if I am not mistaken. > > My concern with that is that even though it's a one-line change, it's a > one-line change which people don't already _have_. We really do need to > remain compatible with existing setups. > > For _now_, I think it's much better to leave it in /lib/firmware where > existing upstream udev will find it. Let's change udev ASAP and then we > can talk about when it makes sense to change the default setting of > $(INSTALL_FW_PATH) to match. fair enough. What about keeping symlink in /lib/firmware, but actually doing the install in a versioned directory? > I'm not too worried about overwriting existing firmware > in /lib/firmware. We very rarely change firmware anyway, when we _do_ > change it it's almost always compatible rather than having ABI changes. > On the rare occasions that remain, the incompatibly changed firmware > really ought to have a new filename so that older drivers don't pick it > up when they want the old one. Actually in some case we do. I think about the case where I have an two years old kernel that came with the distro and would need that firmware to make the driver work. However now we have the new firmware and it falls over. Breaking a distro install is worse then breaking a new kernel. At least this is how I see it. I do like to have the distro setup as fallback or rescue when I mess up. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/