From: Wolfgang Denk <wd@denx.de>
To: Thomas Maenner <tmaenner@aehr.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: TQM 860L, 64MB RAM, ELDK4.1, TQM860L, Kernel 2.6.19
Date: Thu, 22 Mar 2007 22:26:15 +0100 [thread overview]
Message-ID: <20070322212615.553FE35260B@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 22 Mar 2007 14:10:37 MST." <200703221410.37767.tmaenner@aehr.com>
In message <200703221410.37767.tmaenner@aehr.com> you wrote:
> Tried out the following u-boot "setting":
> setenv ramargs setenv bootargs ramdisk_size=6144 root=/dev/ram console=ttyCPM0 rw
>
> No change; still no output in the console
Then buy a debugger and dig into it...
> Note that my module has 64MB, rather that 16; I thought it doesn't matter, or?
It doesn't.
You are aware that TQM8xxL is not yet supported in the context of the
2.6 Linux kernel, aren't you? [And we will not support it in the
ARCH=ppc context any more.]
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
Office: Kirchenstr. 5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
We are all agreed that your theory is crazy. The question which
divides us is whether it is crazy enough to have a chance of being
correct. My own feeling is that it is not crazy enough. - Niels Bohr
next prev parent reply other threads:[~2007-03-22 21:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 3:44 TQM 860L, 64MB RAM, ELDK4.1, TQM860L, Kernel 2.6.19 Thomas Maenner
2007-03-22 7:40 ` Wolfgang Denk
2007-03-22 15:01 ` Thomas Maenner
2007-03-22 21:10 ` Thomas Maenner
2007-03-22 21:26 ` Wolfgang Denk [this message]
2007-03-23 11:19 ` Ralph Hempel
2007-03-23 13:27 ` Wolfgang Denk
2007-03-23 17:29 ` Thomas Maenner
2007-03-25 19:35 ` Wolfgang Denk
2007-03-23 17:26 ` Thomas Maenner
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=20070322212615.553FE35260B@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@ozlabs.org \
--cc=tmaenner@aehr.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;
as well as URLs for NNTP newsgroup(s).