From: "Alexey Dyatchkov" <alexey@waves.com>
To: <linuxppc-embedded@ozlabs.org>
Cc: 'Ami Levi' <ami@waves.com>
Subject: Denx linux 2.4.25 on RPXLITE
Date: Wed, 16 Nov 2005 13:14:28 +0200 [thread overview]
Message-ID: <001f01c5ea9e$ea775a70$0100000a@Omerxp> (raw)
[-- Attachment #1: Type: text/plain, Size: 625 bytes --]
Hi,
I'm trying to bring up Denx linux-2.4.25, latest found on
ftp.denx.de/pub/linux, on our proprietary board.
Our board is very much similar to RPXLITE. In fact it is RPXLITE with few
minor changes.
We did such works before, and all we usualy needed was to tune the io
mapping.
I did so with this kernel and it stucks in calibrate_delay() on "while
(ticks==jiffies)", row 207.
And it seems that no interrupts are coming to kernel (breakpoint in do_irq
is never achieved).
(No printk's on console, btw)
I'm not experienced enough in kernel debugging and feel stuck.
Please help!
Thanks in advance,
Alexey
[-- Attachment #2: Type: text/html, Size: 4276 bytes --]
reply other threads:[~2005-11-16 11:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='001f01c5ea9e$ea775a70$0100000a@Omerxp' \
--to=alexey@waves.com \
--cc=ami@waves.com \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).