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.

-Ravi




--~--~---------~--~----~------------~-------~--~----~



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. the detail source code for getFromLocation

hello guys,

is the Android source code have detail code for
GeoCoder.getFromLocation() method(how to implement and work)??
I just find GeoCoder.java(/home/stanly/mydroid/frameworks/base/
location/java/android/location) and ILocationManager.aidl(/home/stanly/
mydroid/frameworks/base/location/java/android/location)

can somebidy help me??

thanks

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: 

2. Quick Yes/No question about the UI thread during a screen rotation

Hello,

Am I correct in assuming that any callbacks of the AsyncTask that are
run on the UI thread (e.g. onPostExecute) are 'queued' during a screen
rotation?

Example:
1. an AsyncTask is executed
2. a screen rotation is initiated
3a. AsyncTask's doInBackground() finishes, or
3b. AsyncTask's publishProgress() is called before the rotation is
done
--- now what happens here? is it
4. screen rotation is completed before the 'pending'
AsyncTask.onPostExecute/onProgressUpdate is run?

I assumed so, since looking at DDMS, it seems like the rotation does
NOT create a new UI thread, in which case any calls to the UI must be
stalled while the UI thread is busy completing the rotation, right?

It would be great if this was true, since it would save me from having
to do a bunch of synchronization work for posting back from AsyncTasks
(I am keeping the tasks running during a rotation) - at least so I
think..

Thank you for any tips on this,

-szabolcs

--~--~---------~--~----~------------~-------~--~----~

3. How to output the log when boot?

4. Halt the Target VM, my app becomes unstable

5. Anyone else notice more frequent GC in 1.6?

6. Eclipse is stuck at "Android SDK Content Loader 60%"

7. HttpURLConnection