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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Mon, 16 Nov 2009 11:16:45 +0000
From:	Philip Downer <phil@...devices.co.uk>
To:	Arjan van de Ven <arjan@...radead.org>
CC:	Robert Hancock <hancockrwd@...il.com>, venu <vjosyula@...il.com>,
	Roland Dreier <rdreier@...co.com>, linux-kernel@...r.kernel.org
Subject: Re: firmware loading interface

Arjan van de Ven wrote:
> it's not unusual to have a sysfs attribute that, when written to, will
> just do a request_firmware().
> It's not pretty, but it's cleaner than the alternatives....
>   

This was in fact what I was considering when making my initial post, but 
couldn't find any examples or drivers which do use sysfs and request 
firmware in this way and as you say, it's not pretty. However if it's 
considered to be cleaner by others (I certainly think it to be so) then 
I am inclined to use this method as opposed to the ioctl method 
suggested by Arnd earlier in the thread.

Arjan, could you possibly point me at any drivers which already work in 
this way?

Thanks,

Philip Downer

--
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/