From: Randy Dunlap <rdunlap@infradead.org>
To: bcain@codeaurora.org, 'Arnd Bergmann' <arnd@kernel.org>
Cc: 'Nick Desaulniers' <ndesaulniers@google.com>,
"'open list:QUALCOMM HEXAGON...'" <linux-hexagon@vger.kernel.org>,
'clang-built-linux' <clang-built-linux@googlegroups.com>,
'linux-arch' <linux-arch@vger.kernel.org>,
'Guenter Roeck' <linux@roeck-us.net>
Subject: Re: ARCH=hexagon unsupported?
Date: Fri, 23 Apr 2021 14:47:27 -0700 [thread overview]
Message-ID: <24da08a4-e055-d8ac-8214-97d86cdcfd3d@infradead.org> (raw)
In-Reply-To: <027401d7387e$f5630120$e0290360$@codeaurora.org>
On 4/23/21 1:26 PM, Brian Cain wrote:
>> -----Original Message-----
>> From: bcain=codeaurora.org@codeaurora.org
> ...
>> There is a hexagon cross toolchain used for testing QEMU (userspace) guest
>> code test cases. This same toolchain can be used to build the kernel. I will
>> share a reference to that toolchain, standby.
>
> It's published as a container in the Gitlab Container Registry. You can use docker/podman to pull "registry.gitlab.com/qemu-project/qemu/qemu/debian-hexagon-cross" in order to use it.
Hi Brian,
Maybe that will be useful to someone.
However, I am looking for something like a tarball that I can download
and deploy locally, like one can find at these locations:
https://toolchains.bootlin.com/
https://download.01.org/0day-ci/cross-package/
https://mirrors.edge.kernel.org/pub/tools/crosstool/
thanks.
--
~Randy
next prev parent reply other threads:[~2021-04-23 21:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 22:12 ARCH=hexagon unsupported? Nick Desaulniers
2021-04-23 9:36 ` Arnd Bergmann
2021-04-23 17:43 ` Randy Dunlap
2021-04-23 18:17 ` Arnd Bergmann
2021-04-23 18:26 ` Miguel Ojeda
2021-04-23 19:31 ` Brian Cain
2021-04-23 20:26 ` Brian Cain
2021-04-23 21:47 ` Randy Dunlap [this message]
2021-04-23 22:25 ` Brian Cain
2021-04-23 22:26 ` Randy Dunlap
2021-05-19 15:28 ` Brian Cain
2021-04-23 18:35 ` Brian Cain
2021-04-23 21:40 ` Nick Desaulniers
2021-04-26 13:13 ` Brian Cain
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=24da08a4-e055-d8ac-8214-97d86cdcfd3d@infradead.org \
--to=rdunlap@infradead.org \
--cc=arnd@kernel.org \
--cc=bcain@codeaurora.org \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=ndesaulniers@google.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).