Re: passing arguments from bootloader to kernel

Correct. There is no official way to pass parameters between bootloader and
OS. How you do it (meaning what global memory you choose to use) is up to
you. Some of the BSPs that come with PB have done it in one particular way,
doesn't mean you have to do it that way.

It's also not necessarily true that you need to pass data at all. That is
also up to you (whatever you do in the loader you could also do in the
kernel).

--
Dean Ramsier - eMVP
BSQUARE Corporation


"Ulrich Eckhardt" <eckhardt@xxxxxxxxxxxxxx> wrote in message
news:c4jb53-tp2.ln1@xxxxxxxxxxxxxxxxxxxxxxxxx
> Ulrich Eckhardt wrote:
>> I have traced EBOOT to the point where it jumps into the image and there
>> is no place where it writes any arguments to the RAM. I know there is a
>> struct BOOT_ARGS at address 0xA00FFC00 (used by the bootloader and
>> identifiable by its signature) which is also where EBOOT reads some of
>> the
>> configuration data from, but this is not where and what the kernel
>> expects.
>>
>> The kernel (in ..SRC\KERNEL\OAL\args.c) expects a struct BSP_ARGS
>> somewhere. [...]
>
> OK, I just stumbled across an article in the help "Creating Driver Globals
> and Boot Args". Now, if I understand that right, this struct BOOT_ARGS is
> supposed to be adapted to the needs of the implementor and is nothing
> 'fixed', right?
> If so, I really need to adapt the kernel in order to extract the info from
> the particular layout of the struct.
>
> Can anyone confirm this?
>
> Uli
>


.

Relevant Pages

  • Re: passing arguments from bootloader to kernel
    ... but if the bootloader writes to a BOOT_ARGS ... struct at 0xA00FFC00 and the kernel reads from a BOOT_ARGS struct at ... > I have traced EBOOT to the point where it jumps into the image and there ...
    (microsoft.public.windowsce.platbuilder)
  • Re: passing arguments from bootloader to kernel
    ... > struct at 0xA00FFC00 and the kernel reads from a BOOT_ARGS struct at ... my problem is rather that the bootloader uses a struct BOOT_ARGS at ... 0xa00ffc00 but the kernel expects a struct BSP_ARGS. ... the bootloader came with a BSP that was written for PB4.2 ...
    (microsoft.public.windowsce.platbuilder)
  • Gcov-kernel patch update for 2.6.0-test3
    ... Here's another resync of the kernel patch (originally by Hubertus Franke ... and Rajan Ravindran) to allow the gcov coverage analysis tool to be used ... * The .ctors-section contains a list of pointers to constructor ... static struct memchunk *freechunks; ...
    (Linux-Kernel)
  • [RFC v3][PATCH 2/2] intel_txt: Intel(R) TXT and tboot kernel support
    ... Linux support for IntelTrusted Execution Technology. ... struct boot_params { ... shared data structure with tboot and kernel and functions ... +Trusted Boot (tboot) is an open source, pre- kernel/VMM module that uses Intel ...
    (Linux-Kernel)
  • [RFC v4][PATCH 2/2] intel_txt: Intel(R) TXT and tboot kernel support
    ... Linux support for IntelTrusted Execution Technology. ... struct boot_params { ... * tboot.h: shared data structure with tboot and kernel and functions ...
    (Linux-Kernel)