Add patch to bring A64 pinctrl driver inline with other sunxi pintctrl drivers by disabling strict mode. With kernel 4.15.y (and later): * Strict mode was enabled by default via commit 1396007286b1e2fd5dd10ae6a5ccaaaed51ab762 which can/will cause breakage with existing implementations. * The ability to configure strict mode was added via commit aae842a3ff3385f27f1df8a9ee1494a416ec032d to allow older drivers to maintain existing behavior and avoid breakage. * Commit cd70387f892205bcd7b8093b0837269b0739cbe0 had then explicitly disabled strict mode for most other existing SoCs but did not include A64. This change is to update the A64 pinctrl driver similar to the other pre-existing SoC pinctrl drivers. |
||
|---|---|---|
| .github | ||
| config | ||
| lib | ||
| packages | ||
| patch | ||
| .dockerignore | ||
| .gitignore | ||
| compile.sh | ||
| config-docker.conf | ||
| config-vagrant.conf | ||
| Dockerfile | ||
| LICENSE | ||
| main.sh | ||
| README.md | ||
| Vagrantfile | ||
Armbian
Debian based Linux for ARM based single-board computers
How to build an image or a kernel?
Supported build environment is Ubuntu Bionic 18.04 x64 (minimal iso image).
- guest inside a VirtualBox or other virtualization software,
- guest managed by Vagrant. This uses Virtualbox (as above) but does so in an easily repeatable way,
- inside a Docker, systemd-nspawn or other container environment (example),
- running natively on a dedicated PC or a server (not recommended),
- 25GB disk space or more and 2GB RAM or more available for the VM, container or native OS,
- superuser rights (configured
sudoor root access).
Execution
apt-get -y install git
git clone https://github.com/armbian/build
cd build
./compile.sh
Make sure that full path to the build script does not contain spaces.
You will be prompted with a selection menu for a build option, a board name, a kernel branch and an OS release. Please check the documentation for advanced options and additional customization.
Build process uses caching for the compilation and the debootstrap process, so consecutive runs with similar settings will be much faster.
How to report issues?
Please read this notice first before opening an issue.
How to contribute?
- Fork the project
- Make one or more well commented and clean commits to the repository.
- Perform a pull request in github's web interface.
If it is a new feature request, don't start the coding first. Remember to open an issue to discuss the new feature.
If you are struggling, check this detailed step by step guide on contributing.