All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Anholt <eta@lclark.edu>
To: Alexander Stohr <AlexanderS@ati.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Filip Sneppe <filip.sneppe@yucom.be>,
	faith@valinux.com, DRI Devel <dri-devel@lists.sourceforge.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: [Dri-devel] Re: 2.4.22-rc2 unresolved symbols in drm/sis.o wh en CONFIG_AGP=m
Date: Tue, 26 Aug 2003 15:27:23 -0700	[thread overview]
Message-ID: <1061936842.23451.5.camel@leguin> (raw)
In-Reply-To: <328A30E823B7D511A0BF00065B042A3B0172D80D@fgl00exh01.fgl.atitech.com>

On Sun, 2003-08-17 at 09:12, Alexander Stohr wrote:
> why wont the module compilation still pass
> when SIS fb configuration flags from the
> Linux kernel configuration are missing?
> 
> sorry if that requirement is already
> mentioned in the readme. i am just wondering.

The SiS DRM uses sisfb to allocate the framebuffer memory (XFree86 uses
sisfb, too, when present).  There is currently no fallback method for
when sisfb is not present.  I am working at the moment on removing this
requirement.  We could have ifdeffed appropriately and built a
non-functional module, but that wasn't done.

I hope nobody minds me making massive style changes on the sis DRM
code.  I find it quite ugly at the moment.

-- 
Eric Anholt                                eta@lclark.edu          
http://people.freebsd.org/~anholt/         anholt@FreeBSD.org


      reply	other threads:[~2003-08-26 22:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-17 16:12 [Dri-devel] Re: 2.4.22-rc2 unresolved symbols in drm/sis.o wh en CONFIG_AGP=m Alexander Stohr
2003-08-26 22:27 ` Eric Anholt [this message]

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=1061936842.23451.5.camel@leguin \
    --to=eta@lclark.edu \
    --cc=AlexanderS@ati.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=faith@valinux.com \
    --cc=filip.sneppe@yucom.be \
    --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.