linux-mips
[Top] [All Lists]

Re: CONFIG_MIPS_UNCACHED

To: "Kevin D. Kissell" <kevink@mips.com>
Subject: Re: CONFIG_MIPS_UNCACHED
From: "Justin Carlson" <carlson@sibyte.com>
Date: Mon, 25 Jun 2001 10:35:43 -0700
Cc: linux-mips@oss.sgi.com
In-reply-to: <001f01c0fd43$3865b680$0deca8c0@Ulysses>
Organization: Sibyte
References: <3B34BE3B.B72D40F1@mvista.com> <20010624214232.A18389@mvista.com> <001f01c0fd43$3865b680$0deca8c0@Ulysses>
Reply-to: carlson@sibyte.com
Sender: owner-linux-mips@oss.sgi.com
On Sun, 24 Jun 2001, you wrote:

> That's a position that would sound reasonable to someone working
> on Linux for legacy DEC/SGI systems, but not one that I would
> expect to satisfy someone working on embedded Linux.  It would
> need to be governed by a config option, but I would think
> that ultimately we need to have a Linux that can be ROMed
> and branched to directly from the reset vector.  Why force
> everyone doing an embedded MIPS/Linux widget to re-invent
> the wheel?

Because there are very good reasons for having a firmware seperate from
the OS.  Otherwise, you're more or less proposing a new run-time-environment
that has to do all the hardware sanitizations and initializations before we
get to the bootstrap environment.  That's going to be so system-specific and
disparate from the kernel that it doesn't, IMHO, make any sense to put it
there.  This is especially true since *not* having it in the kernel gives you
the chance to exploit the same firmware environment for non-linux OS'es. 

-Justin


<Prev in Thread] Current Thread [Next in Thread>