linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Akira Tsukamoto <akira.tsukamoto@gmail.com>
To: "Paul Walmsley" <paul.walmsley@sifive.com>,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	"Albert Ou" <aou@eecs.berkeley.edu>,
	"Atish Patra" <atish.patra@wdc.com>,
	"Anup Patel" <anup.patel@wdc.com>,
	"Emil Renner Berthing" <kernel@esmil.dk>,
	"Björn Töpel" <bjorn@kernel.org>,
	"Akira Tsukamoto" <akira.tsukamoto@gmail.com>,
	"Sagar Shrikant Kadam" <sagar.kadam@sifive.com>,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH 0/1] Adding jh7100 SoC to defconfig
Date: Wed, 23 Jun 2021 21:45:52 +0900	[thread overview]
Message-ID: <f22f6d7e-97ab-85db-5448-c2bcef0ea0e7@gmail.com> (raw)


Would like to have comments for adding jh7100 SoC to defconfig.

To make the upstream friendly, try to add as minimum as possible in
arch/riscv/configs/defconfig required for beaglev-beta against the
upstream defconfig. I might have added too much configs.

Then the distro vendors could use:
make defconfig beablev-fedora.config
or
make defconfig beablev-debian.config

while distro vendors keeping beablev-fedora.config and
beablev-debian.config in their own repositories to make one binary kernel
which boots for all riscv boards.

Probably, it is not good practice to add a different defconfig file under
arch/riscv/configs/ when each new riscv board comes out.

Akira Tsukamoto (1):
  config: Enable jh7100 SoC

 arch/riscv/configs/defconfig | 105 +++++++++++++++++++++++++++++++++++
 1 file changed, 105 insertions(+)

-- 
2.17.1


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

             reply	other threads:[~2021-06-23 12:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-23 12:45 Akira Tsukamoto [this message]
2021-06-23 12:46 ` [PATCH 1/1] config: Enable jh7100 SoC Akira Tsukamoto
2021-06-23 13:21   ` Jisheng Zhang
2021-06-24 14:35     ` Akira Tsukamoto
2021-06-23 19:08   ` Drew Fustini
2021-06-24 14:49     ` Akira Tsukamoto
2021-06-23 18:50 ` [RFC PATCH 0/1] Adding jh7100 SoC to defconfig Drew Fustini
2021-06-24 14:42   ` Akira Tsukamoto

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=f22f6d7e-97ab-85db-5448-c2bcef0ea0e7@gmail.com \
    --to=akira.tsukamoto@gmail.com \
    --cc=anup.patel@wdc.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=atish.patra@wdc.com \
    --cc=bjorn@kernel.org \
    --cc=kernel@esmil.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=sagar.kadam@sifive.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).