Luigi 'Comio' Mantellini wrote:
> Hi Bartlomiej,
>
> I posted a week ago some considerations about the new image format (with
> subject "[U-Boot-Users] New Image format: headers hashes."). Please,
> can you give an your opinion about these consideration? I'm really
> interested to support new imag
Hi Bartlomiej,
I posted a week ago some considerations about the new image format (with
subject "[U-Boot-Users] New Image format: headers hashes."). Please,
can you give an your opinion about these consideration? I'm really
interested to support new image in my firmwares, but I need to
understan
Haavard Skinnemoen wrote:
> On Wed, 26 Mar 2008 17:31:40 +0100
> Bartlomiej Sieka <[EMAIL PROTECTED]> wrote:
>
>> BTW: were you able to compile the tools/ directory for the above board?
>> If yes, what were the differences versus the failing build you posted in
>> your other email?
>
> Ah, sorry.
Stefan Roese <[EMAIL PROTECTED]> writes:
> On Thursday 27 March 2008, Haavard Skinnemoen wrote:
>> > BTW: were you able to compile the tools/ directory for the above board?
>> > If yes, what were the differences versus the failing build you posted in
>> > your other email?
>>
>> Ah, sorry. I sent
On 15:16 Wed 26 Mar , Wolfgang Denk wrote:
> Hello everybody,
>
> now that the new image format has been merged into mainline, I
> propose that we make it mandatory for all newly added boards. That
> means, that each new board that gets added shall at least contain
I'll personnaly d
Before applying this patch, I encounter the same issue as Stefan on
mpc8544 and mpc8548 boards.
After applying this patch, they are OK.
This patch should be applied ASAP, which affetcs boundle of boards.
Roy
On Thu, 2008-03-27 at 17:01 +0800, Stefan Roese wrote:
> On Thursday 27 March 2008, Haavard
> Ah, sorry. I sent a patch, but didn't realize it went only to Wolfgang.
> Here it is.
Thanks, the patch works for me.
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just
On Thursday 27 March 2008, Haavard Skinnemoen wrote:
> > BTW: were you able to compile the tools/ directory for the above board?
> > If yes, what were the differences versus the failing build you posted in
> > your other email?
>
> Ah, sorry. I sent a patch, but didn't realize it went only to Wolfg
On Wed, 26 Mar 2008 17:31:40 +0100
Bartlomiej Sieka <[EMAIL PROTECTED]> wrote:
> BTW: were you able to compile the tools/ directory for the above board?
> If yes, what were the differences versus the failing build you posted in
> your other email?
Ah, sorry. I sent a patch, but didn't realize it
> I'm running Ubuntu and am getting this errors too. Even without
> enabling CONFIG_FIT:
When I build the MPC837XEMDS/MPC8360EMDS on Ubuntu, I happen the same
error.
-
Check out the new SourceForge.net Marketplace.
It's the
In message <[EMAIL PROTECTED]> you wrote:
> PiANCj4gSSdtIHJ1bm5pbmcgVWJ1bnR1IGFuZCBhbSBnZXR0aW5nIHRoaXMgZXJyb3JzIHRvby4g
> RXZlbiB3aXRob3V0DQo+IGVuYWJsaW5nIENPTkZJR19GSVQ6DQoNCldoZW4gSSBidWlsZCBNUEM4
> MzYwRU1EUy9NUEM4MzdYRU1EUyBvbiBVYnVudHUsIHRoZSBzYW1lIGVycm9yDQpoYXBwZW4gdG8g
> bWUuIA0KDQpUaGFua3
>
> I'm running Ubuntu and am getting this errors too. Even without
> enabling CONFIG_FIT:
When I build MPC8360EMDS/MPC837XEMDS on Ubuntu, the same error
happen to me.
Thanks,
Dave
-
Check out the new SourceForge.net Market
On Thursday 27 March 2008, Jerry Van Baren wrote:
> I also am running debian and am getting the error. Apparently our
> /usr/include/linux/types.h files are different from yours, or we have
> something set up differently/wrongly.
>
> Adding -isystem ../include (to override the host's include files
Haavard Skinnemoen wrote:
> On Wed, 26 Mar 2008 15:16:44 +0100
> Wolfgang Denk <[EMAIL PROTECTED]> wrote:
>
>> now that the new image format has been merged into mainline, I
>> propose that we make it mandatory for all newly added boards. That
>> means, that each new board that gets adde
Bartlomiej Sieka wrote:
Haavard Skinnemoen wrote:
On Wed, 26 Mar 2008 15:16:44 +0100
Wolfgang Denk <[EMAIL PROTECTED]> wrote:
Can we agree on this?
Can we please un-break the existing tree first?
gcc -g -Wall -idirafter /home/hskinnemoen/git/u-boot/upstream/include
-idirafter /home/hskinnem
Guennadi Liakhovetski wrote:
> HEAD. Which is almost 30% increase... Sorry, I didn't follow the "new
> format" discussion, is it also going to be useful on ARM and on other
> platforms not using FDT?
As MIPS custodian I feel the same, too.
I'm just wondering, if this feature is useful for all a
In message <[EMAIL PROTECTED]> you wrote:
>
> I'm getting 34KB increase iin the resulting binary just by enabling the
> required for FIT config macros in an arm11 build with the current git
We need to check where this size penalty is coming from. It's not
supposed top be that big.
> HEAD. W
On Wed, 26 Mar 2008, Haavard Skinnemoen wrote:
> On Wed, 26 Mar 2008 15:16:44 +0100
> Wolfgang Denk <[EMAIL PROTECTED]> wrote:
>
> > now that the new image format has been merged into mainline, I
> > propose that we make it mandatory for all newly added boards. That
> > means, that each
Haavard Skinnemoen wrote:
> On Wed, 26 Mar 2008 15:16:44 +0100
> Wolfgang Denk <[EMAIL PROTECTED]> wrote:
>
>> now that the new image format has been merged into mainline, I
>> propose that we make it mandatory for all newly added boards. That
>> means, that each new board that gets adde
Haavard Skinnemoen wrote:
> On Wed, 26 Mar 2008 15:16:44 +0100
> Wolfgang Denk <[EMAIL PROTECTED]> wrote:
>
>> Can we agree on this?
>
> Can we please un-break the existing tree first?
>
> gcc -g -Wall -idirafter /home/hskinnemoen/git/u-boot/upstream/include
> -idirafter /home/hskinnemoen/git/u
On Wed, 26 Mar 2008 15:16:44 +0100
Wolfgang Denk <[EMAIL PROTECTED]> wrote:
> now that the new image format has been merged into mainline, I
> propose that we make it mandatory for all newly added boards. That
> means, that each new board that gets added shall at least contain
>
>
On Wed, 26 Mar 2008 15:16:44 +0100
Wolfgang Denk <[EMAIL PROTECTED]> wrote:
> Can we agree on this?
Can we please un-break the existing tree first?
gcc -g -Wall -idirafter /home/hskinnemoen/git/u-boot/upstream/include
-idirafter /home/hskinnemoen/git/u-boot/upstream/include2 -idirafter
/home/h
On Mar 26, 2008, at 9:57 AM, Wolfgang Denk wrote:
> In message
> <[EMAIL PROTECTED]> you wrote:
>>
>>> Can we agree on this?
>>
>> I haven't tried out the CONFIG_FIT stuff yet so some of these
>> concerns
>> might not be real issues:
>> 1. Are their changes to linux kernel build system to crea
In message <[EMAIL PROTECTED]> you wrote:
>
> > Can we agree on this?
>
> I haven't tried out the CONFIG_FIT stuff yet so some of these concerns
> might not be real issues:
> 1. Are their changes to linux kernel build system to create a
> FIT .uImage ?
Not yet.
> 2. if "#define CONFIG_FIT 1
Kumar Gala wrote:
[...]
> I haven't tried out the CONFIG_FIT stuff yet so some of these concerns
> might not be real issues:
> 1. Are their changes to linux kernel build system to create a
> FIT .uImage ?
No, new uImage support has not been integrated with the kernel build system.
> 2. if "#d
Wolfgang Denk wrote:
> Hello everybody,
>
> now that the new image format has been merged into mainline, I
> propose that we make it mandatory for all newly added boards. That
> means, that each new board that gets added shall at least contain
>
> #define CONFIG_FIT 1
On Mar 26, 2008, at 9:16 AM, Wolfgang Denk wrote:
> Hello everybody,
>
> now that the new image format has been merged into mainline, I
> propose that we make it mandatory for all newly added boards. That
> means, that each new board that gets added shall at least contain
>
> #defi
Hello everybody,
now that the new image format has been merged into mainline, I
propose that we make it mandatory for all newly added boards. That
means, that each new board that gets added shall at least contain
#define CONFIG_FIT 1
in it's board config file; I re
28 matches
Mail list logo
