From: David Weinehall <tao@acc.umu.se>
To: David Mosberger-Tang <David.Mosberger@acm.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Intel x86-64 support merge
Date: Thu, 19 Feb 2004 10:36:10 +0100 [thread overview]
Message-ID: <20040219093610.GF17140@khan.acc.umu.se> (raw)
In-Reply-To: <ugisi4vsql.fsf@panda.mostang.com>
On Wed, Feb 18, 2004 at 04:05:22PM -0800, David Mosberger-Tang wrote:
> >>>>> On Thu, 19 Feb 2004 00:40:24 +0100, Arjan van de Ven <arjan@fenrus.demon.nl> said:
>
> Arjan> On Wed, 2004-02-18 at 23:57, H. Peter Anvin wrote:
> >> Because they were caught by surprise and just hacked the chips
> >> they had in the pipeline, presumably.
>
> Arjan> fair enough; I hope this means the next generation has this
> Arjan> wart fixed...
>
> I wouldn't hold my breath. My impression was that the Intel chipset
> folks don't want I/O MMU because (a) Windows doesn't need it and (b)
> real machines use (close-to-)64-bit-capable hardware.
Does Windows(-users) really need anything more than ever-more advanced
graphics-adapters with ever-more buggy drivers and ever-faster CPU's,
both to support their ever-more advanced and mind numbing games. Oh,
and ever-bigger hard disks to hold their ever-growing collections of
mp3's and movies that they probably don't even listen to/watch...
Yeeshh...
Some day maybe even manufactors of Intel hardware might start to create
intelligent, thought through hardware, but I seriously doubt it.
Regards: David Weinehall
--
/) David Weinehall <tao@acc.umu.se> /) Northern lights wander (\
// Maintainer of the v2.0 kernel // Dance across the winter sky //
\) http://www.acc.umu.se/~tao/ (/ Full colour fire (/
next prev parent reply other threads:[~2004-02-19 9:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1qHr5-2tJ-39@gated-at.bofh.it>
[not found] ` <1qHr5-2tJ-37@gated-at.bofh.it>
[not found] ` <1qIZw-6b9-17@gated-at.bofh.it>
[not found] ` <1qJsI-6Be-57@gated-at.bofh.it>
2004-02-19 0:05 ` David Mosberger-Tang
2004-02-19 9:36 ` David Weinehall [this message]
[not found] <1qK5k-7g2-67@gated-at.bofh.it>
[not found] ` <1qK5k-7g2-69@gated-at.bofh.it>
[not found] ` <1qK5k-7g2-71@gated-at.bofh.it>
[not found] ` <1qK5k-7g2-73@gated-at.bofh.it>
[not found] ` <1qK5k-7g2-65@gated-at.bofh.it>
2004-02-19 22:06 ` Bill Davidsen
2004-02-20 4:03 ` David Mosberger-Tang
2004-02-20 4:19 ` Jeff Garzik
2004-02-20 7:48 ` Jes Sorensen
2004-02-21 2:07 ` David Mosberger
[not found] <200402182006.i1IK6CsS022562@hera.kernel.org>
2004-02-18 21:21 ` Arjan van de Ven
2004-02-18 22:57 ` H. Peter Anvin
2004-02-18 23:16 ` Arjan van de Ven
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=20040219093610.GF17140@khan.acc.umu.se \
--to=tao@acc.umu.se \
--cc=David.Mosberger@acm.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
all inboxes | Powered by JetHome®