Differences between revisions 27 and 28
Revision 27 as of 2015-03-16 11:55:01
Size: 4837
Editor: HolgerLevsen
Comment: add link to new page
Revision 28 as of 2015-03-20 21:22:29
Size: 4837
Comment:
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
Generally, your best bet is to use [[http://www.raspbian.org/|Raspbian]] - which is (mostly) Debian armhf rebuilt by members of Debian for the RPi's ARMv6+VFP2 ARM variant. Raspbian releases usually follow the corresponding debian release but do deviate in a handful of cases for various reasons. Generally, your best bet is to use [[http://www.raspbian.org/|Raspbian]] - which is (mostly) Debian armhf rebuilt by members of Debian for the RPi's ARMv6+VFP2 ARM variant. Raspbian releases usually follow the corresponding Debian release but do deviate in a handful of cases for various reasons.
Line 12: Line 12:
Be aware that the raspbian images distributed by the raspberry pi foundation contain additional packages supplied by them including updated versions of some software and the addition of non-free software including Oracle Java and Wolfram Mathematica. Be aware that the Raspbian images distributed by the Raspberry Pi Foundation contain additional packages supplied by them including updated versions of some software and the addition of non-free software including Oracle Java and Wolfram Mathematica.
Line 25: Line 25:
 * Large and active community.  * Large and active community
Line 29: Line 29:
 * The Raspberry Pi 1's processor falls uncomfortably between the processor families that Debian has chosen to target. While Raspbian solves this to some degree an unofficial port will always give less certainty than an official one. (This does not count for the Raspberry Pi 2.)
 * 3D acceleration is not integrated with X or other standard mechanisms and the Raspberry pi foundation don't seem to show any interest in doing so. Therefore 3D applications will require Pi specific builds.
 * The Raspberry Pi 1's processor falls uncomfortably between the processor families that Debian has chosen to target. While Raspbian solves this to some degree an unofficial port will always give less certainty than an official one. (This doesn' stand anymore for the Raspberry Pi 2)
 * 3D acceleration is not integrated with X or other standard mechanisms and the Raspberry Pi Foundation don't seem to show any interest in doing so. Therefore 3D applications will require Pi specific builds.
Line 47: Line 47:
 * The CPU in the Raspberry Pi 1 implements the ARMv6 ISA (with VFP2) and is thus incompatible with the Debian armhf port baseline of ARMv7+VFP3 and ARM hardware-floating-point ports for other distributions, which all have the same baseline. It is compatible with Debian armel (armv4t, soft(emulated) FP), but floating-point tasks will be slow when running the Debian armel port. (This does not count for the Raspberry Pi 2.)
 * The Raspberry Pi boots from its GPU and only non-free software is currently available for the GPU, even starting the machine requires a large (2MB) blob of non-free, unsupportable software.
 * The 3D driver for the Raspberry Pi, while free software, is just a shim that passes OpenGL commands directly to the non-free software running on the GPU. This means that any issues with OpenGL cannot be fixed nor performance improved. This is better than some other GPUs because the ARM part can be rebuilt. More recently an alternative driver has become available that drives the 3D core in the GPU directly from the arm rather than passing messages to the VPU core in the GPU which in turn drove the 3D core.
 * The CPU in the Raspberry Pi 1 implements the ARMv6 ISA (with VFP2) and is thus incompatible with the Debian armhf port baseline of ARMv7+VFP3 and ARM hardware-floating-point ports for other distributions, which all have the same baseline. It is compatible with Debian armel (armv4t, soft(emulated) FP), but floating-point tasks will be slow when running the Debian armel port. (This doesn't stand for the Raspberry Pi 2)
 * The Raspberry Pi boots from its GPU and only non-free software is currently available for the GPU, even starting the machine requires a large (2MB) blob of non-free, unsupportable software
 * The 3D driver for the Raspberry Pi, while Free Software, is just a shim that passes OpenGL commands directly to the non-free software running on the GPU. This means that any issues with OpenGL cannot be fixed nor performance improved. This is better than some other GPUs because the ARM part can be rebuilt. More recently an alternative driver has become available that drives the 3D core in the GPU directly from the ARM rather than passing messages to the VPU core in the GPU which in turn drove the 3D core.
Line 53: Line 53:
The binary blob needed to boot the Raspberry Pi can be downloaded using the rpi-update script available from https://raw.githubusercontent.com/Hexxeh/rpi-update/master/rpi-update . It can be used with vmdebootstrap to create a bootable SD card image, according to The binary blob needed to boot the Raspberry Pi can be downloaded using the rpi-update script available from https://raw.githubusercontent.com/Hexxeh/rpi-update/master/rpi-update. It can be used with vmdebootstrap to create a bootable SD card image, according to

Can I put Debian on my Raspberry Pi?

Yes.

Raspberry Pi 1 (A, B, A+, B+)

Debian armel will work (with a custom kernel), but will not make best use of the floating point hardware. Debian armhf will not work (see below).

Generally, your best bet is to use Raspbian - which is (mostly) Debian armhf rebuilt by members of Debian for the RPi's ARMv6+VFP2 ARM variant. Raspbian releases usually follow the corresponding Debian release but do deviate in a handful of cases for various reasons.

Be aware that the Raspbian images distributed by the Raspberry Pi Foundation contain additional packages supplied by them including updated versions of some software and the addition of non-free software including Oracle Java and Wolfram Mathematica.

Raspberry Pi 2

Debian armhf will work (with a custom kernel). See the blog posting Debian Jessie on Raspberry Pi 2 by Sjoerd Simons of Collabora for details.

RaspberryPi2 aims to collect information how to run Debian nicely on this hardware.

Should I buy a Raspberry Pi?

That is a decision that you will have to make given your application, below are some pros and cons that you should consider.

Pros:

  • Large and active community
  • Low price for the capabilities offered

Cons:

  • The Raspberry Pi 1's processor falls uncomfortably between the processor families that Debian has chosen to target. While Raspbian solves this to some degree an unofficial port will always give less certainty than an official one. (This doesn' stand anymore for the Raspberry Pi 2)
  • 3D acceleration is not integrated with X or other standard mechanisms and the Raspberry Pi Foundation don't seem to show any interest in doing so. Therefore 3D applications will require Pi specific builds.
  • A binary blob used by the GPU must be present on the SD card for the system to boot.
  • While some hardware documentation has been released the documentation is sorely lacking.
  • While schematics are available the board design is closed and the main processor is not available for purchase by the general public.

A number of similar boards are available, generally at slightly higher prices but also usually with more powerful processors. Some examples are given below, more can be found in the FreedomBox targetted hardware list.

Raspberry Pi issues

The Raspberry Pi issues relate to technical problems, software freedom and hype:

  • The CPU in the Raspberry Pi 1 implements the ARMv6 ISA (with VFP2) and is thus incompatible with the Debian armhf port baseline of ARMv7+VFP3 and ARM hardware-floating-point ports for other distributions, which all have the same baseline. It is compatible with Debian armel (armv4t, soft(emulated) FP), but floating-point tasks will be slow when running the Debian armel port. (This doesn't stand for the Raspberry Pi 2)
  • The Raspberry Pi boots from its GPU and only non-free software is currently available for the GPU, even starting the machine requires a large (2MB) blob of non-free, unsupportable software
  • The 3D driver for the Raspberry Pi, while Free Software, is just a shim that passes OpenGL commands directly to the non-free software running on the GPU. This means that any issues with OpenGL cannot be fixed nor performance improved. This is better than some other GPUs because the ARM part can be rebuilt. More recently an alternative driver has become available that drives the 3D core in the GPU directly from the ARM rather than passing messages to the VPU core in the GPU which in turn drove the 3D core.

Binary blob needed to boot

The binary blob needed to boot the Raspberry Pi can be downloaded using the rpi-update script available from https://raw.githubusercontent.com/Hexxeh/rpi-update/master/rpi-update. It can be used with vmdebootstrap to create a bootable SD card image, according to a recipe from Petter Reinholdtsen. No known effort to reverse engineer the blob is known as of 2013-10-30.