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: Re: ipfire work around for newer pi yet?
Date: Tue, 23 Jul 2013 10:48:25 +0200	[thread overview]
Message-ID: <1374569305.11196.28.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <CABek4LW8zS6etqqKGivK+MnoT_BT9pXpJh_TTjgEV_4fPbY-Tw@mail.gmail.com>

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

Hey Shane,

unfortunately it's not our fault that the Raspberry Pi Foundation and
Broadcom (who is the vendor of the SoC working on the RPi) are not very
helpful with supporting free software.

There is a proprietary firmware blob that had some changes for the new
versions of the RPi, but there is no kernel patchset for our version of
the Linux kernel (which is 3.2 - very recent and commonly used by a lot
of distributions), that works with the new firmware blob.

As the firmware is completely closed, we cannot do much about it,
because we cannot see what has been changed inside. We could probably
guess, and try to backport kernel patches from the latest releases (if
there are any), but for that, we don't have enough time.

So at this point, IPFire (or stable versions of the Linux kernel) do not
support the new Raspberry Pi versions.
If you want to help, please dig into the topic and if there are any
questions we could help with, or if you found someone who tried to do
the same for their version of the Linux kernel, feel free to contact
me/us on this mailing list.

Best,
-Michael

On Mon, 2013-07-22 at 21:50 -0500, Shane O'Neill wrote:
> Tried doing the setup outlined in
> 
> http://wiki.ipfire.org/en/hardware/arm/rpi
> 
> 
> including copying over the three boot files.
> 
> 
> When I start the pi with the expanded sd card, I don't get a boot at
> all.
> 
> 
> Any ideas?
> 
> 
> Thanks in advance,
> 
> Shane
> 
> _______________________________________________
> SIG-ARM mailing list
> SIG-ARM(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/sig-arm


           reply	other threads:[~2013-07-23  8:48 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CABek4LW8zS6etqqKGivK+MnoT_BT9pXpJh_TTjgEV_4fPbY-Tw@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=1374569305.11196.28.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