[U-Boot] [PATCH] board/BuR/kwb: implement board-specific do_go_exec to form vxWorks bootline

[Hannes Schmelzer]

> Hi Hannes,
Hi,

> >>
> >> Could you please try this patch series [1] instead?
> >>
> >> With that series, we can construct VxWorks bootline from U-Boot env.
> >> Like you can store your additional bootline info to U-Boot env
> >> variable "othbootargs", like
> >>
> >> => setenv othbootargs u=vxWorksFTP pw=vxWorks o=fb_addr=xxx
> > factory_setting=yyy
> > I will have a closer look to this.
> > The framebuffer base is stored at this time in gd->fb_base
> >
> >         sprintf(vxworksbootline,
> >                 "%s h=%s e=%s:%s g=%s %s 
o=0x%08x;0x%08x;0x%08x;0x%08x",
> >                 DEFAULT_BOOTLINE,
> >                 getenv("serverip"),
> >                 getenv("ipaddr"), getenv("netmask"),
> >                 getenv("gatewayip"),
> >                 VXWORKS_USER,
> >                 (unsigned int) gd->fb_base-0x20,
> >                 (u32)getenv_ulong("vx_memtop", 16, gd->fb_base-0x20),
> >                 (u32)getenv_ulong("vx_romfsbase", 16, 0),
> >                 (u32)getenv_ulong("vx_romfssize", 16, 0));
> >
> > do you thank that i cal realize a bootline like this with current 
tools?
> >
> 
> Yes, I think you can do something like setenv("othbootargs",
> addtional_bootlines) where addtional_bootlines holds the value for
> frame buffer address from gd->fb_base.

OK, the plan would be:

a) setup some othbootargs out from board.c (because gd->fb_base isn't 
accessible through cli)
b) call bootvx instead go ... to start vxWorks kernel

right?

> 
> Regards,
> Bin
regards,
Hannes