Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 22 Oct 2001 18:44:40 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 22 Oct 2001 18:44:32 -0400 Received: from lightning.swansea.linux.org.uk ([194.168.151.1]:9489 "EHLO the-village.bc.nu") by vger.kernel.org with ESMTP id ; Mon, 22 Oct 2001 18:44:00 -0400 Subject: Re: 2.4.13-pre6 breaks Nvidia's kernel module To: drevil@warpcore.org Date: Mon, 22 Oct 2001 23:50:59 +0100 (BST) Cc: linux-kernel@vger.kernel.org In-Reply-To: <20011022172742.B445@virtucon.warpcore.org> from "drevil@warpcore.org" at Oct 22, 2001 05:27:42 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Alan Cox Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > > Only Nvidia can help you > > With a problem caused by someone else and not them? Interesting viewpoint. I > also find it interesting that people think NVidia is the sole company in control > of whether or not ther drivers are opened considering SGI and other 3rd parties > own code in the 'driver pie'. This is a simplistic naive view IMHO.... I can't debug Nvidia's code even to see why it might have broken. Its as simple as that - no politics, no agenda on them opening it, simple technical statement of fact. I really doubt Nvidia will open their driver code. I've heard them explain some of the reasons they don't and in part they make complete sense. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/