All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dan Baker" <dan_baker@eli.net>
To: "'Grant Grundler'" <grundler@dsl2.external.hp.com>
Cc: <parisc-linux@lists.parisc-linux.org>
Subject: RE: [parisc-linux] X problems...
Date: Thu, 20 Feb 2003 09:28:04 -0800	[thread overview]
Message-ID: <009c01c2d905$6d72a910$830c1bac@vli82k7dbaker> (raw)
In-Reply-To: <20030220051506.GA10418@dsl2.external.hp.com>

the other driver is at
ftp://ftp.hp.com/pub/ccd/soar2sdd/wk259/wk259mu/hpgraphics_kernel-1.5.13-1.s
rc.rpm

Sorry

Dan Baker

-----Original Message-----
From: parisc-linux-admin@lists.parisc-linux.org
[mailto:parisc-linux-admin@lists.parisc-linux.org]On Behalf Of Grant
Grundler
Sent: Wednesday, February 19, 2003 9:15 PM
To: Dan Baker
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] X problems...


On Wed, Feb 19, 2003 at 05:42:29PM -0800, Dan Baker wrote:
> BUT, I did download source code for HP's Intel linux visualize driver. I
> can't get it to compile, the assembler tells me there's an invalid opcode
> (??) in the .o file. I'm not really a programmer, so I'm hoping somebody
out
> there can take a look at what they're doing and fix it.

Well, it's not that easy even for someone who can read C.

First, some bad news:
o x86 version of the card has extra VGA cruft+BIOS.
  PA-Risc version uses STI firmware for initialization.
o IIRC, the X11 server (or maybe just gfx card driver?) is a custom,
  closed source code.  Hopefully I'm wrong and someone will correct me.
o I'll guess that many (most of the?) interesting bits are in the XF86
  hpgfx driver module. I'm assuming one exists.

Good news: 3d acceleration for x86 cards uses the same RISC engines
as the parisc cards.

Several years ago I asked someone in the HP gfx group if they
could port the HPUX driver to parisc-linux but our port wasn't
ready then (I think it is now). The gfx driver interacts *alot*
with the rest of the kernel *and* the X11 server.
The above is what I remember from conversations with people.

> The files are at
>
>
ftp://ftp.hp.com/pub/ccd/soar2sdd/wk207/wk207en/hpgraphics_kernel-1.5.3-1.sr
> c.rpm
> and
>
ftp://ftp.hp.com/pub/ccd/soar2sdd/wk207/wk207en/hpgraphics_kernel-1.5.3-1.sr
> c.rpm

uhm...'cuse me, but aren't those the same?

hth
grant
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2003-02-20 17:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030220012101.7198.23807.Mailman@dsl2.external.hp.com>
2003-02-20  1:42 ` [parisc-linux] X problems Dan Baker
2003-02-20  5:15   ` Grant Grundler
2003-02-20 17:28     ` Dan Baker [this message]
     [not found]     ` <3E54DBA200000169@ocpmta3.freegates.net>
2003-02-23  2:46       ` Grant Grundler
2003-02-21 16:17 Joel Soete
2003-02-21 16:50 ` Rüdiger Scholz
2003-02-21 17:09   ` Joel Soete
2003-02-21 17:05 ` Joel Soete
  -- strict thread matches above, loose matches on Subject: below --
2003-02-22  1:48 caslivkoff
2003-02-23  2:52 ` Grant Grundler

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='009c01c2d905$6d72a910$830c1bac@vli82k7dbaker' \
    --to=dan_baker@eli.net \
    --cc=grundler@dsl2.external.hp.com \
    --cc=parisc-linux@lists.parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.