From: Daniel Barkalow <barkalow@iabervon.org>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: richard kennedy <richard@rsk.demon.co.uk>,
bryan.wu@analog.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Bryan Wu <cooloney.lkml@gmail.com>
Subject: Re: [rfc] exposing MMR's of on-chip peripherals for debugging purposes
Date: Mon, 28 Jan 2008 19:30:09 -0500 (EST) [thread overview]
Message-ID: <alpine.LNX.1.00.0801281919490.13593@iabervon.org> (raw)
In-Reply-To: <8bd0f97a0801281615w6fbdd77aifda714685f56cc41@mail.gmail.com>
On Mon, 28 Jan 2008, Mike Frysinger wrote:
> On Jan 28, 2008 7:08 PM, Daniel Barkalow <barkalow@iabervon.org> wrote:
> > Could you submit the XML files and the autogeneration code? The C file
> > isn't really source. Not only is it big, it'll probably change around a
> > whole lot when you make small changes to your process, be hard to review,
> > etc.
>
> that would require the build system to have xml tools installed ...
> that doesnt sound pleasant.
If they're only required for building blackfin debugging stuff, that
shouldn't be a big deal. People building embedded kernels with debugging
from source can probably handle the extra requirement. Setting up a
cross-compilation toolchain for embedded processors is much trickier than
getting xml tools.
> that said, the XML files in question are probably 10x+ the size of the
> C file. swapping 1 meg for 10+ megs ? :)
If it's a bunch of smaller files, and if changes tend to be localized,
that would be a good tradeoff. Alternatively, have them packaged
separately, which might be more appropriate anyway if people might want to
use them for other purposes (on the host when using jtag, perhaps).
-Daniel
*This .sig left intentionally blank*
prev parent reply other threads:[~2008-01-29 0:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 10:16 Mike Frysinger
2008-01-28 10:19 ` Mike Frysinger
2008-01-28 10:40 ` Bryan Wu
2008-01-28 11:06 ` Mike Frysinger
2008-01-28 13:04 ` richard kennedy
2008-01-28 13:10 ` Mike Frysinger
2008-01-29 0:08 ` Daniel Barkalow
2008-01-29 0:15 ` Mike Frysinger
2008-01-29 0:30 ` Daniel Barkalow [this message]
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=alpine.LNX.1.00.0801281919490.13593@iabervon.org \
--to=barkalow@iabervon.org \
--cc=bryan.wu@analog.com \
--cc=cooloney.lkml@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@rsk.demon.co.uk \
--cc=vapier.adi@gmail.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®