All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michel Dänzer <daenzer@relog.ch>
To: SteffenH@hyperion-software.de
Cc: Iain Sandoe <iain@sandoe.co.uk>,
	takashi oe <toe@unlserve.unl.edu>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: LinuxPPC X Server
Date: Mon, 31 Jul 2000 11:03:14 +0200	[thread overview]
Message-ID: <398540D2.78A1388E@relog.ch> (raw)
In-Reply-To: yam8247.1300.146578880@mail.lf-online.de


Steffen Haeuser wrote:

> >agpgart was required _for r128 DRI_ until some time ago. It's possible that
> >it's still needed by the driver in X 4.0.1 but definitely not in the latest
> >DRI CVS.
>
> That is really good news :) If anyone had the chance to try it out, please
> tell so...

Hold on, I will :)


> if this works, we might even take some of you guys into the Sin Beta Tester
> programs, if I remember right, we still need a handful of testers (but I
> have to check with the guy doing the Betatester issues in our company...).

I for one wouldn't say no...


> Driver Coding normally has not that much to do with the OS... :)
> The main work is to find out how this Chip works, and then duplicate the
> functionality of an API by using the Chip Registers (and some of those
> sometimes do things in a *really cruel way*... some years ago I had to do
> some stuff on the old Virge chip...
> this was nasty...) The difficult is usually the register setup... not the
> interface to the OS...

AFAIK the specs for Rage128 aren't publicly available, but there's working
code in DRI - I'm convinced it will be far more easier to get it working than
write something new from scratch.


Michel


--
UNIX is like Sex:
If you don't know it, you don't miss it. But if you know it, you'll need it.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

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

  reply	other threads:[~2000-07-31  9:03 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-30 20:33 LinuxPPC X Server Iain Sandoe
2000-07-31  7:50 ` Michel Dänzer
2000-07-31  9:25   ` Steffen Haeuser
2000-07-31  8:47     ` Michel Dänzer
2000-07-31 10:05       ` Steffen Haeuser
2000-07-31  9:03         ` Michel Dänzer [this message]
2000-07-31 10:21           ` Steffen Haeuser
2000-08-01 12:54       ` Kostas Gewrgiou
2000-08-01 16:25         ` Steffen Haeuser
2000-08-01 21:06         ` Daniel Jacobowitz
2000-08-02  9:20           ` Michel Dänzer
2000-08-02 18:17           ` Kostas Gewrgiou
  -- strict thread matches above, loose matches on Subject: below --
2000-08-02 16:07 Jack Howarth
2000-08-03 13:27 ` Kostas Gewrgiou
2000-08-02  0:25 Iain Sandoe
2000-07-31 14:07 Benjamin Herrenschmidt
2000-08-01 19:05 ` Michel Dänzer
     [not found]   ` <20000801191739.26835@mailhost.mipsys.com>
2000-08-01 19:37     ` Michel Dänzer
     [not found]       ` <20000801204113.29901@mailhost.mipsys.com>
2000-08-01 21:31         ` Michel Dänzer
2000-08-02 12:45           ` Geert Uytterhoeven
2000-08-02 23:27             ` Michel Dänzer
2000-07-30 21:24 Iain Sandoe
2000-07-31 12:53 ` Josh Huber
2000-07-31 16:28   ` Michael Schmitz
2000-07-30 20:00 Iain Sandoe
2000-07-30 18:14 ` Michel D nzer
2000-07-30 22:33   ` Steffen Haeuser
2000-07-31  3:12   ` Daniel Jacobowitz
2000-07-31  7:40     ` Michel Dänzer
2000-08-01 21:03       ` Daniel Jacobowitz
2000-07-31 16:05   ` Michael Schmitz
2000-08-02 10:40     ` Martin Costabel
2000-07-30 22:46 ` Steffen Haeuser
2000-07-30 16:56 Iain Sandoe
2000-07-30 19:29 ` Steffen Haeuser
2000-07-30 21:13 ` Timothy A. Seufert
2000-07-29 13:31 Steffen Haeuser
2000-07-29 22:55 ` Takashi Oe
2000-07-30 11:27   ` Steffen Haeuser
2000-07-30 11:54     ` Takashi Oe
2000-07-30 14:40       ` Steffen Haeuser
2000-07-30 14:41         ` Takashi Oe
2000-07-30 16:13           ` Steffen Haeuser

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=398540D2.78A1388E@relog.ch \
    --to=daenzer@relog.ch \
    --cc=SteffenH@hyperion-software.de \
    --cc=daenzerm@student.ethz.ch \
    --cc=iain@sandoe.co.uk \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=toe@unlserve.unl.edu \
    /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.