From: "Nicholas Knight" <tegeran@home.com>
To: <drevil@warpcore.org>, <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.13-pre6 breaks Nvidia's kernel module
Date: Mon, 22 Oct 2001 21:44:41 -0700 [thread overview]
Message-ID: <003801c15b7d$6e2e4410$01c510ac@c779218a> (raw)
In-Reply-To: <20011022172742.B445@virtucon.warpcore.org> <E15vnuN-0003jW-00@the-village.bc.nu> <20011022203159.A20411@virtucon.warpcore.org> <20011022214324.A18888@alcove.wittsend.com> <20011022211622.B20411@virtucon.warpcore.org>
----- Original Message -----
From: <drevil@warpcore.org>
To: <linux-kernel@vger.kernel.org>
Sent: Monday, October 22, 2001 7:16 PM
Subject: Re: 2.4.13-pre6 breaks Nvidia's kernel module
> On Mon, Oct 22, 2001 at 09:43:24PM -0400, Michael H. Warfield wrote:
> > 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.
>
> > 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).
>
> Hmm...where did I say once that the user upgraded their version of
windows?
> Note, I said windows 'update', not windows 'upgrade'. Theoretically, based
off
> the whole "odd", "even", "stable", "unstable" numbering system that was
given,
> Kernel 2.4.x should be one 'version', and should not randomly break
> programs/drivers during it's 'completely bugfix' development? I wonder how
much
> more driver support we might see under Linux if it didn't break
compatability
> with existing drivers so much...
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
next prev parent reply other threads:[~2001-10-23 4:44 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-22 18:45 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
2001-10-23 2:16 ` drevil
2001-10-23 4:44 ` Nicholas Knight [this message]
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='003801c15b7d$6e2e4410$01c510ac@c779218a' \
--to=tegeran@home.com \
--cc=drevil@warpcore.org \
--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
all inboxes | Powered by JetHome®