From: Kumar Gala <kumar.gala@freescale.com>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: akpm <akpm@osdl.org>,
linuxppc-dev@ozlabs.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][PPC32] Add setup_indirect_pci_nomap() routine
Date: Mon, 8 Nov 2004 17:02:01 -0600 [thread overview]
Message-ID: <32E32A44-31DA-11D9-9BE7-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <418FF992.8040604@mvista.com>
Mark,
Out of interest, why would we not want to ioremap the cfg addr/data
registers?
- kumar
On Nov 8, 2004, at 4:56 PM, Mark A. Greer wrote:
> This patch adds a routine that sets up indirect pci config space access
> but doesn't ioremap the config space addr/data registers.
>
> Signed-off-by: Mark Greer <mgreer@mvista.com>
> <indirect_pci.patch>
WARNING: multiple messages have this Message-ID (diff)
From: Kumar Gala <kumar.gala@freescale.com>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: "lkml" <linux-kernel@vger.kernel.org>, "akpm" <akpm@osdl.org>,
<linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH][PPC32] Add setup_indirect_pci_nomap() routine
Date: Mon, 8 Nov 2004 17:02:01 -0600 [thread overview]
Message-ID: <32E32A44-31DA-11D9-9BE7-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <418FF992.8040604@mvista.com>
Mark,
Out of interest, why would we not want to ioremap the cfg addr/data
registers?
- kumar
On Nov 8, 2004, at 4:56 PM, Mark A. Greer wrote:
> This patch adds a routine that sets up indirect pci config space access
> but doesn't ioremap the config space addr/data registers.
>
> Signed-off-by: Mark Greer <mgreer@mvista.com>
> <indirect_pci.patch>
next prev parent reply other threads:[~2004-11-08 23:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-08 22:56 [PATCH][PPC32] Add setup_indirect_pci_nomap() routine Mark A. Greer
2004-11-08 22:56 ` Mark A. Greer
2004-11-08 23:02 ` Kumar Gala [this message]
2004-11-08 23:02 ` Kumar Gala
2004-11-08 23:55 ` Mark A. Greer
2004-11-08 23:55 ` Mark A. Greer
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=32E32A44-31DA-11D9-9BE7-000393DBC2E8@freescale.com \
--to=kumar.gala@freescale.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mgreer@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 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.