Andrea Adami wrote:
> Ok, I can finally confirm all works 'as before'.
> Was just a matter of adding CONFIG_MTD_PHYSMAP=y
>
> Stanislav, I don't know how much useful that dictionary could be...it
> doesn't seem worth breaking the partition order, though ;)
Me too, but this dictionary was always
On Wed, Jan 13, 2010 at 12:08:05AM +0100, Stanislav Brabec wrote:
> Martin Jansa wrote:
> > On Tue, Jan 12, 2010 at 01:36:31PM +0100, Stanislav Brabec wrote:
> > >
> > > Note: I sent a patch to the kernel that fixes PROM layout and introduces
> > > two partitions in PROM: Boot PROM System and EN-JP
Ok, I can finally confirm all works 'as before'.
Was just a matter of adding CONFIG_MTD_PHYSMAP=y
Stanislav, I don't know how much useful that dictionary could be...it
doesn't seem worth breaking the partition order, though ;)
Thx
Andrea
___
Zaurus-
Martin Jansa wrote:
> On Tue, Jan 12, 2010 at 01:36:31PM +0100, Stanislav Brabec wrote:
> >
> > Note: I sent a patch to the kernel that fixes PROM layout and introduces
> > two partitions in PROM: Boot PROM System and EN-JP DB3.
>
> With 2.6.32-rc3 I don't see that 2nd PROM partition and didn't no
On Tue, Jan 12, 2010 at 01:36:31PM +0100, Stanislav Brabec wrote:
> Andrea Adami wrote:
> > Hello Stanislav,
> >
> > > Unfortunately I have a fresh report from JaMa about wrong...
> >
> > BTW this was on Spitz. So the question is: does the prom appear
> > somewhere in /proc/partitions? I could no
> Stanislav Brabec
> http://www.penguin.cz/~utx/zaurus
Stanislav, thanks for the long explanations!
We'll retry the all-static in kernel way, lets's hope it produces
deterministic results.
>root at zaurus:~# modprobe physmap
Ah.. actually I think my config lacks physmap...he
>In the last case, I
Andrea Adami wrote:
> > But this is critical problem only for boot. In the user space, there is
> > a lot of chances to prevent it (udev, mount by ID).
> ...
> > So it would not be possible. Either mtd0 or mtd2.
>
> ok, so the only issue could be with pre 2.6.30 kernels / userspaces ?
No. It is g
> But this is critical problem only for boot. In the user space, there is
> a lot of chances to prevent it (udev, mount by ID).
...
> So it would not be possible. Either mtd0 or mtd2.
ok, so the only issue could be with pre 2.6.30 kernels / userspaces ?
With patched kexecboot I got now get :
Got
Andrea Adami wrote:
> Hello Stanislav,
>
> > Unfortunately I have a fresh report from JaMa about wrong...
>
> BTW this was on Spitz. So the question is: does the prom appear
> somewhere in /proc/partitions? I could not find it on say mtd3...
It should (I don't have the latest vanilla just now).
Hello Stanislav,
> Unfortunately I have a fresh report from JaMa about wrong...
BTW this was on Spitz. So the question is: does the prom appear
somewhere in /proc/partitions? I could not find it on say mtd3...
> Kernel makes no guarantee of partition order. It depends on order of
> evaluation.
Andrea Adami wrote:
> Unfortunately I have a fresh report from JaMa about wrong
> /proc/partitions starting with mtd0 System Area :/
Kernel makes no guarantee of partition order. It depends on order of
evaluation. If both drivers (PROM, NAND) are in modules, it can vary
even across reboots.
Unfortunately I have a fresh report from JaMa about wrong
/proc/partitions starting with mtd0 System Area :/
2 options: my defconfigs are bad (I hope) or there is a bug ...
Cheers
Andrea
___
Zaurus-devel mailing list
Zaurus-devel@lists.linuxtogo.org
ht
Hello,
still lacking the rom partition in mtd0. Partitions count is wrong
(kernel in mtd0).
I would hope the corgi OOB/BBT are ok...
And about MMC, I suppose I'm doing something wrong because if I
exchange the SD card and reScan the kexecboot menu removes the old
entries but doesn't list the new
Andrea Adami wrote:
> well, I reply to myself:
>
> in sharpsl-flash.c we had:
>
> static struct mtd_partition sharpsl_partitions[1] = {
> <-->{
> <--><-->name:<-><-->"Boot PROM Filesystem",
> <-->}
> };
This was a map for PROM, and it was incorrect! "Boot PROM Filesystem" is
well, I reply to myself:
in sharpsl-flash.c we had:
static struct mtd_partition sharpsl_partitions[1] = {
<-->{
<--><-->name:<-><-->"Boot PROM Filesystem",
<-->}
};
Now in corgi.c we have:
static struct mtd_partition sharpsl_nand_partitions[] = {
<-->{
<--><-->.
>
> 1) lack of sharpsl-flash (mtdblock1)
I mean PROM on mtd0 and kernel in mtd1
> how can I revive it and have root in mtd2
and a second jffs2 image on mtd3
Andrea
___
Zaurus-devel mailing list
Zaurus-devel@lists.linuxtogo.org
http://lists.linuxtogo.or
Hi,
testing 2.6.33-rc3 on corgi, with limited configuration for kexecboot.
Kexecbooy fails with >2.6.30 kernels , with open flash: No such device.
I found out in the code the reason: we hardcode some mtd readings...see issue #1
Issues not present fin 2.6.26 found so far:
1) lack of sharpsl-flash
Hi!
>Can you share the config you used for spitz?
>I tried rc1 last week and rc2 yesterday (as 2nd stage kernel as well as
>linux-kexecboot), but still have issues with framebuffer/lcd (slowly going
>to all white WSOD or quickly all black - like backlight/lcd turned off).
>When
Hi,
Can you share the config you used for spitz?
I tried rc1 last week and rc2 yesterday (as 2nd stage kernel as well as
linux-kexecboot), but still have issues with framebuffer/lcd (slowly going
to all white WSOD or quickly all black - like backlight/lcd turned off).
When it booted a bit farthe
Not only it boots on spitz, it suspends/resumes too. Obviously more
testing is needed, but... good news so far.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pa
20 matches
Mail list logo
