lkml.org 
[lkml]   [2001]   [Oct]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.4.13-pre6 breaks Nvidia's kernel module
On Mon, Oct 22, 2001 at 08:31:59PM -0500, drevil@warpcore.org wrote:
> On Mon, Oct 22, 2001 at 11:50:59PM +0100, Alan Cox wrote:
> > 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.

> On one side I can see this, on the other I can't. For example, no matter how
> many times a user visits windows update, chances are his drivers will still work
> with his current version of windows. Admittedly, some may not consider this a

Really? Sure as hell hasn't been my experience. Oh! That only
works with Windows 95! Ok, now you can get the driver to support Windows
98 but it won't support Windows NT (got one RIGHT NOW like that). Oops,
you upgraded to Windows 2000, can't support that with that driver, we
don't have a driver for that yet. Windows XP, sorry, we don't have the
Windows XP certified driver, yet, try back in a few months.

Think that's a joke? I think it's pathetic and it is EXACTLY
what I have experienced with multimedia cards, scanners, and printers.

> feature, but I think a lot do. Why should a 'stable' kernel series break
> existing drivers?

Why would Windows XP break all the non-MS Windows 2000 drivers
(don't you dare tell me it didn't, I work at a place that got slammed by
their shit). Why would things that work on Windows 98 (Delorme Eartha
DVD) not work on Windows NT or Windows 2000. The Windows mess is a swamp
out there of what drivers work with what version (some don't even work
between the original editions and updated editions - Windows 95 had
three editions that I have in hand).

> > 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...

Mike
--
Michael H. Warfield | (770) 985-6132 | mhw@WittsEnd.com
/\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/
NIC whois: MHW9 | An optimist believes we live in the best of all
PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of 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/

\
 
 \ /
  Last update: 2005-03-22 13:10    [from the cache]
©2003-2011 Jasper Spaans. Advertise on this site