linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Dave Jones <davej@codemonkey.org.uk>,
	James Simmons <jsimmons@infradead.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	dank@reflexsecurity.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test1-ac1 Matrox Compile Error
Date: Tue, 15 Jul 2003 21:28:53 +0200	[thread overview]
Message-ID: <20030715192853.GE8240@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20030715191328.GB20424@suse.de>

On Tue, 15 July 2003 20:13:28 +0100, Dave Jones wrote:
> 
> Sorry, any vendor contemplating shipping 2.6test in a device at this stage
> is a lunatic.  I don't care about lunatics.  As we saw recently there
> are a lot of wireless routers and the like out there all stuck on some
> magical 2.4.5 kernel. That sucks, but it's at least better than putting
> beta quality code in something people pay money for.

Well, the good old embedded process is this:

Take what's availlable (2.4.5 then).
Adapt to the hardware.
Test for a while.
Ship it.
Don't touch it anymore.

So what is lunatic about doing the same with 2.6test?  It may make the
test a little more expensive, but the adaptation will be cheaper, so
you are just about even.  And the result is no less frightening than a
2.4.2 kernel with various backports from 2.4.younameit, and even more
quick hacks.

The only thing we agree on is that it would be loony to port known
working hardware to a newer kernel.

Jörn

-- 
Courage is not the absence of fear, but rather the judgement that
something else is more important than fear.
-- Ambrose Redmoon

  reply	other threads:[~2003-07-15 19:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15 16:03 2.6.0-test1-ac1 Matrox Compile Error Adam Voigt
2003-07-15 16:16 ` nick black
2003-07-15 16:40   ` James Simmons
2003-07-15 17:13     ` Dave Jones
2003-07-15 17:30       ` Alan Cox
2003-07-15 17:43         ` James Simmons
2003-07-15 17:49           ` Alan Cox
2003-07-15 18:36             ` James Simmons
2003-07-15 17:57           ` Dave Jones
2003-07-15 18:49             ` Jörn Engel
2003-07-15 19:13               ` Dave Jones
2003-07-15 19:28                 ` Jörn Engel [this message]
2003-07-15 19:32                   ` Dave Jones
2003-07-15 20:00                     ` Jörn Engel
2003-07-17 17:03             ` James Simmons
2003-07-17 17:07               ` Dave Jones
2003-07-17 17:37                 ` James Simmons
2003-07-15 17:02   ` Adam Voigt

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=20030715192853.GE8240@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dank@reflexsecurity.com \
    --cc=davej@codemonkey.org.uk \
    --cc=jsimmons@infradead.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).