9 ms·

Raspberry Pi (2 and 3) support in Fedora 25 Beta

100 points by cheiVia0 10y ago

mwambua 10y ago
I'm pretty excited about this! I started using f22 after using Ubuntu for a number of years, and I was particularly impressed by its package management. I personally find yum/dnf easier to use than apt and slightly more transparent. F24 has been an exceptional release and I look forward to running 25 on a pi. Hopefully we'll have a Pi with better IO by the time it releases. :)
- astrodust 10y ago
  It's nice that it's a unified command (yum vs. apt-get, apt-cache, etc.) and the commands do seem less obtuse. I've been using Fedora since the first cut, and by and large it's always been pretty great. The one thing I'd like to see ported over is ufw, as that's one thing about Ubuntu to envy. firewall-cmd is downright annoying and bizarrely designed.
  - mwambua 10y ago
    I'll agree with you on firewall-cmd. One major problem is its documentation. They should initially provide really simple instructions on getting a base firewall (22,443,80) going... And then provide instructions on how to do zoning and what-not on the side.
    - astrodust 10y ago
      I like the idea of firewalld, but what I don't like is the way you have to do things like --list--all-zones and other nonsense. The end results are good, it's just how you have to implement them that's ridiculous. At least Ansible provides a tidy wrapper for it. git has a reputation for being annoyingly quirky, but firewalld is leaps ahead in terms of marching to the beat of its own drum.
  - andrewchambers 10y ago
    You should give some of the BSD package tools a try for less obtuse package commands.
    - astrodust 10y ago
      Yeah, but then I'd have to go BSD, which at this point is really going to be an obstacle.
  - seanp2k2 10y ago
    IMO just learn the real iptables commands. They're seriously one-liners with just a few args, and then you'll know how to set up a basic firewall on most distros. https://fedoraproject.org/wiki/How_to_edit_iptables_rules https://fedoraproject.org/wiki/How_to_edit_iptables_rules is the fedora guide. There are others. Here's how to disable firewalld: https://fedoraproject.org/wiki/FirewallD#Using_static_firewall_rules_with_the_iptables_and_ip6tables_services https://fedoraproject.org/wiki/FirewallD#Using_static_firewa... Note here that if everyone just spent the 5 minutes it takes to learn the few basic iptables commands, we wouldn't have ufw and firewalld and firehol and vuurmuur and Crazy Bob's Super Simple VBA-to-XML iptables rule generator. Every attempt at making iptables "easy", I consider harmful, as it's a basic systems administration skill that people continually hurt themselves by not learning. iptables is not hard, but all of these wrappers make it hard by introducing their own dumb syntax while adding complexity and quashing any hope of a standard interface between distros to control networking rules, which iptables already was before they tried to "fix" it.
    - cheiVia0 10y ago
      iptables is obsolete btw, Linux kernel developers replaced it with nftables.
      - Nux 10y ago
        From their docs, nftables is "available upstream since Linux kernel 3.13. It supports 3/4 of the existing iptables features" - 3/4 is still a long way to obsoleting iptables.
    - beagle3 10y ago
      I used to hold the same opinion as you, but I've recently changed my opinion of firehol; it's a little higher level than ufw and friends, and highly encourages good practices which are easy to forget or get wrong if you iptables all the way. I've realised that when I noticed that the comments I wrote for others on my iptable configs were comparable in length and content to firehol (but not verifiable or executable). Unlike ufw, firehol actually saved me significant time and effort even though I know (and use) iptables directly.
  - Symbiote 10y ago
    "apt" is the unified command for apt-get etc, since a year or two ago.
  - Narishma 10y ago
    "apt" already combines all those apt-* in one command.
