View Single Post
Posts: 1,203 | Thanked: 3,027 times | Joined on Dec 2010
#26
Originally Posted by joerg_rw View Post
not experimental, but yes, all /porting/* branches are supposed to be relatively identical components in there and hw specific. I don't think we want to follow the mainline kernel path to have universal sources so the code can run on every arbitrary hw platform, rather we might need an adapted MCE, PA/ALSA, whatnot else variant for each device, and we keep all those (obviously non-blob aka FOSS) variants in their according branches of /porting/* repos. For N900 it would contain only FOSS replacements of blobs, for other targets it may also contain hw-specific variants of already opensource bits
I used "experimental" just to identify development as being separate from what current every day users would be running at the moment. Not really best choice of word.

So if I get your meaning correctly:

Porting/ - Modifed packages to depend on virtual package for hw feature, eg. cam-firmware
Porting/N900 - N900-cam-firmare with provide: cam-firmware
Porting/Neo - Neo-cam-firmare with provide: cam-firmware
Porting/...
 

The Following User Says Thank You to Android_808 For This Useful Post: