linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>,
	John Cherry <cherry@osdl.org>,
	Matthew Dharm <mdharm-kernel@one-eyed-alien.net>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: Linux v2.6.9... (compile stats)
Date: Wed, 20 Oct 2004 20:29:59 -0400	[thread overview]
Message-ID: <41770307.5060304@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0410201710370.2317@ppc970.osdl.org>

Linus Torvalds wrote:
> 
> On Wed, 20 Oct 2004 viro@parcelfarce.linux.theplanet.co.uk wrote:
> 
>>>   drivers/scsi/pcmcia: 3 warnings, 0 errors
>>>   drivers/scsi: 148 warnings, 0 errors
>>
>>Mostly dealt with, but I'm still messing with SATA parts.
> 
> 
> Jeff had SATA patches - it needs to use the new iomap interfaces, and then
> it's much cleaner. I tested that his patches worked for me several weeks
> ago, but nor all architectures had the iomap interface, so I assume Jeff
> wasn't very eager to push it out.
> 
> Anyway, Al, talk to Jeff. Jeff?


Current patch is at
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/patch.iomap.bz2

I still merging stuff, so won't get around to it for another day or so :)

I certainly don't mind anyone stealing the task from me, but the effort 
is larger than the other iomap conversions.  The patch above hits all 
the easily-picked fruit, leaving the stuff that requires a modicum of 
effort:

* map/unmap N PCI bars (N >= 4, per controller)
* map/unmap 2 ISA I/O regions (0x170, 0x1f0)
* accurately handle the odd situation where IDE driver steals 0x170 
while libata steals 0x1f0 (or vice versa), a.k.a. the reason for 
quirk_intel_ide_combined() and the ____request_resource nastiness

Currently the code is set up to handle:
* N PIO ports
	or
* a single MMIO address that contains all the registers the driver needs
(mmio_base)



       reply	other threads:[~2004-10-21  0:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.58.0410181540080.2287@ppc970.osdl.org>
     [not found] ` <1098196575.4320.0.camel@cherrybomb.pdx.osdl.net>
     [not found]   ` <20041019161834.GA23821@one-eyed-alien.net>
     [not found]     ` <1098310286.3381.5.camel@cherrybomb.pdx.osdl.net>
     [not found]       ` <20041020224106.GM23987@parcelfarce.linux.theplanet.co.uk>
     [not found]         ` <Pine.LNX.4.58.0410201710370.2317@ppc970.osdl.org>
2004-10-21  0:29           ` Jeff Garzik [this message]
2004-10-21  0:44             ` Linux v2.6.9... (compile stats) viro
2004-10-21  1:55             ` viro
2004-10-21  1:59               ` Jeff Garzik
2004-10-21  2:24                 ` viro
2004-10-21  2:37                   ` Jeff Garzik
2004-10-21  4:35                     ` viro
2004-10-21  8:57                       ` 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=41770307.5060304@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=cherry@osdl.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdharm-kernel@one-eyed-alien.net \
    --cc=torvalds@osdl.org \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /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).