All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jeremy Drake <jeremyd@apptechsys.com>
Cc: Chuck Slivkoff <caslivkoff@yahoo.com>,
	Ryan Bradetich <rbradetich@uswest.net>,
	parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] X on J5000
Date: Thu, 28 Mar 2002 00:32:54 +0100	[thread overview]
Message-ID: <20020328003254.A2300@solo.franken.de> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0203262318530.13376-100000@eiger.apptechsys.com>; from jeremyd@apptechsys.com on Tue, Mar 26, 2002 at 11:22:01PM -0800

On Tue, Mar 26, 2002 at 11:22:01PM -0800, Jeremy Drake wrote:
> On Wed, 27 Mar 2002, Chuck Slivkoff wrote:
> 
> > That would be a Visualize-FXe. It is completely different than any of
> > the supported devices.
> 
> Does this mean I don't get any X?  Maybe I could be of some help testing

correct. None of the FX card is supported at the moment, because there is
still no documenatation available. I tried to treat the framebuffer as
a 24bit non packed framebuffer, but that gives me some really odd looking
graphic. Looks like PDC sets it up to some special pixel writing mode,
because it only deals with 3 planes.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea.                                 [ Alexander Viro on linux-kernel ]

  reply	other threads:[~2002-03-28 19:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-27  1:19 [parisc-linux] X on J5000 Jeremy Drake
2002-03-27  1:39 ` Ryan Bradetich
2002-03-27  4:54   ` Jeremy Drake
2002-03-27  6:08     ` Ryan Bradetich
2002-03-27  7:09       ` Chuck Slivkoff
2002-03-27  7:22         ` Jeremy Drake
2002-03-27 23:32           ` Thomas Bogendoerfer [this message]
2002-03-27  3:20 ` Carlos O'Donell Jr.
2002-03-27  4:57   ` Jeremy Drake

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=20020328003254.A2300@solo.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=caslivkoff@yahoo.com \
    --cc=jeremyd@apptechsys.com \
    --cc=parisc-linux@parisc-linux.org \
    --cc=rbradetich@uswest.net \
    /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.