[Top] [All Lists]

Re: How to work with Linux-Mips ?

To: Franck Bui-Huu <>
Subject: Re: How to work with Linux-Mips ?
From: Ralf Baechle <>
Date: Tue, 26 Sep 2006 14:48:48 +0100
In-reply-to: <>
Original-recipient: rfc822;
References: <>
User-agent: Mutt/
On Tue, Sep 26, 2006 at 09:14:07AM +0200, Franck Bui-Huu wrote:

> These patchs have been kindly reviewed and acked by Atsushi Nemoto,
> but then no feedback from the MIPS team. I tried to get a status for
> MIPS team a couple of time, to know if something was wrong with them
> but MIPS people seem to not care about them. They even haven't
> bothered to take 10 seconds for replying something like:
>   - your patches are broken because...
>   - your patches do not respect our MIPS protocol, please resend...
>   - Sorry we are very busy, please hold on...

You should interpret a non-answer as exactly this.

>   - OK your patches suck please try to work on ARM chips because MIPS
>     is a very closed circle reserved to MIPS gurus.
> Another question, is that MIPS tree seems to not care about linux
> mainline release process. I actually notice that even Linus do not
> pull MIPS tree anymore during the last release candidate cycle.

While my employer encourages my activities at times there
are things that take priority and that has happened before 2.6.18 until
the time where it was too late to submit anything.  Still 2.6.18 from is usable on MIPS.

> Is MIPS aware that some of its customers are trying to make stable
> releases ?

I pass on answering a polemic question.

> Does the linux-mips team exist to ease life of its
> customers to use the linux kernel on MIPS chips or is the purpose of
> this team doing only some development for fun ?

You should draw a line between and MIPS Technologies. isn't a formal organization and not to be considered part
of MTI.  If anything call it a loosely knit group of hackers with
interest in running Linux and anything and all that has a MIPS processors.
There is more to be said I guess you rather want me to return to my
pending patches ;-)


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