From: David Woodhouse <David.Woodhouse@intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"patches@opensource.wolfsonmicro.com"
<patches@opensource.wolfsonmicro.com>
Subject: Re: [PATCH] ihex: Add support for CS:IP/EIP records
Date: Sat, 11 Sep 2010 09:29:04 +0100 [thread overview]
Message-ID: <1284193744.20200.13.camel@i7.infradead.org> (raw)
In-Reply-To: <1284039626-30394-1-git-send-email-broonie@opensource.wolfsonmicro.com>
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@intel.com Intel Corporation
next prev parent reply other threads:[~2010-09-11 8:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 13:40 Mark Brown
2010-09-11 8:29 ` David Woodhouse [this message]
2010-09-11 10:06 ` Mark Brown
2010-09-15 21:27 ` Andrew Morton
2010-09-16 10:41 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1284193744.20200.13.camel@i7.infradead.org \
--to=david.woodhouse@intel.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®