Re: [PATCH 0/5] kbuild

Tom Rini
2004-06-15T21:24:37Z

On Tue, Jun 15, 2004 at 11:02:40PM +0200, Sam Ravnborg wrote:

> On Tue, Jun 15, 2004 at 12:27:40PM -0700, Tom Rini wrote:
> >
> > What I don't see is why:
> > 'znetboot - Build a zImage and put into /tftpboot/
> > uImage - Build an image for U-Boot
> > rom.img - Build an image to live on ROM
> > srec - Build an SREC image'
> >
> > etc, isn't sufficient, in the archhelp.
>
> Two things.
> 1) You better remember to specify them each and every time.
> Otherwise uImage gets out of sync with the kernel.

Yes, you better. If you want the kernel to do a little extra for you,
you need to remember to tell it that.

> 2) I know the srec format, but that is no help to expaling me
> the actual content of the file.
> Memory layout, start address or whatever. Where to find this info.
> Same goes for other targets. I you know your stuff no swaet.
> But for $random hacker it becomes another obstacle

Let me try this a different way. The only valid boot targets on ppc32
are:
- zImage (which is what all does)
- znetboot (zImage + copy to /tftpboot/)
- uImage (U-Boot'ify a kernel)

wrt the last one, I'm torn between making it something that always
happens, since it's just so easy, and if it fails, we can just not care
about it (||true it, or something) or just not worry about it, since if
you're using U-Boot most likely you've already flashed it on, and know
what you're doing).

The "pick the right target" mojo done to ppc32 is like doing it on i386,
it's not a good example of what'll be cleaned up. Same, so it seems,
with ARM. WRT MIPS, I've pointed Ralf at the thread, and he should
speak up soon, I hope :)

--
Tom Rini