From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Setting Defaults for RISCV64 Architecture
Date: Tue, 14 Aug 2018 15:05:54 +0200 [thread overview]
Message-ID: <20180814150554.3fdc4fd0@windsurf> (raw)
In-Reply-To: <29a7876d-c734-e09c-4e60-8d62e08c7775@embecosm.com>
Hello,
On Tue, 14 Aug 2018 13:35:37 +0100, Mark Corbin wrote:
> > For the Linux kernel itself, there isn't really a problem, as we allow
> > the user to select the Linux kernel version/source with lots of freedom
> > (arbitrary official version from kernel.org, arbitrary commit/tag from
> > a Git repository, arbitrary tarball, etc.).
> I know that the options are pretty flexible,? but is there a good way to
> preselect the correct version for riscv64? At the moment the default is
> 'Latest version (4.17)' and the user would have to go and reconfigure
> this by hand to point at the custom git repo.
Nope, for the Linux kernel source code, I don't think we want to add
architecture-specific default versions. Just leave it to the user to
know which version to build. It's already something a user has to do on
other architectures as well: the vanilla v4.17 is not always the right
choice for a given HW platform.
> > However, there is a problem for the kernel headers. If the recently
> > released 4.18 kernel still doesn't have what's need for RISCV64, then I
> > guess we'll have to temporarily add a special Linux kernel headers
> > version in package/linux-headers/Config.in.host for RISCV64.
> Is this for building the toolchain?
Yes, this is for building the toolchain.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-08-14 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 9:39 [Buildroot] Setting Defaults for RISCV64 Architecture Mark Corbin
2018-08-14 12:03 ` Thomas Petazzoni
2018-08-14 12:35 ` Mark Corbin
2018-08-14 13:05 ` Thomas Petazzoni [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=20180814150554.3fdc4fd0@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 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.