From owner-freebsd-hackers Wed Jul 10 14:16:54 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA14671 for hackers-outgoing; Wed, 10 Jul 1996 14:16:54 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA14664 for ; Wed, 10 Jul 1996 14:16:48 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA25223; Wed, 10 Jul 1996 15:13:01 -0600 (MDT) Date: Wed, 10 Jul 1996 15:13:01 -0600 (MDT) Message-Id: <199607102113.PAA25223@rocky.mt.sri.com> From: Nate Williams To: Terry Lambert Cc: nate@mt.sri.com (Nate Williams), jgreco@brasil.moneng.mei.com, davidg@Root.COM, hackers@freebsd.org Subject: Re: Some recent changes to GENERIC In-Reply-To: <199607102105.OAA27228@phaeton.artisoft.com> References: <199607101640.KAA23663@rocky.mt.sri.com> <199607102105.OAA27228@phaeton.artisoft.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Yes, but 'newer' SVGA cards *now* blow up when sio3 is enabled. In the > > past this wasn't a big deal, but even in 2.1R we had quite a few folks > > who got wiped out by sio3 (read Usenet), and this is only going to get > > worse with the faster S3/ATI/Mach cards becoming more commonplace. > > I posted the assembly code used to detect these cards once already. Yeah, so? By disabling the probe, we have a solution as well. Having access to pointers to all the relevant information is a good thing, but when the current solution is acceptable then a different solution won't be done. If you think the 'assembly code' probe fix is worth it, generate a set of patches and send them to me and I'll integrate them if I find them acceptable. (And I *do* understand the issues, but don't have time nor desire to fix it like you think it should be fixed.) Nate