From: Dirk Behme <dirk.behme@googlemail.com>
To: Philip Balister <philip@balister.org>,
OMAP <Linux-omap-open-source@linux.omap.com>
Subject: Re: Recent git kernels and OSK
Date: Tue, 03 Oct 2006 17:24:21 +0200 [thread overview]
Message-ID: <452280A5.5080805@gmail.com> (raw)
In-Reply-To: <45226BC5.9050201@gmail.com>
Dirk Behme wrote:
> Philip Balister wrote:
...
>> Has anyone successfully booted a recent git kernel on the OSK?
...
> Just checked it. Seems that recent git on OSK is really broken. Enabling
> lowlevel debug last thing I get is kernel command line output [3]. On my
> last working kernel next output would be clock stuff [2]
> Any ideas?
Seems to me that it hangs in arch/arm/mach-omap1/clock.c in
omap1_clk_init in
...
/* USB_REQ_EN will be disabled later if necessary (usb_dc_ck) */
reg = omap_readw(SOFT_REQ_REG) & (1 << 4);
omap_writew(reg, SOFT_REQ_REG);
if (!cpu_is_omap15xx())
omap_writew(0, SOFT_REQ_REG2);
...
If I remove "omap_writew(reg, SOFT_REQ_REG);" in code above
it goes on booting but then crashes later in clk_disable()
(as the comment above implies ;) ):
...
Initializing OMAP McBSP system
<6>omap_dsp_init() done
USB: hmc 16, usb0 2 wires
<6>i2c_omap i2c_omap.1: bus 0 rev2.2 at 100 kHz
<2>kernel BUG at arch/arm/plat-omap/clock.c:138!
<1>Unable to handle kernel NULL pointer dereference at
virtual address 00000000
...
If I'm correct here (not sure, can anybody reproduce this?)
I really wonder why it may hang in (unchanged) write access
to SOFT_REQ_REG?
Again, any ideas?
Cheers
Dirk
next prev parent reply other threads:[~2006-10-03 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-02 22:35 Recent git kernels and OSK Philip Balister
2006-10-02 23:29 ` David Brownell
2006-10-03 13:55 ` Dirk Behme
2006-10-03 15:24 ` Dirk Behme [this message]
2006-10-04 9:03 ` Dirk Behme
[not found] ` <4523892B.3000505@balister.org>
2006-10-04 13:27 ` Dirk Behme
2006-10-06 9:58 ` Dirk Behme
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=452280A5.5080805@gmail.com \
--to=dirk.behme@googlemail.com \
--cc=Linux-omap-open-source@linux.omap.com \
--cc=philip@balister.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 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.