From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Pavel Machek <pavel@ucw.cz>
Cc: lenz@cs.wisc.edu, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: arm: how to operate leds on zaurus?
Date: Mon, 11 Jul 2005 20:45:34 +0100 [thread overview]
Message-ID: <20050711204534.C1540@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20050711193454.GA2210@elf.ucw.cz>; from pavel@ucw.cz on Mon, Jul 11, 2005 at 09:34:54PM +0200
On Mon, Jul 11, 2005 at 09:34:54PM +0200, Pavel Machek wrote:
> Hi!
>
> 2.6.12-rc5 (and newer) does not boot on sharp zaurus sl-5500. It
> blinks with green led, fast; what does it mean? I'd like to verify if
> it at least reaches .c code in setup.c. I inserted this code at
> begining of setup.c:674...
>
> #define locomo_writel(val,addr) ({ *(volatile u16 *)(addr) = (val); })
> #define LOCOMO_LPT_TOFH 0x80
> #define LOCOMO_LED 0xe8
> #define LOCOMO_LPT0 0x00
>
> locomo_writel(LOCOMO_LPT_TOFH, LOCOMO_LPT0 + LOCOMO_LED);
>
> ...but that does not seem to do a trick -- it only breaks the boot :-(
Basically because you do not have access to IO during the early boot.
The easiest debugging solution is to enable CONFIG_DEBUG_LL and
throw a printascii(printk_buf) into printk.c, after vscnprintf.
That might get you some boot messages through the serial port (if
it's implemented it correctly.)
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-07-11 19:49 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 [this message]
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
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=20050711204534.C1540@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=lenz@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.