mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: Dave Airlie <airlied@linux.ie>,
	lkml <linux-kernel@vger.kernel.org>,
	akpm <akpm@linux-foundation.org>
Subject: Re: [RFC: -next patch] don't allow FB_SIS=m, DRM_SIS=y
Date: Tue, 19 Aug 2008 15:31:00 -0700	[thread overview]
Message-ID: <20080819153100.3bc3d8ef.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20080813215728.GD7071@cs181140183.pp.htv.fi>

On Thu, 14 Aug 2008 00:57:28 +0300 Adrian Bunk wrote:

> On Tue, Aug 12, 2008 at 10:37:00PM +0100, Dave Airlie wrote:
> > 
> > > > 
> > > > Maybe the other way around, I don't want DRM_SIS influencing whether 
> > > > FB_SIS is on or off, if the user wants sisfb on, then when they select it, 
> > > > DRM_SIS should be built in the same way. But if sisfb isn't selected by 
> > > > the user, then selecting DRM_SIS shouldn't enable it.
> > > 
> > > If FB_SIS=m, should DRM_SIS=y be allowed or should in this case DRM_SIS 
> > > be restricted to n/m?
> > 
> > Probably not. if FB_SIS is selected at all, DRM_SIS should match it, if 
> > FB_SIS isn't selected, DRM_SIS should not select it.
> 
> I assume FB_SIS=y, DRM_SIS=m should still be possible?
> 
> If this assumption is correct the fix is below.
> 
> > Dave.
> 
> cu
> Adrian
> 
> 
> <--  snip  -->
> 
> 
> FB_SIS=m, DRM_SIS=y is not a legal configuration.
> 
> Reported-by: Randy Dunlap <randy.dunlap@oracle.com>
> Signed-off-by: Adrian Bunk <bunk@kernel.org>
> 
> ---
> c303119b9561e13be97f3d4b0d7eaa6930fc21d8 
> diff --git a/drivers/gpu/drm/Kconfig b/drivers/gpu/drm/Kconfig
> index 610d6fd..bf9003e 100644
> --- a/drivers/gpu/drm/Kconfig
> +++ b/drivers/gpu/drm/Kconfig
> @@ -87,6 +87,7 @@ config DRM_MGA
>  config DRM_SIS
>  	tristate "SiS video cards"
>  	depends on DRM && AGP
> +	depends on FB_SIS || FB_SIS=n
>  	help
>  	  Choose this option if you have a SiS 630 or compatible video
>            chipset. If M is selected the module will be called sis. AGP
> 
> --

Thanks, Adrian.

I don't know if that's the proper fix, but something needs to be fixed/merged.  :(


---
~Randy
Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA
http://linuxplumbersconf.org/

      reply	other threads:[~2008-08-19 22:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-07 15:32 [PATCH -next] drm: sis depends on FB_SIS Randy Dunlap
2008-08-07 23:09 ` Dave Airlie
2008-08-08  0:55   ` Randy Dunlap
2008-08-08  2:11     ` Dave Airlie
2008-08-12 12:59       ` Adrian Bunk
2008-08-12 21:37         ` Dave Airlie
2008-08-13 21:57           ` [RFC: -next patch] don't allow FB_SIS=m, DRM_SIS=y Adrian Bunk
2008-08-19 22:31             ` Randy Dunlap [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=20080819153100.3bc3d8ef.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=airlied@linux.ie \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@kernel.org \
    --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

Powered by JetHome