All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: James Abernathy <jfabernathy@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: HOW DO I - new one added for EMGD and Crownbay
Date: Sun, 05 Feb 2012 12:19:24 -0800	[thread overview]
Message-ID: <4F2EE44C.7090809@linux.intel.com> (raw)
In-Reply-To: <2779C8B7-F034-4F86-8BCF-0CC6374AD803@gmail.com>



On 02/05/2012 11:44 AM, James Abernathy wrote:
> 
> On Feb 5, 2012, at 2:19 PM, Darren Hart wrote:
> 
>> On 02/04/2012 07:21 AM, jfabernathy wrote:
>>> I just added and EMGD example to the How Do I in the wiki.
>>
>> Jim, really appreciate your work here. For those of us not following
>> quite as closely, please provide links to the pages you update so we
>> don't have to go hunting for them.
>>
> It's the How Do I link on the wiki page:
> 
> https://wiki.yoctoproject.org/wiki/How_do_I

I see. This Question heading seems a bit inconsistent with what you are
actually doing. Step 1 of getting EMGD on Crownbay is adding alsa to
MACHINE_FEATURES for a BSP called meta-mymachine?

This appears to be just trying to get commercial codecs working with
accelerated graphics.

The reason I raise this, is that while it's good to have these sorts of
"Tactical" guides, if we aren't careful they can dilute the
documentation space and end up confusing users more than they help. The
README for crownbay covers what is necessary to enable EMGD accelerated
graphics. Please consider renaming the title to someting more consistent
with what you're trying accomplish.

--
Darren

> 
>> I'm interested to see what more was needed for EMGD and Crownbay than is
>> already in the BSP README.
>>
>>>
>>> In my opinion, we need to think about breaking this one big edit up into 
>>> individual How Do I's.  It would simplify editing and make getting to 
>>> the individual How Do I's much easier and quicker.
>>>
>>> I don't know how to do that, but I think it needs doing.
>>>
>>> Jim A
>>>
>>> _______________________________________________
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>
>> -- 
>> Darren Hart
>> Intel Open Source Technology Center
>> Yocto Project - Linux Kernel
> 

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


  reply	other threads:[~2012-02-05 20:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-04 15:21 HOW DO I - new one added for EMGD and Crownbay jfabernathy
2012-02-05 19:19 ` Darren Hart
2012-02-05 19:44   ` James Abernathy
2012-02-05 20:19     ` Darren Hart [this message]
2012-02-06 13:00       ` James Abernathy
2012-02-06 15:59         ` Darren Hart
2012-02-06 17:13           ` jfabernathy
2012-02-06 17:32             ` Darren Hart
2012-02-06 18:19               ` James Abernathy
2012-02-06 18:27                 ` Darren Hart
2012-02-06 22:47                   ` jfabernathy

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=4F2EE44C.7090809@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=jfabernathy@gmail.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.