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]
Date:	Tue, 29 May 2007 12:51:53 -0400
From:	"Jon Smirl" <jonsmirl@...il.com>
To:	"Pavel Machek" <pavel@....cz>
Cc:	"Dave Airlie" <airlied@...il.com>,
	"Jesse Barnes" <jbarnes@...tuousgeek.org>,
	"Jeff Garzik" <jeff@...zik.org>,
	"Jesse Barnes" <jesse.barnes@...el.com>,
	linux-kernel@...r.kernel.org,
	"Antonino A. Daplas" <adaplas@...il.com>
Subject: Re: [RFC] enhancing the kernel's graphics subsystem

On 5/29/07, Pavel Machek <pavel@....cz> wrote:
> > I have already implemented this once and submitted a
> > patch.
>
> Seems you were not persistent enough. 'I submitted a patch long time
> ago' is still no reason to block new work.

This is a well researched area and the flaws are widely know. Adding
this new mode setting code to the kernel is not adding a new
subsystem, it is an attempt to replace an existing subsystem.  In
order to replace a subsystem the general rule is that the new one must
be better than the old one. I have not seen sufficient arguments made
to justify replacing fbdev instead of extending it.

As for writing more patches, I have been burnt once by "show us the
code" being used as a way to getting rid of someone when the people
saying "show us the code" have no intention of agreeing to the changes
being proposed. I'm not going to fall for it again.

-- 
Jon Smirl
jonsmirl@...il.com
-
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