From: Tom Bogendoerfer <tsbogend@alpha.franken.de>
To: John David Anglin <dave.anglin@bell.net>
Cc: linux-parisc@vger.kernel.org
Subject: Re: HP-UX for C8000
Date: Fri, 6 Oct 2017 16:39:17 +0200 [thread overview]
Message-ID: <20171006143917.GA4906@alpha.franken.de> (raw)
In-Reply-To: <692A47DA-6F88-44E7-AA7C-2DE516387604@bell.net>
On Sun, Oct 01, 2017 at 11:02:01AM -0400, John David Anglin wrote:
> On 2017-10-01, at 7:46 AM, Tom Bogendoerfer wrote:
>
> > does it have a working graphics card ?
>
> It's a FireGL T2:
> 80:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV350 GL [FireGL T2] (rev 80)
perfect.
Took me a little bit longer to play with a method to dump quicksilver
register. Since I don't have a working HP-UX 11 box, I looked how
to do it with Linux from userspace.
dd if=/dev/mem doesn't work, because it will only give access to memory.
So I recycled my small dump program, which I only used on Linux/MIPS
so far. The nice thing is, it also works for Linux/PARISC:-)
Now the challenge is to see, if it compiles and works on HP-UX the same
way...
A correct dump should start with
3c10b412 4601b002 10000006 20c00000 0c000040 00000000 00000000 00000000
Thomas.
#include <sys/types.h>
#define __USE_LARGEFILE64
#include <sys/mman.h>
#include <fcntl.h>
#include <unistd.h>
#include <stdlib.h>
#include <stdio.h>
#define QUICKSILVER_ADDR 0xfffffffffed28000
int main(int argc, char **argv)
{
int fd;
int i;
unsigned int *agp;
fd = open("/dev/mem", O_RDWR|O_SYNC);
agp = mmap64(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE, fd,
QUICKSILVER_ADDR);
if (agp == (void *)-1) {
perror ("mmap");
exit (1);
}
for (i = 0; i < 0x800 / 4; i++) {
printf ("%08x ", agp[i]);
if ((i & 7) == 7) {
printf ("\n");
}
}
close (fd);
}
--
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-10-06 14:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-30 15:25 HP-UX for C8000 Tom Bogendoerfer
2017-09-30 17:34 ` 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 [this message]
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=20171006143917.GA4906@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=dave.anglin@bell.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