All of lore.kernel.org
 help / color / mirror / Atom feed
From: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
To: poky@yoctoproject.org
Subject: Re: [PATCH 0/1] meta-fishriver: new BSP
Date: Sun, 10 Apr 2011 13:48:41 -0700	[thread overview]
Message-ID: <4DA217A9.8090709@intel.com> (raw)
In-Reply-To: <4D99FCE4.6000209@intel.com>

I'll get this into the autobuilder config this week.

-b

On 04/04/2011 10:16 AM, Saul Wold wrote:
> On 03/30/2011 05:41 PM, Tom Zanussi wrote:
>> From: Tom Zanussi<tom.zanussi@intel.com>
>>
>> This patchset implements a new BSP for Fish River Island (Z530/EG20T).
>>
>> The basic platorm support works e.g. network, sato desktop,
>> USB keyboard/mouse, but it currently only supports vesa.
>>
>> Better graphics support and support for more of the Fish River Island
>> devices will be added later.
>>
>> Please pull into meta-intel/master.
>>
>> Pull URL: git://git.pokylinux.org/meta-intel.git
>>     Branch: tzanussi/meta-fishriver-initial-BSP
>>     Browse: http://git.pokylinux.org/cgit/cgit.cgi/meta-intel/log/?h=tzanussi/meta-fishriver-initial-BSP
>>
>> Tom Zanussi (1):
>>     meta-fishriver: new layer for Fish River Island (Z530/EG20T) systems
>>
>>    meta-fishriver/COPYING.MIT                         |   17 ++++
>>    meta-fishriver/README                              |   94 ++++++++++++++++++++
>>    meta-fishriver/conf/layer.conf                     |   10 ++
>>    meta-fishriver/conf/machine/fishriver.conf         |   46 ++++++++++
>>    .../formfactor/formfactor/fishriver/machconfig     |    3 +
>>    .../recipes-bsp/formfactor/formfactor_0.0.bbappend |    3 +
>>    .../xserver-xf86-config/fishriver/xorg.conf        |   26 ++++++
>>    .../xorg-xserver/xserver-xf86-config_0.1.bbappend  |    3 +
>>    .../recipes-kernel/linux/linux-yocto_git.bbappend  |    4 +
>>    9 files changed, 206 insertions(+), 0 deletions(-)
>>    create mode 100644 meta-fishriver/COPYING.MIT
>>    create mode 100644 meta-fishriver/README
>>    create mode 100644 meta-fishriver/binary/.gitignore
>>    create mode 100644 meta-fishriver/conf/layer.conf
>>    create mode 100644 meta-fishriver/conf/machine/fishriver.conf
>>    create mode 100644 meta-fishriver/recipes-bsp/formfactor/formfactor/fishriver/machconfig
>>    create mode 100644 meta-fishriver/recipes-bsp/formfactor/formfactor_0.0.bbappend
>>    create mode 100644 meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config/fishriver/xorg.conf
>>    create mode 100644 meta-fishriver/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
>>    create mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto_git.bbappend
>>
>> _______________________________________________
>> poky mailing list
>> poky@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/poky
>>
> Pushed into meta-intel master
>
> Thanks
> 	Sau!
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky

-- 
------------------
Elizabeth Flanagan
Yocto Project
Release Engineer


      reply	other threads:[~2011-04-10 20:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-31  0:41 [PATCH 0/1] meta-fishriver: new BSP Tom Zanussi
2011-04-04 17:16 ` Saul Wold
2011-04-10 20:48   ` Elizabeth Flanagan [this message]

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=4DA217A9.8090709@intel.com \
    --to=elizabeth.flanagan@intel.com \
    --cc=poky@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.