[U-Boot] is it possilbe to have uboot find the kernel in the file system?

[Wolfgang Denk]

Dear John Stile,

In message <1357323597.6335.19.camel at genx.eng.msli.com> you wrote:
>
> > I see the following board configurations supported in current mainline
> > code: at91sam9g20ek_nandflash, at91sam9g20ek_dataflash_cs0, and
> > at91sam9g20ek_dataflash_cs1 .  Anything wrong with those?
> 
> I'm going to have to wrestle with buildroot's uboot configuration or
> something... But it would be helpful to know what he build error means.
...
> BR2_TARGET_UBOOT_BOARDNAME="at91sam9g20ek"

I don't know what "BOARDNAME" is exactly supposed to mean here, but
probably this should be one of the configuration names I listed above.

...
> BR2_TARGET_AT91BOOTSTRAP_BOARD="at91sam9g20ek"

Or this? I have no idea what the difference between BOARDNAME and
BOARD might be...

> BR2_TARGET_AT91BOOTSTRAP_MEMORY="dataflash"

OK, it appears you want one of the at91sam9g20ek_dataflash_csX
configurations...

> make: *** No rule to make target `at91sam9g20ek_config'.  Stop.

Well, as mentioned in my previous message, the known config names are
"at91sam9g20ek_nandflash", "at91sam9g20ek_dataflash_cs0", and
"at91sam9g20ek_dataflash_cs1";  plain "at91sam9g20ek" is NOT a known
config name.

> What should the target be?

Depending whether you want to use CS0 or CS1 to address the dataflash
on your board, it should probably be  "at91sam9g20ek_dataflash_cs0"
or  "at91sam9g20ek_dataflash_cs1".

> Maybe my buildroot is also so old it doesn't support the new uboot
> configuration syntax?

I think it's just misconfigured.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
I don't see any direct evidence ...  but, then, my crystal ball is in
dire need of an ectoplasmic upgrade. :-)              -- Howard Smith