From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH] powerpc: Add legacy PCI access via sysfs
Date: Fri, 10 Oct 2008 09:02:29 -0700 [thread overview]
Message-ID: <200810100902.30191.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <20081010025101.B48CADDEF7@ozlabs.org>
On Thursday, October 9, 2008 7:50 pm Benjamin Herrenschmidt wrote:
> This patch adds support for legacy_io and legacy_mem files in
> bus class directories in sysfs for powerpc
>
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> ---
>
> This is version 2, slightly different approach for getting at VGA
> memory which works a lot better with bridges providing a separate
> ISA Memory hole (which is the case of most of them).
>
> Also tested on a variety of hardware with a little tool using x86emu
> to run VGA BIOSes, do VBE calls and whack text mode.
>
> This patch relies on its generic counterpart, posted previously
> being applied first.
>
> Jesse, due to the dependency, it's better if we have both in
> the powerpc tree -or- both in the PCI tree, what do you think
> is best ? Either that or I have to delay applying it to powerpc
> until you get the generic part in.
Ah I was worried the first one might need a respin, but it applied fine, so
I'll go ahead and apply this one too.
Thanks,
Jesse
next prev parent reply other threads:[~2008-10-10 16:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 2:50 [PATCH] powerpc: Add legacy PCI access via sysfs Benjamin Herrenschmidt
2008-10-10 16:02 ` Jesse Barnes [this message]
2008-10-10 23:19 ` Benjamin Herrenschmidt
2008-10-10 17:39 ` Jesse Barnes
2008-10-13 14:07 ` Josh Boyer
2008-10-13 17:29 ` Jesse Barnes
2008-10-13 23:39 ` Benjamin Herrenschmidt
2008-10-14 0:32 ` Benjamin Herrenschmidt
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=200810100902.30191.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=benh@kernel.crashing.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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 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).