- krylon 10y ago
  > Hopefully we'll have a Pi with better IO by the time it releases. :) Are there any official plans to release a new model with, say, an on-board SSD connector or SATA port? Or is this just "Hopefully" as in "Hopefully it stops raining before I have to walk to the train station"?
  - imtringued 10y ago
    Very likely the latter. All the "innovation" happens in the mobile phone SoC space. My two years old phone is already good enough. Any improvement beyond it is a nice bonus but I could easily live without. Yet the ARM SBCs are so far behind. I'm betting at some point in the future phones have progressed so fast that it's better to just dump them into a server rack with ethernet over USB 2.0 than to actually buy ARM servers.
    - krylon 10y ago
      Yeah, it's a little sad. ARM based servers have been on the horizon for a couple of years now, but they seem to be forever out of reach. :-/
alxmdev 10y ago
Excellent! I tried out Ubuntu MATE 16.04 on a Raspberry Pi 3 a few months ago, and I was pleasantly surprised by how well it runs. The 1GB RAM is an unfortunate limitation, but even so the Pi is a viable little desktop. Great to see upstream kernel support and official releases from major distros.
- swiley 10y ago
  I've done quite a lot of homework on a Pi3 I got for free from someone who didn't want it. They're actually a functional desktop.
  - paulmd 10y ago
    They work as a desktop but you're better off using something designed around the task. SD cards are not really designed for heavy random writes on a long-term basis and can be sensitive to corruption during brownouts that don't necessarily trigger a full system dropout. The GPU was primitive even for its day and has not gotten better with age. There's no SATA or USB 3.0, no GigE, and everything runs across a single USB 2.0 bus. For desktop or server use, the Pi is in the same price range as systems built on laptop chipsets (Kabini, Baytrail/Cherrytrail/Goldmont, etc). These can easily be had for sub-$150 normally and sub-$100 if you shop around. That's about the same price as the Pi once you factor in all the other things you have to purchase to get your "$35 computer" to boot. They are are lot faster and a lot more fully-featured. You can easily get SATA, GigE, USB 3.0, and you can even get ECC RAM on the AM1 platform. Also check out the Liva series from ECS and the ZBOX series from Zotac. Of course if you have the cash you can also look at a NUC or BRIX or other mini-PC but those are aimed a little higher in the market. Also it's kinda sad to hold up an Intel product as a positive example of open source, but it's much better than the Raspberry Pi. You are still reliant on binary blobs to boot the hardware to this day. The graphics stack is open source, the ThreadX-based VideoCore OS RTOS the GPU uses is not, and the documentation/drivers are restricted to usage only on official Raspberry Pi hardware.
    - khedoros1 10y ago
      A lot of people seem to want something like a more-powerful Arduino that they can interface to a few I2C or SPI sensors, run some relays or servos, and embed into a project. Use your old cell phone charger, buy a microSD for $5, borrow a keyboard and some time on an HDMI TV to configure wifi, then just access it through VNC. Before the Pi3 with it's built-in wifi, it was also common to connect the Pi to a laptop with an ethernet cable and access it that way. For some people, one of those cheap X86 systems would make more sense, because they're trying to use it as a desktop or to do something that benefits from a higher-power CPU (real-time object recognition comes to mind). For a lot of others, a little ARM board hits a few important points: it's small, doesn't use much power, is easy to re-flash if it gets corrupted, is actually available in their country, is generally easy to adapt Arduino code to work on, and has a huge community around it focused on learning, experimentation, and building things. There's a nice little niche that it and similar boards fill.
andrewchambers 10y ago
Running plan9 on a raspberry pi 2 is so fast. It ruined linux on a raspberry pi for me, software currently is so heavy weight.
- pjmlp 10y ago
  When I installed GNU/Linux for the first time, a Slackware 2.0 in 1995, I had a Pentium 75 with 4 MB with a 512 MB HD.... Now compare with a PI or the modern GNU/Linux distributions.
- rcarmo 10y ago
  And what do you do to browse the web?
ekianjo 10y ago
Why does every raspberry install recommend dd instead of the cp tool? Cp does the same thing and has a much better syntax.
- snuxoll 10y ago
  GNU coreutils' version of `cp` supports copying to block devices, but not every other implementation does (busybox's doesn't, for example). `dd` is explicitly required to support block devices by the POSIX specification, `cp` is not.
  - ce4 10y ago
    Why not just use cat? cat $image.file > /dev/$BLOCK_DEV
    - snuxoll 10y ago
      cat has issues with partial reads and is not suitable for copying files, let alone images.
