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: Tue, 8 Aug 2017 15:40:12 +0200 [thread overview]
Message-ID: <20170808134012.GA7601@alpha.franken.de> (raw)
In-Reply-To: <4d46bfba-170f-2c79-cf69-45d02ccc5a9f@gmx.de>
On Fri, Aug 04, 2017 at 12:45:31AM +0200, Helge Deller wrote:
> I had lots of such problems when I tried various VGA and other
> PCI cards in my c3000.
I know, but the get a MACH64 card up to sync in a B2600, with a small
change in aty driver. And the change is because Astro/Elroy behave incorrect
in respect to PCI standards, IMHO. It looks like it colapses multiple PCI
mem accesses into one access.
aty_st_8(CLOCK_CNTL_ADDR, ((offset << 2) & PLL_ADDR) | PLL_WR_EN, par);
/* write the register value */
aty_st_8(CLOCK_CNTL_DATA, val & PLL_DATA, par);
aty_st_8(CLOCK_CNTL_ADDR, ((offset << 2) & PLL_ADDR) & ~PLL_WR_EN, par);
B2600 HPMCs in this code sequence, probably because the two accesses
to CNTL_ADDR end up in just the last access. Placing in aty_ld_8 after
the first aty_st_8 avoids the problem. In a B180 everything is fine,
so Dino doesn't do that. Next testbed is the C360, which shows the PCI
resourec issue before it even comes to aty drvier.
> I think HP designed many of the PCI slots for special usage only,
> e.g. some slots allow PCI graphic cards while others don't.
>
> Maybe plug your cards one-by-one into another slot and check again?
will do that, but what looks strange to me is the fact that ethernet and
scsi also don't get all resources assigned. This happened without the VGA
card plugged in, too.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2017-08-08 13:40 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 [this message]
2017-08-08 15:48 ` Helge Deller
2017-08-08 18:32 ` John David Anglin
2017-08-12 21:15 ` Tom Bogendoerfer
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=20170808134012.GA7601@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