From: Grant Likely <grant.likely@secretlab.ca>
To: Thomas Maenner <tmaenner@aehr.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Need stable 2.6 kernel for TQM823L
Date: Wed, 2 Jul 2008 23:58:19 -0600 [thread overview]
Message-ID: <20080703055819.GB643@secretlab.ca> (raw)
In-Reply-To: <200807021418.13596.tmaenner@aehr.com>
On Wed, Jul 02, 2008 at 02:18:13PM -0700, Thomas Maenner wrote:
> Hi Guys,
>
> I have used the 2.4 kernel successfully on the TQM823L and 855s, and wanted to
> try out a 2.6 version. So I downloaded the latest from Wolfgang @ git.denx.de
> but I'm getting all sorts of compile errors....
>
> Before I continue to dive in, I wanted to ask the group some questions:
> - Is 2.6 ported to the TQM8xx modules?
$ ls arch/powerpc/boot/dts/tqm*
arch/powerpc/boot/dts/tqm5200.dts arch/powerpc/boot/dts/tqm8555.dts
arch/powerpc/boot/dts/tqm8540.dts arch/powerpc/boot/dts/tqm8560.dts
arch/powerpc/boot/dts/tqm8541.dts
Unfortunately, it doesn't look like any of the tqm8xx boards have been
added to the device tree directory, so the answer is probably, 'no'.
> - If so, is it stable?
I believe 8xx support is stable in arch/powerpc, but you'll need to
write a device tree file for the board. Look for a similar board in
arch/powerpc/boot/dts/ to use as a starting point.
You'll probably also need to add a platform file to arch/powerpc/platforms/8xx
that matches against your new device tree file.
g.
next prev parent reply other threads:[~2008-07-03 5:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 21:18 Need stable 2.6 kernel for TQM823L Thomas Maenner
2008-07-03 5:58 ` Grant Likely [this message]
2008-07-03 18:59 ` Thomas Maenner
2008-07-03 19:04 ` Grant Likely
2008-07-04 1:39 ` Thomas Maenner
2008-07-04 8:10 ` Stefan Roese
2008-07-04 10:12 ` Jochen Friedrich
2008-07-22 23:27 ` 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=20080703055819.GB643@secretlab.ca \
--to=grant.likely@secretlab.ca \
--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 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.