On Mon, Mar 24, 2014 at 10:34:44PM -0500, Joel Fernandes wrote:
> Loading kernel at offset 0x1 works only for zImage, but not for Image,
> because the kernel expect the start of decompressed kernel (.head.text) to be
> at an address that's a distance that's 16MB aligned from PAGE_OFFSET +
> TE
On Thu, Apr 17, 2014 at 11:34 PM, Christopher Covington
wrote:
> On 04/17/2014 06:02 AM, Peter Maydell wrote:
>> On 2 April 2014 13:47, Peter Maydell wrote:
>>> On 2 April 2014 13:11, Peter Crosthwaite
>>> wrote:
Like others, I have been carrying this change locally. Good to see it up!
>>>
On Fri, Apr 18, 2014 at 5:26 AM, Peter Maydell wrote:
> On 17 April 2014 17:58, Rob Herring wrote:
>> On Thu, Apr 17, 2014 at 5:02 AM, Peter Maydell
>> wrote:
>>> On 2 April 2014 13:47, Peter Maydell wrote:
On 2 April 2014 13:11, Peter Crosthwaite
wrote:
> Like others, I have b
On 17 April 2014 17:58, Rob Herring wrote:
> On Thu, Apr 17, 2014 at 5:02 AM, Peter Maydell
> wrote:
>> On 2 April 2014 13:47, Peter Maydell wrote:
>>> On 2 April 2014 13:11, Peter Crosthwaite
>>> wrote:
Like others, I have been carrying this change locally. Good to see it up!
>>>
>>> Wh
On Thu, Apr 17, 2014 at 5:02 AM, Peter Maydell wrote:
> On 2 April 2014 13:47, Peter Maydell wrote:
>> On 2 April 2014 13:11, Peter Crosthwaite
>> wrote:
>>> Like others, I have been carrying this change locally. Good to see it up!
>>
>> Why are you all booting raw Images anyway (just out of cu
On Thu, Apr 17, 2014 at 8:34 AM, Christopher Covington
wrote:
> On 04/17/2014 06:02 AM, Peter Maydell wrote:
>> On 2 April 2014 13:47, Peter Maydell wrote:
>>> On 2 April 2014 13:11, Peter Crosthwaite
>>> wrote:
Like others, I have been carrying this change locally. Good to see it up!
>>>
On 04/17/2014 06:02 AM, Peter Maydell wrote:
> On 2 April 2014 13:47, Peter Maydell wrote:
>> On 2 April 2014 13:11, Peter Crosthwaite
>> wrote:
>>> Like others, I have been carrying this change locally. Good to see it up!
>>
>> Why are you all booting raw Images anyway (just out of curiosity)?
On 2 April 2014 13:47, Peter Maydell wrote:
> On 2 April 2014 13:11, Peter Crosthwaite wrote:
>> Like others, I have been carrying this change locally. Good to see it up!
>
> Why are you all booting raw Images anyway (just out of curiosity)?
Given the recent feedback from the kernel mailing list
On Wed, Apr 2, 2014 at 7:47 AM, Peter Maydell wrote:
> On 2 April 2014 13:11, Peter Crosthwaite wrote:
>> Like others, I have been carrying this change locally. Good to see it up!
>
> Why are you all booting raw Images anyway (just out of curiosity)? All my
> test cases boot either a zImage or a
[On 04/02/2014 08:47 AM, Peter Maydell wrote:
> On 2 April 2014 13:11, Peter Crosthwaite wrote:
>> Like others, I have been carrying this change locally. Good to see it up!
>
> Why are you all booting raw Images anyway (just out of curiosity)? All my
> test cases boot either a zImage or a uImage,
On Wed, Apr 2, 2014 at 10:47 PM, Peter Maydell wrote:
> On 2 April 2014 13:11, Peter Crosthwaite wrote:
>> Like others, I have been carrying this change locally. Good to see it up!
>
> Why are you all booting raw Images anyway (just out of curiosity)? All my
> test cases boot either a zImage or a
On 2 April 2014 13:11, Peter Crosthwaite wrote:
> Like others, I have been carrying this change locally. Good to see it up!
Why are you all booting raw Images anyway (just out of curiosity)? All my
test cases boot either a zImage or a uImage, or occasionally a full SD card
image, or I'd have noti
On Wed, Apr 2, 2014 at 3:10 AM, Peter Maydell wrote:
> On 25 March 2014 03:34, Joel Fernandes wrote:
>> Loading kernel at offset 0x1 works only for zImage, but not for Image,
>> because the kernel expect the start of decompressed kernel (.head.text) to be
>> at an address that's a distance th
On 25 March 2014 03:34, Joel Fernandes wrote:
> Loading kernel at offset 0x1 works only for zImage, but not for Image,
> because the kernel expect the start of decompressed kernel (.head.text) to be
> at an address that's a distance that's 16MB aligned from PAGE_OFFSET +
> TEXT_OFFSET (see vm
On Tue, Mar 25, 2014 at 7:29 AM, Christopher Covington
wrote:
> Hi Joel,
>
> On 03/24/2014 11:34 PM, Joel Fernandes wrote:
>> Loading kernel at offset 0x1 works only for zImage, but not for Image,
>> because the kernel expect the start of decompressed kernel (.head.text) to be
>
> Nit: expects
On 03/25/2014 08:13 AM, Peter Maydell wrote:
> On 25 March 2014 03:34, Joel Fernandes wrote:
>> Loading kernel at offset 0x1 works only for zImage, but not for Image,
>> because the kernel expect the start of decompressed kernel (.head.text) to be
>> at an address that's a distance that's 16MB
On 25 March 2014 03:34, Joel Fernandes wrote:
> Loading kernel at offset 0x1 works only for zImage, but not for Image,
> because the kernel expect the start of decompressed kernel (.head.text) to be
> at an address that's a distance that's 16MB aligned from PAGE_OFFSET +
> TEXT_OFFSET (see vm
Hi Joel,
On 03/24/2014 11:34 PM, Joel Fernandes wrote:
> Loading kernel at offset 0x1 works only for zImage, but not for Image,
> because the kernel expect the start of decompressed kernel (.head.text) to be
Nit: expects
> at an address that's a distance that's 16MB aligned from PAGE_OFFSET
Loading kernel at offset 0x1 works only for zImage, but not for Image,
because the kernel expect the start of decompressed kernel (.head.text) to be
at an address that's a distance that's 16MB aligned from PAGE_OFFSET +
TEXT_OFFSET (see vmlinux.lds.S). This check is enfornced in __fixup_pv_tab
19 matches
Mail list logo