From: Romain Goyet <r.goyet@gmail.com>
Cc: OMAP Linux mailing list <linux-omap-open-source@linux.omap.com>
Subject: Re: OMAP5912 and Intel P30 Flash
Date: Fri, 2 Dec 2005 14:06:34 +0100 [thread overview]
Message-ID: <8028e5750512020506p41b7b81fk@mail.gmail.com> (raw)
In-Reply-To: <2CBB9620-2407-4313-9AE8-7222247BC0BD@capgo.com>
Hello everybody,
I'm still porting Linux to the Palm Tungsten E , and it happened that
Linux stopped working when I upgraded from 2.6.13 to 2.6.15-rc2.
My biggest problem is that this board has _no_ UART nor JTAG, so
it's _very_ difficult to debug. I managed to find out that the kernel
crashes in paging_init, but I couldn't find out why.
Could you give me any suggestions ? In particular, I would like to
know what changed in arch/arm/mm between 2.6.13 and 2.6.15, since
2.6.13 was working like a charm.
What's rather weird is that it sounds to be working OK on other
OMAP1510 devices. As the Tungsten E uses an OMAP310 which defines
IS_OMAP_15XX, I don't really understand why it doesn't work as well on
the OMAP310.
Kind regards,
Romain Goyet
next prev parent reply other threads:[~2005-12-02 13:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 6:39 OMAP5912 and Intel P30 Flash Graham Henstridge
2005-12-02 13:06 ` Romain Goyet [this message]
2005-12-02 13:07 ` Romain Goyet
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=8028e5750512020506p41b7b81fk@mail.gmail.com \
--to=r.goyet@gmail.com \
--cc=linux-omap-open-source@linux.omap.com \
/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