| 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
| ||
|
Date: Tue, 7 Jan 2014 16:40:06 +0100 From: Linus Walleij <linus.walleij@...aro.org> To: Pavel Machek <pavel@....cz> Cc: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>, Pali Rohár <pali.rohar@...il.com>, Sebastian Reichel <sre@...g0.de>, "Kim, Milo" <milo.kim@...com>, Bryan Wu <cooloney@...il.com>, David Lang <david@...g.hm>, Joe Xue <lgxue@...mail.com>, "rpurdie@...ys.net" <rpurdie@...ys.net>, "rob@...dley.net" <rob@...dley.net>, "linux-leds@...r.kernel.org" <linux-leds@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org> Subject: Re: n900 led compiler (was Re: [PATCH] Add LED pattern trigger) On Sun, Jan 5, 2014 at 11:23 PM, Pavel Machek <pavel@....cz> wrote: > I implemented compiler for it (should we put it into tools/ somewhere?) We have a precedent for putting firmware compilers into the kernel tree: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/scsi/aic7xxx/aicasm But that one used FLEX. And I think the assumption is that then you store the firmware source with the driver, and the sysfs (or similar) interface would just load and trigger one of the pre-defined firmware programs, not have it be sent in from userspace. Yours, Linus Walleij -- 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