Le 04/12/2015 19:54, Adam Farden a écrit :
> 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

Juan stopped working on that one

> Galaxy Nexus

That just got working again

> Nexus S

Still requires some local patches and still the laggy feeling even if
nothing looks bad profile wise

> flo (Nexus 7)

No idea

> 
> otoro
> unagi
> inari

Those three are early devices close to ZTE OPEN

> keon
> peak

Devices from Geeksphone. Community still use it

> hamachi

TCL Fire, still being hacked by community

> helix

I don't know what that one is

> tarako

Well known low cost device, I don't know the status but I think bad

> dolphin

I don't remember that one

> pandaboard

Development board, used in the early days, maybe thomas knows the status?

> vixen

An aborted tablet I think?

> flatfish

Another tablet that we dropped

> rpi

Well known Raspberry Pi

> 
> 
> _______________________________________________
> dev-fxos mailing list
> dev-fxos@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-fxos
> 

_______________________________________________
dev-fxos mailing list
dev-fxos@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-fxos

Reply via email to