From: Andrei Gherzan <andrei@gherzan.ro>
To: "Petter Mabäcker" <petter@technux.se>
Cc: yocto@yoctoproject.org
Subject: Re: [meta-raspberrypi][PATCH 1/1] README: Mention all the supported machines
Date: Mon, 4 Apr 2016 20:33:05 +0200 [thread overview]
Message-ID: <20160404183305.GC14683@resin> (raw)
In-Reply-To: <5702B35C.1070106@technux.se>
[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]
On Mon, Apr 04, 2016 at 08:33:00PM +0200, Petter Mabäcker wrote:
> On 04/04/2016 07:54 PM, Andrei Gherzan wrote:
> >Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
> >---
> > README | 5 ++++-
> > 1 file changed, 4 insertions(+), 1 deletion(-)
> >
> >diff --git a/README b/README
> >index 536926b..542b135 100644
> >--- a/README
> >+++ b/README
> >@@ -73,7 +73,10 @@ revision: HEAD
> > a. source poky/oe-init-build-env rpi-build
> > b. Add needed layer to bblayers.conf:
> > - meta-raspberrypi
> >-c. Set MACHINE to "raspberrypi"/"raspberrypi2" in local.conf
> >+c. Set MACHINE in local.conf to one of the supported boards:
> >+ - raspberrypi
> >+ - raspberrypi2
> >+ - raspberrypi3
> > d. bitbake rpi-hwup-image
> > e. dd to a SD card the generated sdimg file (use xzcat if rpi-sdimg.xz is used)
> > f. Boot your RPI.
> Good, this is a tiny but important change! Should we also mention
> raspberrypi0? Currently it just includes raspberrypi.conf and the the
> raspberrypi0 MACHINEOVERRIDE isn't used for anything, but still it is a
> defined MACHINE. What do you think?
>
Forgot it. Will send PR2.
> BR Petter
--
Andrei Gherzan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2016-04-04 18:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 17:54 [meta-raspberrypi][PATCH 1/1] README: Mention all the supported machines Andrei Gherzan
2016-04-04 18:33 ` Petter Mabäcker
2016-04-04 18:33 ` Andrei Gherzan [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=20160404183305.GC14683@resin \
--to=andrei@gherzan.ro \
--cc=petter@technux.se \
--cc=yocto@yoctoproject.org \
/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.