Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OpenEmbedded 2011.3 Release: Request for targets!
Date: Fri, 18 Feb 2011 08:33:24 -0700	[thread overview]
Message-ID: <4D5E9144.8010100@mentor.com> (raw)
In-Reply-To: <AANLkTinxsHq86KY7xBBd4=iJmG3Xcz_8nx3Ex0hHHM=P@mail.gmail.com>

On 02/11/2011 05:53 AM, Frans Meulenbroeks wrote:
> 2011/2/11 Ulf Samuelsson<ulf.samuelsson@atmel.com>:
>> Stefan Schmidt skrev 2011-02-09 11:02:
>>>
>>> Hello.
>>>
>>> On Tue, 2011-02-08 at 07:42, Tom Rini wrote:
>>>>
>>>> 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!).
>>>
>>> I will do compile and runtime testing on bug20 (omap3). Targets would be
>>> console-, minimal- and bug-image-production. The later one includes the
>>> complete
>>> oenjdk-6 stuff with zero as JIT, the osgi recipes and much of the normal X
>>> and
>>> linux stuff.
>>>
>>
>> I think that for the AT91 the three most important targets are:
>>
>> AT91SAM9M10EKES
>> AT91SAM9G20EK
>> AT91SAM9263EK

Was missing at91sam10ekes, added.

>> I noted that when I added the gpe-mini-browser2
>> to my image, the boot fails.
>>
>
> If there is room left, we have interest in:
>
> calamari/minimal/console-image
> mpc8313e-rdb/minimal/console-image

Added.

> nslu2le/slugos/slugos-image
> nslu2be/slugos/slugos-image

Already in.

-- 
Tom Rini
Mentor Graphics Corporation



  reply	other threads:[~2011-02-18 15:34 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
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 [this message]
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=4D5E9144.8010100@mentor.com \
    --to=tom_rini@mentor.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