From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
Anton Blanchard <anton@samba.org>
Subject: Re: [RFC/PATCH] powerpc: Rewrite IO allocation & mapping on powerpc64
Date: Tue, 15 May 2007 10:06:17 +1000 [thread overview]
Message-ID: <1179187577.32247.140.camel@localhost.localdomain> (raw)
In-Reply-To: <200705150139.41722.arnd@arndb.de>
> An interesting case is the frame buffer, most fb drivers use hardcoded
> register numbers for the VGA ports, without calling check_legacy_ioport,
> but rely on PCI probing to detect the presence of the device.
> Some IDE drivers do the same, but libata does not. Apparently, these
> are already broken if you plug such hardware into a secondary PCI bus.
VGA is on my todo list for a fix. A lot of framebuffers don't access
legacy VGA ports though. I'm pretty sure none of the ATI or nvidia ones
do nowadays.
We need three different things I beleive:
- A clean/generic way to obtain the pci_dev for vgacon/vesafb
- A nice hook to provide an IO "offset" for a given PCI bus for legacy
accesses (which is allowed to fail if that bus cannot do it).
- Same for VGA memory
Ben.
next prev parent reply other threads:[~2007-05-15 0:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 7:53 [RFC/PATCH] powerpc: Rewrite IO allocation & mapping on powerpc64 Benjamin Herrenschmidt
2007-05-14 7:59 ` Benjamin Herrenschmidt
2007-05-14 8:03 ` Benjamin Herrenschmidt
2007-05-14 9:18 ` Benjamin Herrenschmidt
2007-05-14 13:50 ` Segher Boessenkool
2007-05-14 20:53 ` Benjamin Herrenschmidt
2007-05-15 0:17 ` Paul Mackerras
2007-05-15 4:33 ` Segher Boessenkool
2007-05-15 6:04 ` Benjamin Herrenschmidt
2007-05-14 14:37 ` Arnd Bergmann
2007-05-14 15:04 ` Segher Boessenkool
2007-05-14 23:56 ` Arnd Bergmann
2007-05-15 0:05 ` Olof Johansson
2007-05-14 20:59 ` Benjamin Herrenschmidt
2007-05-14 23:39 ` Arnd Bergmann
2007-05-15 0:06 ` Benjamin Herrenschmidt [this message]
2007-05-15 10:56 ` Christoph Hellwig
2007-05-15 20:42 ` 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=1179187577.32247.140.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=anton@samba.org \
--cc=arnd@arndb.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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