public inbox for sig-arm@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: sig-arm@lists.ipfire.org
Subject: [SIG-ARM] Has somebody got interest in Raspberry Pi?
Date: Sun, 04 Mar 2012 15:03:38 +0100	[thread overview]
Message-ID: <1330869818.2169.56.camel@rice-oxley.tremer.info> (raw)

[-- Attachment #1: Type: text/plain, Size: 2714 bytes --]

Hello,

it has been a little bit quite on this list, so I am going to start a
new conversation about Raspberry Pi, a cheap board with an ARM SoC.

Originally, there has been a request on the forums whether IPFire will
support this hardware. I would like to pass this question on to the SIG.

On the pro side of the equation:

The Raspberry Pi Foundation is a charity and is trying to bring small
PCs to poor countries and people who can not afford any. I'd like to
support that.

Usable software is still missing, but I guess the major distributions
will come up with such very soon. However, among them, there is a
router/firewall distribution missing, and as IPFire is the only Open
Source firewall which has support for ARM, we should consider to enhance
this support for the Raspberry Pis as well. We could bring firewalls to
poorer countries which is quite nice with IPFire: ISPs are planning to
provide LTE (which works with IPFire) and providing a connection to the
internet to small networks like in schools. I suppose that is what the
R-Pi-Foundation is aiming to do.

On the technical side: The hardware should be powerful enough for
connections to a couple of MBits/s but too weak for powerful services
like the filtering proxy and the intrusion detection system won't work
well.

The userland of the ARM port should run without any major modification.
Maybe we need to make some amendments on tools like the bootloader
(U-Boot) or others, but we should not expect any trouble there. The left
thing that is to do is to build a new kernel for that device. It uses a
Broadcom chipset which is supported by the Linux kernel and does not
need any patches unless we want to use the GPU.

The contra side:

The Raspberry Pi Foundation apparently messed up the launch. It is not
possible to get one and a lot of blokes are going to buy the few that
were already built to create home servers and stuff like that. That's
bad for us, because we cannot test any created code without the
hardware.

The hardware is weak. As mentioned earlier, it will work for a lot of
things, but not all of the features IPFire provides. I consider the
project rather a toy than a serious piece of computing hardware, so
supposedly the amount of interest will decrease soon when people realize
that they cannot really do what they intended to do with the boards in
the first place.

-----------------------------------------------------------------------

The question now is, if it should take the effort and build a new kernel
for the Broadcom SoC and support the Raspberry Pi boards. Is somebody
willing to do this? Has someone already tried something out? Did you try
to order a board?

Please mail me your thoughts.

Michael


             reply	other threads:[~2012-03-04 14:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-04 14:03 Michael Tremer [this message]
2012-03-05  1:53 ` R. W. Rodolico
2012-03-05  7:52   ` Arne Fitzenreiter
2012-03-05 23:17     ` Michael Tremer
2012-04-14 15:08       ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1330869818.2169.56.camel@rice-oxley.tremer.info \
    --to=michael.tremer@ipfire.org \
    --cc=sig-arm@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox