Re: passing arguments from bootloader to kernel

Tech-Archive recommends: Fix windows errors by optimizing your registry

That would be totally up to you and your BSP. I am not sure that I follow
everything that you wrote, but if the bootloader writes to a BOOT_ARGS
struct at 0xA00FFC00 and the kernel reads from a BOOT_ARGS struct at
0xA00FF0C00 then it should work. Just make sure that both addresses point
to the same physical address.

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

"Ulrich Eckhardt" <eckhardt@xxxxxxxxxxxxxx> wrote in message
news:lf9b53-7d2.ln1@xxxxxxxxxxxxxxxxxxxxxxxxx
> Hi!
>
> I'm currently porting a BSP from PB4.2 to PB5. The board I'm developing
> for
> is derived from the AMP DBAU1100 boards. I currently have the problem that
> I can't pass things like the MAC and IP addresses from EBOOT to the
> kernel.
>
> 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.
> My main questions are:
> - What has changed between 4.2 and 5 that this ceased to work?
> - Is it in fact something that changed in PB (I read that EBOOT barely
> changed since PB3) or is it some adaptions that must have taken place in
> our 4.2 version (which unfortunately was not written in house...) which
> have to be repeated for the PB5 port?
> - What would be the best way to tackle this problem, should I (as good as
> possible) copy the BOOT_ARGS struct to a BSP_ARGS struct? Should I replace
> the implementation of OALArgsQuery with one that looks at the BOOT_ARGS
> struct?
>
> thanks for any suggestions
>
> Uli
>
>


.

Relevant Pages

  • Re: passing arguments from bootloader to kernel
    ... There is no official way to pass parameters between bootloader and ... How you do it (meaning what global memory you choose to use) is up to ... >> struct BOOT_ARGS at address 0xA00FFC00 (used by the bootloader and ... but this is not where and what the kernel ...
    (microsoft.public.windowsce.platbuilder)
  • passing arguments from bootloader to kernel
    ... I'm currently porting a BSP from PB4.2 to PB5. ... I can't pass things like the MAC and IP addresses from EBOOT to the kernel. ... I know there is a struct ...
    (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)