From: Jes Sorensen <jes@sunsite.dk>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Bob Glamm <glamm@mail.ece.umn.edu>, linux-kernel@vger.kernel.org
Subject: Re: Will 2.6 require Python for any configuration ? (CML2)
Date: 23 Aug 2001 22:02:07 +0200 [thread overview]
Message-ID: <d3g0aituio.fsf@lxplus051.cern.ch> (raw)
In-Reply-To: <20010822030807.N120@pervalidus> <20010823140555.A1077@newton.bauerschmidt.eu.org> <20010823103620.A6965@kittpeak.ece.umn.edu> <20010823085900.F14302@cpe-24-221-152-185.az.sprintbbd.net> <d3k7zutw5y.fsf@lxplus051.cern.ch> <20010823124109.S14302@cpe-24-221-152-185.az.sprintbbd.net>
In-Reply-To: Tom Rini's message of "Thu, 23 Aug 2001 12:41:09 -0700"
>>>>> "Tom" == Tom Rini <trini@kernel.crashing.org> writes:
Tom> You've said this before. :) Just how small of an 'embedded'
Tom> system are you talking about? I know of people who do compile a
Tom> kernel now and again on a 'small' system, for fun. On a larger
Tom> (cPCI) system, I don't see your point. If you can somehow
Tom> transport the 21mb[1] bzip2 kernel source to your system, you can
Tom> transport python. If you're porting to a brand new arch, there's
Tom> still good tests before you have shlib support (You've mentioned
Tom> that before too I think).
I am actually much more concerned about bringing up new systems than
embedded however it is not uncommon to have very limited space to work
in (like 64MB). My point is that the transport process of the kernel
image is painful. Some of the embedded devices or new systems being
brought up may only have serial some do not have network or
floppy. This makes it *very* painful to move things around because you
have to physically move your disk or similar. In particular when
bringing up a system you tend to disable large parts of the kernel in
order to make the thing compile and you don't want to have to copy
things back and forth constantly because you found that serial no
longer compiles and you don't want to fight that while you are trying
to fix a bug in your video driver. Hence you just disable serial and
recompile - with the new system this has suddenly become extremely
painful.
>> And introduces new problems that so far haven't been addressed.
Tom> Which is what? The dependancy on python2?
Yes
>> The solution seems to be that someone implements CML2 in C, once
>> that happens we are talking something completely different.
Tom> As long as it does everything the current version does and is
Tom> just as fast I don't think there'll be much of an argument for
Tom> either. Hell, probably both for a while...
Well getting a C versions means we can get rid of the Python hell, it
would be a major win.
Jes
next prev parent reply other threads:[~2001-08-23 20:02 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-22 6:08 Will 2.6 require Python for any configuration ? (CML2) =?unknown-8bit?B?RnLpZOlyaWMgTC4gVy4=?= Meunier
2001-08-23 12:05 ` Roland Bauerschmidt
2001-08-23 15:36 ` Bob Glamm
2001-08-23 15:55 ` Disconnect
2001-08-23 18:36 ` Daniel Phillips
2001-08-23 18:44 ` Disconnect
2001-08-23 19:01 ` David Weinehall
2001-08-23 19:22 ` Alan Cox
2001-08-23 19:02 ` Roland Bauerschmidt
2001-08-23 19:09 ` Rik van Riel
2001-08-23 19:31 ` Disconnect
2001-08-23 22:52 ` John Alvord
2001-08-24 1:51 ` Keith Owens
2001-08-23 15:55 ` Joshua Schmidlkofer
2001-08-23 15:59 ` Tom Rini
2001-08-23 19:26 ` Jes Sorensen
2001-08-23 19:32 ` David Weinehall
2001-08-23 19:41 ` Tom Rini
2001-08-23 19:50 ` Tom Rini
2001-08-23 20:02 ` Jes Sorensen [this message]
2001-08-23 20:13 ` Tom Rini
2001-08-23 20:43 ` Jes Sorensen
2001-08-23 21:12 ` Tom Rini
2001-08-24 4:59 ` Denis Perchine
2001-08-24 6:35 ` Leonid Mamtchenkov
2001-08-24 7:13 ` Denis Perchine
2001-08-24 15:01 ` Mark Hahn
2001-08-24 13:35 ` Ryan W. Maple
2001-08-25 1:14 ` Michael Peddemors
2001-08-24 17:42 ` David Lang
2001-08-23 16:24 ` Roland Bauerschmidt
2001-08-23 17:57 ` Kurt Roeckx
2001-08-24 8:10 ` Matthias Andree
-- strict thread matches above, loose matches on Subject: below --
2001-08-23 20:41 Samium Gromoff
2001-08-23 20:53 ` Tom Rini
2001-08-25 4:11 ` Ben Ford
2001-08-25 14:51 ` Tom Rini
2001-08-23 20:56 Samium Gromoff
2001-08-23 21:14 ` Tom Rini
2001-08-23 21:08 Rick Hohensee
2001-08-23 21:01 ` Tom Rini
2001-08-23 21:12 Samium Gromoff
2001-08-23 21:32 ` Tom Rini
2001-08-23 21:18 Samium Gromoff
2001-08-23 21:34 ` Tom Rini
2001-08-24 12:59 ` Jes Sorensen
2001-08-24 15:37 ` Tom Rini
2001-08-24 15:42 ` Jes Sorensen
2001-08-24 15:50 ` Tom Rini
2001-08-24 16:03 ` Jes Sorensen
2001-08-23 21:39 Samium Gromoff
[not found] <20010823191423.I14302@cpe-24-221-152-185.az.sprintbbd.net>
2001-08-24 3:01 ` Rick Hohensee
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=d3g0aituio.fsf@lxplus051.cern.ch \
--to=jes@sunsite.dk \
--cc=glamm@mail.ece.umn.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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