[Top] [All Lists]

Re: How to work with Linux-Mips ?

To: Jonathan Day <>
Subject: Re: How to work with Linux-Mips ?
From: Franck Bui-Huu <>
Date: Thu, 28 Sep 2006 10:45:16 +0200
Cc: Peter Popov <>, Franck <>, Ralf Baechle <>,
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta;; h=received:message-id:date:reply-to:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:from; b=cDPhIQg8p8jbtr00J8EhhnwNXOdlGzzmBpbd697z96ojr11Sm1HUxBQIG0pdcOdlg4RIyklwahLdw1ZqMSMwwJlgmPPpUBG2T37HkwcFjkLez29CO6E8mmzeJHTXa6TcfmP9tfPM1edfZhe56WxRiJ1bJ9sLoi3x7GLM+r1hV8U=
In-reply-to: <>
Original-recipient: rfc822;
References: <>
Reply-to: Franck <>
User-agent: Thunderbird (X11/20060614)

Jonathan Day wrote:
> Whilst I agree entirely, I think we need to put a
> little more perspective on this. The Linux kernel is
> big. Very, very big. By my estimate, it would take an
> army of 10,000+ full-time software engineers skilled
> in "Extreme Programming" and formal methods to be able
> to verify something of the complexity and intricacy of
> the Linux kernel within a single year, excluding any
> changes made during that time, which will likely
> replace so much of the code that the verification
> won't tell you much anyway.
> If every company and every University involved in
> Linux - not just every consortium - were to
> contribute, you might be able to amass that kind of
> manpower. One full-time coder for the entire of the
> MIPS side of the tree is valuable and it's doubtful
> any branch could now survive long without at least
> that, one person is simply not capable of replacing
> ten thousand, no matter how brilliant they are.

Well, I'm not sure about that. Now knowing that Ralf is not
maintaining/developing on linux-mips tree full time is a good
information to keep in mind. I think he's able to take care of any
MIPS specific code if he had time. The current number of patches sent
to linux-mips is not so big. Look at how Andrew Morton is maintaining
the mm branch. This branch is far more active and patches included in
this tree are far more complex than those sent to this mailing list.

> This isn't to say MIPS Tech should necessarily throw
> in more manpower, although I certainly wouldn't argue
> with that. It's that there's simply no realistic way
> to get enough manpower together to do code reviews in
> the kind of timeframes that people are asking for.

Well IMHO MIPS Tech may be under-estimating its Linux kernel port. I
think it's a real advantage to sell some hardwares and to give some
softwares that is already running on that hardware, specially if this
software is a full operating system like Linux. But if MIPS' customers
don't know on how fast this software will involve, will be fixed, it's
a bit scaring to rely on that software.

It would be interesting to know how well Linux is supported on the
different arches keeping in mind the market that they are targeting
(embedded, huge server...).


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