public inbox for linux-parisc@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: debian-hppa@lists.debian.org,
	John David Anglin <dave.anglin@bell.net>,
	linux-parisc <linux-parisc@vger.kernel.org>
Subject: stifb broken on PCI - was: Upgrade woes - was Re: install/update/upgrade dance
Date: Sat, 25 May 2013 00:23:40 +0200	[thread overview]
Message-ID: <519FE86C.8070701@gmx.de> (raw)
In-Reply-To: <BLU0-SMTP46578E0659F1ECF756D7DC97AB0@phx.gbl>

On 05/24/2013 02:51 AM, John David Anglin wrote:
> On 23-May-13, at 8:36 PM, Dave Land wrote:
> 
>> May 23 10:48:21 hpviz kernel: [    1.880000] STI GSC/PCI core graphics driver V$
>> May 23 10:48:21 hpviz kernel: [    1.880000] sti 0000:01:01.0: enabling SERR an$
>> May 23 10:48:21 hpviz kernel: [    1.884000] STI PCI graphic ROM found at fffff$
>> *May 23 10:48:21 hpviz kernel: [    1.952000] Unable to handle STI device '0000:$*
> 
> 
> This is exactly the problem that I see.

Me too :-(

On my 32bit "old" parisc machine 715/64 with GSC bus it still works.

But on all my PCI machines it fails the same way.
Same result as Dave: pdc_add_valid() returns error.

For me it seems something has changed wrt PCI.

I tried to debug it somewhat, but I have no clue.
Maybe this commit is somewhat related: ?

commit 39c2462e163448c7df466c7262109ec6a24d5f88
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Feb 23 20:19:03 2012 -0700
    parisc/PCI: get rid of device resource fixups
    Tell the PCI core about host bridge address translation so it can take
    care of bus-to-resource conversion for us.

Helge

           reply	other threads:[~2013-05-24 22:23 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <BLU0-SMTP46578E0659F1ECF756D7DC97AB0@phx.gbl>]

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=519FE86C.8070701@gmx.de \
    --to=deller@gmx.de \
    --cc=dave.anglin@bell.net \
    --cc=debian-hppa@lists.debian.org \
    --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