linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Karim Yaghmour <karim@opersys.com>
To: linuxppc-embedded@ozlabs.org
Subject: 2.6.x with TQM860L
Date: Mon, 11 Apr 2005 00:16:09 -0400	[thread overview]
Message-ID: <4259FA09.8040508@opersys.com> (raw)


I've been trying to get a 2.6.x kernel working with a TQM860L board
with little success. I can get 2.6.11.6 to boot and _sometimes_ get
to a shell, but most of the times it dies while starting init. From
reading the archives, this looks very much like an SDRAM config issue
(i.e. dies mostly when bursting.) Has anyone on this list got a
2.6.x kernel working with the TQM860L?

Thanks,

Karim
-- 
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 1-866-677-4546

             reply	other threads:[~2005-04-11  4:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-11  4:16 Karim Yaghmour [this message]
2005-04-11  6:08 ` 2.6.x with TQM860L Pantelis Antoniou
2005-04-21 17:13   ` Karim Yaghmour
2005-04-11  7:24 ` Wolfgang Denk
2005-04-21 17:17   ` Karim Yaghmour

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=4259FA09.8040508@opersys.com \
    --to=karim@opersys.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).