linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: nick@acolyte.merseine.nu
To: linux-kernel@vger.kernel.org
Subject: linux 2.5+2.6 SiS 730 DRM/DRI
Date: Thu, 17 Jul 2003 05:56:16 -0400	[thread overview]
Message-ID: <20030717095616.GA27930@acolyte.merseine.nu> (raw)

i've recently upgraded to 2.6.0-test on my machines. one of them has a sis 730 video card
built into the motherboard. as i recall, the 2.4.21 kernel allowed you to compile in DRM support for SiS 630/730 cards 
in the "Character Devices" section under DRM. i've checked DRI support with glxinfo in 2.4.21 and direct rendering is
enabled, while in 2.6 it is not. do the 2.6(and 2.5) kernels have support for DRM with the SiS 630/730 chipset? i know the config
has changed, is there anything i have to compile in so i can get DRI working with these cards? the framebuffer device, frambebuffer
console and agpgart are working fine. 

                 reply	other threads:[~2003-07-17  9:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030717095616.GA27930@acolyte.merseine.nu \
    --to=nick@acolyte.merseine.nu \
    --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;
as well as URLs for NNTP newsgroup(s).