Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Joao Pinto <Joao.Pinto@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] board: add support for ARM Juno r1 Development Board
Date: Fri, 9 Oct 2015 16:53:14 +0100	[thread overview]
Message-ID: <5617E2EA.2040601@synopsys.com> (raw)
In-Reply-To: <20151009174818.5a2797ce@free-electrons.com>

Dear Thomas,

Firstly let me congratulate you on your presentation in the Auditorium.

On 10/9/2015 4:48 PM, Thomas Petazzoni wrote:
> Dear Joao Pinto,
> 
> On Fri,  9 Oct 2015 16:29:05 +0100, Joao Pinto wrote:
>> The Juno r1 ARM Development Platform (ADP) is a software development
>> platform for ARMv8-A, it includes the Juno r1 Versatile Express board 
>> and an ARMv8-A reference software port available through Linaro.
>>
>> Remark: The kernel' arm64 defconfig lacks a considerable amount of 
>> configuration items regarding the Juno r1 board, and that is the reason
>> of this custom kernel configuration file.
> 
> Can you add a readme.txt file in board/arm/junor1/ that explains how to
> use the result? You're building just a tarball for the root filesystem,
> what are the instructions to actually use it on the board?

I will add a readme.txt file. The Juno r1 accepts typically an ext formatted
pen-drive from where it mounts the root filesystem. The simplest procedure its
to untar the rootfs.tar to the pen-drive and give it a go.

> 
> Thanks,
> 
> Thomas
> 

Thanks,
Joao

      reply	other threads:[~2015-10-09 15:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-09 15:29 [Buildroot] [PATCH v2] board: add support for ARM Juno r1 Development Board Joao Pinto
2015-10-09 15:48 ` Thomas Petazzoni
2015-10-09 15:53   ` Joao Pinto [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=5617E2EA.2040601@synopsys.com \
    --to=joao.pinto@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox