On Mon, Oct 22, 2001 at 09:44:41PM -0700, Nicholas Knight wrote:
> 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
Thanks for the all caps, I love being deafened. However, I do "get it buddy."
Secondly, I don't believe for a second that it isn't possible to trace things
down even in a 'binary-only' driver. I trace things down in a 'binary-only'
program every day practically when dealing with software, many times having the
source to a program doesn't even help me. Often I find myself using strace or
some other program to trace the execution flow of a program because it is often
more informative then the poorly written source.
I'm not complaining about the NVidia driver here. I'm simply stating that IMHO,
I find it odd that for years microsoft has not only retained binary
compatability within a release of windows but API compatability. There should
not be a change to the kernel that would require changes in the driver in a
"stable development" release tree, it's really that simple in my perhaps
somewhat limited view. Admittedly, this breakage (which is still in doubt) that
might have happened did happen with a "pre" version, but I feel this response
would have been no different even if that was not the case.
And as I've mentioned before, I know of specific cases (which I'm not allowed to
divulge) where microsoft did not have access to the vendor's source to a
specific driver, but they collected information that was then forwarded on to
the vendor to handle the request. Nowhere during this entire 'discussion' did I
see an offer to help the user possibly collect that information in a manner that
would be helpful to the vendor, nor an offer of somewhat more information
than "go cry to your vendor, you poor sap" effectively. That is what, if
anything, I'm complaining about.
I deal with issues often day during the course of developing software for my
company that are often caused by other vendor's software, but does that mean I
can tell all my customers "I'm sorry, a change I made or a bug in your vendor's
software prevents this from functioning properly, and I can't help you at all."
My customers wouldn't accept that answer for a minute, they demand something
more than "sorry, it's not my fault." Often times we spend a good amount of time
researching and finding a way to work around the issues with that vendor's
product, which sometimes even involve "fixes" to our own product that exist for
no other reason than because of that vendor's issues. And guess what, we still
have customers :) And considering we're a somewhat small business in a dismal
economy I attribute part of our success to that very thing...
-
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/
This archive was generated by hypermail 2b29 : Tue Oct 23 2001 - 21:00:34 EST