[yocto] HOW DO I - new one added for EMGD and Crownbay

[James Abernathy]

On Mon, Feb 6, 2012 at 12:32 PM, Darren Hart <dvhart at linux.intel.com> wrote:

>
>
> On 02/06/2012 09:13 AM, jfabernathy wrote:
> > On 02/06/2012 10:59 AM, Darren Hart wrote:
> >>
> >> On 02/06/2012 05:00 AM, James Abernathy wrote:
> >>> On Feb 5, 2012, at 3:19 PM, Darren Hart wrote:
> >>>
> >>>>
> >>>> 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.
> >>>>
> >>> Look, I'm not a documentation expert or understand what the project
> >>> team is trying to accomplish with their documentation or wiki.  A
> >>> user on the mailing list asked me to summarize what I did to get all
> >>> the issues resolve related to media acceleration and decoder.  What I
> >>> put in  the How Do I was a summation of the questions and answers
> >>> that were in the email thread. I can just as easily email that user
> >>> the summary, if it's not appropriate for the wiki.
> >>>
> >> Please don't take the above as a criticism of the "How Do I" concept, as
> >> I said at first, I appreciate you doing it - I understand it takes some
> >> considerable additional time to publish it. The goal is clearly to make
> >> things easier for others when they attempt what you're doing. I saw
> >> something in there that might not fit the goal and raised it as a point
> >> of improvement, that's all.
> >>
> >>
> >>> Please feel free to edit what I put there or remove it.
> >> I've CC'd Scott R. to review and see if he might care to adjust things a
> >> bit. I certainly don't want to remove it :)
> >>
> >> --
> >> Darren
> >>
> > What I feel is missing from the standard documentation for EMGD v1.10
> > integration into the Crownbay BSP is all the "other" stuff you need.
> > The README file in the meta-crownbay includes exactly what is needed to
> > integrate the EMGD v 1.10 driver.  But generally, after that users will
> > have the next level of questions about how do I get video and audio
> > media files to play correctly, or test 3D . This is technically not a
> > driver integration question, but can be anticipated because you wouldn't
> > care about integrating the EMGD driver unless you had media and 3D needs
> > in your application/.
>
> Fair enough. As those sorts of things are not BSP specific, I certainly
> think the How-Do-I pages you're creating are a good way to address that
> gap. At some point, this sort of tactical documentation might make sense
> to be rolled up into some more official type of docs. For now, the
> How-Do-I Question title could be improved were to read "How do I enable
> audio and commerial audio and video codecs?" or "How do I get the Sato
> media player to play mp3s?"
>


> If we could make the "How Do I" section of the wiki broken into
> sub-categories so each "How Do I" is a separate item to be edited. That
> would make it easier to find, create, and edit these items. Also once an
> item found it's way into official documentation, it could be removed or
> edited to point to the official doc.


Jim A


> --
> Darren
>
> >
> > Just my thoughts.
> >
> > Jim A
> >
> >>> Jim A
> >>>
> >>>> -- 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 at 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
> >
>
> --
> Darren Hart
> Intel Open Source Technology Center
> Yocto Project - Linux Kernel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20120206/8e74a8a7/attachment.html>