Out of the box, Slackware ARM officially supports these systems:
Starting with Slackware ARM v14.0, packages are compiled for the following minimum target:
This means that the user space will run on the majority of ARM 32-bit devices on the market today.
Unlike the x86, usually each type of ARM device requires a specific kernel. So even on an "unsupported" ARM device, the majority (if not all) Slackware ARM packages will run on the device, you will need a specific Linux kernel for your device. Please read this article for a great introduction to this topic.
Much of the good well written documentation about ARM and Linux comes from the Debian developers.
Please read the following documents to learn more about Linux and ARM in general.
The number of officially supported devices on which Slackware ARM has been tested and can be installed "out of the box" is limited due to the number of ARM devices, availability of developer time and access to the hardware.
However, because the Slackware ARM packages have been compiled to run on most of the systems available today, usually all that is required is a new Kernel which can be "cross-compiled" by the user and some tweaking of the device's boot loader.
The Slackware ARM community have helped fill the void by providing installation documentation and other useful notes to help other users install Slackware onto these devices.
A community supported device is essentially an "overlay" to the Slackware ARM tree, and typically conforms to the following rules:Instructions and packages:
• Provides its own installation instructions
• Provides its own Kernel package(s)
• May (if applicable to the particular ARM device) provide its own Slackware Installer image, or provide a modified "miniroot"
• May provide additional packages specifically required to present a full Slackware experience (examples include graphics drivers and supporting libraries for those, but not anything else that isn't absolutely essential to the operation of the target hardware)
• May provide replacments of a very small number of Slackware ARM base packages in the case where there are some build-time changes required that cannot be incorporated into the official packages. Any such changes are due to the sole reason that without them, the OS cannot be properly used - choices of configuration based on the author's personal preferences are forbidden, as this constitutes a 'fork' which is not aligned with Slackware. Changes required to the Slackware packages should be posed to the Slackware ARM forum as they may be able to be incorporated into the base packages
• Uses all of the Slackware ARM binary packages, apart from exceptions as described above
Essentially, A Community Supported Device must have only a very minimal change set from the Slackware ARM official tree in order to be considered associated with Slackware ARM. For example: anybody making their own ARM port based on the Slackware ARM package build scripts (re-built for another base CPU architecture for example) does not meet the requirements to be considered in anyway attached to the official Slackware ARM port. This is purely because Patrick Volkerding has entrusted his brand name 'Slackware' to be associated with Slackware ARM, and as such every care is taken with the official port to adhere to its standards of quality. With a Community Supported Device adhering to the guidelines above, the risks of standards and quality concerns are limited to an acceptable degree.Help and support
Users of a Community Supported Device can raise questions on the Slackware ARM forum on LinuxQuestions.org, but should also consult the documentation
provided for that platform, as there may be a better or more appropriate place to send questions.