From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Olof Johansson <olof@lixom.net>,
linux-pci@vger.kernel.org, blofeldus@yahoo.com,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cardbus: Add a fixup hook and fix powerpc
Date: Wed, 16 Dec 2009 18:56:27 -0800 [thread overview]
Message-ID: <20091216185627.2ea4f3d8@jbarnes-piketon> (raw)
In-Reply-To: <1260341533.16132.20.camel@pasglop>
On Wed, 09 Dec 2009 17:52:13 +1100
Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> The cardbus code creates PCI devices without ever going through the
> necessary fixup bits and pieces that normal PCI devices go through.
>
> There's in fact a commented out call to pcibios_fixup_bus() in there,
> it's commented because ... it doesn't work.
>
> I could make pcibios_fixup_bus() do the right thing on powerpc easily
> but I felt it cleaner instead to provide a specific hook
> pci_fixup_cardbus for which a weak empty implementation is provided
> by the PCI core.
>
> This fixes cardbus on powerbooks and probably all other PowerPC
> platforms which was broken completely for ever on some platforms and
> since 2.6.31 on others such as PowerBooks when we made the DMA ops
> mandatory (since those are setup by the fixups).
>
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Ah the link failure was my fault. I had fixed up the conflict
incorrectly. It's applied now.
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2009-12-17 3:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 6:52 [PATCH] cardbus: Add a fixup hook and fix powerpc Benjamin Herrenschmidt
2009-12-09 21:37 ` Dominik Brodowski
2009-12-10 3:53 ` Benjamin Herrenschmidt
2009-12-16 19:23 ` Jesse Barnes
2009-12-16 22:01 ` Jesse Barnes
2009-12-16 22:54 ` Benjamin Herrenschmidt
2009-12-17 2:56 ` Jesse Barnes [this message]
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=20091216185627.2ea4f3d8@jbarnes-piketon \
--to=jbarnes@virtuousgeek.org \
--cc=benh@kernel.crashing.org \
--cc=blofeldus@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=olof@lixom.net \
/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