Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757297AbYGNJ3j (ORCPT ); Mon, 14 Jul 2008 05:29:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756296AbYGNJ33 (ORCPT ); Mon, 14 Jul 2008 05:29:29 -0400 Received: from relay1.sgi.com ([192.48.171.29]:46508 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754511AbYGNJ32 (ORCPT ); Mon, 14 Jul 2008 05:29:28 -0400 Message-ID: <487B1C73.5000202@sgi.com> Date: Mon, 14 Jul 2008 11:29:23 +0200 From: Jes Sorensen User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: Jaswinder Singh CC: LKML , David Woodhouse , Alan Cox , kernel-janitors , kernelnewbies , linux-scsi@vger.kernel.org, hch@infradead.org Subject: Re: [PATCH] qla1280: use request_firmware References: <1215770284.2733.10.camel@jaswinder.satnam> In-Reply-To: <1215770284.2733.10.camel@jaswinder.satnam> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 997 Lines: 31 Jaswinder Singh wrote: > this is a first draft; please be kind :) > > Firmware blob is little endian looks like this... > unsigned char Version1 > unsigned char Version2 > unsigned char Version3 > unsigned char Padding > unsigned short start_address > unsigned short data Hello, As the maintainer of this driver I am going to say that I think this is a stupid change. Yes I know that politically there's a move to make everything use request firmware. However for my boot device, this is going to be a royal pain in the butt for developers who wish to boot test kernels with a / sitting on a 1280. IMHO this patch brings us nothing, but provides a lot of unnecessary hassle for users. Nacked-By: Jes Sorensen Regards, Jes -- 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/