From: Jeff Garzik <jgarzik@pobox.com>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: Linus Torvalds <torvalds@osdl.org>, 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 22:37:10 -0400 [thread overview]
Message-ID: <417720D6.1030908@pobox.com> (raw)
In-Reply-To: <20041021022442.GI23987@parcelfarce.linux.theplanet.co.uk>
viro@parcelfarce.linux.theplanet.co.uk wrote:
> IDGI. Why do you insist on releasing these guys in library code? Even
Because there are two distinct and separate models of port mapping/usage:
1) A bunch of separate IO address spaces (PIO). The "mapping" is
currently done in ata_pci_init_native_mode() and ata_pci_init_legacy_mode()
2) One single linear address space (MMIO). The mapping is done in the
low-level driver.
#1 is in the library because the logic is duplicated _precisely_, across
multiple host controllers, according to a hardware specification.
Thus, if the mapping is done in the library core, so should the unmapping.
Jeff
next prev parent reply other threads:[~2004-10-21 2:37 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 ` Linux v2.6.9... (compile stats) Jeff Garzik
2004-10-21 0:44 ` 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 [this message]
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=417720D6.1030908@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).