lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <21d7e9970908201752y352f194byf10bd786dd2d383b@mail.gmail.com>
Date:	Fri, 21 Aug 2009 10:52:13 +1000
From:	Dave Airlie <airlied@...il.com>
To:	Takashi Iwai <tiwai@...e.de>
Cc:	David Airlie <airlied@...ux.ie>, gregkh@...e.de,
	dri-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] drm/kms/radeon: Add kconfig to specify the default 
	modesetting

On Thu, Aug 20, 2009 at 11:26 PM, Takashi Iwai<tiwai@...e.de> wrote:
> This patch adds a Kconfig item to specify the default radeon modeset
> value.  Also fixed the description of CONFIG_DRM_RADEON_KMS.
>
> Since KMS gives problems on some Radeon devices, it's safer to disable
> it as default on distro kernels.  But distros would love to include the
> feature itself instead of disabling KMS completely.
>
> Reference: Novell bnc#527910
>        https://bugzilla.novell.com/show_bug.cgi?id=527910

I'm sort of torn on this, when radeon KMS moves out of staging it will
be disabled by
default using the current option. It will build everything always and
disable/enable like this patch
does. I'm not willing to do that yet esp now in -rcX time as it might
break builds
on some other arches.

So if a distro isn't shipping a compatible userspace, I'd rather they
didn't ship
the kernel support built at all until we move it from staging.

AFAIK you guys don't use -ati on a lot of cards kms is useful so I'm
not sure when you'll
ever have a compatible userspace.

Dave.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