* Re: Adding sparc-leon linux to sourcetree
[not found] <200301301353.h0UDrxO24129@mailgate5.cinetic.de>
@ 2003-01-30 18:44 ` Pete Zaitcev
2003-01-30 18:55 ` perl (Was: Adding sparc-leon linux to sourcetree) Pete Zaitcev
1 sibling, 0 replies; 2+ messages in thread
From: Pete Zaitcev @ 2003-01-30 18:44 UTC (permalink / raw)
To: Konrad Eisele; +Cc: PeteZaitcev, sparclinux, leon_sparc, dfoulds, linux-kernel
> 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
^ permalink raw reply [flat|nested] 2+ messages in thread* perl (Was: Adding sparc-leon linux to sourcetree)
[not found] <200301301353.h0UDrxO24129@mailgate5.cinetic.de>
2003-01-30 18:44 ` Adding sparc-leon linux to sourcetree Pete Zaitcev
@ 2003-01-30 18:55 ` Pete Zaitcev
1 sibling, 0 replies; 2+ messages in thread
From: Pete Zaitcev @ 2003-01-30 18:55 UTC (permalink / raw)
To: Konrad Eisele; +Cc: PeteZaitcev, linux-kernel
> Date: Thu, 30 Jan 2003 14:53:59 +0100
> From: Konrad Eisele <eiselekd@web.de>
> There is also one change I have made on the buildsystem. Because
> I'm using some perl inline scripts in the $cmd_xxx the >'< and >$<
> signs in the inline perl scripts cause trouble (perl -e '...$x=....'),
> the >'< because of the echo command, the >$< when rereading from
> the xxx..cmd files. Could this be applied to the original file?
First, send a patch, not a chunk of a Makefile.
Second, this is something I defer to Kai, Sam, & Co.
Personally, I am opposed to a use of perl, because it's not
installed in my sparc userland, so I would not be able to
self-compile a leon or joint kernel. But ultimately this is
not my call to decide. At one point, Linus approved Python
into the toolchain. So, present good evidence of need and post
to lists.
-- Pete
^ permalink raw reply [flat|nested] 2+ messages in thread