All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: Konrad Eisele <eiselekd@web.de>
Cc: PeteZaitcev <zaitcev@redhat.com>,
	sparclinux@vger.kernel.org, leon_sparc@groups1.vip.scd.yahoo.com,
	dfoulds@pacbell.net, linux-kernel@vger.kernel.org
Subject: Re: Adding sparc-leon linux to sourcetree
Date: Thu, 30 Jan 2003 13:44:02 -0500	[thread overview]
Message-ID: <20030130134402.A12226@devserv.devel.redhat.com> (raw)
In-Reply-To: <200301301353.h0UDrxO24129@mailgate5.cinetic.de>; from eiselekd@web.de on Thu, Jan 30, 2003 at 02:53:59PM +0100

> Date: Thu, 30 Jan 2003 14:53:59 +0100
> From: Konrad Eisele <eiselekd@web.de>

> I would like to ask if it would be possible to add arch/sparc-leon as
> a new architecture to the sourcetree of linux. From 16.12.02 to 16.3.03
> I'm employed at the University and by Jiri Gaisler's Gaisler Reasearch
> to add the MMU that I made as a diploma thesis to the official Leon 
> distiribution (the open source sparc chip). [...]

I think it is a worthy goal to have a generic Linux for a generic
LEON, but before I support this particular project, I would like to
discuss one thing.

Your VHDL target must be in use by someone long term.
I do not even care if Opencores or whoever accepts it, but there
must be a nonzero user base, now and in the future. I do not want
to add it then to rip it out like AP-1000. For comparison, a recurring
topic on Sparclinux list is a removal of sun4 and even sun4c.
I was ready to support David Foulds' MMU before, but it never
materialized.

> Almost all the source is a copy from the original sparc distribution
> of you what I'm basically doing is to write the bootup initialization
> routines for leon and to throw out the sun hardware stuff.

"Throw out the sun hardware stuff" sounds broken. Look closer
at CONFIG_SUN4. So far I do not see why you need a separate
architecture. Sure, throwing the stuff away helps you to finish
your diploma on time, but then I have to maintain what's left.

> I'm currently adjusting linux for that platform based on linux 2.5.53.
> I do not know exactly when I willl have a first running kernel,
> but when I have one then what should I do get it into the sourcetree?

Discuss early, discuss often. Use Sparclinux@vger.kernel.org
and, perhaps, the Leon list at (bleah!) yahoogroups. Learn
to send patches, and be ready to stay as a patch for a while
(a year or so). I think Jeff Dike's UML is a model of project
management for you (http://user-mode-linux.sourceforge.net/).
He stayed outside AND in close contact while he proved that the
project was viable, then Linus took it.

Good luck and send those patches,
-- Pete

       reply	other threads:[~2003-01-30 18:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200301301353.h0UDrxO24129@mailgate5.cinetic.de>
2003-01-30 18:44 ` Pete Zaitcev [this message]
2003-01-30 18:55 ` perl (Was: Adding sparc-leon linux to sourcetree) Pete Zaitcev

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=20030130134402.A12226@devserv.devel.redhat.com \
    --to=zaitcev@redhat.com \
    --cc=dfoulds@pacbell.net \
    --cc=eiselekd@web.de \
    --cc=leon_sparc@groups1.vip.scd.yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.