linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael H. Warfield" <mhw@wittsend.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.13-pre6 breaks Nvidia's kernel module
Date: Mon, 22 Oct 2001 21:43:24 -0400	[thread overview]
Message-ID: <20011022214324.A18888@alcove.wittsend.com> (raw)
In-Reply-To: <20011022172742.B445@virtucon.warpcore.org> <E15vnuN-0003jW-00@the-village.bc.nu> <20011022203159.A20411@virtucon.warpcore.org>
In-Reply-To: <20011022203159.A20411@virtucon.warpcore.org>

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!


  reply	other threads:[~2001-10-23  1:43 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-22 18:45 2.4.13-pre6 breaks Nvidia's kernel module jarausch
2001-10-22 18:51 ` Benjamin LaHaise
2001-10-22 18:51 ` Alexander Viro
2001-10-22 19:35 ` Rik van Riel
2001-10-22 19:46   ` Christopher Friesen
2001-10-22 19:53     ` Daniel T. Chen
2001-10-22 19:53 ` 2.4.13-pre6 breaks Nvidia's kernel module, or not? Stephan von Krawczynski
2001-10-22 20:24 ` 2.4.13-pre6 breaks Nvidia's kernel module Alan Cox
2001-10-22 22:27   ` drevil
2001-10-22 22:43     ` Charles Cazabon
2001-10-22 22:46     ` Doug McNaught
2001-10-22 22:50     ` Alan Cox
2001-10-23  1:31       ` drevil
2001-10-23  1:43         ` Michael H. Warfield [this message]
2001-10-23  2:16           ` drevil
2001-10-23  4:44             ` Nicholas Knight
2001-10-23  5:06               ` Cort Dougan
2001-10-23 11:36                 ` Rik van Riel
2001-10-23 16:13                 ` Alan Cox
2001-10-23  5:08               ` drevil
2001-10-23  5:18                 ` J Sloan
2001-10-23  5:59                 ` Nicholas Knight
2001-10-23  7:21                 ` Helge Hafting
2001-10-23  5:35           ` Matt D. Robinson
2001-10-23 16:16             ` Alan Cox
2001-10-23  9:50           ` David Woodhouse
2001-10-23 23:45             ` Ragnar Hojland Espinosa
2001-10-23  7:57         ` Alan Cox
2001-10-23 14:18           ` drevil
2001-10-23 16:01         ` Geert Uytterhoeven
2001-10-22 23:48     ` Jeff Golds
2001-10-22 23:53 ` Horst von Brand
2001-10-23  9:05 ` Jesper Juhl
2001-10-23 18:07   ` Josh McKinney
2001-10-23 22:51     ` J . A . Magallon
2001-10-24 21:06       ` Reid Hekman
2001-10-25  0:19         ` J . A . Magallon
2001-10-22 18:45 jarausch
2005-01-13 16:19 ` Arjan van de Ven
2005-01-13 16:50 ` Valdis.Kletnieks
2005-01-13 17:25 ` Zan Lynx
2005-01-13 17:38 ` Zwane Mwaikambo
2001-10-22 18:45 jarausch
2001-10-22 18:45 jarausch
2001-10-23  1:50 BH
2001-10-23  9:52 PVotruba
2001-10-23 12:37 Jesse Pollard
     [not found] <fa.fm7f5dv.1cn8eg6@ifi.uio.no>
     [not found] ` <fa.hbvlhav.v369au@ifi.uio.no>
     [not found]   ` <023001c15cf4$4fd5ecc0$1a01a8c0@allyourbase>
2001-10-25  4:15     ` Reid Hekman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20011022214324.A18888@alcove.wittsend.com \
    --to=mhw@wittsend.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).