From: Michael Tremer <michael.tremer@ipfire.org>
To: sig-arm@lists.ipfire.org
Subject: Re: Ipfire form Cubieboard
Date: Wed, 11 Sep 2013 23:49:42 +0200 [thread overview]
Message-ID: <1378936182.8623.16.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <CAFPkFXbLFGH+_67xmn85vQ0t2y-QPR1VSrZ5SeR-bKNmxGm-hw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1741 bytes --]
Hello Daniel,
thanks for writing to me. I will post this reply to our Special Interest
Group ARM mailing list, too.
We are asked a lot about supporting different ARM hardware these days.
Finally, there is a market building up for cheap ARM-based router
hardware, which I am very happy about. Unfortunately, this causes us a
lot of trouble, because supporting an additional piece of hardware takes
us a lot of work. I pointed out some of this over here:
http://planet.ipfire.org/post/why-ipfire-does-not-run-on-all-arm-hardware
There are currently plans for introducing a multiplatform kernel based
on Linux 3.10 to IPFire. This is basically one kernel for multiple
platforms which will be configured by Device Tree.
As far as I can tell (finding the specs of Cubieboard is not very easy),
Cubieboard is based on an Allwinner SoC, which is supported in the
multiplatform kernel. I won't promise anything, but from what it looks
like, it seems that we can support Cubieboard with the next kernel
release that we are shipping.
In order to make this work, please participate in the testing process.
We don't have all the boards and the resources to test all of them, so
please join the development efforts and check what is needed to be done
to get Cubieboard running out of the box.
I hope this answers your question. The short answer is "no, we don't
support Cubieboard right now", but we are going to, if you help us.
-Michael
On Mon, 2013-09-09 at 16:03 -0300, Daniel Lara wrote:
> Hi ,
>
>
> I wonder how this development for the IPFire cubieboard
> and if you have any. img we can test or if we can help with testing
> the use of IPFire in cubieboard
>
> Atenciosamente
> Daniel Lara Souza
> FEDORA AMBASSADOR - BRAZIL
>
>
parent reply other threads:[~2013-09-11 21:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAFPkFXbLFGH+_67xmn85vQ0t2y-QPR1VSrZ5SeR-bKNmxGm-hw@mail.gmail.com>]
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=1378936182.8623.16.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