From: Jaap de Jong <jaap.dejong@nedap.com>
To: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: OpenEmbedded 2011.3 Release: Request for targets!
Date: Tue, 08 Feb 2011 16:02:58 +0100 [thread overview]
Message-ID: <4D515B22.5090600@nedap.com> (raw)
In-Reply-To: <4D51566B.9060603@mentor.com>
Please add
at91sam9263ek
(angstrom-2008.1 / angstrom-2010.x)
On 02/08/2011 03:42 PM, Tom Rini wrote:
> Hey all,
>
> As March is fast approaching I want to gather the list of DISTRO /
> MACHINE / BBPKGS targets that the various distributions would like to
> see at least compile tested (volunteers for HW testing welcome!).
> Today, I have the following setup to be built:
>
> minimal / minimal-uclibc:
> qemux86/ppc/arm/mips/mips64/sh4/mipsel, mpc8315e-rdb, p2020ds, p2020rdb
> +
> nas-server-image/native-sdk-image/console-image/minimal-image/x11-image/meta-toolchain/qt4-x11-demo-image/qt4e-demo-image
>
> angstrom-2008.1 / angstrom-2010.x:
> hawkboard, mini2440, mini6410, beagleboard + console-image /
> qt4-x11-demo-image / qt4e-demo-image
>
> slugos / ucslug:
> nslu2be/le + slugos-image
>
> I'm building all of these for 32bit Ubuntu 8.04, RHEL5 and will be
> adding Ubuntu 10.04 for the next run. What more do people want added?
> I'm looking to fill this matrix out to something that runs "over the
> weekend" and I've still got plenty of room to spare (which is why I've
> bcc'd everyone in the MAINTAINERS file with a Distro by their name).
>
> And of course if you wish to handle building what you care about
> yourself instead, that's great! Please just take this as a gentle
> reminder that there's a release coming up so it's time to crank the
> builders up and make sure your stuff is working.
>
next prev parent reply other threads:[~2011-02-08 15:05 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 14:42 OpenEmbedded 2011.3 Release: Request for targets! Tom Rini
2011-02-08 14:53 ` Graeme Gregory
2011-02-08 14:58 ` Tom Rini
2011-02-09 6:37 ` Bernhard Guillon
2011-02-14 16:11 ` Tom Rini
2011-02-14 16:57 ` Frans Meulenbroeks
2011-02-14 17:19 ` Tom Rini
2011-02-14 17:43 ` Frans Meulenbroeks
2011-02-18 15:27 ` Tom Rini
2011-02-17 21:45 ` Bernhard Guillon
2011-02-17 22:35 ` Khem Raj
2011-02-18 18:48 ` Bernhard Guillon
2011-02-18 15:30 ` Tom Rini
2011-02-18 15:46 ` Khem Raj
2011-02-18 16:00 ` Tom Rini
2011-02-08 15:02 ` Jaap de Jong [this message]
2011-02-08 15:22 ` Tom Rini
2011-02-08 15:53 ` Jaap de Jong
2011-02-08 15:06 ` Thom Nichols
2011-02-08 15:23 ` Tom Rini
2011-02-08 16:30 ` Marco Cavallini
2011-02-08 17:12 ` Tom Rini
2011-02-08 17:33 ` Khem Raj
2011-02-08 19:36 ` Tom Rini
2011-02-11 18:07 ` Ulf Samuelsson
2011-02-11 18:16 ` Tom Rini
2011-02-11 20:20 ` Philip Balister
2011-02-14 16:09 ` Tom Rini
2011-02-15 20:50 ` Cliff Brake
2011-02-15 20:59 ` Tom Rini
2011-02-16 9:25 ` Hauser, Wolfgang (external)
2011-02-08 20:10 ` Yury Bushmelev
2011-02-08 22:51 ` AJ ONeal
2011-02-08 23:00 ` Tom Rini
2011-02-09 8:07 ` Steffen Sledz
2011-02-09 10:02 ` Stefan Schmidt
2011-02-11 10:10 ` Ulf Samuelsson
2011-02-11 12:53 ` Frans Meulenbroeks
2011-02-18 15:33 ` Tom Rini
2011-02-09 17:31 ` Tom Rini
2011-02-10 8:23 ` Martin Jansa
2011-02-10 14:53 ` Tom Rini
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=4D515B22.5090600@nedap.com \
--to=jaap.dejong@nedap.com \
--cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox