![amlogic s905 vs allwinner a64 amlogic s905 vs allwinner a64](https://s.alicdn.com/@sc04/kf/Hd01a0b80f4604599a19b7f62f56025fbn.jpg)
- Amlogic s905 vs allwinner a64 how to#
- Amlogic s905 vs allwinner a64 drivers#
- Amlogic s905 vs allwinner a64 update#
- Amlogic s905 vs allwinner a64 software#
Lastly it does have to be pointed out that Rockchip are not *actively* involved (with the exception of one employee), in supporting or endorsing cooperation, collaboration or any other form of active participation with the Software Libre Community. The developer board of choice at the moment for the RK3288 is the Firefly. The best resource on the RK3288 is therefore the #linux-rockchip freenode channel, which is populated by technically well-informed individuals.
Amlogic s905 vs allwinner a64 how to#
Actual useful resources such as how to boot the processor from scratch over its USB-OTG interface with an entirely libre toolchain, not requiring any proprietary crud at all or requiring any google-sponsored tools, processes or procedures (mandatory use of UEFI boot partitions for example), are completely drowned out by wordpress postings of yet another person's "recipe for installing ".
![amlogic s905 vs allwinner a64 amlogic s905 vs allwinner a64](https://androidtvbox.eu/wp-content/uploads/2015/09/Hisilicon-HI3798C-V2001.jpg)
The only down-side of the popularity of the RK3288 from the google "chrome" bandwagonning effect is the sheer overwhelming amount of crap that people come up with and post online, making it much harder to find useful information than it really should be. Towards the end of 2016 a chinese software libre developer working for Rockchip was permitted to release a gstreamer plugin and associated v4l2 kernel modifications sufficient to have an entirely libre video decode engine up and running. It has been around long enough that the rockchip linux community has had time to get both its boot process reverse-engineered (without needing proprietary tools), as well as get both u-boot and linux kernel mainline upstream support for all features. The RK3288 has had considerable adoption by google partners for use in Chromebooks. Open source code, no licensing issues or good docs are availableĪctively fighting/colliding with open source
![amlogic s905 vs allwinner a64 amlogic s905 vs allwinner a64](https://androidpctv.com/wp-content/uploads/2020/03/amlogic-s905x4-vs-s905x3-n02-min.jpg)
Amlogic s905 vs allwinner a64 drivers#
Good support by community (well working drivers in mainline kernel) Good support by maker (well working drivers in mainline kernel) If you can, please add _popular_ SoCs (those from RPi 1/2/3, amlogic, rockchip, samsung, marvel, qualcomm, intel etc.).Īdopted by google partners in chromebooks, resulting in good license compliance Shall this table focus on particular SoCs? Group similar tier socs? for TL DR people), with notes and examples explained later in the page.
Amlogic s905 vs allwinner a64 update#
Please add more makers, references, update missing fields, etc.
![amlogic s905 vs allwinner a64 amlogic s905 vs allwinner a64](https://www.cnx-software.com/wp-content/uploads/2019/07/Amlogic-S905X2-vs-S905X3.jpg)
I thought it was a good solution to reduce the probability of corrupting the root partition.Īlso, I just put to try to make an initramfs work, do I have to keep anything in mind? If run initramfs at boot, I'll can to run fcsk over rootfs if is corrupt, right? And, after that, run the "normal" kernel.Note: work-in-progress. Now, thanks to you I have realized that I have to eliminate a third partition created for me to save some logs when I move it from ram to sd card. I don't remember if I adding some little thing, but test a lot of them. root partition noatime,nodiratime,data=writeback,discard,errors=remount-ro 0 0). In production scenarios I included improvements like locating logs in ram (/var/log), logrotate with compression every night and reduce permanent writes setting up in fstab (e.g. (useless list since as Zador and me already explained it's more related to software/settings: high commit interval, reducing permanent writes, ability to do a fsck at boot)Ī long list of device!! No doubt you know many SBC What other SBC did you used without corruption errors?