- voltagex_ 10y ago
  And if you really get into using a lot of different images, https://source.tizen.org/documentation/reference/bmaptool https://source.tizen.org/documentation/reference/bmaptool is the way to go - uses sparse images correctly. https://github.com/01org/bmap-tools https://github.com/01org/bmap-tools is the maintained version.
TD-Linux 10y ago
One big thing here is that unlike Raspian or derived distros that use its kernel, Fedora is building their own mainline kernel. We're finally getting close to the day where installing on ARM will be as easy as x86, with no custom kernel or vendor patches.
- pjmlp 10y ago
  Sorry but I doubt it, unless ARM boards start having a standard chipset and vendors don't add their own stuff to ARM designs.
  - TD-Linux 10y ago
    A standard chipset isn't needed - but drivers and a standard way to detect the hardware is. The latter is handled by device trees - a hardware description loaded by the bootloader into memory, alongside the kernel.
    - pjmlp 10y ago
      Ok, I have to look into it.
    - marcoperaza 10y ago
      Isn't the boot process itself non-standard in the ARM world?
      - rkangel 10y ago
        Yes, but the kernel doesn't need to care about that.
- makomk 10y ago
  Yeah, and all it took was the Raspberry Pi Foundation rolling a series of custom chips with as few hardware improvements since 2011 as possible so as not to set back their mainline support. For most ARM chips where features like better graphics, power management and peripherals matter more, mainline support is still impractical and irrelevant.
eschaton 10y ago
Hope this will eventually lead to Fedora on RPi3 with arm64. Like everyone else they say "maybe" and "it only has 1GB RAM" with no consideration of the other reasons to support 64-bit ARM.
- annnnd 10y ago
  Exactly! One reason (though somewhat unpopular around here ;) ) is MongoDB which requires 64 bit OS to use more than 2GB data. > We currently only support this as a ARMv7 device like the upstream Raspberry Pi Foundation. I realize that aarch64 support is now upstream. I was unable to find any info about that... Anyone know more about it? As far as I am concerned, the whole "RPi3 is 64bit" bit is stretch at best and a blatant lie at worst. What does it matter that you have 64 bit CPU when drivers (WiFi, BT, camera, accelerometer) are only available for 32 bit kernel? EDIT: looks like aarch64 support is still not available: https://github.com/raspberrypi/firmware/issues/550 https://github.com/raspberrypi/firmware/issues/550
  - nullr0ute 10y ago
    aarch64 IS available. The firmware supports it when the appropriate options are enabled and the upstream 4.8 kernel supports it. The upstream kernel drivers for the Raspberry Pi, when built as a 64 bit kernel. A lot of the out of tree drivers (video offload etc) have issues with 64 bits mode. The reason Fedora doesn't currently support it is purely the amount of time available in the Fedora 25 cycle and best output for the time investment, also a single image can boot on either the Pi2 or Pi3 so less confusion for the average end user where it makes no real difference (same reason as the Pi foundation). Look for aarch64 support in Fedora 26 :)
    - annnnd 10y ago
      > aarch64 IS available. ... A lot of the out of tree drivers (video offload etc) have issues with 64 bits mode. "Out of tree"? You mean like BT? Yes, I agree completely... But that's "NOT available" in my dictionary! I don't care if there is a kernel which works with the CPU if I can't use the most basic of functionalities that RPi provides (BT, WiFI, accelerometer...). I'd be happy to be corrected, but you'll need to supply some citations.
