From: Denys Dmytriyenko <denis@denix.org>
To: "Osier-mixon, Jeffrey" <jeffrey.osier-mixon@intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: Raspberry Pi
Date: Tue, 08 May 2012 10:06:10 -0400 [thread overview]
Message-ID: <20120508140610.GK11416@denix.org> (raw)
In-Reply-To: <CALZ2gZU7DOYu6+kZ-DY=hw-3v5Gyqn2nABDgz06h+S4rubfL+A@mail.gmail.com>
On Tue, May 08, 2012 at 12:58:32AM -0700, Osier-mixon, Jeffrey wrote:
> Hi Chris & all - there is a small group working on a Yocto Project BSP
> for the Raspberry Pi, particularly to get Qt working (this is the
> QtonPi group to which Brian referred in an earlier message). I can put
> you in touch with them if you like.
There is even a repository available for it now:
https://github.com/djwillis/meta-raspberrypi
--
Denys
> On Tue, May 8, 2012 at 12:43 AM, Chris Tapp <opensource@keylevel.com> wrote:
> > On 15 Dec 2011, at 21:47, 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.
> >
> > Well, I've finally got to the top of the order list and should be getting some hardware within the next few days. Time to get started!
> >
> > I guess the first thing to do is get a kernel built. I'm not up-to-date with ARM - are there any BSPs available for similar devices / the ARM11 core?
> >
> > Chris Tapp
> >
> > opensource@keylevel.com
> > www.keylevel.com
> >
> > _______________________________________________
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
>
>
>
> --
> Jeff Osier-Mixon http://jefro.net/blog
> Yocto Project Community Manager @Intel http://yoctoproject.org
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
next prev parent reply other threads:[~2012-05-08 14:06 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
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 [this message]
-- 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=20120508140610.GK11416@denix.org \
--to=denis@denix.org \
--cc=jeffrey.osier-mixon@intel.com \
--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.