All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Winischhofer <thomas@winischhofer.net>
To: linux-kernel@vger.kernel.org
Subject: Re: COMPILE BUG: SiS DRM Support
Date: Tue, 09 Apr 2002 09:52:13 +0200	[thread overview]
Message-ID: <3CB29DAD.DE763FEB@falke.mail> (raw)


> > > Is there any obvious reasons why this isn't compiling?
> > Try compiling with SiS framebuffer device (CONFIG_FB_SIS and
> > CONFIG_FB_SIS_300 or CONFIG_FB_SIS_315) activated... the SiS DRI driver
> > needs it... don't ask me why ;)
> 
> Because they share common code. It is actually better that they work
> together since this way they will not step on each others toes. Someday I
> plan to merge both the fbdev and drm interfaces together.

More precisely, the framebuffer driver contains all the chipset and
therefore the memory (amount/type) detection stuff. It checks for
eventual Turbo/Commandqueue capabilities (which differ significantly
depending on the actual chipset used) and sets up a memory heap taking
all the hardware specifics into account. Moving the memory management to
the DRM module will result in a lot of duplicate code and a lack of
common memory management.

If you don't want to use the framebuffer, start it with no video mode
specified or with mode=none (or mode:none if as kernel parameter)

Thomas

PS: For updates of the SiS VGA drivers, please check my homepage.

-- 
Thomas Winischhofer
Vienna/Austria                 
mailto:thomas@winischhofer.net            http://www.winischhofer.net/


             reply	other threads:[~2002-04-09  8:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-09  7:52 Thomas Winischhofer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-05 11:46 [PATCH] kernel 2.5.8-pre1, tipar: parallel link cable driver for TI graphing calculators Romain LIEVIN
2002-04-05 12:22 ` COMPILE BUG: SiS DRM Support Brett Nuske
2002-04-05 12:34   ` Sebastian Droege
2002-04-05 17:44     ` James Simmons
2002-04-05 13:07   ` 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=3CB29DAD.DE763FEB@falke.mail \
    --to=thomas@winischhofer.net \
    --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 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.