Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 23 Oct 2001 12:02:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 23 Oct 2001 12:02:05 -0400 Received: from main.sonytel.be ([195.0.45.167]:38800 "EHLO mail.sonytel.be") by vger.kernel.org with ESMTP id ; Tue, 23 Oct 2001 12:01:52 -0400 Date: Tue, 23 Oct 2001 18:01:30 +0200 (MEST) From: Geert Uytterhoeven To: drevil@warpcore.org cc: Linux Kernel Development Subject: Re: 2.4.13-pre6 breaks Nvidia's kernel module In-Reply-To: <20011022203159.A20411@virtucon.warpcore.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 22 Oct 2001 drevil@warpcore.org wrote: > On Mon, Oct 22, 2001 at 11:50:59PM +0100, Alan Cox wrote: > > 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. > > Microsoft deals with companies that won't always give them access to the drivers > directly, but often they will tell users workarounds, or at least attempt to > gather enough knowledge since they are tehnically the OS vendor to give to the > driver provider to fix the problem. If you are the OS provider, and a change you > make breaks user drivers/programs generally I think it's a polite gesture to at > least attempt to find out what's going on and then pass that information on to > the people who can properly handle it... Of course the Linux kernel developers provide information: they even provide the sources of their kernel. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds - 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/