willvarfar 10y ago
What's really needed is RTOS capabilities so that the Pi can be better used in robotics projects. (I don't have a Pi, I have an Arduino redbot. I couldn't find any Pi robots available when I was shopping around: http://williamedwardscoder.tumblr.com/post/136598180858/where-are-all-the-raspberry-pi-robots http://williamedwardscoder.tumblr.com/post/136598180858/wher... Proggit discussed it and pointed to the lack of RTOS: https://www.reddit.com/r/programming/comments/3zf04e/where_are_all_the_raspberry_pi_robots/ https://www.reddit.com/r/programming/comments/3zf04e/where_a... )
- TickleSteve 10y ago
  FreeRTOS and others have already been ported to RPi: [http://www.osrtos.com/rtos/freertos http://www.osrtos.com/rtos/freertos] [http://www.stevebate.net/chibios-rpi/GettingStarted.html http://www.stevebate.net/chibios-rpi/GettingStarted.html]
- gaddr 10y ago
  There's RTAndroid https://git.embedded.rwth-aachen.de/rtandroid/ https://git.embedded.rwth-aachen.de/rtandroid/ Might be interesting to look at.
- bitwize 10y ago
  Linux with Xenomai?
- nullr0ute 10y ago
  You'd be better off using a BeagleBone, the SoC is much better designed for that purpose.
rocky1138 10y ago
I apologize for my ignorance, but why is the original Raspberry Pi not supported? It would seem if the announcement has been made that it will never be supported, a note as to why would make sense. Unfortunately, the news release didn't include one.
- justin66 10y ago
  Dead slow CPU, not a lot of memory.
- nullr0ute 10y ago
  ARMv6 core, Fedora (and a lot of other distros) only support ARMv7 and newer.
  - rocky1138 10y ago
    Yes, but why?
    - nullr0ute 10y ago
      Because ARMv6 is EOL by ARM, has a number of architecture issues and design/toolchain bugs. Until the RPi came along there was literally no other non low end phone devices that had the ARMv6 design in them. Fedora made the decision that ARMv6 wasn't worth the effort in supporting and the performance hit that would affect the ARMv7 devices (at the time based on toolchain optimisation). The original Raspberry Pi was announced long after that decision was made and it was decided that it wasn't worth the effort to support ARMv6, even 5 years on from that decision it's still the right one to have made, and most other distros have had the same discussion around ARMv6 and still made the same decision to not bother with ARMv6 support.
      - rocky1138 10y ago
        Perfect, thanks!

100 points by cheiVia0 10y ago

I'm pretty excited about this! I started using f22 after using Ubuntu for a number of years, and I was particularly impressed by its package management. I personally find yum/dnf easier to use than apt and slightly more transparent. F24 has been an exceptional release and I look forward to running 25 on a pi. Hopefully we'll have a Pi with better IO by the time it releases. :)

astrodust 10y ago
It's nice that it's a unified command (yum vs. apt-get, apt-cache, etc.) and the commands do seem less obtuse. I've been using Fedora since the first cut, and by and large it's always been pretty great. The one thing I'd like to see ported over is ufw, as that's one thing about Ubuntu to envy. firewall-cmd is downright annoying and bizarrely designed.
- mwambua 10y ago
  I'll agree with you on firewall-cmd. One major problem is its documentation. They should initially provide really simple instructions on getting a base firewall (22,443,80) going... And then provide instructions on how to do zoning and what-not on the side.
  - astrodust 10y ago
    I like the idea of firewalld, but what I don't like is the way you have to do things like --list--all-zones and other nonsense. The end results are good, it's just how you have to implement them that's ridiculous. At least Ansible provides a tidy wrapper for it. git has a reputation for being annoyingly quirky, but firewalld is leaps ahead in terms of marching to the beat of its own drum.
- andrewchambers 10y ago
  You should give some of the BSD package tools a try for less obtuse package commands.
  - astrodust 10y ago
    Yeah, but then I'd have to go BSD, which at this point is really going to be an obstacle.
