From: "Clément Leger" <cleger@kalrayinc.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH v2 0/6] Add support for Kalray VLIW family (kvx)
Date: Wed, 15 Apr 2020 11:33:16 +0200 (CEST) [thread overview]
Message-ID: <263361615.15494471.1586943196981.JavaMail.zimbra@kalray.eu> (raw)
In-Reply-To: <187139593.15433138.1586934185883.JavaMail.zimbra@kalray.eu>
Hi Sascha,
We updated the gcc, binutils and newlib earlier to allow building a kvx
toolchain. An official release with pre-built toolchain will be available
in a few days [1]. In the meantime, you can use the following command to
build the toolchain:
export SHA1_GCC=f6f2785ba66afb5b80e17e5409060061781d7ee4
export SHA1_GDB=3aacfa058a0fe41705f67f18a54b8da3733be4ad
export SHA1_NEWLIB=bf737d4d0e0eb0df50ab6ecda7b48bde1dc1aea6
./build-k1-xgcc.sh <prefix_dir>
Be sure to pull the latest master from build-script to allow building a kvx
toolchain (plus some fixes).
Sorry for the inconvenience,
Clément
[1] https://github.com/kalray/build-scripts/releases
----- On 15 Apr, 2020, at 09:03, Clément Leger cleger@kalrayinc.com wrote:
> Hi Sascha,
>
> Since we did a massive renaming to change from k1->kvx, the tools have not
> yet been pushed on github (we only push releases yet). We will update it
> soon and I will keep you updated.
>
> Sorry for the documentation, I forgot to addressed Ahmad comment. I will do it.
>
> Thanks,
>
> Clément
>
> ----- On 15 Apr, 2020, at 08:55, Sascha Hauer s.hauer@pengutronix.de wrote:
>
>> Hi Clement,
>>
>> On Sat, Apr 04, 2020 at 10:29:04PM +0200, Clement Leger wrote:
>>> Kalray kv3 core is embedded in Kalray Coolidge SoC. This core which is the
>>> third of the KV family has the following features:
>>> - 32/64 bits execution mode
>>> - 6-issue VLIW architecture
>>> - 64 x 64bits general purpose registers
>>> - SIMD instructions
>>> - little-endian
>>>
>>> This port is a 64 bits one and allows to boot up to a barebox prompt on a k200
>>> board. kv3 support for clocksource and watchdog is also part of this port.
>>>
>>> In order to build a usable toolchain, build scripts are provided at the
>>> following address: https://github.com/kalray/build-scripts.
>>
>> I merged the series with the comments I made to the timer driver. I am
>> currently on my way trying the toolchain build scripts. If this
>> succeeds I can add the coolidge support to my defconfig builds.
>>
>> It would be nice if you could add a few words to
>> Documentation/boards/coolidge.rst to let the user know what this is all
>> about.
>>
>> Sascha
>>
>> --
>> Pengutronix e.K. | |
>> Steuerwalder Str. 21 | http://www.pengutronix.de/ |
>> 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
>> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2020-04-15 9:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-04 20:29 Clement Leger
2020-04-04 20:29 ` [PATCH v2 1/6] kvx: Initial Kalray Coolidge (kv3) architecture support Clement Leger
2020-04-04 20:29 ` [PATCH v2 2/6] kvx: Add processor definitions Clement Leger
2020-04-04 20:29 ` [PATCH v2 3/6] kvx: Add support for device tree Clement Leger
2020-04-04 20:29 ` [PATCH v2 4/6] kvx: Implement reset source and reset Clement Leger
2020-04-04 20:29 ` [PATCH v2 5/6] clocksource: kvx: Add kvx clocksource support Clement Leger
2020-04-14 12:59 ` Sascha Hauer
2020-04-04 20:29 ` [PATCH v2 6/6] watchdog: kvx: Add kvx watchdog support Clement Leger
2020-04-15 6:55 ` [PATCH v2 0/6] Add support for Kalray VLIW family (kvx) Sascha Hauer
2020-04-15 7:03 ` Clément Leger
2020-04-15 9:33 ` Clément Leger [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=263361615.15494471.1586943196981.JavaMail.zimbra@kalray.eu \
--to=cleger@kalrayinc.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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