From: Jurriaan <thunder7@xs4all.nl>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH 1/2] fbdev: S3 Savage Framebuffer Driver
Date: Wed, 10 Nov 2004 20:17:35 +0100 [thread overview]
Message-ID: <20041110191735.GA19864@middle.of.nowhere> (raw)
In-Reply-To: <200410230436.42009.adaplas@hotpop.com>
From: Antonino A. Daplas <adaplas@hotpop.com>
Date: Sat, Oct 23, 2004 at 04:36:41AM +0800
> S3 Savage Frambuffer Driver for the following chipsets:
>
> Savage 3D
> Savage MX
> Savage 4
> Savage 2000
> ProSavage
> SuperSavage
>
Excellent. I tried this (in 2.6.10-rc1-mm4) with my Thinkpad T23, which
has a SuperSavage IX/C SDR according to lspci.
If I compile the framebuffer into the kernel, it hangs during boot. The
oops is only partly visible, but the first line of the traceback
contains savage_setup_i2c_bus.
If I compile it as a module, it comes up with 800x600, which looks like
sh*t on a 1024x768 lcd panel. All my attempts to change the resolution,
either with fbset, or variations on this command
modprobe savagefb mode=1024x768-60
didn't work.
Would you give me any hints on how to get it to come up with 1024x768?
I would love to see if it's faster than the vesa framebuffer I've been
using so far.
Thanks,
Jurriaan
--
I am the neurosis that requires a $500 an hour shrink
Darkwing Duck
Debian (Unstable) GNU/Linux 2.6.9-mm1 2x6078 bogomips load 0.84
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
next prev parent reply other threads:[~2004-11-10 19:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 20:36 [PATCH 1/2] fbdev: S3 Savage Framebuffer Driver Antonino A. Daplas
2004-10-22 23:38 ` Denis Oliver Kropp
2004-10-25 9:02 ` Andrew Morton
2004-10-25 12:34 ` Antonino A. Daplas
2004-11-10 19:17 ` Jurriaan [this message]
2004-11-11 2:23 ` Antonino A. Daplas
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=20041110191735.GA19864@middle.of.nowhere \
--to=thunder7@xs4all.nl \
--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 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.