| 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
| ||
|
Message-ID: <20091114102919.54606831@infradead.org> Date: Sat, 14 Nov 2009 10:29:19 -0800 From: Arjan van de Ven <arjan@...radead.org> To: Robert Hancock <hancockrwd@...il.com> Cc: venu <vjosyula@...il.com>, Roland Dreier <rdreier@...co.com>, Philip Downer <phil@...devices.co.uk>, linux-kernel@...r.kernel.org Subject: Re: firmware loading interface On Sat, 14 Nov 2009 12:19:13 -0600 Robert Hancock <hancockrwd@...il.com> wrote: > On Sat, Nov 14, 2009 at 10:55 AM, venu <vjosyula@...il.com> wrote: > > who triggers this upgrade from userspace ? I understand it is a > > naivee / beginers questions but i hope somebody explains me how ? > > The request_firmware interface probably isn't suitable for that.. > using an ioctl or read/write-based interface, possibly on a separate > device node, would likely be the way to go.. > 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.... -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org -- 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/
Powered by blists - more mailing lists