From: Sylvain Munaut <tnt@246tnt.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Linux/MIPS Development <linux-mips@linux-mips.org>
Subject: Re: Linux 2.6 on AMD Alchemy Au1500
Date: Wed, 28 Jan 2004 16:46:55 +0100 [thread overview]
Message-ID: <4017D96F.2080202@246tNt.com> (raw)
In-Reply-To: <20040128153627.GB14580@linux-mips.org>
>>>Ok. Is it available on some CVS / www page ?
>>>If we eventually choose Au1500 as platform I may be able to test it as
>>>well and bug reports.
>>>
>>>
>>No yet, but I'll email it to the mailing list in the next couple of
>>days. I would consider it Beta.
>>
>>
>>
Ok, anyway I don't yet have a board ...
>>Just curious, why 2.6? 2.4 is solid, everything works, provides a mature
>>kernel and drivers ...?
>>
>>
>
>Because in the not too far future the Linux community will largely run
>away from 2.4? In fact the motivation of many developers to continue
>with 2.4 is quite down already and Marcelo is going to put 2.4 into
>deep freeze after 2.4.25.
>
>
>
Yes that's one of my main reason. And by the time the products ships to
customers it will be tested. I think that one more person testing it is
one more person able to find/debug problems.
There are also some features that are natively in 2.6 and requires
external patches / drivers in a 2.4 series kernel ( ipsec, preemption,
alsa, ... )
Sylvain Munaut
WARNING: multiple messages have this Message-ID (diff)
From: Sylvain Munaut <tnt@246tnt.com>
Cc: Linux/MIPS Development <linux-mips@linux-mips.org>
Subject: Re: Linux 2.6 on AMD Alchemy Au1500
Date: Wed, 28 Jan 2004 16:46:55 +0100 [thread overview]
Message-ID: <4017D96F.2080202@246tNt.com> (raw)
Message-ID: <20040128154655.smd7Pf1hhNIXXvmP0uRKbFbUV_THjfN6qO0mPoj1FMM@z> (raw)
In-Reply-To: <20040128153627.GB14580@linux-mips.org>
>>>Ok. Is it available on some CVS / www page ?
>>>If we eventually choose Au1500 as platform I may be able to test it as
>>>well and bug reports.
>>>
>>>
>>No yet, but I'll email it to the mailing list in the next couple of
>>days. I would consider it Beta.
>>
>>
>>
Ok, anyway I don't yet have a board ...
>>Just curious, why 2.6? 2.4 is solid, everything works, provides a mature
>>kernel and drivers ...?
>>
>>
>
>Because in the not too far future the Linux community will largely run
>away from 2.4? In fact the motivation of many developers to continue
>with 2.4 is quite down already and Marcelo is going to put 2.4 into
>deep freeze after 2.4.25.
>
>
>
Yes that's one of my main reason. And by the time the products ships to
customers it will be tested. I think that one more person testing it is
one more person able to find/debug problems.
There are also some features that are natively in 2.6 and requires
external patches / drivers in a 2.4 series kernel ( ipsec, preemption,
alsa, ... )
Sylvain Munaut
next prev parent reply other threads:[~2004-01-28 15:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 10:44 Linux 2.6 on AMD Alchemy Au1500 Sylvain Munaut
2004-01-28 15:03 ` Dan Malek
2004-01-28 15:15 ` Sylvain Munaut
2004-01-28 15:05 ` Pete Popov
2004-01-28 15:18 ` Sylvain Munaut
2004-01-28 15:22 ` Pete Popov
2004-01-28 15:36 ` Ralf Baechle
2004-01-28 15:46 ` Sylvain Munaut [this message]
2004-01-28 15:46 ` Sylvain Munaut
2004-01-28 15:57 ` Dan Malek
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=4017D96F.2080202@246tNt.com \
--to=tnt@246tnt.com \
--cc=linux-mips@linux-mips.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