From: Andrey Volkov <avolkov@varma-el.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: [RFC] Remove G2_LE core decl from CLASSIC_PPC part of arch/ppc/kernel/cputable.c
Date: Fri, 27 Aug 2004 15:34:54 +0400 [thread overview]
Message-ID: <927068331.20040827153454@varma-el.com> (raw)
Hello all,
Since G2_LE is NOT a "classic" core ( in particular - true little-endian),
may be now is time to remove it from CLASSIC_PPC part of
arch/ppc/kernel/cputable.c, and move it to itself part.
I bear in mind next:
from arch/ppc/kernel/cputable.c:
#if CLASSIC_PPC
.....
{ /* All G2_LE (603e core, plus some) have the same pvr */
0x7fff0000, 0x00820000, "G2_LE",
CPU_FTR_SPLIT_ID_CACHE | CPU_FTR_CAN_DOZE | CPU_FTR_USE_TB |
CPU_FTR_CAN_NAP | CPU_FTR_HAS_HIGH_BATS,
COMMON_PPC,
32, 32,
__setup_cpu_603
},
....
#endif /* CLASSIC_PPC */
May be better like this:
#if CONFIG_G2_LE
{ /* All G2_LE (603e core, plus some) have the same pvr */
0x7fff0000, 0x00820000, "G2_LE",
CPU_FTR_SPLIT_ID_CACHE | CPU_FTR_CAN_DOZE | CPU_FTR_USE_TB |
CPU_FTR_CAN_NAP | CPU_FTR_HAS_HIGH_BATS,
COMMON_PPC,
32, 32,
__setup_cpu_603
},
#endif
With that move we'll conserve some memory of kernel,
but need some explanations which PPCs based on
it, for modify Kconfig ( I know MPC52xx and MPC82xx based on it).
--
Best regards,
Andrey Volkov
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-08-27 11:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 11:34 Andrey Volkov [this message]
2004-08-27 14:15 ` [RFC] Remove G2_LE core decl from CLASSIC_PPC part of arch/ppc/kernel/cputable.c Kumar Gala
2004-08-27 15:00 ` Re[2]: " Andrey Volkov
2004-08-27 15:00 ` Dan Malek
2004-08-27 15:16 ` Re[2]: " Andrey Volkov
2004-08-27 17:49 ` 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=927068331.20040827153454@varma-el.com \
--to=avolkov@varma-el.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).