From: Florian Lohoff <flo@rfc822.org>
To: Joe deBlaquiere <jadb@redhat.com>
Cc: "Kevin D. Kissell" <kevink@mips.com>, linux-mips@oss.sgi.com
Subject: Re: Embedded MIPS/Linux Needs
Date: Mon, 26 Mar 2001 19:25:59 +0200 [thread overview]
Message-ID: <20010326192559.A8385@paradigm.rfc822.org> (raw)
In-Reply-To: <3ABEB120.8020609@redhat.com>; from jadb@redhat.com on Sun, Mar 25, 2001 at 09:01:52PM -0600
On Sun, Mar 25, 2001 at 09:01:52PM -0600, Joe deBlaquiere wrote:
> Just some unsorted random ideas:
>
> 1. Would it be possible to lump some of the different MIPS variants
> together more closely? In my dream world I could build one kernel that
> would boot on every mips architecture. This way the work can be more
> general. As it stands now, if you want Tx39 or Vr41 variants you're
> working out of a different tree. With the number of SoC core products
> coming out at present, this predicament is only likely to get more
> serious. I know at one point in time you could boot a single ARM kernel on
> several different systems and it would adapt it's processor specifics at
> runtime. Such a design might help to bring the MIPS world together a bit.
There is at least a problem with endianess - I dont think there can be
a little and big endian kernel coexist in the same object or at least
not with major rework.
Why would you suggest having vr41 and TX39 in a seperat tree ? I had a
look in the linux-vr tree and i dont like some of their #ifdef spaghetti
stuff so i am currently working on TX39 stuff on top of the oss tree
which could be made cleanly. (Dont integrate all TX39 archs into one
subarch *grrr*)
Flo
--
Florian Lohoff flo@rfc822.org +49-5201-669912
Why is it called "common sense" when nobody seems to have any?
next prev parent reply other threads:[~2001-03-26 17:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-22 11:48 Embedded MIPS/Linux Needs Kevin D. Kissell
2001-03-22 11:48 ` Kevin D. Kissell
2001-03-22 14:01 ` Jay Carlson
2001-03-22 14:01 ` Jay Carlson
2001-03-22 18:32 ` Jun Sun
2001-03-22 14:17 ` Mike McDonald
2001-03-22 18:23 ` Jeff Harrell
2001-03-22 18:23 ` Jeff Harrell
2001-03-26 3:01 ` Joe deBlaquiere
2001-03-26 3:23 ` Keith Owens
2001-03-26 4:06 ` Keith M Wesolowski
2001-03-26 17:25 ` Florian Lohoff [this message]
2001-03-26 18:47 ` Joe deBlaquiere
2001-03-26 23:24 ` Jun Sun
-- strict thread matches above, loose matches on Subject: below --
2001-03-22 12:27 Phil Thompson
2001-03-22 19:02 Justin Carlson
2001-03-22 19:03 ` nick
2001-03-22 19:22 ` Keith M Wesolowski
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=20010326192559.A8385@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=jadb@redhat.com \
--cc=kevink@mips.com \
--cc=linux-mips@oss.sgi.com \
/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