linux-csky.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Guo Ren <guoren@kernel.org>
Cc: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>,
	arnout@mind.be, linux-csky@vger.kernel.org,
	buildroot@buildroot.org, Guo Ren <ren_guo@c-sky.com>
Subject: Re: [PATCH V3 01/10] arch/csky: Use VDSP instead of DSP
Date: Wed, 29 May 2019 11:23:17 +0200	[thread overview]
Message-ID: <20190529112317.08fe1013@windsurf.home> (raw)
In-Reply-To: <CAJF2gTQfu_FAck2YM5b=d8QaYQhBHoCSeG4tvL1i8a1=7vgofA@mail.gmail.com>

Hello,

On Wed, 29 May 2019 17:02:29 +0800
Guo Ren <guoren@kernel.org> wrote:

> DSP is no use in current buildroot and gcc default enable the DSP
> feature for C-SKY.
> So DSP is part of our standard ISA, we needn't put it in -mcpu=xxx.

"DSP is no use in current Buildroot" is not correct. The option exists,
and it changes the BR2_GCC_TARGET_CPU value. So it *is* used: it adds
"e" to BR2_GCC_TARGET_CPU. So this explanation is not really
good/sufficient.

I am willing to help you formulate this properly, but since I still
don't understand why you are dropping the DSP option, I can't really
help by proposing a better wording.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2019-05-29  9:23 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-29  7:18 [PATCH V3 00/10] Update arch/csky for buildroot guoren
2019-05-29  7:18 ` [PATCH V3 01/10] arch/csky: Use VDSP instead of DSP guoren
2019-05-29  7:21   ` Thomas Petazzoni
2019-05-29  7:30     ` Guo Ren
2019-05-29  7:56       ` Thomas Petazzoni
2019-05-29  8:12         ` Guo Ren
2019-05-29  8:38           ` Thomas Petazzoni
2019-05-29  9:02             ` Guo Ren
2019-05-29  9:06               ` Guo Ren
2019-05-29  9:23               ` Thomas Petazzoni [this message]
2019-05-29  9:45                 ` Guo Ren
2019-05-29 11:58                   ` Thomas Petazzoni
2019-05-29 12:34                     ` Guo Ren
2019-05-29  7:18 ` [PATCH V3 02/10] arch/csky: Add ck860 supported guoren
2019-05-29  7:18 ` [PATCH V3 03/10] arch/csky: Add FLOAT_ABI compiler options guoren
2019-05-29  7:23   ` Thomas Petazzoni
2019-05-29  7:30     ` Guo Ren
2019-05-29  7:57       ` Thomas Petazzoni
2019-05-29  8:30         ` Guo Ren
2019-05-29  8:39           ` Thomas Petazzoni
2019-05-29  8:53             ` Guo Ren
2019-05-29  7:39     ` Guo Ren
2019-05-29  7:18 ` [PATCH V3 04/10] arch/csky: Add ABI variable for toolchain build guoren
2019-05-29  7:18 ` [PATCH V3 05/10] package/binutils: Add C-SKY support guoren
2019-05-29  7:18 ` [PATCH V3 06/10] package/gcc: " guoren
2019-05-29  7:18 ` [PATCH V3 07/10] package/gdb: " guoren
2019-05-29  7:18 ` [PATCH V3 08/10] package/glibc: " guoren
2019-05-29  7:18 ` [PATCH V3 09/10] configs/qemu_cskyXXX_virt: new defconfig guoren
2019-05-29  7:18 ` [PATCH V3 10/10] arch/csky: Enable csky toolchain build guoren

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=20190529112317.08fe1013@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --cc=arnout@mind.be \
    --cc=buildroot@buildroot.org \
    --cc=guoren@kernel.org \
    --cc=linux-csky@vger.kernel.org \
    --cc=ren_guo@c-sky.com \
    --cc=thomas.de_schampheleire@nokia.com \
    /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).