From: "Clément Leger" <cleger@kalray.eu>
To: Roland Hieber <rhi@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH 0/5] Add support for Kalray k1c core
Date: Thu, 16 Jan 2020 10:53:31 +0100 (CET) [thread overview]
Message-ID: <1874850414.12533097.1579168411117.JavaMail.zimbra@kalray.eu> (raw)
In-Reply-To: <20200116094919.4zqv43u2u4mdsw2k@pengutronix.de>
Hi Roland,
----- On 16 Jan, 2020, at 10:49, Roland Hieber rhi@pengutronix.de wrote:
> On Wed, Jan 15, 2020 at 11:26:45AM +0100, Clement Leger wrote:
>> Kalray k1c core is embedded in Kalray Coolidge SoC. This core has the
>> following features:
>> - 32/64 bits
>> - 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. k1c 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.
>>
>> Kalray uses FOSS which is available at https://github.com/kalray
>>
>> Clement Leger (5):
>> k1c: Initial Kalray Coolidge (k1c) architecture support
>> k1c: Add processor definitions
>> k1c: Add support for device tree
>> clocksource: k1c: Add k1c clocksource support
>> watchdog: k1c: Add k1c watchdog support
>
> Uuuh, a shiny new architecture! You might also want to add some
> (minimal) documentation in Documentation/boards/ to advertise it. This
> way it will also appear on
> https://www.barebox.org/doc/latest/boards.html :)
Nice, thanks for the info !
Clément
>
> - Roland
>
> --
> Roland Hieber, Pengutronix e.K. | r.hieber@pengutronix.de |
> Steuerwalder Str. 21 | https://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
prev parent reply other threads:[~2020-01-16 9:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 10:26 Clement Leger
2020-01-15 10:26 ` [PATCH 1/5] k1c: Initial Kalray Coolidge (k1c) architecture support Clement Leger
2020-01-16 9:26 ` Sascha Hauer
2020-01-16 10:49 ` Clément Leger
2020-01-16 10:55 ` Sascha Hauer
2020-01-16 12:24 ` Clément Leger
2020-01-16 13:11 ` Sascha Hauer
2020-01-16 13:26 ` Clément Leger
2020-01-16 13:34 ` Sascha Hauer
2020-01-15 10:26 ` [PATCH 2/5] k1c: Add processor definitions Clement Leger
2020-01-15 10:26 ` [PATCH 3/5] k1c: Add support for device tree Clement Leger
2020-01-15 10:26 ` [PATCH 4/5] clocksource: k1c: Add k1c clocksource support Clement Leger
2020-01-15 10:26 ` [PATCH 5/5] watchdog: k1c: Add k1c watchdog support Clement Leger
2020-01-20 15:10 ` Ahmad Fatoum
2020-01-20 16:08 ` Clément Leger
2020-01-16 8:25 ` [PATCH 0/5] Add support for Kalray k1c core Sascha Hauer
2020-01-16 8:53 ` Clément Leger
2020-01-16 9:22 ` Sascha Hauer
2020-01-16 9:37 ` Clément Leger
2020-01-16 9:46 ` Sascha Hauer
2020-01-16 9:49 ` Roland Hieber
2020-01-16 9:53 ` 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=1874850414.12533097.1579168411117.JavaMail.zimbra@kalray.eu \
--to=cleger@kalray.eu \
--cc=barebox@lists.infradead.org \
--cc=rhi@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