On Fri, Aug 20, 2010 at 05:54:20PM -0400, James Westby wrote:
On Fri, 20 Aug 2010 18:49:58 -0300, Christian Robottom Reis email@example.com wrote:
On Fri, Aug 20, 2010 at 04:26:46PM -0400, James Westby wrote:
- What are the use cases for tags? I can only see X/no X in the spec.
One other I see is OpenMAX + Gstreamer versus pure Gstreamer versus OpenCORE. I guess the generic use case I see there is being able to identify what sort of software components the hardware pack provides support for -- a hardware pack for X would require some X-specific glue code that wouldn't be required in a different environment.
Note that even X/no-X may be simplistic, because the no-X case can be varied and potentially require different contents in the hardware packs.
So would it be simpler to just allow exclusion of specific packages from the hardware pack? As written there are likely to be less than 10 packages, and all the combinations of tags is going to far exceed that.
The simplest form would be to make it so the hardware pack would be installable on a number of different stacks and it would just work. But that would mean that the packs would contain a number of potentially conflicting packages.
I'm not sure I understand your question, though. Are you asking if packages could be excluded at hardware-pack install time or at creation time?
One thing which is nice about tags is that it's clear what platforms are supported in which configurations. So you can look at board X and see ah, it has a no-X gstreamer hardware pack, but no X gstreamer pack, which means at the moment there's no X acceleration for it.