public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [MIPS] Convert CPU type name into CONFIG_CPU_*
Date: Sat, 24 May 2008 22:09:08 +0200	[thread overview]
Message-ID: <20080524200908.593BC247F5@gemini.denx.de> (raw)
In-Reply-To: Your message of "Sat, 24 May 2008 22:43:08 +0900." <48381B6C.5000901@ruby.dti.ne.jp>

In message <48381B6C.5000901@ruby.dti.ne.jp> you wrote:
> Adjust to the current Linux way.
> 
> Signed-off-by: Shinya Kuribayashi <skuribay@ruby.dti.ne.jp>
...
> -#define CONFIG_MIPS32		1  /* MIPS32 CPU core	*/
> +#define CONFIG_CPU_MIPS32_R1	1  /* MIPS32 CPU core	*/

I have to admit that I don't like this changes.

We're adding a lot of fine ganularity here, and we pay for this with
added memory footprint - but I fail to see any significant benefits
from this.

What exactly is the reason for all these changes? Which problem are
you trying to fix?

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
What the gods would destroy they first submit to  an  IEEE  standards
committee.

  reply	other threads:[~2008-05-24 20:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-24 13:43 [U-Boot-Users] [MIPS] Convert CPU type name into CONFIG_CPU_* Shinya Kuribayashi
2008-05-24 20:09 ` Wolfgang Denk [this message]
2008-05-25 15:15   ` Shinya Kuribayashi
2008-05-25 15:35     ` Wolfgang Denk
2008-05-31  5:32       ` Shinya Kuribayashi
2008-07-05 22:32         ` Wolfgang Denk
2008-07-06  3:17           ` Shinya Kuribayashi

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=20080524200908.593BC247F5@gemini.denx.de \
    --to=wd@denx.de \
    --cc=u-boot@lists.denx.de \
    /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