| 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: <1284193744.20200.13.camel@i7.infradead.org> Date: Sat, 11 Sep 2010 09:29:04 +0100 From: David Woodhouse <David.Woodhouse@...el.com> To: Mark Brown <broonie@...nsource.wolfsonmicro.com> Cc: Andrew Morton <akpm@...ux-foundation.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "patches@...nsource.wolfsonmicro.com" <patches@...nsource.wolfsonmicro.com> Subject: Re: [PATCH] ihex: Add support for CS:IP/EIP records On Thu, 2010-09-09 at 14:40 +0100, Mark Brown wrote: > ihex firmwares can include a jump address for starting execution. Add > a -j option which will cause this to be written into the generated > file as a record with address zero and data consisting of the address > to jump to, allowing drivers to make use of this information. Some questions... - Which firmware blobs that are *already* in the kernel would need this? Remember, we're not adding new crap to the kernel source tree; new firmware images get added to linux-firmware.git instead. - Why make the include_jump code optional? When would we ever *not* want to include such a record -- when does the input ihex file contain such a record that the kernel driver *must* not see because it can't cope with it? -- David Woodhouse Open Source Technology Centre David.Woodhouse@...el.com Intel Corporation -- 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