Project

General

Profile

Upstream » History » Version 27

Denis 'GNUtoo' Carikli, 06/17/2018 09:28 AM
Add other devices for reference

1 12 Denis 'GNUtoo' Carikli
h1. Upstream Linux
2 1 Denis 'GNUtoo' Carikli
3 11 Denis 'GNUtoo' Carikli
h2. Benefits of using Upstream Linux
4 2 Denis 'GNUtoo' Carikli
5 11 Denis 'GNUtoo' Carikli
Currently, Replicant uses device specific Hardware Abstraction Layers, because device manufacturers implemented non-standard kernel interfaces. However, Android works with upstream kernels and supports plug-n-play hardware nowadays, so it makes sense to have generic Hardware Abstraction Layers for the standard interfaces of the Linux kernel (ALSA, V4L2, etc).
6 2 Denis 'GNUtoo' Carikli
7
Benefits:
8
* It would allow supporting external WiFi dongles such as the ones supported by the ath9k_htc driver and free firmwares without the need for a specific application or configuration.
9 11 Denis 'GNUtoo' Carikli
* It would make devices last longer by alleviating the device specific maintenance burden: If LineageOS stops supporting a Replicant supported device, Replicant would need to maintain it by its own. This would require a lot of work, unless the device is already supported the upstream Linux kernel and generic hardware abstractions layers. This would enable Replicant to support devices that are not currently supported by LineageOS.
10
* It would enable the support for devices that are or will be added to upstream Linux.
11 2 Denis 'GNUtoo' Carikli
12 22 Denis 'GNUtoo' Carikli
As GNU/Linux expects standard kernel interfaces, this would also enable to run GNU/Linux out of the box on such devices.
13
This has some interesting outcomes:
14
* The device specific work could be shared between GNU/Linux communities and Replicant communities. This could result in less work to do to support individual devices. Since Android libraries depends on Android's libc, non-standard proprietary libraries might be harder to reuse than the free software implementations.
15
* It would enable GNU/Linux distributions to more easily support smartphones and tablets, which would hopefully enable FSDG distributions to be as usable as Replicant. This way, if one day Android devices stop using the Linux kernel or if the code takes directions that is too much problematic, having an Android alternative that is based on GNU/Linux would be easier.
16 23 Denis 'GNUtoo' Carikli
* Older devices with less amount of RAM than Replicant current minimum requirements could be used with GNU/Linux and possibly repurposed for other usages, reducing the amount of electronic devices waste.
17 22 Denis 'GNUtoo' Carikli
18 2 Denis 'GNUtoo' Carikli
h2. Requirements
19
20
* Adding a generic WiFi HAL for external dongles only requires a device that is supported by Replicant, and that can provide enough power for the dongle.
21 11 Denis 'GNUtoo' Carikli
* For the other standard interfaces (like ASLA, etc) a device running a upstream Linux Kenrel with as few patches as possible is required.
22 2 Denis 'GNUtoo' Carikli
23 4 Denis 'GNUtoo' Carikli
h2. Devices
24
25 5 Denis 'GNUtoo' Carikli
It is best to use a device that requires the least amount of work to be functional under Replicant.
26
More precisely we want to minimize:
27 11 Denis 'GNUtoo' Carikli
* The work needed to have the device usable with upstream Linux.
28 5 Denis 'GNUtoo' Carikli
* The work porting or writing Android hardware abstractions layers.
29
30
To achieve that we can choose a device that:
31
* requires no or very minimal work to be fully supported by Linux.
32
* have less hardware features (so we don't need to support them in Linux and in the HALs).
33
* is easy to buy, so the work can be shared among multiple people.
34
35 6 Denis 'GNUtoo' Carikli
It is also a good idea to keep one image per device, as trying to make a single image that
36 11 Denis 'GNUtoo' Carikli
would work on all ARM device supported by upstream Linux is complicated: Even ARM GNU/Linux
37 6 Denis 'GNUtoo' Carikli
distributions still have some issues with that.
38
39 11 Denis 'GNUtoo' Carikli
h3. Smartphones and tablets with a free software bootloader and work in progress upstream Linux support
40 4 Denis 'GNUtoo' Carikli
41 24 Denis 'GNUtoo' Carikli
|_. Device |_. Linux dts | comments |
42 25 Denis 'GNUtoo' Carikli
| Optimus Black | "omap3-sniper.dts":https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/omap3-sniper.dts | no display(no driver), very few peripherals |
43 26 Denis 'GNUtoo' Carikli
| Amazon Kindle Fire (first generation) | "omap4-kc1.dts":https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/omap4-kc1.dts | no display(no driver), very few peripherals |
44 14 Denis 'GNUtoo' Carikli
45 4 Denis 'GNUtoo' Carikli
h3. Replicant supported Samsung Exynos devices
46
47 26 Denis 'GNUtoo' Carikli
|_. Device |_. Linux dts |
48
| i9100 (Galaxy S II)  | "exynos4210-trats.dts":https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/exynos4210-trats.dts  |
49
| i9300 (Galaxy S III) | "exynos4412-trats2.dts":https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/exynos4412-trats2.dts |
50 1 Denis 'GNUtoo' Carikli
51 27 Denis 'GNUtoo' Carikli
h3. Other devices with some upstream support.
52
53
|_. Vendor |_. Product |_. Linux dts | Linux status page | Issues |
54
| Nokia | N900 | | https://elinux.org/N900 | Has a signed bootloader |
55
| Nokia | N9 | "omap3-n9.dts": https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/omap3-n9.dts | https://elinux.org/N9 | Probably has a signed bootloader |
56
| Nokia | N950 | "omap3-n950.dts":https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/omap3-n950.dts | https://elinux.org/N950 | Probably has a signed bootloader |
57
58
59 1 Denis 'GNUtoo' Carikli
h3. Allwinner devices
60 13 Denis 'GNUtoo' Carikli
61
Devices with Allwinner SOCs are an interesting targets because:
62
* Many of them do not use signed bootloaders.
63
* Many of the SOCs and various devices using them have good Linux and u-boot mainline support
64
65
For instance the Lime 2 from Olimex is pretty well supported and is easy to find.
66
However this device is a single board computer and, as such it doesn't have the have the usual peripherals that are commonly found in tablets and smartphones. This makes a port on this device less relevant and less useful.
67
68
Some research is needed to identify which devices are easiest to work with. Tablets that don't have a modem seem to be better than smartphones, as supporting the modem would require to have it supported in Linux and the userspace libraries. This might even require to write and upstream a Linux driver for the modem.
69
70
A good tablet for this task should have:
71
* A SOC that has good mainline support, see "the Linux mainlining effort page on linux-sunxi":https://linux-sunxi.org/Linux_mainlining_effort for more details.
72
* A Free software bootloader, or the ability to easily add support for the tablet to a free software bootloader.
73
* The ability to power and use an USB WiFi card or chip that is compatible with the ath9k_htc driver.
74
75
It would also be better if the chosen tablet doesn't use an AllWinner SOC with a PowerVR GPU, as MALI GPU have more probability to be usable with free software in the future.
76 1 Denis 'GNUtoo' Carikli
77
h2. See also
78
79
* [[Google Summer of Code 2018]]
80 12 Denis 'GNUtoo' Carikli
81 19 Denis 'GNUtoo' Carikli
h1. Userspace
82
83
h2. Upstream userspace hardware support libraries
84 1 Denis 'GNUtoo' Carikli
85 17 Denis 'GNUtoo' Carikli
|_. Usage |_. Replicant |_. GNU/Linux |_. comments |
86
| Bluetooth stack | BlueDroid | Bluez | |
87 16 Denis 'GNUtoo' Carikli
88 20 Denis 'GNUtoo' Carikli
h2. Upstream non-hardware specific userspace
89 18 Denis 'GNUtoo' Carikli
90
|_. Usage |_. Replicant |_. GNU/Linux |_. comments |
91
| Unix command line tools | ? | Busybox, Coreutils | |