From: Richard Purdie <rpurdie@rpsys.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: John Lenz <lenz@cs.wisc.edu>,
kernel list <linux-kernel@vger.kernel.org>,
Russell King <rmk+lkml@arm.linux.org.uk>
Subject: Re: Sharp Zaurus sl-5500 broken in 2.6.12
Date: Tue, 19 Jul 2005 21:22:31 +0100 [thread overview]
Message-ID: <1121804551.7499.55.camel@localhost.localdomain> (raw)
In-Reply-To: <20050719192104.GB32757@elf.ucw.cz>
On Tue, 2005-07-19 at 21:21 +0200, Pavel Machek wrote:
> Hi!
>
> > ...and that's well known; but now I did some back tracking, and
> > 2.6.12-rc1 works, 2.6.12-rc2 does *not* and 2.6.12-rc2 with arm
> > changes reverted works. I'll play a bit more.
>
> This fixes at least one break-the-boot bug in -rc2...
>
> Pavel
>
> --- linux-z11.rc2bad/arch/arm/mach-sa1100/collie.c 2005-07-19 20:49:07.000000000 +0200
> +++ linux-z11/arch/arm/mach-sa1100/collie.c 2005-07-19 21:05:54.000000000 +0200
> @@ -235,7 +235,7 @@
> sa11x0_set_flash_data(&collie_flash_data, collie_flash_resources,
> ARRAY_SIZE(collie_flash_resources));
>
> - sharpsl_save_param();
> +// sharpsl_save_param();
> }
>
> static struct map_desc collie_io_desc[] __initdata = {
Could you check this wasn't caused by this typo please:
http://www.rpsys.net/openzaurus/patches/collie_typofix-r0.patch
(this has been fixed in recent kernels)
Cheers,
Richard
next prev parent reply other threads:[~2005-07-19 20:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 19:34 arm: how to operate leds on zaurus? Pavel Machek
2005-07-11 19:45 ` Russell King
2005-07-11 19:50 ` Pavel Machek
2005-07-12 7:16 ` Hamera Erik
2005-07-12 7:21 ` Russell King
2005-07-12 1:07 ` John Lenz
2005-07-19 18:06 ` Sharp Zaurus sl-5500 broken in 2.6.12 Pavel Machek
2005-07-19 19:21 ` Pavel Machek
2005-07-19 20:22 ` Richard Purdie [this message]
2005-07-20 17:57 ` Pavel Machek
2005-07-21 2:41 ` John Lenz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1121804551.7499.55.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=lenz@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rmk+lkml@arm.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox