All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH 0/1] meta/pandaboard: add pandaboard bsp
Date: Fri, 05 Aug 2011 13:55:24 -0400	[thread overview]
Message-ID: <4E3C2E8C.8090404@balister.org> (raw)
In-Reply-To: <4E3C2AAF.9030601@windriver.com>

On 08/05/2011 01:38 PM, Bruce Ashfield wrote:
> On 11-08-05 01:34 PM, Khem Raj wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 08/04/2011 10:58 PM, jingdong.lu@windriver.com wrote:
>>> From: Jingdong Lu<jingdong.lu@windriver.com>
>>>
>>> Add pandaboard bsp
>>
>> why not use meta-ti ?
>
> I'm hoping to not repeat all the discussions that we've had
> around the beagle board here. Anything that applies to that
> applies here.
>
> This is a reference BSP done by the Wind River folks on top
> of the linux-yocto kernel. It is not intended to be a replacement
> for any existing pandaboard efforts, but is intended to be used
> as an example of an integrated board.

Would you mind re-summarizing the discussion? I know there has been a 
lot of back and forth, and it seems like a summary would be helpful for 
people who stopped following the discussion.

It is very confusing for many of us to see duplicate and or competing BSP's.

Philip

>
> Cheers,
>
> Bruce
>
>>
>>>
>>> Jingdong Lu (1): pandaboard: add pandaboard bsp
>>>
>>> .../bsp/pandaboard/pandaboard-non_hardware.cfg | 30 ++
>>> .../bsp/pandaboard/pandaboard-standard.scc | 7 +
>>> .../cfg/kernel-cache/bsp/pandaboard/pandaboard.cfg | 346
>>> ++++++++++++++++++++
>>> .../cfg/kernel-cache/bsp/pandaboard/pandaboard.scc | 5 + 4 files
>>> changed, 388 insertions(+), 0 deletions(-) create mode 100644
>>> meta/cfg/kernel-cache/bsp/pandaboard/pandaboard-non_hardware.cfg
>>> create mode 100644
>>> meta/cfg/kernel-cache/bsp/pandaboard/pandaboard-standard.scc create
>>> mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard.cfg
>>> create mode 100644
>>> meta/cfg/kernel-cache/bsp/pandaboard/pandaboard.scc
>>>
>>> _______________________________________________ yocto mailing list
>>> yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>> - --
>> - -Khem
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.11 (GNU/Linux)
>>
>> iEYEARECAAYFAk48KZcACgkQuwUzVZGdMxSjEwCdHLqsMwcYEhAblghgJio7tJPK
>> Sm8An2Xps8CntGIGV0bFxTJw/dIAL6pV
>> =PeJ+
>> -----END PGP SIGNATURE-----
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>


  reply	other threads:[~2011-08-05 17:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-05  5:58 [PATCH 0/1] meta/pandaboard: add pandaboard bsp jingdong.lu
2011-08-05  5:58 ` [PATCH 1/1] pandaboard: " jingdong.lu
2011-08-05 17:34 ` [PATCH 0/1] meta/pandaboard: " Khem Raj
2011-08-05 17:38   ` Bruce Ashfield
2011-08-05 17:55     ` Philip Balister [this message]
2011-08-05 18:10       ` Bruce Ashfield
2011-08-07  2:47         ` Bruce Ashfield

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=4E3C2E8C.8090404@balister.org \
    --to=philip@balister.org \
    --cc=bruce.ashfield@windriver.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.