From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Krzysztof Helt <krzysztof.h1@poczta.fm>
Cc: Linux-fbdev-devel <linux-fbdev-devel@lists.sourceforge.net>,
Andrew Morton <akpm@linux-foundation.org>,
Helge Deller <deller@gmx.de>,
linux-parisc@vger.kernel.org
Subject: Re: [RESEND] [PATCH] convert sticore.c to PCI ROM API
Date: Fri, 06 Jun 2008 18:27:41 -0500 [thread overview]
Message-ID: <1212794861.16182.39.camel@localhost.localdomain> (raw)
In-Reply-To: <20080606223507.0daf2b80.krzysztof.h1@poczta.fm>
On Fri, 2008-06-06 at 22:35 +0200, Krzysztof Helt wrote:
> On Thu, 05 Jun 2008 17:26:54 -0500
> James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
>
> >
> > I'm really not sure this is such a good idea. pci_map_rom() can do an
> > ioremap() on the region. In that case, gsc_readl which punches through
> > our virtual memory into physical I/O space will fail. What assurance do
> > we have that all STI roms are correctly set up so pci_map_rom() isn't
> > inclined to ioremap them?
> >
>
> I haven't thought about this. The ROM the Helge tested was obviously
> set up correctly, otherwise reading the ROM signature would be impossible.
I suspect Helge only tested GSC based cards, which will work just fine
because they use the old logic.
> What is you advise for this patch James?
The more I look at this the more I doubt that it's a good thing. STI is
really a platform driver; it has to function for both GSC and PCI
busses. pci_map_rom() seems to be a bit of a minefield designed for x86
centric video cards, which STI definitely isn't. The sticore driver is
also designed to operate on unmapped ranges ... at least this is the way
it's designed for the GSC, so the PCI part has to follow suit.
Our simple base get and enabling transparently the driver currently has
says what we're doing; I don't really see why it needs to switch to
pci_map_rom. Additionally, I fear that switching to pci_map_rom will
cause us to break later on down the road.
James
next prev parent reply other threads:[~2008-06-06 23:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 21:13 [RESEND] [PATCH] convert sticore.c to PCI ROM API Krzysztof Helt
2008-06-05 22:11 ` Andrew Morton
2008-06-06 18:52 ` Krzysztof Helt
2008-06-05 22:26 ` James Bottomley
2008-06-06 20:35 ` Krzysztof Helt
2008-06-06 23:27 ` James Bottomley [this message]
2008-06-07 9:08 ` Krzysztof Helt
2008-06-07 20:34 ` Grant Grundler
2008-06-06 21:23 ` Helge Deller
-- strict thread matches above, loose matches on Subject: below --
2008-06-07 20:51 Jon Smirl
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=1212794861.16182.39.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=deller@gmx.de \
--cc=krzysztof.h1@poczta.fm \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-parisc@vger.kernel.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).