mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Robert Vojta <robert@v0jta.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Henrique de Moraes Holschuh <hmh@debian.org>,
	linux-kernel@vger.kernel.org
Subject: Re: SiS630S FrameBuffer & LCD
Date: Wed, 24 Oct 2001 09:54:23 +0200	[thread overview]
Message-ID: <20011024095423.E1178@ipex.cz> (raw)
In-Reply-To: <20011023153015.F4709@khazad-dum> <E15w5Yw-0000Q5-00@the-village.bc.nu>
In-Reply-To: <E15w5Yw-0000Q5-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Tue, Oct 23, 2001 at 06:42:02PM +0100

[-- Attachment #1: Type: text/plain, Size: 2236 bytes --]

> SiS actually had a much updated frame buffer console driver that never made
> it into the kernel (stuff needed fixing and I never got a reply so it
> dropped out of the tree)

  AFAIK the new informations from SiS are still doesn't working. I have this
SiS630 chipset too and I must use VesaFB for correct chipset initialization
and correct settings. VesaFB must have the same resolution and bpp which
I want in X. And I can use accelerated functions in X (not FB) by ugly hack
in sis_driver.c like, so it leaves settings from VesaFB and functions like
SiSPreSetMode(pScrn) and SiSSetMode(xf86Screens[scrnIndex], mode) are
skipped. I have this driver (precompiled) available on my pages
http://www.v0jta.net/gericom/gericom.php3?&menu=4#vga with all steps how
to make this chipset working with linux.

---
XFree86-4.1.0/xc/programs/Xserver/hw/xfree86/drivers/sis/sis_driver.c.orig
Fri Jul 13 20:42:56 2001
+++
XFree86-4.1.0/xc/programs/Xserver/hw/xfree86/drivers/sis/sis_driver.c
@@ -1210,7 +1210,9 @@
     vgaHWRestore(pScrn, vgaReg, VGA_SR_MODE);

     if ((pSiS->Chipset == PCI_CHIP_SIS300) ||
+#if 0
             (pSiS->Chipset == PCI_CHIP_SIS630) ||
+#endif
             (pSiS->Chipset == PCI_CHIP_SIS540)) {
         SiSPreSetMode(pScrn);
         SiSSetMode(pScrn, pScrn->currentMode);
@@ -1550,7 +1552,9 @@
     ScrnInfoPtr pScrn = xf86Screens[scrnIndex];
     SISPtr pSiS = SISPTR(pScrn);
     if ((pSiS->Chipset == PCI_CHIP_SIS300) ||
+#if 0
             (pSiS->Chipset == PCI_CHIP_SIS630) ||
+#endif
             (pSiS->Chipset == PCI_CHIP_SIS540))
         return SiSSetMode(xf86Screens[scrnIndex], mode);
     else
@@ -1661,7 +1665,9 @@

     /* Should we re-save the text mode on each VT enter? */
     if((pSiS->Chipset == PCI_CHIP_SIS300) ||
+#if 0
             (pSiS->Chipset == PCI_CHIP_SIS630) ||
+#endif
             (pSiS->Chipset == PCI_CHIP_SIS540)) {
         SiSPreSetMode(pScrn);
         if (!SiSSetMode(pScrn, pScrn->currentMode))

                                                            --Robert V0jta

-- 
    Robert Vojta <vojta at {pharocom.net - work | v0jta.net - private}>
          GPG: ID 1024D/A0CB7953            http://www.v0jta.net/ 

[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]

  reply	other threads:[~2001-10-24  7:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-23  6:54 Stuart Young
2001-10-23 17:30 ` Henrique de Moraes Holschuh
2001-10-23 17:42   ` Alan Cox
2001-10-24  7:54     ` Robert Vojta [this message]
2001-10-25  0:10   ` Stuart Young
2001-10-25  0:20   ` Stuart Young
2001-10-25 12:50     ` Alan Cox

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=20011024095423.E1178@ipex.cz \
    --to=robert@v0jta.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hmh@debian.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®