From: Alexander Kern <alex.kern@gmx.de>
To: fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: 2.5.70 - Blank Screen with VESA VGA Framebuffer
Date: Sat, 14 Jun 2003 00:06:32 +0200 [thread overview]
Message-ID: <200306140006.33037.alex.kern@gmx.de> (raw)
In-Reply-To: <Pine.GSO.4.21.0306131123460.11546-100000@vervain.sonytel.be>
Am Freitag, 13. Juni 2003 11:24 schrieb Geert Uytterhoeven:
> On Fri, 13 Jun 2003, Parag Warudkar wrote:
> > You mean to say you have 2.5.XX working with VESA VGA Framebuffer or
> > ATYFB? If yes, could you please direct me to relevant sources / patches?
>
> I mean atyfb in 2.4.20. But it's not yet working out-of-the-box, it needs
> an program to play with some registers, and more investigation. Stay
> tuned...
> > > The graphics chip is ATI RAGE Mobility M1(LT) AGP2X - a MACH64 Derivate
> > > with 8Mb RAM.. For X, 3D acceleration (DRI, direct rendering) works
Hi,
search for a '"Re: [Linux-fbdev-devel] [PATCH resend] aty rage 3d mobility m1"
on the list. This is a patch on top of 2.5.69. I test and develop it with
ARMADA notebook, chip ATI RAGE 3D Mobility M1. I think, it will work with
"LTPro" too, but for "LT" I can't believe.
Daniêl's patch is only for 2.4.XX, he worked and tested with LTPro 800x600.
Regards Alex
-------------------------------------------------------
This SF.NET email is sponsored by: eBay
Great deals on office technology -- on eBay now! Click here:
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
next prev parent reply other threads:[~2003-06-13 22:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 9:04 2.5.70 - Blank Screen with VESA VGA Framebuffer Parag Warudkar
2003-06-13 9:24 ` Geert Uytterhoeven
2003-06-13 22:06 ` Alexander Kern [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-14 3:50 Parag Warudkar
2003-06-13 8:36 Parag Warudkar
2003-06-13 8:54 ` Geert Uytterhoeven
2003-06-13 2:32 Parag Warudkar
2003-06-13 8:06 ` Geert Uytterhoeven
2003-06-10 9:36 Parag Warudkar
2003-06-12 18:57 ` James Simmons
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=200306140006.33037.alex.kern@gmx.de \
--to=alex.kern@gmx.de \
--cc=linux-fbdev-devel@lists.sourceforge.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 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).