From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Cc: Kumar Gala <galak@gate.crashing.org>, Paul Mackerras <paulus@samba.org>
Subject: FSL vs. IBM BookE
Date: Sat, 04 Nov 2006 20:21:54 +1100 [thread overview]
Message-ID: <1162632114.28571.33.camel@localhost.localdomain> (raw)
Out of curiosity... I noticed we have both head_44x.S and
head_fsl_booke.S, the later being a fork of the former with changed from
Kumar (and possibly others) to support E200 and E500.
How bad are the differences between those cores ? Would it be possible
to reconcile those and IBM 44x into a single processor family ? Or are
there some fundamental differences making that impossible ? (even with a
bit of CPU feature patching).
Also, I suppose we should rename head_4xx.S to head_40x.S no ?
Cheers,
Ben.
next reply other threads:[~2006-11-04 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-04 9:21 Benjamin Herrenschmidt [this message]
2006-11-04 16:16 ` FSL vs. IBM BookE Josh Boyer
2006-11-04 16:56 ` Kumar Gala
2006-11-04 17:24 ` Dan Malek
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=1162632114.28571.33.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=galak@gate.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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 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.