Re: Merge window ...

Re: Merge window ...

[Mark.Zhan]

> RBHMA4500
> SNI RM200
> Sibyte BCM91250A-SWARM
> Wind River PPMC(New one, It'll be fixed)

I just submitted the patch of the base support to Wind River PPMC Board a few weeks ago.
So please don't remove this board. And I will submit another patch against the current
Linux/MIPS git repository, to fix the build error for this board.

Best Regards,
Mark.Zhan

Merge window ...

[Ralf Baechle]

Just a reminder that 2.6.17 is out and as usual there is now a merge
window of two weeks, so try anything that you wish to see to go to
Linus to me asap ...

  Ralf

Re: Merge window ...

[Yoichi Yuasa]

Hi Ralf,

On Mon, 19 Jun 2006 11:36:53 +0100
Ralf Baechle <ralf@linux-mips.org> wrote:

> Just a reminder that 2.6.17 is out and as usual there is now a merge
> window of two weeks, so try anything that you wish to see to go to
> Linus to me asap ...

I think we should remove old boards support.
Cannot build the following boards now.

MIPS Atlas
MIPS Malta
MIPS SEAD
EV64120
ITE 8172G
Globespan IVR
Momentum Jaguar
Toshiba JMR-TX3927
Toshiba RBTX4938
Victor MP-C30X(I'm fixing it now)
Momentum Jaguar
Momentum Ocelot-3
Momentum Ocelot-C
Momentum Ocelot-G
MyCable XXS1500
RBHMA4500
SNI RM200
Sibyte BCM91250A-SWARM
Wind River PPMC(New one, It'll be fixed)

Also the folowing boards don't have config file.

4G Systems MTX-1
AMD Alchemy Bosporus
AMD Alchemy Mirage
Jazz family
Toshiba TBTX49[23]7

These boards are candidate for removal.
If there are none objection, we can add to feature-removal-schedule.txt.

Yoichi

Re: Merge window ...

[Sergei Shtylyov]

Yoichi Yuasa wrote:

> I think we should remove old boards support.
> Cannot build the following boards now.

    Some boards named here can hardly be considered old. :-)

> Toshiba RBTX4938
> RBHMA4500

    This is the same board. I think it's too early to remove this. MV has a 
number of patches for it BTW, only there was/is no time to push them upstream.

> Sibyte BCM91250A-SWARM

    It's really too early to remove this one. MV is working on the new kernel.

> Also the folowing boards don't have config file.

> Toshiba TBTX49[23]7

    I've pushed some patches for those resently...

> These boards are candidate for removal.
> If there are none objection, we can add to feature-removal-schedule.txt.

> Yoichi

WBR, Sergei

Re: Merge window ...

[Yoichi Yuasa]

Hello,

On Mon, 19 Jun 2006 19:10:15 +0400
Sergei Shtylyov <sshtylyov@ru.mvista.com> wrote:

> > Toshiba RBTX4938
> > RBHMA4500
> 
>     This is the same board. I think it's too early to remove this. MV has a 
> number of patches for it BTW, only there was/is no time to push them upstream.
> 
> > Sibyte BCM91250A-SWARM
> 
>     It's really too early to remove this one. MV is working on the new kernel.
> 
> > Also the folowing boards don't have config file.
> 
> > Toshiba TBTX49[23]7
> 
>     I've pushed some patches for those resently...

Can you provide config file for TBTX49[23]7 ?

How about JMR-TX3927?

Yoichi

Re: Merge window ...

[Sergei Shtylyov]

Hello.

Yoichi Yuasa wrote:
>>>Also the folowing boards don't have config file.

>>>Toshiba TBTX49[23]7

>>    I've pushed some patches for those resently...

> Can you provide config file for TBTX49[23]7 ?

    Maybe later -- I'M SWAMPED... :-(

> How about JMR-TX3927?

    Well, I've sent a patch for it last autumn but it looks like this is a 
candidate for removal indeed. MV is not going to support that kernel anymore...

> Yoichi

WBR, Sergei

Re: Merge window ...

[Ralf Baechle]

On Tue, Jun 20, 2006 at 12:03:46AM +0900, Yoichi Yuasa wrote:

> 
> 4G Systems MTX-1
> AMD Alchemy Bosporus
> AMD Alchemy Mirage
> Jazz family
> Toshiba TBTX49[23]7
> 
> These boards are candidate for removal.
> If there are none objection, we can add to feature-removal-schedule.txt.

A little too much.  Malta for example works and I'm running top of tree.
Jazz is happy, SNI was doing ok and received a major upgrade just on
the weekend  and the Broadcom stuff - aside of slight bitrot is crucially
important for many projects as the provider of horsepower for native
builds.

My candidates for nuking are marked with a big red box in the wiki in
the hope somebody will fix the code:

  http://www.linux-mips.org/wiki/Category:Deprecated

Many eval boards tend to have a short livespan unlike vintage workstation
and server hardware, so I tend to be trigger happier for eval board
type of stuff.

  Ralf

Re: Merge window ...

[Karsten Merker]

On Mon, Jun 19, 2006 at 04:50:01PM +0100, Ralf Baechle wrote:
> On Tue, Jun 20, 2006 at 12:03:46AM +0900, Yoichi Yuasa wrote:

[board list]
> > These boards are candidate for removal.
> > If there are none objection, we can add to feature-removal-schedule.txt.
> 
> A little too much.  Malta for example works and I'm running top of tree.
> Jazz is happy, SNI was doing ok and received a major upgrade just on
> the weekend  and the Broadcom stuff - aside of slight bitrot is crucially
> important for many projects as the provider of horsepower for native
> builds.

Indeed - if you kick out the Broadcom Swarm support, you would
effectively kill the Debian/mips(el) build farm, which relies
heavily on this type of system.

Regards,
Karsten
-- 
#include <standard_disclaimer>
Nach Paragraph 28 Abs. 3 Bundesdatenschutzgesetz widerspreche ich der Nutzung
oder Uebermittlung meiner Daten fuer Werbezwecke oder fuer die Markt- oder
Meinungsforschung.

Re: Merge window ...

[Yoichi Yuasa]

Hello Ralf,

On Mon, 19 Jun 2006 16:50:01 +0100
Ralf Baechle <ralf@linux-mips.org> wrote:

> On Tue, Jun 20, 2006 at 12:03:46AM +0900, Yoichi Yuasa wrote:
> 
> > 
> > 4G Systems MTX-1
> > AMD Alchemy Bosporus
> > AMD Alchemy Mirage
> > Jazz family
> > Toshiba TBTX49[23]7
> > 
> > These boards are candidate for removal.
> > If there are none objection, we can add to feature-removal-schedule.txt.
> 
> A little too much.  Malta for example works and I'm running top of tree.
> Jazz is happy, SNI was doing ok and received a major upgrade just on
> the weekend  and the Broadcom stuff - aside of slight bitrot is crucially
> important for many projects as the provider of horsepower for native
> builds.

Thank you for your comment.

> My candidates for nuking are marked with a big red box in the wiki in
> the hope somebody will fix the code:
> 
>   http://www.linux-mips.org/wiki/Category:Deprecated
>
> Many eval boards tend to have a short livespan unlike vintage workstation
> and server hardware, so I tend to be trigger happier for eval board
> type of stuff.

How about EV64120 and Momentum Ocelot-G ?

Yoichi

Re: Merge window ...

[Ralf Baechle]

On Tue, Jun 20, 2006 at 10:55:55PM +0900, Yoichi Yuasa wrote:

> > the hope somebody will fix the code:
> > 
> >   http://www.linux-mips.org/wiki/Category:Deprecated
> >
> > Many eval boards tend to have a short livespan unlike vintage workstation
> > and server hardware, so I tend to be trigger happier for eval board
> > type of stuff.
> 
> How about EV64120 and Momentum Ocelot-G ?

Ocelot G was on my to be grilled list as posted a while ago I think. I
just created a wiki page for it, so it's now widely visible as death
candidate.

I'd do the same for the EV64120 - but I know nothing about that board, I
haven't heared of anybody trying to use, so it's a candidate as well.

Could anybody out there who knows enough to write a quick description of
the EV64120 write a quick wiki page?  Thanks :-)

  Ralf

Re: Merge window ...

[Ivan Korzakow]

2006/6/19, Ralf Baechle <ralf@linux-mips.org>:
> Just a reminder that 2.6.17 is out and as usual there is now a merge
> window of two weeks, so try anything that you wish to see to go to
> Linus to me asap ...

Does that mean that MIPS, eventually, is doing like others arch for
releasing ? If so does that mean that we can get a MIPS kernel from
Linus tree without pulling from the (huge) mips repo ?

Ivan.

Re: Merge window ...

[Ralf Baechle]

On Tue, Jun 20, 2006 at 05:14:02PM +0200, Ivan Korzakow wrote:

> Does that mean that MIPS, eventually, is doing like others arch for
> releasing ? If so does that mean that we can get a MIPS kernel from
> Linus tree without pulling from the (huge) mips repo ?

For some systems that is working since quite a while already.  For some
of the other platforms (Alchemy, Sibyte to name the biggest offenders)
kernel.org won't have a chance of working until somebody rewrites the
bloddy drivers for those things into something that actually can be
merged.

  Ralf