PV Open Core architecture docs

by jerand » Wed, 21 Jan 2009 13:28:41 GMT

Sponsored Links
 Where can i find documents pertaining to the design and architecture
of Open Core ?

PV Open Core architecture docs

by David Lindquist » Wed, 21 Jan 2009 18:45:51 GMT

 You can find documentation in the doc directory with the source code.
The file pvplayer_developers_guide.pdf may be a good place to start.
 http://android.git.kernel.org/?p=platform/external/opencore.git ;a=tree 


Sponsored Links

PV Open Core architecture docs

by jerand » Thu, 22 Jan 2009 09:59:53 GMT

 Basically i need to find information on how the various components are
attached together and how the scheduling of the components happen.
Possibility of prioritizing my components task and so on..


PV Open Core architecture docs

by rktb » Thu, 22 Jan 2009 11:54:44 GMT

 There have been earlier posts related to this. Please go through them
and then post specific questions.



PV Open Core architecture docs

by jerand » Thu, 22 Jan 2009 15:07:11 GMT

 from the earlier replies, I understand that the scheduler relinquishes
control on completing its task. i would like to know how different
nodes that get attached are categorized within the scheduler.

1. For instance, certain nodes which give data to sink nodes have to
processed first to avoid
   starvation while others need to be scheduled more frequently to
take data from a buffer/ network
   so on. So based on this can you explain how different nodes get
attached to the scheduler ?

2 .Is there a way to prioritize my task nodes attached with the
scheduler ?

3. Does the scheduler follow FIFO policy ?

4. Is there a limitation on the number of task nodes that can be
attached with the scheduler ?

5. if am using seperate threads instead using of PV scheduler, what
priority should I give for the same ? What are the effects on using
the same priority as that of scheduler thread ?

6. Where can i find the scheduler code ?

PV Open Core architecture docs

by giri » Mon, 26 Jan 2009 19:57:56 GMT

 Every component that uses the scheduler is an active object. So a node
is an active object. Or in other words scheduler maintains a prority
queue of various AOs and schedules various active objects from that
priority queue. Each active object in its implementation adds /
removes itself to scheduler queue. Implementations can also set
priorities for active objects. Scheduler does not interrupt an AO but
it does take into account priorities of AOs while scheduling.
Scheduler does follow FIFO among AOs that have the same priority.


Other Threads

1. LayoutInflater.inflate

the method has 3 parameters.and I'm confused by the second and the
  I read api.
  root Optional view to be the parent of the generated hierarchy (if
attachToRoot is true), or else simply an object that provides a set of
LayoutParams values for root of the returned hierarchy (if
attachToRoot is false.)
attachToRoot Whether the inflated hierarchy should be attached to the
root parameter? If false, root is only used to create the correct
subclass of LayoutParams for the root view in the XML.

     I know when the attackToRoot is true.then the root will be parent
of the items in the xml. but what would happend when the attackToRoot
is falase? it's just take the values form xml and don't create any


2. full time computer jobs delhi, mumbai, bombay - search for ...

full time computer jobs delhi, mumbai, bombay - search for ...
full time computer jobs delhi, mumbai, bombay, full time work,
 permanent part time work,
 contract work.
Jobs in India - Computer,software jobs in India Bangalore,Mumbai ...
Search jobs in India, career by location at India, Bombay,Delhi,Pune,
Hyderabad,Nagpur,Coimbatore. Employers
can post vacancy for careers in management ...


3. Desktop,laptop computers and digital camera's

4. install Android app from Gmail

5. Pitch Change

6. Android devices

7. the method LayoutInflater.inflate