- seanp2k2 10y ago
  IMO just learn the real iptables commands. They're seriously one-liners with just a few args, and then you'll know how to set up a basic firewall on most distros. https://fedoraproject.org/wiki/How_to_edit_iptables_rules https://fedoraproject.org/wiki/How_to_edit_iptables_rules is the fedora guide. There are others. Here's how to disable firewalld: https://fedoraproject.org/wiki/FirewallD#Using_static_firewall_rules_with_the_iptables_and_ip6tables_services https://fedoraproject.org/wiki/FirewallD#Using_static_firewa... Note here that if everyone just spent the 5 minutes it takes to learn the few basic iptables commands, we wouldn't have ufw and firewalld and firehol and vuurmuur and Crazy Bob's Super Simple VBA-to-XML iptables rule generator. Every attempt at making iptables "easy", I consider harmful, as it's a basic systems administration skill that people continually hurt themselves by not learning. iptables is not hard, but all of these wrappers make it hard by introducing their own dumb syntax while adding complexity and quashing any hope of a standard interface between distros to control networking rules, which iptables already was before they tried to "fix" it.
  - cheiVia0 10y ago
    iptables is obsolete btw, Linux kernel developers replaced it with nftables.
    - Nux 10y ago
      From their docs, nftables is "available upstream since Linux kernel 3.13. It supports 3/4 of the existing iptables features" - 3/4 is still a long way to obsoleting iptables.
  - beagle3 10y ago
    I used to hold the same opinion as you, but I've recently changed my opinion of firehol; it's a little higher level than ufw and friends, and highly encourages good practices which are easy to forget or get wrong if you iptables all the way. I've realised that when I noticed that the comments I wrote for others on my iptable configs were comparable in length and content to firehol (but not verifiable or executable). Unlike ufw, firehol actually saved me significant time and effort even though I know (and use) iptables directly.
- Symbiote 10y ago
  "apt" is the unified command for apt-get etc, since a year or two ago.
- Narishma 10y ago
  "apt" already combines all those apt-* in one command.
krylon 10y ago
> Hopefully we'll have a Pi with better IO by the time it releases. :) Are there any official plans to release a new model with, say, an on-board SSD connector or SATA port? Or is this just "Hopefully" as in "Hopefully it stops raining before I have to walk to the train station"?
- imtringued 10y ago
  Very likely the latter. All the "innovation" happens in the mobile phone SoC space. My two years old phone is already good enough. Any improvement beyond it is a nice bonus but I could easily live without. Yet the ARM SBCs are so far behind. I'm betting at some point in the future phones have progressed so fast that it's better to just dump them into a server rack with ethernet over USB 2.0 than to actually buy ARM servers.
  - krylon 10y ago
    Yeah, it's a little sad. ARM based servers have been on the horizon for a couple of years now, but they seem to be forever out of reach. :-/

alxmdev 10y ago

Excellent! I tried out Ubuntu MATE 16.04 on a Raspberry Pi 3 a few months ago, and I was pleasantly surprised by how well it runs. The 1GB RAM is an unfortunate limitation, but even so the Pi is a viable little desktop. Great to see upstream kernel support and official releases from major distros.

swiley 10y ago
I've done quite a lot of homework on a Pi3 I got for free from someone who didn't want it. They're actually a functional desktop.
- paulmd 10y ago
  They work as a desktop but you're better off using something designed around the task. SD cards are not really designed for heavy random writes on a long-term basis and can be sensitive to corruption during brownouts that don't necessarily trigger a full system dropout. The GPU was primitive even for its day and has not gotten better with age. There's no SATA or USB 3.0, no GigE, and everything runs across a single USB 2.0 bus. For desktop or server use, the Pi is in the same price range as systems built on laptop chipsets (Kabini, Baytrail/Cherrytrail/Goldmont, etc). These can easily be had for sub-$150 normally and sub-$100 if you shop around. That's about the same price as the Pi once you factor in all the other things you have to purchase to get your "$35 computer" to boot. They are are lot faster and a lot more fully-featured. You can easily get SATA, GigE, USB 3.0, and you can even get ECC RAM on the AM1 platform. Also check out the Liva series from ECS and the ZBOX series from Zotac. Of course if you have the cash you can also look at a NUC or BRIX or other mini-PC but those are aimed a little higher in the market. Also it's kinda sad to hold up an Intel product as a positive example of open source, but it's much better than the Raspberry Pi. You are still reliant on binary blobs to boot the hardware to this day. The graphics stack is open source, the ThreadX-based VideoCore OS RTOS the GPU uses is not, and the documentation/drivers are restricted to usage only on official Raspberry Pi hardware.
  - khedoros1 10y ago
    A lot of people seem to want something like a more-powerful Arduino that they can interface to a few I2C or SPI sensors, run some relays or servos, and embed into a project. Use your old cell phone charger, buy a microSD for $5, borrow a keyboard and some time on an HDMI TV to configure wifi, then just access it through VNC. Before the Pi3 with it's built-in wifi, it was also common to connect the Pi to a laptop with an ethernet cable and access it that way. For some people, one of those cheap X86 systems would make more sense, because they're trying to use it as a desktop or to do something that benefits from a higher-power CPU (real-time object recognition comes to mind). For a lot of others, a little ARM board hits a few important points: it's small, doesn't use much power, is easy to re-flash if it gets corrupted, is actually available in their country, is generally easy to adapt Arduino code to work on, and has a huge community around it focused on learning, experimentation, and building things. There's a nice little niche that it and similar boards fill.

