public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: lenz@cs.wisc.edu, kernel list <linux-kernel@vger.kernel.org>
Cc: Hamera Erik <HAMERAE@cs.felk.cvut.cz>
Subject: Re: arm: how to operate leds on zaurus?
Date: Mon, 11 Jul 2005 21:50:59 +0200	[thread overview]
Message-ID: <20050711195059.GA2219@elf.ucw.cz> (raw)
In-Reply-To: <20050711204534.C1540@flint.arm.linux.org.uk>

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.)

I'm afraid I do not have serial cable :-(. I'll try to get one [erik,
do you have one you don't need?], but zaurus has "little" nonstandard
connector.

Would code above work if executed later?
								Pavel
-- 
teflon -- maybe it is a trademark, but it should not be.

  reply	other threads:[~2005-07-11 19:58 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 [this message]
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=20050711195059.GA2219@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=HAMERAE@cs.felk.cvut.cz \
    --cc=lenz@cs.wisc.edu \
    --cc=linux-kernel@vger.kernel.org \
    /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