All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	ksummit-2008-discuss@lists.linux-foundation.org,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-ide <linux-ide@vger.kernel.org>,
	Jeff Garzik <jeff@garzik.org>
Subject: Re: Kernel Summit request for Discussion of future of ATA (libata) and IDE
Date: Mon, 04 Aug 2008 15:48:17 -0600	[thread overview]
Message-ID: <48977921.5040403@shaw.ca> (raw)
In-Reply-To: <20080804220619.76b94ceb@lxorguk.ukuu.org.uk>

Alan Cox wrote:
>> You mentioned in the thread for Willy's patch that "some
>> controllers have quirky rules for 32bit xfers" - any details anywhere?
> 
> There are two main ones
> 
> - Some controllers only support 32bit I/O for a multiple of 32bit values
> [sometimes 'unless the fifo is disabled']. I'd have to go back over the
> docs but I think the AMD may be one of those

The AMD-766 doc I have says that when the Secondary Posted Write Buffer 
or Primary Posted Write Buffer are enabled, only 32-bit writes are 
allowed to the data port. It doesn't say anything about a restriction 
with the read prefetch buffer though.

I guess it depends if any other controllers could potentially have this 
restriction. I suspect non-multiple-of-32-bit transfers are rare enough 
we could just fall back to 16-bit IO always for them, but maybe not.

> - Some controllers (VLB generally) require a magic sequence before the
> transfer. You'll see that in the pata_legacy bits.
> 
> Alan
> 

  reply	other threads:[~2008-08-04 21:48 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.OGeO7gZvBG4obEzRbVltjSebgTQ@ifi.uio.no>
     [not found] ` <fa.KtvYE2B2yrJqUleolhtMPN9ljAQ@ifi.uio.no>
     [not found]   ` <fa.AqEKTvguYFAzDFHy/We/8MpOqmo@ifi.uio.no>
2008-08-04 20:07     ` Kernel Summit request for Discussion of future of ATA (libata) and IDE Robert Hancock
2008-08-04 19:55       ` Alan Cox
2008-08-04 21:17         ` Robert Hancock
2008-08-04 21:06           ` Alan Cox
2008-08-04 21:48             ` Robert Hancock [this message]
2008-08-06  0:21             ` Robert Hancock
2008-08-06  0:44               ` Tejun Heo
2008-08-06  2:30                 ` Robert Hancock
2008-08-06 11:27                 ` Sergei Shtylyov
2008-08-06 13:04                   ` [Ksummit-2008-discuss] " Tejun Heo
2008-08-06  8:51               ` Alan Cox
2008-08-04 21:55         ` Sergei Shtylyov
2008-08-04 21:43           ` Alan Cox
2008-08-04 22:45             ` Sergei Shtylyov
2008-08-04 22:52               ` Sergei Shtylyov
2008-08-06 11:17                 ` Sergei Shtylyov
2008-08-04 22:12         ` Mark Lord
2008-08-04 22:00           ` Alan Cox
2008-08-04 20:37       ` Jeff Garzik
2008-08-04 23:49         ` [Ksummit-2008-discuss] " Tejun Heo
2008-08-03 15:57 James Bottomley
2008-08-03 16:39 ` Alan Cox
2008-08-03 17:10   ` James Bottomley
2008-08-03 18:45     ` Alan Cox
2008-08-03 19:21       ` James Bottomley
2008-08-03 19:17         ` Alan Cox
2008-08-03 20:19           ` Bartlomiej Zolnierkiewicz
2008-08-03 22:07             ` Alan Cox
2008-08-03 19:46       ` Felix Miata
2008-08-03 22:08         ` Tejun Heo
2008-08-03 22:05           ` Alan Cox
2008-08-03 22:36             ` Tejun Heo
2008-08-03 23:23             ` Felix Miata
2008-08-04  5:37         ` Benjamin Herrenschmidt
2008-08-03 17:32   ` Willy Tarreau
2008-08-03 17:45     ` Rafael J. Wysocki
2008-08-03 17:57       ` Willy Tarreau
2008-08-04  5:35   ` Benjamin Herrenschmidt
2008-08-04 13:16   ` Kumar Gala
2008-08-04 13:07     ` Alan Cox
2008-08-03 20:09 ` Bartlomiej Zolnierkiewicz
2008-08-03 22:01   ` Alan Cox
2008-08-03 23:10 ` Jeff Garzik

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=48977921.5040403@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bzolnier@gmail.com \
    --cc=jeff@garzik.org \
    --cc=ksummit-2008-discuss@lists.linux-foundation.org \
    --cc=linux-ide@vger.kernel.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 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.