From: Andrey Volkov <avolkov@varma-el.com>
To: Dan Malek <dan@embeddededge.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re[2]: [RFC] Remove G2_LE core decl from CLASSIC_PPC part of arch/ppc/kernel/cputable.c
Date: Fri, 27 Aug 2004 19:16:42 +0400 [thread overview]
Message-ID: <314790494.20040827191642@varma-el.com> (raw)
In-Reply-To: <E832C827-F839-11D8-BF10-003065F9B7DC@embeddededge.com>
Hello Dan,
Friday, August 27, 2004, 7:00:59 PM, you wrote:
>> Since G2_LE is NOT a "classic" core ( in particular - true
>> little-endian),
> How is it not a classic core? It certainly isn't bookE, and it isn't
> 8xx.
> No one should care about little-endian anyway. I'm voting for the
> first candidate that makes that illegal. :-)
Agree.
>> With that move we'll conserve some memory of kernel,
> How does this single change save anything but a few bytes of
> cpu table?
Maybe ~2K of rubbish for somebody "few" - for me not :) (don't forget
its embedded platform).
>> but need some explanations which PPCs based on
>> it, for modify Kconfig ( I know MPC52xx and MPC82xx based on it).
> What other kernel changes would you make based on
> this configuration?
Only Kconfig, nothing more.
--
Best regards,
Andrey Volkov
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-08-27 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 11:34 [RFC] Remove G2_LE core decl from CLASSIC_PPC part of arch/ppc/kernel/cputable.c Andrey Volkov
2004-08-27 14:15 ` Kumar Gala
2004-08-27 15:00 ` Re[2]: " Andrey Volkov
2004-08-27 15:00 ` Dan Malek
2004-08-27 15:16 ` Andrey Volkov [this message]
2004-08-27 17:49 ` Re[2]: " 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=314790494.20040827191642@varma-el.com \
--to=avolkov@varma-el.com \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.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).