Hi Mike, On Tue, Oct 25, 2011 at 2:54 AM, Mike Frysinger <[email protected]> wrote: > is there a stable region of memory for the native u-boot to play with > ? certainly "md.b 0" doesn't work :). > > in looking at /proc/`pidof u-boot`/maps, i couldn't pick out anything stable. > > i'm thinking that memory accesses need to be virtualized as well ... > -mike >
I have been using this locally - have sent a patch to the list which shows how to use it with 'md'. The memory buffer is simply malloced ATM. FYI here are the patch titles of things I haven't yet sent out. I will get around to cleaning this up in the next week but if you want something sooner that you can clean up yourself please let me know. Some are Chrome OS-specific. 13e2a89 sandbox: Add Chrome OS memory areas 78a6999 Change md command to use map_physmem b778bfa sandbox: Add board test flash interface eb27542 sandbox: Read contents of SPI flash from file 5f03a47 sandbox: fdt: Add Chrome-OS-specific definitions 9553b03 Change tpm sendrecv prototype cfaac27 sandbox: Add test GPIO driver 7305c9a sandbox: Add test TPM driver cfaf6af sandbox: Add test serial driver 172bc76 sandbox: Add test SPI flash driver aeb8a7b sandbox: Add piglet vbexport plumbing 4c08926 sandbox: Add piglet chromeos plumbing Regards, Simon _______________________________________________ U-Boot mailing list [email protected] http://lists.denx.de/mailman/listinfo/u-boot
