linux-kernel - Re: firmware loading interface

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 14 Nov 2009 10:08:52 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	Roland Dreier <rdreier@...co.com>
CC:	Philip Downer <phil@...devices.co.uk>, linux-kernel@...r.kernel.org
Subject: Re: firmware loading interface

On 11/13/2009 06:35 PM, Roland Dreier wrote:
>
>   >  However our device will have flash to store the firmware in and, whilst
>   >  it looks as though it would be possible for us to use request_firmware
>   >  to provide occasional firmware upgrades from userspace, I can't find any
>   >  reference as to whether this is an accepted method for doing so. Could
>   >  someone please confirm for me whether or not it's a good idea to use
>   >  request_firmware for this, or perhaps point me at another standard
>   >  method for doing firmware updates from userspace?
>
> I think request_firmware() is fine for this... you could have a look at
> drivers/net/cxgb3 to see a device that writes new firmware to flash when
> it detects a version mismatch between driver and device.

It depends on the consequences of a failed flash due to losing power, 
crash, etc - if it has the potential to brick the device then I don't 
think that should happen without the user triggering it explicitly..
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/