From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Ingo Molnar <mingo@elte.hu>, Alessandro Rubini <rubini@gnudd.com>,
Giancarlo Asnaghi <giancarlo.asnaghi@st.com>,
Alan Cox <alan@linux.intel.com>,
linux-pci@vger.kernel.org
Subject: Re: [rubini@gnudd.com: [PATCH V2 3/3] x86: initial support for sta2x11]
Date: Fri, 10 Feb 2012 11:52:02 -0800 [thread overview]
Message-ID: <20120210115202.33103150@jbarnes-desktop> (raw)
In-Reply-To: <20120131011928.GA5819@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
On Tue, 31 Jan 2012 02:19:29 +0100
Ingo Molnar <mingo@elte.hu> wrote:
>
> This would be yours I suppose?
>
> Thanks,
>
> Ingo
>
> ----- Forwarded message from Alessandro Rubini <rubini@gnudd.com> -----
>
> Date: Mon, 30 Jan 2012 17:09:52 +0100
> From: Alessandro Rubini <rubini@gnudd.com>
> To: linux-kernel@vger.kernel.org
> Cc: giancarlo.asnaghi@st.com, alan@linux.intel.com, tglx@linutronix.de, mingo@redhat.com,
> hpa@zytor.com, x86@kernel.org
> Subject: [PATCH V2 3/3] x86: initial support for sta2x11
>
> The "ConneXt" sta2x11 I/O Hub is a bridge from PCIe to AMBA, and is
> used as main chipset in some Atom boards. The set of peripherals it
> exports live in an AMBA bus internal to the chip, so a custom
> remapping of addresses is needed. This is implemented by fixup calls
> for the PCI deivices, based on CONFIG_X86_DEV_DMA_OPS and
> CONFIG_X86_DMA_REMAP .
>
> Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
> Acked-by: Giancarlo Asnaghi <giancarlo.asnaghi@st.com>
> Cc: Alan Cox <alan@linux.intel.com>
Looks like this depends on some x86 Kconfig options I don't have in my
tree, so I dropped the selects for them. Please check it out in my
-next tree and apply any fixes on top.
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
parent reply other threads:[~2012-02-10 19:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20120131011928.GA5819@elte.hu>]
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=20120210115202.33103150@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=alan@linux.intel.com \
--cc=giancarlo.asnaghi@st.com \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rubini@gnudd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox