All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Winischhofer <tw@webit.com>
To: Cesar Suga <sartre@linuxbr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: A simple patch for SIS (documentation and kbuild)
Date: Wed, 20 Feb 2002 21:53:22 +0100	[thread overview]
Message-ID: <3C740CC2.21E57B5F@webit.com> (raw)
In-Reply-To: <Pine.LNX.4.40.0202201625000.2588-100000@sartre.linuxbr.com>

Cesar Suga wrote:
> 
> On Wed, 20 Feb 2002, Thomas Winischhofer wrote:
> 
> > +SiS 300/540/630
> > +CONFIG_DRM_SIS
> > +  Choose this option if you have a SIS 300, 540 or 630 graphics card.
> > +  If M is selected, the module will be called sis.o.  AGP support is
> > +  required for this driver to work.
> 
> > Before posting patches you'd better inform yourself.
> 
> > AGP is *not* required.
> 
>         Ah, sorry. I didn't notice __MUST_HAVE_AGP to be zero. I'll take
> care.

I'd recommend the following dependencies:

Rule 1:
If SiS DRM is selected, SiS framebuffer *MUST* be selected as well

Rule 2:
If SiS framebuffer is a MODULE, SiS DRM *MUST* be a MODULE, too

Rule 3:
If SiS DRM is compiled into the kernel (which I don't recommend), sisfb
*MUST* be compiled into the kernel, too.

(SiS framebuffer can be inside the kernel, in this case DRM can be a
module)

Thomas


-- 
Thomas Winischhofer
Vienna/Austria
mailto:tw@webit.com                  *** http://www.webit.com/tw

  reply	other threads:[~2002-02-20 21:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-20 18:32 A simple patch for SIS (documentation and kbuild) Thomas Winischhofer
2002-02-20 19:27 ` Cesar Suga
2002-02-20 20:53   ` Thomas Winischhofer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-20  2:50 Jean Paul Sartre

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=3C740CC2.21E57B5F@webit.com \
    --to=tw@webit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sartre@linuxbr.com \
    /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.