From: Michael Tremer <michael.tremer@ipfire.org>
To: sig-arm@lists.ipfire.org
Subject: Re: News on Utilite?
Date: Mon, 13 Jan 2014 12:37:05 +0100 [thread overview]
Message-ID: <1389613025.19959.31.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <CAMVU60ZQ0n2bUywmvperZAAP3zM81QXjfCJOA34YJdBZchC7Yw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1856 bytes --]
On Mon, 2014-01-13 at 09:57 +0100, Christer Solskogen wrote:
> On Sun, Jan 12, 2014 at 6:49 PM, Michael Tremer
> <michael.tremer(a)ipfire.org> wrote:
>
> > I wish I had good news for you, but unfortunately there has not been any
> > progress at all regarding Utilite support. However, there have been huge
> > advancements towards the unified ARM kernel and for the 2.15 release in
> > general.
> >
>
> If IPFire would provide binaries for armv7 - you could, in theory, use
> the kernel from archlinux.
> CompuLab provides their own kernel source at
> https://gitorious.org/utilite which arch uses. So you can also cross
> compile the kernel if you like.
Unfortunately we cannot do that.
IPFire is built from source and there is a reason for it: We want to be
able to control what is enabled and what not. Especially in the kernel,
there is lots of stuff that we don't need and other stuff that we do
need, but which is often not enabled in the mainstream distributions.
This is for example networking features or very strong hardening which
is not very suitable on a desktop system. We apply grsecurity and more
things and we have our own hardened compiler.
Therefore we require the sources and we need to compile them ourselves.
Other distributions take arbitrary kernel images they found on they
Internet and bundle them with their userland and then claim to support a
certain board. But there are never updates, the kernel differs a lot
from the original distribution kernel, you never know if someone added
some malware - or added some patches that make the system insecure or
unstable - and there are so many other issues...
We simply cannot do this.
But currently, the kernel is not the issue here. I am confident that it
will run decently on the board. It just cannot be booted right now. And
that is a problem caused by uboot.
-Michael
prev parent reply other threads:[~2014-01-13 11:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEVn7dmsxtBwmYdxw2spJKc0YwBG3kV9ny1x2sevvnY0X=zLLg@mail.gmail.com>
2014-01-12 17:49 ` Michael Tremer
2014-01-12 18:33 ` Christer Solskogen
2014-01-12 19:03 ` Michael Tremer
2014-01-13 15:39 ` Igor Grinberg
2014-01-15 15:19 ` Michael Tremer
2014-01-16 8:49 ` Christer Solskogen
2014-01-16 9:21 ` Michael Tremer
2014-01-16 8:50 ` Igor Grinberg
2014-01-16 9:20 ` Michael Tremer
2014-01-16 9:57 ` Igor Grinberg
2014-01-16 10:31 ` Michael Tremer
2014-01-16 11:26 ` Igor Grinberg
2014-01-13 8:57 ` Christer Solskogen
2014-01-13 11:37 ` Michael Tremer [this message]
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=1389613025.19959.31.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