Hi, I'm not quite sure, if this is the right place to ask this, so apologies, if it is not.
I'm working on a froyo image for a multimedia set top box. The original image comes with a customized mplayer, which has hardware support for SoC. The Android multimedia frameworks (audio/video) are completely bypassed and all playback is done with this mplayer. To make it even worse, mplayer is compiled with OSS instead of ALSA. My medium term goal is, to integrate alsa with dmix support in the android platform and compile mplayer with alsa support, so that both android and mplayer can play concurrently. In the meantime I want to change smaller things on the original image (mostly UI,UX). So I'm thinking of having two branches. One for the original and slightly improved image and one for the bigger alsa changes. The alsa branch would have some other git repositories than the original one, for example the alsa stuff. Furthermore some git projects might need to have its own branch for the alsa implementation (mplayer for alsa output, bionic for shared memory, etc.). So, to switch between the original branch and the alsa branch, I had to switch the branch of some git repositories and there would be some repositories, which are exclusive for the alsa branch. Can I achieve this with repo? Is this just a matter of starting a alsa topic branch with repo? Could you please describe, how you would setup the android platform for this? Any hints are appreciated. Cheers, Henrik P.S. Does it make sense to define two different products for this scenario? -- -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting --- You received this message because you are subscribed to the Google Groups "android-porting" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
