On Tue, Feb 2, 2010 at 3:22 AM, Andrea Adami wrote:
> OMG... we can even avoid that pxa-linking-bug-r1 patch!
> 2.6.33-rc6 boots vanilla.
>
That really depends - I have several kernel images that can be loaded
without problem, but note size and alignment do look relevant.
> [more after LZMA test
OMG... we can even avoid that pxa-linking-bug-r1 patch!
2.6.33-rc6 boots vanilla.
[more after LZMA testing]
Andrea
___
Zaurus-devel mailing list
Zaurus-devel@lists.linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Well, please wait a bit more before reporting...
Eric, with 'fixed' updater.sh I could flash linux-kexecboot 2.6.33-rc6
and it boots!
Still experimenting around.
I'll report later.
TIA
Andrea
___
Zaurus-devel mailing list
Zaurus-devel@lists.linuxtogo
This is the correct version
>>> I'd say it must be the commit e7db7b427 because
>>> kernel 2.6.33-rc3 was booting just fine on corgi.
2.6.33-rc3 has been tested on spitz by other devs (JaMa and pwgen)
Ok, my last doubt is I only tested on corgi.
Anybody tested flashing newer rc on spitz?
The co
>>>
>>> Back to compressors, I say it must be the commit e7db7b427 because
>>> kernel 2.6.33-rc4 was booting just fine.
>>
>> Report regression to rjw and patch author (cc l-k), then, and get the
>> patch reverted.
>
> Pavel,
>
> Please hold on for a while. Andrea may have some more comments?
>
YE
On Tue, Feb 2, 2010 at 2:15 AM, Pavel Machek wrote:
> On Mon 2010-02-01 18:07:01, Andrea Adami wrote:
>> >> 3) kernel size is uninfluent: I tested 930KiB-lzma kernels and 1240KiB
>> >> gzip-kernels.
>>
>> >It sounds to me like this is because of the 1.4M (cannot
>> >remember the exact size) const
On Mon 2010-02-01 18:07:01, Andrea Adami wrote:
> >> 3) kernel size is uninfluent: I tested 930KiB-lzma kernels and 1240KiB
> >> gzip-kernels.
>
> >It sounds to me like this is because of the 1.4M (cannot
> >remember the exact size) constraint of the kernel size
> >on NAND that the bootloader is
On Tue, Feb 2, 2010 at 1:07 AM, Andrea Adami wrote:
>>> 3) kernel size is uninfluent: I tested 930KiB-lzma kernels and 1240KiB
>>> gzip-kernels.
>
>>It sounds to me like this is because of the 1.4M (cannot
>>remember the exact size) constraint of the kernel size
>>on NAND that the bootloader is a
>> 3) kernel size is uninfluent: I tested 930KiB-lzma kernels and 1240KiB
>> gzip-kernels.
>It sounds to me like this is because of the 1.4M (cannot
>remember the exact size) constraint of the kernel size
>on NAND that the bootloader is able to load?
Unfortunately not :(
Kernel did not exceed th
It sounds to me like this is because of the 1.4M (cannot
remember the exact size) constraint of the kernel size
on NAND that the bootloader is able to load?
On Mon, Feb 1, 2010 at 8:14 PM, Pavel Machek wrote:
> Hi!
>
> I guess Andrea wanted me to forward this
>
> - Forwarded message from
Hi!
I guess Andrea wanted me to forward this
- Forwarded message from Andrea Adami -
Date: Mon, 1 Feb 2010 13:08:44 +0100
From: Andrea Adami
To: pa...@ucw.cz
Subject: About kernel decompressors
Pavel,
I'd like to add a couple of observations in the "Uncompressing broken
with comm
11 matches
Mail list logo
