On Tuesday 11. June 2019 14.54.36 H. Nikolaus Schaller wrote: > > Maybe you could also try the letux tree. The idea of the letux tree is that > we can collaborate on it and contribute good things to kernel.org if we are > successful.
I'll put the CI20 to work on it as soon as it is finished building a Raspberry Pi Zero toolchain that maybe will work this time. Since my hardware tends not to withstand the weight of these repositories under Git management, I will download the snapshot of the tree from the appropriate page: http://git.goldelico.com/?p=letux-kernel.git;a=snapshot;h=refs/heads/letux-5.1.8;sf=tgz > The main benefit I see in using the letux tree is that we support several > almost identically configured ARM boards for comparisons. So you can easily > find out if it is configuration or driver code or device tree or user-space > or specific to some SoC model. > > This makes doing cross-checks between them much easier than trying different > trees you find in github etc. Indeed. Linux kernel development is like the Wild West with all these different repositories all over GitHub and the Internet. Microsoft's servers must be full of Linux kernel source tree copies. > And my dream is to have a single patch set for PVR/SGX for ARM and MIPS > which is only in reach within this managed jacket of letuxos kernel and same > tree and config options. One step at a time! ;-) Paul P.S. I know that you weren't too enthusiastic about it, but I changed my makesd variant to use the system definition syntax I mentioned: https://hg.boddie.org.uk/remakesd/file/8e8e8d934afa/makesd-defs More work is needed to support all the features, however. _______________________________________________ Community mailing list Community@tinkerphones.org http://lists.goldelico.com/mailman/listinfo.cgi/community http://www.tinkerphones.org
