[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.LNX.1.00.0801281919490.13593@iabervon.org>
Date: Mon, 28 Jan 2008 19:30:09 -0500 (EST)
From: Daniel Barkalow <barkalow@...ervon.org>
To: Mike Frysinger <vapier.adi@...il.com>
cc: richard kennedy <richard@....demon.co.uk>, bryan.wu@...log.com,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Bryan Wu <cooloney.lkml@...il.com>
Subject: Re: [rfc] exposing MMR's of on-chip peripherals for debugging
purposes
On Mon, 28 Jan 2008, Mike Frysinger wrote:
> On Jan 28, 2008 7:08 PM, Daniel Barkalow <barkalow@...ervon.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*
--
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