[U-Boot-Users] bootm support for netbsd question

Anyone know why we pass the image_header_t * to the netbsd loader?
/* * Booting a (NetBSD) kernel image * * This process is pretty similar to a standalone application: * The (first part of an multi-) image must be a stage-2 loader, * which in turn is responsible for loading & invoking the actual * kernel. The only differences are the parameters being passed: * besides the board info strucure, the loader expects a command * line, the name of the console device, and (optionally) the * address of the original image header. */ ...
/* * NetBSD Stage-2 Loader Parameters: * r3: ptr to board info data * r4: image address * r5: console device * r6: boot args string */ (*loader) (gd->bd, os_hdr, consdev, cmdline);
this is some pretty tight coupling with u-boot. Is the stage-2 loader part of u-boot?
- k

Kumar Gala wrote:
Anyone know why we pass the image_header_t * to the netbsd loader?
*snip*
this is some pretty tight coupling with u-boot. Is the stage-2 loader part of u-boot?
I believe this is meant to be NetBSD's last stage bootloader and not any U-Boot piece. See for example their PREP loader variant: http://fxr.watson.org/fxr/source/arch/prep/stand/
As I understand it, to boot NetBSD from U-Boot they produce a fat image (the above stage2 loader + kernel as a multi-image file), which is booted via bootm, but I never exercised the procedure myself.
Rafal

Rafal Jaworowski wrote:
Kumar Gala wrote:
Anyone know why we pass the image_header_t * to the netbsd loader?
*snip*
this is some pretty tight coupling with u-boot. Is the stage-2 loader part of u-boot?
I believe this is meant to be NetBSD's last stage bootloader and not any U-Boot piece. See for example their PREP loader variant: http://fxr.watson.org/fxr/source/arch/prep/stand/
Ooops, I meant: http://fxr.watson.org/fxr/source/arch/prep/stand/?v=NETBSD
Rafal
participants (2)
-
Kumar Gala
-
Rafal Jaworowski