Hi Adam. I support your idea, I'm trying to give some support to old devices but is a little annoying because usually have a lot of troubles, actually I have a Hamachi, Inari, Keon, Peak and Flatfish. From the branch 2.5 I just can compile for Hamachi and Keon, so your idea would be great to continue the support for those devices.
Regards! Date: Fri, 4 Dec 2015 19:54:41 +0100 Subject: Legacy devices and what to do with them From: [email protected] To: [email protected] When 2.5 was forked we had some minor trouble with several manifests being removed for active devices. I am looking at the list of build targets in config.sh and sure enough, it is impossible to see which devices are still relevant. I'd like to reorganize this list according to base AOSP version (determined by its manifest) so it is easier to see how 'old' a specific port is, and move any devices that cannot build on Gecko master to a config-legacy.sh I believe anything pre JB is not working on Gecko master, is that correct? I'd also like any specific info on the below devices, as I don't know anything nor do I hear anything about these devices. Are they at all used? Are they legacy? Are they abandoned? Galaxy S2 Galaxy Nexus Nexus S flo (Nexus 7) otoro unagi inari keon peak hamachi helix tarako dolphin pandaboard vixen flatfish rpi _______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