andrewchambers 10y ago

Running plan9 on a raspberry pi 2 is so fast. It ruined linux on a raspberry pi for me, software currently is so heavy weight.

pjmlp 10y ago
When I installed GNU/Linux for the first time, a Slackware 2.0 in 1995, I had a Pentium 75 with 4 MB with a 512 MB HD.... Now compare with a PI or the modern GNU/Linux distributions.
rcarmo 10y ago
And what do you do to browse the web?

ekianjo 10y ago

Why does every raspberry install recommend dd instead of the cp tool? Cp does the same thing and has a much better syntax.

snuxoll 10y ago
GNU coreutils' version of `cp` supports copying to block devices, but not every other implementation does (busybox's doesn't, for example). `dd` is explicitly required to support block devices by the POSIX specification, `cp` is not.
- ce4 10y ago
  Why not just use cat? cat $image.file > /dev/$BLOCK_DEV
  - snuxoll 10y ago
    cat has issues with partial reads and is not suitable for copying files, let alone images.
voltagex_ 10y ago
And if you really get into using a lot of different images, https://source.tizen.org/documentation/reference/bmaptool https://source.tizen.org/documentation/reference/bmaptool is the way to go - uses sparse images correctly. https://github.com/01org/bmap-tools https://github.com/01org/bmap-tools is the maintained version.

TD-Linux 10y ago

One big thing here is that unlike Raspian or derived distros that use its kernel, Fedora is building their own mainline kernel. We're finally getting close to the day where installing on ARM will be as easy as x86, with no custom kernel or vendor patches.

pjmlp 10y ago
Sorry but I doubt it, unless ARM boards start having a standard chipset and vendors don't add their own stuff to ARM designs.
- TD-Linux 10y ago
  A standard chipset isn't needed - but drivers and a standard way to detect the hardware is. The latter is handled by device trees - a hardware description loaded by the bootloader into memory, alongside the kernel.
  - pjmlp 10y ago
    Ok, I have to look into it.
  - marcoperaza 10y ago
    Isn't the boot process itself non-standard in the ARM world?
    - rkangel 10y ago
      Yes, but the kernel doesn't need to care about that.
makomk 10y ago
Yeah, and all it took was the Raspberry Pi Foundation rolling a series of custom chips with as few hardware improvements since 2011 as possible so as not to set back their mainline support. For most ARM chips where features like better graphics, power management and peripherals matter more, mainline support is still impractical and irrelevant.

eschaton 10y ago

Hope this will eventually lead to Fedora on RPi3 with arm64. Like everyone else they say "maybe" and "it only has 1GB RAM" with no consideration of the other reasons to support 64-bit ARM.

