Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 23 Oct 2001 01:10:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 23 Oct 2001 01:10:05 -0400 Received: from hq.fsmlabs.com ([209.155.42.197]:49424 "EHLO hq.fsmlabs.com") by vger.kernel.org with ESMTP id ; Tue, 23 Oct 2001 01:09:55 -0400 Date: Mon, 22 Oct 2001 23:06:31 -0600 From: Cort Dougan To: Nicholas Knight Cc: drevil@warpcore.org, linux-kernel@vger.kernel.org Subject: Re: 2.4.13-pre6 breaks Nvidia's kernel module Message-ID: <20011022230631.A976@ftsoj.fsmlabs.com> In-Reply-To: <20011022172742.B445@virtucon.warpcore.org> <20011022203159.A20411@virtucon.warpcore.org> <20011022214324.A18888@alcove.wittsend.com> <20011022211622.B20411@virtucon.warpcore.org> <003801c15b7d$6e2e4410$01c510ac@c779218a> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <003801c15b7d$6e2e4410$01c510ac@c779218a>; from tegeran@home.com on Mon, Oct 22, 2001 at 09:44:41PM -0700 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org If the binary only module in question sticks with the "published interface" (as is required) isn't it a problem in Linux then? } look buddy, you don't get it } without access to nvidia's source, we can't know what it does, where it does } it, and what we can break by doing what to the kernel } WE CAN NOT KNOW SO WE CAN NOT PREVENT IT } it is THAT simple } complain to nvidia, not the people that CAN NOT DO ANYTHING ABOUT IT - 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/