From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <486E28BB.1030205@garzik.org> Date: Fri, 04 Jul 2008 09:42:19 -0400 From: Jeff Garzik MIME-Version: 1.0 Subject: Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" References: <20080703020236.adaa51fa.akpm@linux-foundation.org> <20080703205548.D6E5.KOSAKI.MOTOHIRO@jp.fujitsu.com> <486CC440.9030909@garzik.org> <1215177471.10393.753.camel@pmac.infradead.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Takashi Iwai Cc: David Woodhouse , Hugh Dickins , KOSAKI Motohiro , mchan@broadcom.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Andrew Morton , netdev@vger.kernel.org List-ID: Takashi Iwai wrote: > Ah I see. I thought you implemented the built-in firmware even for > modules, but apparently it's not. Correct. > Is mkinitrd clever enough to put all needed firmware files to initrd > automatically? Otherwise this can still break the existing setup... mkinitrd and similar scripts must be updated, so that drivers that worked prior to dwmw2's changes will continue to work after dwmw2's changes. If you fail to update some script somewhere, then the driver will be copied into the initramfs, but not the firmware, with obvious results. This is not a fail-safe system. This is an enforced-breakage, flag-day change that will cause a lot of additional work for a lot of people. Jeff -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org