Thank you for the responses guys, much appreciated. We will look into using
the latest release.
Another question...
Can we still use setenv() in the board file?
Before, we setup environment variables in board_late_intit() with setenv,
but it doesn't seem to work in new u-boot
I also tried it in
Hello Dave,
On Wed, Nov 5, 2014 at 7:04 PM, Stefano Babic wrote:
> On 05/11/2014 18:16, DaveKucharczyk wrote:
>> Stefano Babic wrote
>>> You do not need to care about that. Cache is activated per default with
>>> mx5/mx6, if you do not explicitely deactivate it in your config file.
>>> You do not
Hi Dave,
On 05/11/2014 18:16, DaveKucharczyk wrote:
> Stefano Babic wrote
>> You do not need to care about that. Cache is activated per default with
>> mx5/mx6, if you do not explicitely deactivate it in your config file.
>> You do not need to bother about MMU setup in your board files.
>
> Ok t
Stefano, thank you for the very fast response. :)
Stefano Babic wrote
> Instead of doing this, I think it will be easier if you start from the
> current mx53loco nad make the customization for your board. Freescale's
> U-Boot (2009.08) and mainline diverged, as well as some internal API.
Initiall
Hi David,
On 05/11/2014 17:36, DaveKucharczyk wrote:
> I'm trying to upgrade u-boot-2009.08 to u-boot-2014.07.
>
> Our board is loosely based on the Freescale mx53loco board. I used the old
> board file and config header files and moved them over to new u-boot
> directory. Then using the new api
I'm trying to upgrade u-boot-2009.08 to u-boot-2014.07.
Our board is loosely based on the Freescale mx53loco board. I used the old
board file and config header files and moved them over to new u-boot
directory. Then using the new api to make changes.
I'm now trying to figure out how to port and
6 matches
Mail list logo
