From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Rudolf Streif <rstreif@linuxfoundation.org>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: is there a list of yocto-supported dev kits somewhere?
Date: Fri, 29 Aug 2014 12:01:44 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1408291157030.10554@localhost> (raw)
In-Reply-To: <CA+gsK-p1xVazx+guAy3Zo1nTrEVmnC3iMQVv9ZDoN28qhaKYKQ@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2096 bytes --]
On Fri, 29 Aug 2014, Rudolf Streif wrote:
> I think this is a great idea and I volunteer to help with the effort.
>
> that is kinda what i was after. i realize it's an open-ended
> request, but it would be great if there was a list of "recommended"
> dev kits representing various architectures/processors that people new
> to YP could purchase for experimentation, *knowing* that those dev
> kits had a YP build that would work out of the box. not necessarily
> technically complete, but that it would just boot and let them start
> playing.
>
> The "work out of the box" part is the tricky one. Unfortunately,
> many YP BSP layers do not include instructions on what to do after
> the build has completed. If you don't know what to do with boot
> loader and kernel images, flattened device tree files, root file
> system archives and images then you are at a loss. Commonly the
> boards also require a special boot media partitioning and the like.
exactly true, but without that final bit of information, i contend
that the YP build is utterly useless unless the developer is told what
to do with the final image objects.
> While this type of info should be in the BSP readme files I think it
> would be good to have step by step instructions that gets one from
> setting up the build environment to building and creating bootable
> media for each board.
and those step-by-step instructions don't need to be terribly
verbose. remember, you're not trying to explain how to use YP; you're
simply summarizing what it takes to get it running on a particular dev
kit. all of that should fit on a single page at most.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2014-08-29 16:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 7:38 is there a list of yocto-supported dev kits somewhere? Robert P. J. Day
2014-08-28 7:53 ` Samuel Stirtzel
2014-08-28 8:09 ` Robert P. J. Day
2014-08-28 15:08 ` Jeff Osier-Mixon
2014-08-29 11:22 ` Robert P. J. Day
2014-08-29 15:49 ` Rudolf Streif
2014-08-29 16:01 ` Robert P. J. Day [this message]
2014-08-29 16:22 ` Sven Ebenfeld
2014-08-30 9:32 ` Robert P. J. Day
2014-08-30 10:14 ` Robert P. J. Day
2014-09-05 13:35 ` Bryan Evenson
2014-09-09 9:36 ` Robert P. J. Day
2014-09-09 10:25 ` Bryan Evenson
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=alpine.LFD.2.11.1408291157030.10554@localhost \
--to=rpjday@crashcourse.ca \
--cc=rstreif@linuxfoundation.org \
--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.