Re: Useless and missing kernel variants in our builds
Izumi Tsutsui <[email protected]>
| Newsgroups | gmane.os.netbsd.ports.arm |
|---|---|
| Message-ID | <[email protected]> |
martin@ wrote:
> I checked, and we do have them:
>
> https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/202407281510Z/evbarm-earmv5/installation/instkernel/netbsd-SHEEVAPLUG_INSTALL.gz
>
> and also
>
> https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/202407281510Z/evbarm-earmv5/installation/instkernel/netbsd-SHEEVAPLUG_INSTALL.img.gz
>
>
> OK, fine. But: I have no idea how to boot either of those. There might be
> some magic how to load the elf kernel file into memory, figure out the entry
> point and just "go" there from u-boot. I don't even know what format .img
> is.
It looks src/distrib/distrib/evbarm/instkernel/instkernel/Makefile
builds .img as "binary" and it doesn't care about .ub format.
> What would be really usefull for this kernel would be a .ub variant.
> For the real kernel we do exactly that - why not for the _INSTALL version?
Maybe we need the same ${TOOL_MKUBOOTIAMGE} magics in
src/distrib/distrib/evbarm/instkernel/instkernel/Makefile
as mk.marvell does?
> Can we find a simple way to drop the useless variants and add the missing
> ones?
We should have a simple script to invoke ${OBJCOPY} and
${TOOL_MKUBOOTIMAGE} ant share it between mk.marvell and
instkernel/Makefile?
---
Izumi Tsutsui