From: Martin Dalecki <dalecki@evision-ventures.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andries.Brouwer@cwi.nl, torvalds@transmeta.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: [PATCH] IDE clean 12 3rd attempt
Date: Thu, 28 Feb 2002 15:19:29 +0100 [thread overview]
Message-ID: <3C7E3C71.6050604@evision-ventures.com> (raw)
In-Reply-To: <UTC200202241352.g1ODqeb08003.aeb@apps.cwi.nl> <3C79435E.8030208@evision-ventures.com> <20020228094444.GB750@elf.ucw.cz>
Pavel Machek wrote:
> I sure hope they do.
>
> I run 2.4.x on 486sx, which is .... pretty close to 386. 386 support
> is not going to get dropped anytime soon...
Well the 486sx is the same die as 486 with coproc disabled. And in
contrast the the 386 the 486 is a scalar, tough not super-scalar CPU.
(This is what this "pipline stuff" and multiple pipeline stuff is about ;-).
Please trust me they are *not* very similar from CPU design point
of view. They are only similar on the command set level.
Anyway just to put it straight: Your system certainly won't be affected
by the removal.
next prev parent reply other threads:[~2002-02-28 14:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-24 13:52 [PATCH] Re: [PATCH] IDE clean 12 3rd attempt Andries.Brouwer
2002-02-24 19:47 ` Martin Dalecki
2002-02-24 19:54 ` arjan
2002-02-24 20:02 ` Martin Dalecki
2002-02-24 20:45 ` Arjan van de Ven
2002-02-24 21:05 ` Martin Dalecki
2002-02-24 21:03 ` Vojtech Pavlik
2002-02-24 19:58 ` [PATCH] IDE clean 13 Martin Dalecki
2002-02-24 21:17 ` Martin Dalecki
2002-02-24 20:02 ` [PATCH] Re: [PATCH] IDE clean 12 3rd attempt Eric Krout
2002-02-24 20:41 ` Alan Cox
2002-02-28 9:44 ` Pavel Machek
2002-02-28 14:19 ` Martin Dalecki [this message]
2002-02-28 18:01 ` Jeff Garzik
2002-02-28 18:13 ` Martin Dalecki
2002-02-25 11:45 ` Paul Gortmaker
2002-02-25 12:03 ` Martin Dalecki
-- strict thread matches above, loose matches on Subject: below --
2002-02-25 1:29 Andries.Brouwer
2002-02-25 1:33 Andries.Brouwer
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=3C7E3C71.6050604@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=torvalds@transmeta.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.