public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Winischhofer <tw@webit.com>
To: linux-kernel@vger.kernel.org
Subject: Re: SiS630 and 5591/5592 AGP
Date: Mon, 12 Nov 2001 17:59:55 +0100	[thread overview]
Message-ID: <3BF0000B.6F118A43@falke.mail> (raw)


Alright, AFAIK it's like this:

The SiS630 - although only one chip - contains a real bunch of
components, such as SiS300 (vga), SiS900 (network) etc. In general, all
the SiS "chips" that list in lspci are actually part of the SiS630.

The vga component, as said, the SiS300, is capable of using either
direct vga output (standard vga connector) as well a video bridge, most
of the cases SiS301.

The SiS301 is responsible for controlling TV-out and LCD panels.

The problem with the current driver for Linux (kernel) and XFree ist,
that SiS did not release any (up-to-date) data sheets on the SiS301.

Thus nobody knows how to tell the SiS300 how to tell the SiS301 that it
should enable output on - let's say - a LCD panel.

The current work-around is as Stuart said: We are forced to use VESA (ie
the BIOS) to set up a display on the LCD panel. Apart from the display
(mode) setup, the xfree sis_drv.o works perfectly. (The same applies for
SiS630 on standard CTR on vga connector; this works even without a
patch)

I've been using Stuart's patch for quite a while now and it works
flawlessly.

Thomas

-- 
Thomas Winischhofer
Vienna/Austria                  Check it out:
mailto:tw@webit.com              http://www.webit.com/tw
ICQ #63288080


             reply	other threads:[~2001-11-12 17:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-12 16:59 Thomas Winischhofer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-11 18:59 SiS630 and 5591/5592 AGP Gavin Baker
2001-11-11 23:26 ` Stuart Young
2001-11-12 14:16   ` Marco Colombo
2001-11-12 16:36   ` Gavin Baker
2001-11-13  0:15   ` Stuart Young
2001-11-13 12:20     ` Gavin Baker
2001-11-13 12:40       ` 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=3BF0000B.6F118A43@falke.mail \
    --to=tw@webit.com \
    --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