Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Drew Fustini <drew@beagleboard.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/4] Support for the Beagle-V platform
Date: Fri, 30 Apr 2021 01:27:03 -0700	[thread overview]
Message-ID: <20210430082703.GA139460@x1> (raw)
In-Reply-To: <20210429074636.724046-1-thomas.petazzoni@bootlin.com>

On Thu, Apr 29, 2021 at 09:46:31AM +0200, Thomas Petazzoni wrote:
> Hello,
> 
> The beta version of the Beagle-V RISC-V 64-bit platform has been
> showing up at the front door of a few lucky people around the world in
> the past days.

Thank you for getting this posted so fast! The primary goal of our beta
developer program for the BeagleV Starlight is to get the upstream
process going so we are in a good position when the production board
launches with distributors in September [1]. Anyone interested can join
our public BeagleV forum to stay updated [2].

This is the first upstream patch series for BeagleV Starlight which
made me realize I need to provide some clarification on naming guidance
for the boards and SoCs. I have added a new section to the README [3].

Small nit for this cover letter is that it should be BeagleV instead of
Beagle-V.  But more importantly I want to make everyone aware that there
there will eventually be two different BeagleV Starlight boards:

- BeagleV Starlight board with StarFive JH7100 SoC (2x SiFive U74)
- BeagleV Starlight board with StarFive JH7110 SoC (4x U74, PCIe, GPU)

The board that a limited number of beta developers like Thomas have just
received is the JH7100 version.

Thank you,
Drew Fustini
BeagleBoard.org Foundation

[1] https://github.com/beagleboard/beaglev-starlight
[2] https://forum.beagleboard.org/c/beaglev
[3] https://github.com/beagleboard/beaglev-starlight#guidance-on-naming-conventions

      parent reply	other threads:[~2021-04-30  8:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29  7:46 [Buildroot] [PATCH 0/4] Support for the Beagle-V platform Thomas Petazzoni
2021-04-29  7:46 ` [Buildroot] [PATCH 1/4] boot/opensbi: add support for version configuration Thomas Petazzoni
2021-04-29 12:45   ` Bin Meng
2021-04-30  7:48   ` Peter Korsgaard
2021-04-30  8:51   ` Drew Fustini
2021-04-30  8:56     ` Thomas Petazzoni
2021-04-29  7:46 ` [Buildroot] [PATCH 2/4] boot/opensbi: allow using U-Boot as a payload Thomas Petazzoni
2021-04-29 12:45   ` Bin Meng
2021-04-30  7:49   ` Peter Korsgaard
2021-04-29  7:46 ` [Buildroot] [PATCH 3/4] boot/opensbi: add options to enable/disable image installation Thomas Petazzoni
2021-04-29 12:39   ` Bin Meng
2021-04-29  7:46 ` [Buildroot] [PATCH 4/4] configs/beaglev_defconfig: new defconfig Thomas Petazzoni
2021-04-29 12:44   ` Bin Meng
2021-05-01 14:37   ` Frank Hunleth
2021-04-29 12:39 ` [Buildroot] [PATCH 0/4] Support for the Beagle-V platform Erico Nunes
2021-04-29 13:01   ` Thomas Petazzoni
2021-04-29 13:26     ` Erico Nunes
2021-04-29 13:48       ` Thomas Petazzoni
2021-04-29 13:52         ` Erico Nunes
2021-04-29 14:26           ` Thomas Petazzoni
2021-04-29 14:55             ` Erico Nunes
2021-04-30  0:35   ` Drew Fustini
2021-04-30  8:27 ` Drew Fustini [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=20210430082703.GA139460@x1 \
    --to=drew@beagleboard.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox