From: Jeff Garzik <jgarzik@pobox.com>
To: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: [GIT PATCH] More PCI patches for 2.6.13
Date: Sat, 10 Sep 2005 19:44:18 -0400 [thread overview]
Message-ID: <43236FD2.6010501@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0509101548230.30958@g5.osdl.org>
Linus Torvalds wrote:
>
> On Sat, 10 Sep 2005, Andrew Morton wrote:
>
>>Who do I bug about these longstanding ppc64 warnings, btw ;)
>>
>>drivers/scsi/sata_svw.c: In function `k2_sata_tf_load':
>>drivers/scsi/sata_svw.c:111: warning: passing arg 2 of `eeh_writeb' makes pointer from integer without a cast
>>drivers/scsi/sata_svw.c:116: warning: passing arg 2 of `eeh_writew' makes pointer from integer without a cast
>>drivers/scsi/sata_svw.c:117: warning: passing arg 2 of `eeh_writew' makes pointer from integer without a cast
> I used to have a patch to fix them, and sent it to Jeff ages ago. At that
> point, he didn't want to use the iomap() functionality, but maybe that has
> changed.
>
> Jeff? It requires making almost all the SATA IO base pointers be iomapped:
> the current
Glad you two asked! :)
I -do- want to use iomap. The problem is that no one has yet come up
with a few that does all the proper resource reservation. Everybody
(including myself) did the ioread/iowrite part, but gave up before
handling all cases of (a) legacy ISA iomap, (b) native PCI IDE iomap,
and (c) non-standard MMIO iomap.
This "works, but leaks resources" code exists in the 'iomap' branch of
rsync://rsync.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
It languished in this incomplete stage for a while, but very recently
got moving again:
> commit 374b1873571bf80dc0c1fcceaaad067980f3b9de
> Author: Jeff Garzik <jgarzik@pobox.com>
> Date: Tue Aug 30 05:42:52 2005 -0400
>
> [libata] update several drivers to use pci_iomap()/pci_iounmap()
I actually made a promise to use iomap, since libata will benefit quite
a bit from ioread/iowrite usage. I intend to keep that promise... it's
just taking me a while to get us there. Now that I figured out the path
I want to take, we should get there around 2.6.1[56].
Jeff
next prev parent reply other threads:[~2005-09-10 23:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-10 21:07 [GIT PATCH] More PCI patches for 2.6.13 Alan Stern
2005-09-10 21:12 ` Linus Torvalds
2005-09-10 21:58 ` Jeff Garzik
2005-09-10 22:31 ` Andrew Morton
2005-09-10 22:53 ` Linus Torvalds
2005-09-10 23:44 ` Jeff Garzik [this message]
2005-09-11 0:02 ` Linus Torvalds
2005-09-11 0:17 ` Jeff Garzik
2005-09-11 0:27 ` Linus Torvalds
2005-09-10 23:02 ` Pavel Machek
2005-09-11 11:38 ` Pavel Machek
2005-09-10 22:32 ` Alistair John Strachan
2005-09-10 23:47 ` Jeff Garzik
2005-09-11 6:47 ` David Woodhouse
2005-09-11 4:41 ` Greg KH
2005-09-11 6:47 ` Alistair John Strachan
-- strict thread matches above, loose matches on Subject: below --
2005-09-11 2:34 Gabriel A. Devenyi
2005-09-09 22:07 Greg KH
2005-09-09 22:37 ` Linus Torvalds
2005-09-09 22:54 ` Greg KH
2005-09-09 23:22 ` Linus Torvalds
2005-09-09 23:28 ` Linus Torvalds
2005-09-09 23:36 ` Andrew Morton
2005-09-10 0:22 ` Linus Torvalds
2005-09-10 1:27 ` Jeff Garzik
2005-09-10 18:33 ` John W. Linville
2005-09-10 18:53 ` Linus Torvalds
2005-09-11 11:33 ` Pavel Machek
2005-09-10 10:05 ` 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=43236FD2.6010501@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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