Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: John Crispin <blogic@openwrt.org>, linux-mips@linux-mips.org
Subject: Re: Single MIPS kernel
Date: Wed, 22 Oct 2014 10:36:42 -0700	[thread overview]
Message-ID: <5447EB2A.3030001@gmail.com> (raw)
In-Reply-To: <54478C94.4060208@openwrt.org>

On 10/22/2014 03:53 AM, John Crispin wrote:
> Hi Ralf,
> 
> On 22/10/2014 10:34, Ralf Baechle wrote:
>> This question comes up every once in a while and I've also been
>> approached during ELCE in Düsseldorf why there is no single MIPS
>> kernel for all platforms, so I thought I should post a writeup on
>> the topic.
>>
> 
> for the SoCs supported by OpenWrt this is a no-go. we are already
> having a hard time fighting bloat. to get the images to fit we need to
> already build device specific images that only hold the DT, drivers,
> ... that a specific board needs. having a kernel that can boot on X
> devices wont even fit into flash and if it does there is not space
> left for the userland.

A multi-platform kernel should allow to compile in/out specific
platforms (like what ARM does), such that we can still achieve a small
kernel goal in OpenWrt.

> 
> I think this feature is only interesting for the older platforms and
> the upcoming mobile SoC based in MIPS. i.e. the users are debian and
> android type device.

You mean, older systems such as Sibyte, the SGI's IPxx and similar?
Those may have memory architecture requirements (spaces.h) that make it
difficult if possible to support.
--
Florian

  reply	other threads:[~2014-10-22 17:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22  8:34 Single MIPS kernel Ralf Baechle
2014-10-22 10:53 ` John Crispin
2014-10-22 17:36   ` Florian Fainelli [this message]
2014-10-22 17:56 ` David Daney
2014-10-22 19:05   ` Ralf Baechle
2014-10-22 19:19     ` Maciej W. Rozycki
2014-10-22 20:42       ` Ralf Baechle
2014-10-22 21:10         ` David Daney
2014-10-22 21:53         ` James Hogan
2014-10-22 21:53           ` James Hogan
2014-10-22 22:18           ` David Daney
2014-10-22 18:03 ` David Daney
2014-10-22 19:20   ` Ralf Baechle
2014-10-22 22:15     ` Ben Hutchings
2014-10-22 23:22       ` Ralf Baechle
2014-10-23  1:02         ` Ben Hutchings
2014-10-23  3:13           ` Joshua Kinard

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=5447EB2A.3030001@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=blogic@openwrt.org \
    --cc=linux-mips@linux-mips.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