annnnd 10y ago
Exactly! One reason (though somewhat unpopular around here ;) ) is MongoDB which requires 64 bit OS to use more than 2GB data. > We currently only support this as a ARMv7 device like the upstream Raspberry Pi Foundation. I realize that aarch64 support is now upstream. I was unable to find any info about that... Anyone know more about it? As far as I am concerned, the whole "RPi3 is 64bit" bit is stretch at best and a blatant lie at worst. What does it matter that you have 64 bit CPU when drivers (WiFi, BT, camera, accelerometer) are only available for 32 bit kernel? EDIT: looks like aarch64 support is still not available: https://github.com/raspberrypi/firmware/issues/550 https://github.com/raspberrypi/firmware/issues/550
- nullr0ute 10y ago
  aarch64 IS available. The firmware supports it when the appropriate options are enabled and the upstream 4.8 kernel supports it. The upstream kernel drivers for the Raspberry Pi, when built as a 64 bit kernel. A lot of the out of tree drivers (video offload etc) have issues with 64 bits mode. The reason Fedora doesn't currently support it is purely the amount of time available in the Fedora 25 cycle and best output for the time investment, also a single image can boot on either the Pi2 or Pi3 so less confusion for the average end user where it makes no real difference (same reason as the Pi foundation). Look for aarch64 support in Fedora 26 :)
  - annnnd 10y ago
    > aarch64 IS available. ... A lot of the out of tree drivers (video offload etc) have issues with 64 bits mode. "Out of tree"? You mean like BT? Yes, I agree completely... But that's "NOT available" in my dictionary! I don't care if there is a kernel which works with the CPU if I can't use the most basic of functionalities that RPi provides (BT, WiFI, accelerometer...). I'd be happy to be corrected, but you'll need to supply some citations.

willvarfar 10y ago

What's really needed is RTOS capabilities so that the Pi can be better used in robotics projects. (I don't have a Pi, I have an Arduino redbot. I couldn't find any Pi robots available when I was shopping around: http://williamedwardscoder.tumblr.com/post/136598180858/where-are-all-the-raspberry-pi-robots http://williamedwardscoder.tumblr.com/post/136598180858/wher... Proggit discussed it and pointed to the lack of RTOS: https://www.reddit.com/r/programming/comments/3zf04e/where_are_all_the_raspberry_pi_robots/ https://www.reddit.com/r/programming/comments/3zf04e/where_a... )

TickleSteve 10y ago
FreeRTOS and others have already been ported to RPi: [http://www.osrtos.com/rtos/freertos http://www.osrtos.com/rtos/freertos] [http://www.stevebate.net/chibios-rpi/GettingStarted.html http://www.stevebate.net/chibios-rpi/GettingStarted.html]
gaddr 10y ago
There's RTAndroid https://git.embedded.rwth-aachen.de/rtandroid/ https://git.embedded.rwth-aachen.de/rtandroid/ Might be interesting to look at.
bitwize 10y ago
Linux with Xenomai?
nullr0ute 10y ago
You'd be better off using a BeagleBone, the SoC is much better designed for that purpose.

rocky1138 10y ago

I apologize for my ignorance, but why is the original Raspberry Pi not supported? It would seem if the announcement has been made that it will never be supported, a note as to why would make sense. Unfortunately, the news release didn't include one.

justin66 10y ago
Dead slow CPU, not a lot of memory.
nullr0ute 10y ago
ARMv6 core, Fedora (and a lot of other distros) only support ARMv7 and newer.
- rocky1138 10y ago
  Yes, but why?
  - nullr0ute 10y ago
    Because ARMv6 is EOL by ARM, has a number of architecture issues and design/toolchain bugs. Until the RPi came along there was literally no other non low end phone devices that had the ARMv6 design in them. Fedora made the decision that ARMv6 wasn't worth the effort in supporting and the performance hit that would affect the ARMv7 devices (at the time based on toolchain optimisation). The original Raspberry Pi was announced long after that decision was made and it was decided that it wasn't worth the effort to support ARMv6, even 5 years on from that decision it's still the right one to have made, and most other distros have had the same discussion around ARMv6 and still made the same decision to not bother with ARMv6 support.
    - rocky1138 10y ago
      Perfect, thanks!