From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] board: add support for ARC HS Development Kit (HSDK)
Date: Mon, 19 Feb 2018 07:56:46 +0000 [thread overview]
Message-ID: <1519027005.14718.2.camel@synopsys.com> (raw)
In-Reply-To: <1517993000.5728.8.camel@synopsys.com>
Hi gents,
Most probably this thread somehow slipped through the cracks...
I guess that's already too late for 2018.02 as we're on RC2 already :(
But anyways is there a chance to review/comment on this one?
-Alexey
On Wed, 2018-02-07 at 09:43 +0100, Alexey Brodkin wrote:
> Hi Thomas, Peter, Arnout,
>
> On Wed, 2018-01-31 at 10:58 +0300, Alexey Brodkin wrote:
> > Hello,
> >
> > On Tue, 2017-12-19 at 17:55 +0300, Evgeniy Didin wrote:
> > > Synopsys DesignWare HSDK (which stands for ARC HS
> > > Development Kit) is the latest and greatest development
> > > platform that sports quad-core ARC HS38 in real silicon.
> > >
> > > Most noticeable features of the board are:
> > > * Quad-core ARC HS38 CPU running at 1GHz
> > > * 4Gb of DDR
> > > * Built-in Vivante GPU (well supported via open source
> > > Etnaviv drivers)
> > > * Built-in Wi-Fi/Bluetooth module (RedPine RS-9113)
> > >
> > > And as usual we have:
> > > * [micro] SD-card slot
> > > * 2 USB 2.0 ports
> > > * 1Gbit Ethernet port
> > > * Built-in Digilent JTAG probe
> > > * Serial port accessible via micro-USB port
> > >
> > > Writing sdcard.img on SDcard creates two partitions:
> > > * FAT32 with uImage and uboot.env
> > > * EXT4 with root filesystem
> > >
> > > We modify kernel config because in default hsdk kernel config
> > > CONFIG_INITRAMFS_SOURCE parameter is set and when we build
> > > rootfs separately (BR2_TARGET_ROOTFS_INITRAMFS is not set)
> > > error appears. Also we set up CONFIG_ARC_UBOOT_SUPPORT which
> > > enables usage of uboot variables in the boot process.
> > >
> > > Signed-off-by: Evgeniy Didin <didin@synopsys.com>
> > > Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> > > Cc: Alexey Brodkin <abrodkin@synopsys.com>
> > > Cc: arc-buildroot at synopsys.com
> > > ---
> > > Changes since v1:
> > > -add entries in DEVELOPERS and .gitlab-ci.yml
> > > -change genimage-hsdk.cfg to genimage.cfg
> > > -enable BR2_TARGET_UBOOT_ENVIMAGE against mkenvimage in post-image.sh
> > > -add renaming "uboot-env.bin" to "uboot.env" in post-image.sh
> > > -changed tar to gzip when archiving sdcard.img
> >
> > I'm worried if we can make it merged before the next Buildroot
> > release. Any comments [except probably requirement to rebase as
> > it's been more than a month since v2 was posted] or/and suggestions on
> > this one?
>
> Please pardon myself for being that annoying but it looks like 2018.02-rc1
> was recently cut and that patch is not there yet.
>
> It would be really cool if we may still get this one merged ASAP so
> it becomes a part of the upcoming release.
>
> FWIW the board was now officially released, see
> https://www.synopsys.com/dw/ipdir.php?ds=arc-hs-development-kit
> and we're looking forward to have more people working with that
> quite capable board.
>
> -Alexey
next prev parent reply other threads:[~2018-02-19 7:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 14:55 [Buildroot] [PATCH v2] board: add support for ARC HS Development Kit (HSDK) Evgeniy Didin
2018-01-17 10:26 ` Evgeniy Didin
2018-01-31 7:58 ` Alexey Brodkin
2018-02-07 8:43 ` Alexey Brodkin
2018-02-19 7:56 ` Alexey Brodkin [this message]
2018-03-29 10:58 ` Evgeniy Didin
2018-03-31 12:56 ` Romain Naour
2018-03-31 13:25 ` Arnout Vandecappelle
2018-04-02 15:28 ` Alexey Brodkin
2018-04-02 20:27 ` Arnout Vandecappelle
2018-03-31 13:10 ` Thomas Petazzoni
2018-03-31 14:06 ` Peter Korsgaard
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=1519027005.14718.2.camel@synopsys.com \
--to=alexey.brodkin@synopsys.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.