From: Tejun Heo <htejun@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: akpm@osdl.org, linux-ide@vger.kernel.org, jeff@garzik.org
Subject: Re: [PATCH] libata: Store bus addresses (versus -mm for testing)
Date: Sat, 28 Jul 2007 17:11:42 +0900 [thread overview]
Message-ID: <46AAFA3E.50407@gmail.com> (raw)
In-Reply-To: <20070726192315.61ffe93d@the-village.bc.nu>
Alan Cox wrote:
> As we cannot reverse iomap results portably as we tried before the libata
> layer needs to keep bus addresses around for reporting. This first big
> patch adds a structure for it and teaches the drivers to keep the
> information. Thankfully most drivers go via libata-sff and it can do the
> work for them.
>
> For the others we replace ata_std_ports with ata_std_io_ports /
> std_mmio_ports and pass both the mapped and some bus address info.
>
> We don't keep all the mappings in both forms. We only need cmd, ctrl and
> status (for wait_status() reporting). We also keep a "base" for devices
> where the taskfile (cmd/ctl) mapping makes no sense.
>
> This patch stores all the data but doesn't yet change the display side.
> I've got a couple of variants I'm playing with on the display side and
> want to get that right. In the mean time this should store all the data
> and have no side effects for anyone, so is a good first chunk for testing
> alone.
>
> Signed-off-by: Alan Cox <alan@redhat.com>
Eeeek... I don't think this is a good idea. I liked the getting
original address from mapped address thing. Is it impossible to get
that working on some archs? Or is it just not there yet?
Thanks.
--
tejun
next prev parent reply other threads:[~2007-07-28 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 18:23 [PATCH] libata: Store bus addresses (versus -mm for testing) Alan Cox
2007-07-28 8:11 ` Tejun Heo [this message]
2007-07-28 11:55 ` Alan Cox
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=46AAFA3E.50407@gmail.com \
--to=htejun@gmail.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=linux-ide@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.