public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@fenrus.demon.nl>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Intel x86-64 support merge
Date: Wed, 18 Feb 2004 22:21:48 +0100	[thread overview]
Message-ID: <1077139308.4479.8.camel@laptop.fenrus.com> (raw)
In-Reply-To: <200402182006.i1IK6CsS022562@hera.kernel.org>

On Wed, 2004-02-18 at 20:44, Linux Kernel Mailing List wrote:

> 	The ugliest part is probably the swiotlb code.  In fact the code for
> 	that is not even included, but just reused from IA64.  swiotlb
> 	implements the PCI DMA API using bounce buffering.  I don't like this at
> 	all, but there was no other way to support non DAC capable hardware
> 	(like IDE or USB) on machines with >3GB.  Please redirect all flames for
> 	that to the Intel chipset designers.

ehm... so why on earth did Intel cripple this new platform?????


       reply	other threads:[~2004-02-18 21:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200402182006.i1IK6CsS022562@hera.kernel.org>
2004-02-18 21:21 ` Arjan van de Ven [this message]
2004-02-18 22:57   ` [PATCH] Intel x86-64 support merge H. Peter Anvin
2004-02-18 23:16     ` Arjan van de Ven
     [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
     [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

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=1077139308.4479.8.camel@laptop.fenrus.com \
    --to=arjan@fenrus.demon.nl \
    --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