From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: Raspberry Pi
Date: Thu, 15 Dec 2011 20:14:57 -0500 [thread overview]
Message-ID: <4EEA9B91.9010905@windriver.com> (raw)
In-Reply-To: <1323987793.4568.72.camel@ted>
On 11-12-15 5:23 PM, Richard Purdie wrote:
> On Thu, 2011-12-15 at 21:47 +0000, Chris Tapp wrote:
>> Is anyone on this list considering (or working on) a BSP for the
>> Raspberry Pi (http://www.raspberrypi.org/faqs) ?
>>
>> For those that haven't seen it, it's a credit-card sized 'home pc'
>> aimed primarily at educational users that includes a 700MHz ARM11
>> core, HDMI, OpenGL ES 2.0, ethernet and audio for about $35. It will
>> be supporting Debian, Fedora and ArchLinux at launch.
>>
>> Looks like a good board for people that want to get in to Yocto /
>> embedded linux. Also looks like it's a good platform for some of my
>> stuff...
>>
>> I would be interested in working on a BSP / distro if anyone is
>> working on it or would like to work on it.
>
> I'm not aware of anyone working on this but I like the idea of a BSP for
> it and it shouldn't be too hard to do. I'd be happy to ensure we have a
> repository somewhere on git.yoctoproject.org to support this (and any
> other similar BSP efforts) if that would help?
We can also help here @ Wind River. This board is one that's on my short
list for the BSP refresh covered by:
http://bugzilla.pokylinux.org/show_bug.cgi?id=1634
So I'd like to see it right in the yocto kernel as a hardware reference
platform.
I'm about to finalize a suggested list of boards and after that, we can
see what resources/people want to collaborate on some BSPs.
Cheers,
Bruce
>
> Cheers,
>
> Richard
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
next prev parent reply other threads:[~2011-12-16 1:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 21:47 Raspberry Pi Chris Tapp
2011-12-15 22:23 ` Richard Purdie
2011-12-16 1:14 ` Bruce Ashfield [this message]
2011-12-16 1:28 ` Jeff Osier-Mixon
2011-12-16 23:37 ` Chris Tapp
2011-12-17 18:27 ` Robert Berger
2012-02-08 0:52 ` Joshua Lock
2012-02-08 2:35 ` Brian Hutchinson
2012-02-08 2:36 ` Brian Hutchinson
2012-02-08 9:17 ` Jack Mitchell
2012-05-08 7:43 ` Chris Tapp
2012-05-08 7:58 ` Osier-mixon, Jeffrey
2012-05-08 14:06 ` Denys Dmytriyenko
-- strict thread matches above, loose matches on Subject: below --
2012-12-01 17:17 GOPIKRISHNAN S
2012-12-01 19:37 ` McClintock Matthew-B29882
2012-12-01 19:41 ` Andrei Gherzan
2012-12-03 16:58 ` McClintock Matthew-B29882
2012-12-01 20:02 ` Fabio Estevam
2012-12-01 23:09 ` Andrei Gherzan
2017-06-30 14:33 Michael Williams
2017-06-30 15:21 ` St Leger, Jim
2017-06-30 16:21 ` Michael Williams
2017-06-30 19:28 ` Jim Thompson
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=4EEA9B91.9010905@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=richard.purdie@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.