Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] configs/csky_gx6605s: bump kernel to 5.0 and use buildroot toolchain
Date: Mon, 24 Jun 2019 05:52:07 +0200	[thread overview]
Message-ID: <20190624055207.59b0c7bf@windsurf> (raw)
In-Reply-To: <1561347693-16089-1-git-send-email-guoren@kernel.org>

Hello,

On Mon, 24 Jun 2019 11:41:33 +0800
guoren at kernel.org wrote:

> From: Guo Ren <ren_guo@c-sky.com>
> 
> The most thing is to use the toolchain compiled by buildroot itself. And
> we also bump kernel to 5.0 with kernel.org.
> 
> For all 610s including qemu we use 0x10000000 PHYS_OFFSET for unified
> maintain.

I'm not sure what you mean by "unified maintain". How does it matter,
considering that the Buildroot defconfig is anyway for one single
platform ?

> There is no gx6605s.dts for the config, so we need wget it from
> csky gitlab CI storage.

Meh, this is not great. Is the Gitlab CI URL really permanent? Jobs
artifacts are usually removed after a configurable time, isn't it the
case as well for this artifact ?

Also, why isn't this .dts not submitted to the upstream Linux kernel ?

Overall, I think I would prefer to see a patch to the Linux kernel in
board/csky/ rather than downloading a random .dtb. Or just have
the .dts file directly in board/csky/.

For the record, DT is not about "config", it's about describing the
hardware. You might give the DT kernel maintainers a heart attack if
you call the DT "configuration"! :-)

Thanks,

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

  reply	other threads:[~2019-06-24  3:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-24  3:41 [Buildroot] [PATCH] configs/csky_gx6605s: bump kernel to 5.0 and use buildroot toolchain guoren at kernel.org
2019-06-24  3:52 ` Thomas Petazzoni [this message]
2019-06-24  5:57   ` Guo Ren

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=20190624055207.59b0c7bf@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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