From owner-freebsd-stable@FreeBSD.ORG Tue Jan 16 16:07:46 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8224716A407 for ; Tue, 16 Jan 2007 16:07:46 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (ns1.jnielsen.net [69.55.238.237]) by mx1.freebsd.org (Postfix) with ESMTP id 1F8A713C45B for ; Tue, 16 Jan 2007 16:07:46 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from localhost (jn@ns1 [69.55.238.237]) (authenticated bits=0) by ns1.jnielsen.net (8.12.9p2/8.12.9) with ESMTP id l0GG7icG001605; Tue, 16 Jan 2007 08:07:44 -0800 (PST) (envelope-from lists@jnielsen.net) From: John Nielsen To: freebsd-stable@freebsd.org Date: Tue, 16 Jan 2007 11:04:42 -0500 User-Agent: KMail/1.9.5 References: <20070115212338.9AF0516A5D9@hub.freebsd.org> <1168900436.20805.6.camel@acheron> <200701161112.29729.doconnor@gsoft.com.au> In-Reply-To: <200701161112.29729.doconnor@gsoft.com.au> X-Face: #X5#Y*q>F:]zT!DegL3z5Xo'^MN[$8k\[4^3rN~wm=s=Uw(sW}R?3b^*f1Wu*.<=?utf-8?q?of=5F4NrS=0A=09P*M/9CpxDo!D6?=)IY1w<9B1jB; tBQf[RU-R<,I)e"$q7N7 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701161104.42651.lists@jnielsen.net> X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on ns1.jnielsen.net X-Virus-Status: Clean Cc: Patrick Reich Subject: Re: 6.2 & nvidia x11 driver: weird 16bpp/24bpp colorspace damage X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jan 2007 16:07:46 -0000 On Monday 15 January 2007 19:42, Daniel O'Connor wrote: > On Tuesday 16 January 2007 09:03, Patrick Reich wrote: > > Wishful thinking: Too bad there isn't an nvidia-driver-legacy port. > > It wouldn't be too much work to split the current port into 3 separate ones > for this purpose. > > Then you could send-pr and someone could commit it :) There's already a PR open (and assigned to danfe@) that recommends this approach (ports/107717) but doesn't include any patches. Actually doing the work would go a long way toward getting it committed. JN