Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Tom Bogendoerfer <tsbogend@alpha.franken.de>
To: linux-parisc@vger.kernel.org
Subject: HP-UX for C8000
Date: Sat, 30 Sep 2017 17:25:06 +0200	[thread overview]
Message-ID: <20170930152506.GA10542@alpha.franken.de> (raw)

Hi,

while makeing progress on getting better graphic support for C8000
machines, I'm at a point I need some help...

Current status:

- PCI Radeon card is passing the DMA tests (using test hack)
- fixed three bugs in parisc-agp.c (wrong byte order for iommu entries,
  missing coherence information in iommu entries and missing fdc for
  ioemmu entries)
- AGP card are still not working, looks like they don't even start a DMA
  transfer at all

I'm stuck at this point as there is no documentation for quicksilver
agp available. The zx1-ioa document only covers mercury agp bridges
(used and working in ZX2000/ZX6000), but quicksilver is different
and I couldn't find the missing bit(s), yet. I now have two ideas
to make progess. I'm going to measure, if a REQ signal is issued on
the AGP bus and also look if the bridge responds with GNT. The second
idea involves HP-UX. I want to look what HP-UX does with quicksilver.

Does anyone have a C8000 with a running HP-UX on it and can help
getting a register dump of quicksilver ? Otherwise what HP-UX should
I try to get for a C8000 ?

Thomas.

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

             reply	other threads:[~2017-09-30 15:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-30 15:25 Tom Bogendoerfer [this message]
2017-09-30 17:34 ` HP-UX for C8000 John David Anglin
2017-10-01 11:46   ` Tom Bogendoerfer
2017-10-01 13:20     ` John David Anglin
2017-10-01 14:11       ` John David Anglin
2017-10-01 14:47     ` John David Anglin
2017-10-01 15:02     ` John David Anglin
2017-10-06 14:39       ` Tom Bogendoerfer
2017-10-08 16:22         ` John David Anglin
2017-10-08 16:41           ` John David Anglin
2017-10-09 15:34             ` Helge Deller
2017-10-09 16:05               ` Tom Bogendoerfer
2017-10-09 17:40                 ` John David Anglin
2017-10-09 16:30               ` John David Anglin
2017-10-09 17:41                 ` Tom Bogendoerfer
2017-10-09 22:22                   ` John David Anglin
2017-10-10  0:56                   ` John David Anglin
2017-10-10 18:46                     ` Tom Bogendoerfer
2017-10-10 22:06                       ` John David Anglin
2017-11-02  1:57                         ` Brendan Horan
2017-11-02 14:25                           ` John David Anglin
2017-11-02 16:38                             ` Tom Bogendoerfer
2017-11-02 17:45                               ` John David Anglin

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=20170930152506.GA10542@alpha.franken.de \
    --to=tsbogend@alpha.franken.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