Hi Wolfgang,
On Thu, Dec 22, 2011 at 10:04 AM, Wolfgang Denk wrote:
> I'm aware of this. But this was what Fabio quoted from the Linux
> messages:
>
>> > Kernel: arch/arm/boot/Image is ready
>> > Kernel: arch/arm/boot/zImage is ready
>> > multiple load addresses: 0x80008000 0x80008000 0x10008
Dear Stefano Babic,
In message <4ef2f5dc.8010...@denx.de> you wrote:
>
> >>> make uImage LOADADDR=0x70008000
> >>
> >> Exactly, I do the same.
> >
> > Before, you wrote you were using 0x80008000 ...
>
> No, I don't: I wrote that I am using 0x80008000 for MX3. Fabio wrote the
> example for MX53,
On 22/12/2011 10:02, Wolfgang Denk wrote:
> Dear Stefano Babic,
>
> In message <4ef2eff1.1030...@denx.de> you wrote:
>>
>>> make uImage LOADADDR=0x70008000
>>
>> Exactly, I do the same.
>
> Before, you wrote you were using 0x80008000 ...
No, I don't: I wrote that I am using 0x80008000 for MX3. F
Dear Stefano Babic,
In message <4ef2eff1.1030...@denx.de> you wrote:
>
> > make uImage LOADADDR=0x70008000
>
> Exactly, I do the same.
Before, you wrote you were using 0x80008000 ...
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165
On 21/12/2011 23:20, Fabio Estevam wrote:
> Ok, this is the method I can think of:
>
> Let's say I want build a kernel for mx53:
>
> make
> (This will produce a zImage)
>
> make uImage LOADADDR=0x70008000
Exactly, I do the same.
>
> The LOADADDR can be retrieved from:
> arch/arm/mach-imx/Mak
On 21/12/2011 22:24, Fabio Estevam wrote:
> Hi,
>
> When trying to build imx_v4_v5_defconfig, or mx3_defconfig, or
> mx5_defconfig on a 3.2-rc6 kernel I get:
>
> Kernel: arch/arm/boot/Image is ready
> Kernel: arch/arm/boot/zImage is ready
> multiple load addresses: 0x80008000 0x80008000 0x100
> On 12/21/2011 03:20 PM, Fabio Estevam wrote:
> > On Wed, Dec 21, 2011 at 7:24 PM, Fabio Estevam wrote:
> >> Hi,
> >>
> >> When trying to build imx_v4_v5_defconfig, or mx3_defconfig, or
> >> mx5_defconfig on a 3.2-rc6 kernel I get:
> >> ...
> >> multiple load addresses: 0x80008000 0x80008000 0x1
On 12/21/2011 03:20 PM, Fabio Estevam wrote:
> On Wed, Dec 21, 2011 at 7:24 PM, Fabio Estevam wrote:
>> Hi,
>>
>> When trying to build imx_v4_v5_defconfig, or mx3_defconfig, or
>> mx5_defconfig on a 3.2-rc6 kernel I get:
>> ...
>> multiple load addresses: 0x80008000 0x80008000 0x10008000
>> This i
On Wed, Dec 21, 2011 at 7:24 PM, Fabio Estevam wrote:
> Hi,
>
> When trying to build imx_v4_v5_defconfig, or mx3_defconfig, or
> mx5_defconfig on a 3.2-rc6 kernel I get:
>
> Kernel: arch/arm/boot/Image is ready
> Kernel: arch/arm/boot/zImage is ready
> multiple load addresses: 0x80008000 0x80008
Hi,
When trying to build imx_v4_v5_defconfig, or mx3_defconfig, or
mx5_defconfig on a 3.2-rc6 kernel I get:
Kernel: arch/arm/boot/Image is ready
Kernel: arch/arm/boot/zImage is ready
multiple load addresses: 0x80008000 0x80008000 0x10008000
This is incompatible with uImages
Specify LOADADDR o
10 matches
Mail list logo