linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Volkov <avolkov@varma-el.com>
To: Kumar Gala <kumar.gala@freescale.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:00:21 +0400	[thread overview]
Message-ID: <1441098375.20040827190021@varma-el.com> (raw)
In-Reply-To: <87957638-F833-11D8-994C-000393DBC2E8@freescale.com>


Hello Kumar,

Friday, August 27, 2004, 6:15:20 PM, you wrote:

> What purpose does this change really serve.  Linux does not use the
> true little-endian feature of the G2_LE core, beyond that it is very
> much in the class of classic ppc.
> Is the memory savings really that much?

sizeof(*cpu_table) ~ 1300 bytes
+ code in cpu_setup_6xx.S ~ 1000 bytes
+ more simple to filter out some features in Kconfig (ex. SMP,
ALTIVEC...)

And optionally (?):
+ LE (if it will be needed sometime for somebody)
+ "An additional input interrupt signal, core_cint,
   implements a critical interrupt function."

>>
>> 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/

  reply	other threads:[~2004-08-27 15:00 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   ` Andrey Volkov [this message]
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=1441098375.20040827190021@varma-el.com \
    --to=avolkov@varma-el.com \
    --cc=kumar.gala@freescale.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).