From: Scott Wood <scottwood@freescale.com>
To: raul.moreno@telvent.abengoa.com
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: 2.6.22-ppc8xx fec.c bugs
Date: Fri, 11 Jan 2008 11:27:58 -0600 [thread overview]
Message-ID: <4787A71E.7000509@freescale.com> (raw)
In-Reply-To: <OF431AD1B5.8B0529FD-ONC12573CD.002EB1C5-C12573CD.0030B37E@abengoa.com>
raul.moreno@telvent.abengoa.com wrote:
> I didn't know ppc was deprecated. Why is it so?
Having separate 32 and 64 bit powerpc trees was a maintenance headache.
The way arch/ppc is structured was a maintenance headache.
> I have been using this architecture since I started with Linux (not too
> long ago) because I manage a mpc866 processor.
mpc866 chips are supported in arch/powerpc.
> Do you mean that I should port to arch/powerpc?
Yes.
-Scott
prev parent reply other threads:[~2008-01-11 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 16:33 kernel panic after upgrading to 2.6.22 raul.moreno
2008-01-10 15:57 ` 2.6.22-ppc8xx fec.c bugs raul.moreno
2008-01-10 17:48 ` Scott Wood
2008-01-11 8:51 ` raul.moreno
2008-01-11 17:27 ` Scott Wood [this message]
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=4787A71E.7000509@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=raul.moreno@telvent.abengoa.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).