All of lore.kernel.org
 help / color / mirror / Atom feed
From: jason@openinformatics.com (Jason E. Stewart)
To: "Andrew Sharp" <andy@netfall.com>
Cc: debian-powerpc@lists.debian.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: External Monitor under Pismo
Date: 04 Apr 2001 22:55:41 -0700	[thread overview]
Message-ID: <87elv7zy8y.fsf@amadeus.openinformatics.com> (raw)
In-Reply-To: "Andrew Sharp"'s message of "Wed, 04 Apr 2001 18:58:12 -0700"


"Andrew Sharp" <andy@netfall.com> writes:

> Iain Sandoe wrote:
> >
> > because it's useful? ;-)
>
> Interesting word.  I wonder what it means.  But all seriousness
> aside, what I meant was that if I was going to do some development
> on this, I would also simultaneously work on getting the aty128
> direct driver to work.  In other words if it's already in the 128
> driver, then I would try to get that working on Pismo, rather than
> try adding CRT support to the fb driver.  I'm trying to make sense,
> really I am.  Someone else mentioned that X4 and X3 vary greatly.  I
> am aware of those differences.

I'm not clear how the drivers are all related to one another. I
believe that the framebuffer is the actual server module, while the
r128_driver.c is just the low level stuff. I'm not sure at all, but I
suppose I'll know a lot more in a few days ;-)

> OK, some I'm starting to get the clue that Pismo is the G3 powerbook
> w/ rage128, as opposed to Wallstreet, which is G3 PB w/mach64?  A
> couple more years and I'm sure I'll have it straight.

Sorry, yes, pismo is the G3 Firewire.

jas.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-04-05  5:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-04 17:29 External Monitor under Pismo Iain Sandoe
2001-04-05  1:58 ` Andrew Sharp
2001-04-05  5:55   ` Jason E. Stewart [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-04  9:21 Iain Sandoe
2001-04-04 17:01 ` Andrew Sharp
2001-04-04 18:43   ` Jason E. Stewart
2001-04-04 18:01     ` Michel Dänzer
2001-04-04 19:28       ` Jason E. Stewart
2001-04-04 21:45         ` Michel Dänzer
2001-04-04 23:19           ` Jason E. Stewart
2001-04-04 22:22             ` Michel Dänzer
2001-04-05 19:55               ` Jason E. Stewart
2001-04-05 19:48                 ` Michel Dänzer
2001-04-05 21:49                   ` Jason E. Stewart
2001-04-05 23:46               ` Jason E. Stewart
2001-04-05 23:28                 ` Michel Dänzer
2001-04-06  3:04                   ` Steven Hanley
2001-04-02 20:18 Jason E. Stewart
2001-04-03 11:24 ` Andrew Sharp
2001-04-03 15:15   ` Tuomas Kuosmanen
2001-04-04  1:12     ` Steven Hanley
2001-04-04  2:03     ` Jason E. Stewart
2001-04-04  8:38       ` Tuomas Kuosmanen
2001-04-03 18:08   ` Jason E. Stewart

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=87elv7zy8y.fsf@amadeus.openinformatics.com \
    --to=jason@openinformatics.com \
    --cc=andy@netfall.com \
    --cc=debian-powerpc@lists.debian.org \
    --cc=linuxppc-dev@lists.linuxppc.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.