[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
slackwarearm:faq [2017/08/10 08:59 (UTC)] mozesslackwarearm:faq [2017/11/15 09:16 (UTC)] (current) – Added FAQ about detecting soft vs hard float mozes
Line 21: Line 21:
  
 A.  This question is often asked in reference to the Raspberry Pi, which by far has the most wide spread mind share. A.  This question is often asked in reference to the Raspberry Pi, which by far has the most wide spread mind share.
-Slackware ARM is developed by one person whose interest in ARM is very specific.  ARM devices have to have Real Time Clocks, preferably SATA support and most importantly have support in the mainline Kernel.  It's impossible to progress an Operating System if you're tied to a specific version of the Kernel (even if it's for a short period) because it slows down the development cycle.+Slackware ARM is developed by [[http://www.slackware.com/~mozes/|one person]] whose interest in ARM is very specific.  ARM devices have to have Real Time Clocks, preferably SATA support and most importantly have support in the mainline Kernel.  It's impossible to progress an Operating System if you're tied to a specific version of the Kernel (even if it's for a short period) because it slows down the development cycle.
 In addition, the devices targeted for "official" support (devices supported directly from the Slackware ARM tree) need to be open and not require propitiatory/licenced firmware and hacking in order to permit boot of an alternative OS. In addition, the devices targeted for "official" support (devices supported directly from the Slackware ARM tree) need to be open and not require propitiatory/licenced firmware and hacking in order to permit boot of an alternative OS.
 The Slackware ARM community fills in gaps where there is demand. The Slackware ARM community fills in gaps where there is demand.
Line 65: Line 65:
  
 A. Slackware ARM used ScratchBox back in 2002 to originally build the first batch of packages in order to bootstrap the port, and some effort was made in producing scripts to help setup a Slackware-like environment. However, this work was abandoned shortly after the port was able to be self supporting. A. Slackware ARM used ScratchBox back in 2002 to originally build the first batch of packages in order to bootstrap the port, and some effort was made in producing scripts to help setup a Slackware-like environment. However, this work was abandoned shortly after the port was able to be self supporting.
 +
 +==== 3rd party SlackBuild scripts ====
 +
 +//Q. As a maintainer of SlackBuild scripts, how can I differentiate between Slackware 14.2 (Software Floating Point) and Slackware 15.0 (Hardware Floating Point) and greater?
 +//
 +
 +A. [[http://armed.slackware.com/scripts/cflagsarm|This code snippet]] checks the target quadlet from gcc and sets the default compiler flags.
  
 ==== Cross compiling software ==== ==== Cross compiling software ====
 slackwarearm:faq ()