From: Tejun Heo <htejun@gmail.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: Robert Hancock <hancockr@shaw.ca>, Jeff Garzik <jeff@garzik.org>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
ksummit-2008-discuss@lists.linux-foundation.org,
linux-kernel <linux-kernel@vger.kernel.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-ide <linux-ide@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [Ksummit-2008-discuss] Kernel Summit request for Discussion of future of ATA (libata) and IDE
Date: Wed, 06 Aug 2008 22:04:27 +0900 [thread overview]
Message-ID: <4899A15B.8000800@gmail.com> (raw)
In-Reply-To: <48998A8B.9040109@ru.mvista.com>
Sergei Shtylyov wrote:
> Hello.
>
> Tejun Heo wrote:
>>> +unsigned int ata_sff_data_xfer(struct ata_device *dev, unsigned char *buf,
>>> + unsigned int buflen, int rw)
>>> +{
>>> + struct ata_port *ap = dev->link->ap;
>>> + void __iomem *data_addr = ap->ioaddr.data_addr;
>>> + unsigned int words = buflen >> 2;
>>>
>> dwords maybe?
>>
>
> Isn't word 32-bit in the 32-bit systems? We're not on 80[12]86
> (despite Intel/MS preference of calling 32-bit memory cells DWORDS)...
Well, as most of machines are 64-bit these days, discussing whether a
word means 16 or 32 bits is kind of moot. I usually just think byte,
word, dword, qword and and libata and pci assume that too -
ata_id_has_dword_io() and PCI configuration accessors. It's ultimately
a peripheral issue either way tho.
Thanks.
--
tejun
next prev parent reply other threads:[~2008-08-06 13:05 UTC|newest]
Thread overview: 21+ 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
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 ` Tejun Heo [this message]
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:32 ` Willy Tarreau
2008-08-03 17:45 ` Rafael J. Wysocki
2008-08-03 20:22 ` [Ksummit-2008-discuss] " David Woodhouse
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=4899A15B.8000800@gmail.com \
--to=htejun@gmail.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=hancockr@shaw.ca \
--cc=jeff@garzik.org \
--cc=ksummit-2008-discuss@lists.linux-foundation.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sshtylyov@ru.mvista.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 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).