Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Tom Bogendoerfer <tsbogend@alpha.franken.de>
To: Helge Deller <deller@gmx.de>
Cc: linux-parisc@vger.kernel.org
Subject: Re: PCI resource problem on C360
Date: Sat, 12 Aug 2017 23:15:43 +0200	[thread overview]
Message-ID: <20170812211543.GA24661@alpha.franken.de> (raw)
In-Reply-To: <7312dbc6-bfba-a25b-a639-6ff7bad35e11@gmx.de>

On Tue, Aug 08, 2017 at 05:48:33PM +0200, Helge Deller wrote:
> Maybe the drivers of such NIC/SCSI cards don't request all available
> resources? 

log is clear that the pci probing stuff is not able to setup pci resources.
And that's nothing a driver fix up later (without dirty tricks of course).
The problem is that dino code doesn't set the space_offset of the host
bridge correctly for 64bit kernels. Will send a patch later.

Now aty driver is happy with the mach64 card:

atyfb 0000:00:03.0: runtime IRQ mapping not provided by arch
atyfb 0000:00:03.0: enabling device (0082 -> 0083)
atyfb 0000:00:03.0: enabling SERR and PARITY (0083 -> 01c3)
atyfb: ATI264VT2 (A4) (Mach64 VT) [0x5654 rev 0x40]
atyfb: 512K RESV, 14.31818 MHz XTAL, 200 MHz PLL, 67 Mhz MCLK, 67 MHz XCLK
Console: switching to colour frame buffer device 80x30
atyfb: fb0: ATY Mach64 frame buffer device on PCI

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      parent reply	other threads:[~2017-08-12 21:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03 14:07 PCI resource problem on C360 Tom Bogendoerfer
2017-08-03 15:58 ` John David Anglin
2017-08-03 22:45   ` Helge Deller
2017-08-03 23:17     ` John David Anglin
2017-08-08 13:40     ` Tom Bogendoerfer
2017-08-08 15:48       ` Helge Deller
2017-08-08 18:32         ` John David Anglin
2017-08-12 21:15         ` Tom Bogendoerfer [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=20170812211543.GA24661@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=deller@gmx.de \
    --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