HOW DO I - new one added for EMGD and Crownbay
I just added and EMGD example to the How Do I in the wiki.
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
Quoted 1 line · jfabernathy
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.
I'm interested to see what more was needed for EMGD and Crownbay than is already in the BSP README.
Quoted 13 lines
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
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel
Quoted 7 lines · Darren Hart
Quoted 1 line · jfabernathy
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
Quoted 21 lines
I'm interested to see what more was needed for EMGD and Crownbay than is already in the BSP README.
Quoted 13 lines
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
[email protected]
https://lists.yoctoproject.org/listinfo/yoctoSignature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel
Quoted 6 lines · James Abernathy
Quoted 3 lines · Darren Hart
Quoted 1 line · jfabernathy
I just added and EMGD example to the How Do I in the wiki.
Quoted 7 lines
Quoted 4 lines
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:
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
Quoted 23 lines
Quoted 22 lines
I'm interested to see what more was needed for EMGD and Crownbay than is already in the BSP README.
Quoted 13 lines
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
[email protected]
https://lists.yoctoproject.org/listinfo/yoctoSignature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel
Quoted 24 lines · Darren Hart
Quoted 6 lines · James Abernathy
Quoted 3 lines · Darren Hart
Quoted 1 line · jfabernathy
I just added and EMGD example to the How Do I in the wiki.
Quoted 7 lines
Quoted 4 lines
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:
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_FEATURESfor a BSP called meta-mymachine?This appears to be just trying to get commercial codecs working with accelerated graphics.
Quoted 7 lines
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 feel free to edit what I put there or remove it.
Jim A
Quoted 31 lines
--
DarrenQuoted 23 lines
Quoted 22 lines
I'm interested to see what more was needed for EMGD and Crownbay than is already in the BSP README.
Quoted 13 lines
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
[email protected]
https://lists.yoctoproject.org/listinfo/yoctoSignature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux KernelSignature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel
Quoted 35 lines · James Abernathy
Quoted 24 lines · Darren Hart
Quoted 6 lines · James Abernathy
Quoted 3 lines · Darren Hart
Quoted 1 line · jfabernathy
I just added and EMGD example to the How Do I in the wiki.
Quoted 7 lines
Quoted 4 lines
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:
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_FEATURESfor a BSP called meta-mymachine?This appears to be just trying to get commercial codecs working with accelerated graphics.
Quoted 7 lines
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.
Quoted 8 lines
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.
Quoted 1 line
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
Quoted 30 lines
Jim A
Quoted 26 lines
-- Darren
Quoted 12 lines
Quoted 12 lines
I'm interested to see what more was needed for EMGD and Crownbay than is already in the BSP README.
Quoted 8 lines
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.
Quoted 9 lines
Quoted 8 lines
Quoted 5 lines
Jim A
_______________________________________________ yocto mailing list [email protected]
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
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel
Quoted 47 lines · Darren Hart
Quoted 29 lines · James Abernathy
Quoted 20 lines · Darren Hart
Quoted 11 lines · James Abernathy
Quoted 6 lines · Darren Hart
Quoted 1 line · jfabernathy
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:
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_FEATURESfor a BSP called meta-mymachine?This appears to be just trying to get commercial codecs working with accelerated graphics.
Quoted 7 lines
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.
Quoted 8 lines
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.
Quoted 7 lines
Quoted 1 line
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/.
Just my thoughts.
Jim A
Quoted 23 lines
Quoted 23 lines
Jim A
Quoted 21 lines
-- Darren
Quoted 10 lines
Quoted 10 lines
I'm interested to see what more was needed for EMGD and Crownbay than is already in the BSP README.
Quoted 7 lines
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.
Quoted 7 lines
Quoted 7 lines
Quoted 5 lines
Jim A
_______________________________________________ yocto mailing list [email protected]
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
Quoted 55 lines · jfabernathy
Quoted 47 lines · Darren Hart
Quoted 29 lines · James Abernathy
Quoted 20 lines · Darren Hart
Quoted 11 lines · James Abernathy
Quoted 6 lines · Darren Hart
Quoted 1 line · jfabernathy
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:
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_FEATURESfor a BSP called meta-mymachine?This appears to be just trying to get commercial codecs working with accelerated graphics.
Quoted 7 lines
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.
Quoted 8 lines
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.
Quoted 7 lines
Quoted 1 line
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
Quoted 9 lines
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?"
--
Darren
Quoted 29 lines
Just my thoughts.
Jim A
Quoted 23 lines
Quoted 23 lines
Jim A
Quoted 21 lines
-- Darren
Quoted 10 lines
Quoted 10 lines
I'm interested to see what more was needed for EMGD and Crownbay than is already in the BSP README.
Quoted 7 lines
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.
Quoted 7 lines
Quoted 7 lines
Quoted 5 lines
Jim A
_______________________________________________ yocto mailing list [email protected]
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
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel
Quoted 78 lines · Darren Hart
Quoted 55 lines · jfabernathy
Quoted 47 lines · Darren Hart
Quoted 29 lines · James Abernathy
Quoted 20 lines · Darren Hart
Quoted 11 lines · James Abernathy
Quoted 6 lines · Darren Hart
Quoted 1 line · jfabernathy
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:
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_FEATURESfor a BSP called meta-mymachine?This appears to be just trying to get commercial codecs working with accelerated graphics.
Quoted 7 lines
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.
Quoted 8 lines
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.
Quoted 7 lines
Quoted 1 line
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 :)
--
DarrenQuoted 9 lines
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?"
Quoted 5 lines
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
Quoted 38 lines
--
DarrenQuoted 29 lines
Just my thoughts.
Jim A
Quoted 23 lines
Quoted 23 lines
Jim A
Quoted 21 lines
-- Darren
Quoted 10 lines
Quoted 10 lines
I'm interested to see what more was needed for EMGD and Crownbay than is already in the BSP README.
Quoted 7 lines
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.
Quoted 7 lines
Quoted 7 lines
Quoted 5 lines
Jim A
_______________________________________________ yocto mailing list [email protected]
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
Quoted 6 lines · James Abernathy
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.
The wiki will do this automatically if you use headings for the questions instead of the bold ''' syntax.
You creating headings with the = characher
= Heading Level 1 =
== Heading Level 2 ==
=== Heading Level 3 ===
etc.
I suggest starting on Headling Level 2, leaving Level 1 for the title. This should also automatically present a Table of Contents at the top of the page which aids in navigation.
This is standard MediaWiki syntax, for reference:
http://www.mediawiki.org/wiki/Help:Formatting#Level_2
http://www.mediawiki.org/wiki/Table_of_Contents
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel
Quoted 12 lines · Darren Hart
Quoted 5 lines · James Abernathy
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.
The wiki will do this automatically if you use headings for the questions instead of the bold ''' syntax.
You creating headings with the = characher
Quoted 8 lines
= Heading Level 1 =
== Heading Level 2 ==
=== Heading Level 3 ===
etc.I suggest starting on Headling Level 2, leaving Level 1 for the title. This should also automatically present a Table of Contents at the top of the page which aids in navigation.
Okay, I've made some edits using the == Heading Level 2 ==. I think it solves some of my issues for editing, etc. Only need the complete edit for starting a new topic, I guess.
Quoted 4 lines
This is standard MediaWiki syntax, for reference:
http://www.mediawiki.org/wiki/Help:Formatting#Level_2
http://www.mediawiki.org/wiki/Table_of_Contents