From: Shinya Kuribayashi <skuribay@ruby.dti.ne.jp>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [MIPS] Convert CPU type name into CONFIG_CPU_*
Date: Sun, 06 Jul 2008 12:17:32 +0900 [thread overview]
Message-ID: <4870394C.80809@ruby.dti.ne.jp> (raw)
In-Reply-To: <20080705223202.57AD0248DE@gemini.denx.de>
Wolfgang Denk wrote:
> In message <4840E304.7090702@ruby.dti.ne.jp> you wrote:
>>> Well, yes - if it's for compiler/assembler options only, then the
>>> board config file is not the correct place for this.
>> I don't think so because 1) CPU type is not board-dependent, and 2) the
>> board config file is not board-specific file, but system config file.
>> CPU type is reasonably one of system configuration, IMO.
>
> I cannot follow you here. Especially I have no idea what you mean by
> "system config file".
>
> To make sure we use the same terms: THe "board config file" is the
> board specific header file "include/configs/<boardname>.h". This file
> is definitely NOT the correct place to tweak compiler and/or assembler
> options (not to mention that I don't see how this would be done).
>
> I _guess_ you might be referring to the cpu/*/config.mk files, but
> then the term "_board_ config file" is wrong.
Sorry for confusion. I see all the aboves.
>> P.S. I decided to defer this patch due to some reason. That's another
>> story and will inform the list later.
>
> Since I haven't heard again about this I assume this is for the next
> merge window (or even later). Is this assumption correct,
Correct.
Shinya
prev parent reply other threads:[~2008-07-06 3:17 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
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 [this message]
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=4870394C.80809@ruby.dti.ne.jp \
--to=skuribay@ruby.dti.ne.jp \
--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 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.