again on enviroment and partition problems

[Omar Pighi <pighi@selea.com>]

reading here:
http://www.spinics.net/lists/u-boot-v2/msg02944.html

it seems that now it works and save enviroments with correct crc.
but when i triy to ypdate_kernel it says_
partition dev/nand0.kernel.bb not found... no one .bb partition has been
created.
it should be done by hush_hack but it doesn't.

reading here:
http://www.spinics.net/lists/u-boot-v2/msg02957.html

but "CONFIG_GLOB=y"

I cannot find it in any kconfig file... so it is not possible to set
using menuconfig... should i add by hand. this means something missin in
the kconfigs...

Thanks
Omar

Dott. Ing. Omar Pighi
R&D Selea s.r.l.
Via A.Moro 69
46015 Cicognara (MN)
ITALY
tel +39-0375-889091
fax +39-0375-889080
web:www.selea.com


Il 18/04/2011 09:29, Sascha Hauer ha scritto:
> On Sat, Apr 16, 2011 at 11:14:13AM -0700, Greg Topmiller wrote:
>   
>> We're are using the Freescale release L2.6.31_MX51_SDK_0912_Image and
>> it will do this on a Freescale Babbage board and our design.  It also
>> does the same thing in Linux when we mmap the address 0xf0000000 and
>> try to read from it.  It does not hang on the Redboot.bin image
>> supplied with the Freescale SDK.  The Redboot dump command displays
>> some data.  On the Freescale 3Stack board we get an illegal address
>> error in Redboot, but it will hang in u-boot.  We realize this is a
>> reserved physical address but would hope that an error of some kind
>> would occur rather than locking up the CPU.  Could it be some sort of
>> MMU initialization difference between Redboot and u-boot?
>>     
> I have no idea how redboot maps the memory in the mmu, but barebox and
> u-boot use a 1:1 mapping which results in the behaviour you see.
> Accessing reserved memory can result in a abort.
>
> Sascha
>
>   

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox