From: Sven LUTHER <luther@maxime.u-strasbg.fr>
To: Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be>,
luther@dpt-info.u-strasbg.fr
Cc: Michel Daenzer <michdaen@iiic.ethz.ch>,
nardinoc@CS.UniBO.IT, Linux/APUS <linux-apus@sunsite.auc.dk>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>,
Linux Frame Buffer Device Development
<linux-fbdev@vuser.vu.union.edu>
Subject: Re: [pm2fb] update 990110 - first public release ;)
Date: Wed, 20 Jan 1999 13:34:04 +0100 [thread overview]
Message-ID: <19990120133404.F2459@maxime.u-strasbg.fr> (raw)
In-Reply-To: <Pine.LNX.4.03.9901201307200.21387-100000@mercator.cs.kuleuven.ac.be>; from Geert Uytterhoeven on Wed, Jan 20, 1999 at 01:17:16PM +0100
On Wed, Jan 20, 1999 at 01:17:16PM +0100, Geert Uytterhoeven wrote:
> On Wed, 20 Jan 1999, Sven LUTHER wrote:
> > but then since i first booted in this mode, the bottom line of the
> > screen don't get erased anymore, very anoying, particularly
> > because it worked fine before.
>
> I guess a problem with the clear_margins routine?
>
> > also, Ilario and Geert, am i right in thinking that the pm2fb
> > initialize the permedia2 chip correclty, and that, when trying to
> > accelerate X i could use it directly, without having to do
> > initialization.
>
> Yes. The X server must not do video mode initialization, but call the frame
> buffer device instead.
>
> > also there is a whole part missing in the xfree pm2 accel servers,
> > so i don't know if it would be a good idea to use them.
> >
> > Ilario, you released the pm2 includes uinder the GPL to go into
> > the kernel, is it ok to put them also in X ?
>
> I don't think that's a good idea: we want to be _integrated_ with XFree86, not
> diverge from them. So IMHO we should use the XFree86 include definitions for
> Permedia2.
Yes, ... i guess you are right, ...
but half the stuff from hw/xfree86/accel/glint is missing, i am not even sure
you can build an accelerated server from the 3.3.3.1 source, i asked on the
xfree-glint list, but got no response yet, so ...
>
> BTW, Gerd Knorr added fbdev support to XF86_SVGA. Currently it supports Matrox
> only (or no accel on other boards) in fbdev mode, but it's a good start.
> Starting from that is probably the best way to have as much acceleration
> support as possible. The unified XFree86 4.0 will be much more similar to the
> current XF86_SVGA than to the other current accelerated servers like
> XF86_{Mach64,S3,S3V}. Adding more accel code to XF68_FBDev is a waste of time.
>
> Yes, I really should try to get XF86_SVGA working on my CHRP box. Once we have
> it working for one chipset, the others should follow soon. XF86_SVGA does
> support not only Permedia2, but also ATI Mach64, S3 Trio64 and S3 ViRGE.
>
> The only things lacking in a fbdev'ed XF86_SVGA for us are the missing support
> for Amiga and Atari bitplanes.
>
> XF86_SVGA has another advantages for PPC: since it works on the `plain'
> chipset, too, we can have a unified X server that uses fbdev where available,
> and bangs the hardware completely where not (e.g. the PPC PReP boxes with S3 or
> Cirrus Logic).
>
> Sven: I'll forward Gerd's patches.
Does that mean that i could build a XF86_SVGA server that will work on with my bvision ?
but it still don't solve the problem of the missing glint stuff.
and playing with my stuff, will permit me to experiment, and later i can merge with the other stuff,
or maybee 4.0 (for when it is scheduled ?)
Friendly,
Sven LUTHER
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1999-01-20 12:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19990120120240.B2072@maxime.u-strasbg.fr>
1999-01-20 12:17 ` [pm2fb] update 990110 - first public release ;) Geert Uytterhoeven
1999-01-20 12:34 ` Sven LUTHER [this message]
1999-01-20 12:35 ` Sven LUTHER
1999-01-20 12:46 ` Geert Uytterhoeven
1999-01-20 12:54 ` Sven LUTHER
1999-01-20 13:37 ` Geert Uytterhoeven
1999-01-20 13:49 ` Sven LUTHER
1999-01-20 14:17 ` Geert Uytterhoeven
1999-01-20 14:43 ` Sven LUTHER
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=19990120133404.F2459@maxime.u-strasbg.fr \
--to=luther@maxime.u-strasbg.fr \
--cc=Geert.Uytterhoeven@cs.kuleuven.ac.be \
--cc=linux-apus@sunsite.auc.dk \
--cc=linux-fbdev@vuser.vu.union.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=luther@dpt-info.u-strasbg.fr \
--cc=michdaen@iiic.ethz.ch \
--cc=nardinoc@CS.UniBO.IT \
/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;
as well as URLs for NNTP newsgroup(s).