Support for new TV card models: MM CD Update 1.26

[tjaoz]

@Trev

I don't think I mentioned 3D drivers anywhere in my initial comments. You brought it up.

Unfortunately, it is you who mentioned there 3dfx Glide and their 3D API.
See your post of 2004/9/15 21:18 Updated 2004/9/15 22:12

The largest number of drivers? Elbox wrote two, the OpenPCI crew (or someone else--I don't
know who) wrote one. Yes, things are really heating up in the race to provide display drivers for Amiga PCI busboards.

Do you have problems with counting? Elbox wrote two drivers? Check here to see all the available drivers for Mediator.

Objection. Leading the witness. But I'll answer anyway. No, it's not true:
http://cvsweb.xfree86.org/cvsweb/xc/programs/Xserver/hw/xfree86/drivers/nv/

I didn't ask you to give a link to linux sources, but to give but a single link where NVidia chipset
documentation is available. Can you give such a link?

Why are you being such an asshole? Why not try to be helpful instead? Aren't we both Amiga
users? [Putting on my tjaoz hat.] You're obviously just a troll who loves Elbox and doesn't give a {bleep} about anyone other than himself. (Please forgive me if American sarcasm doesn't translate well in your society.)

 
As you wrote, you are not a Mediator user. What is a reason of your anti-Elbox trolling here?

If you have lots of Matrox Millenium II cards and you need drivers for them, get up your ass and write these drivers instead of barking at Elbox. Opsss..., sorry..., it not so easy as trolling here...  :lol:

[Trev]

Unfortunately, it is you who mentioned there 3dfx Glide and their 3D API.

You're right, I mentioned 3dfx and their disposition towards Glide; however, I didn't say anything about Warp3D display drivers. You've misinterpreted my statements. English doesn't appear to be your native language, so I apologize for the misunderstanding. Unfortunately, speaking a language other than English is neither mandatory nor even encouraged in the United States, so English is the only language I know (unless you count dirty words and chat up lines in French). Sorry. . . .

Do you have problems with counting? Elbox wrote two drivers? Check here to see all the available drivers for Mediator.

Let's see. Voodoo.card (one) and Virge.card (two). It looks like the total is still two display drivers. Perhaps your understanding of the number two is different from mine.

I didn't ask you to give a link to linux sources, but to give but a single link where NVidia chipset documentation is available. Can you give such a link?

You didn't specify the type of documentation. It's not my fault you can't read C source code.

As you wrote, you are not a Mediator user. What is a reason of your anti-Elbox trolling here?

I'm criticizing Elbox's lack of support for modern display adapters and their closed developer program. As an Amiga user and a prospective PCI busboard buyer, I'm certainly entitled to my opinions.

If you have lots of Matrox Millenium II cards and you need drivers for them, get up your ass and write these drivers instead of barking at Elbox. Opsss..., sorry..., it not so easy as trolling here...

I'm working on the framework for an open source VGA/SVGA 2D driver right now. Whether or not it gets released depends on the licensing restrictions put in place by Elbox, OpenPCI, and Picasso96. It's a fun project, but I'll need the community's help with testing . . . and I don't yet know if the parties involved will let that happen. I'm feeling positive about OpenPCI and Picasso96. Stay tuned.

Trev

[tjaoz]

@Trev

You're right, I mentioned 3dfx and their disposition towards Glide; however, I didn't say anything about Warp3D display drivers. You've misinterpreted my statements.

Oh yes? So what Mediator 3dfx drivers if not Warp 3D drivers you had on your mind writing: "The Mediator 3dfx drivers are almost certainly based on stolen intellectual property. [...], and I don't recall Nvidia starting a 3dfx licensing program." and "They were especially closelipped about Glide, their 3D API,[...]?"

English doesn't appear to be your native language, so I apologize for the misunderstanding.

Sure, English is not my native language. But I think that these "misunderstandings" result mostly from the fact that you are not well versed in the issue about which you talk so easily.

Let's see. Voodoo.card (one) and Virge.card (two). It looks like the total is still two display drivers. Perhaps your understanding of the number two is different from mine.

If they put support for all graphic cards for Mediator in one driver and called it Mediatorgraphic.card, would that mean support for one graphic card only? We talk here about the number of supported chipsets (like: VSA-100, Avenger, Banshee, S3 86C375, S3 86C325), not number of driver file names.

You didn't specify the type of documentation.

"Documentation" doesn't mean Linux sources, right? Documentation as a rule is a pretty thick book (electronic or paper) with descriptions of all registers, chipset operation, etc. Who thinks seriously about writing drivers, shouldn't he know what documentation is?

BTW. Asking you again: Can you give a single link where NVidia chipset documentation is available?

I'm criticizing Elbox's lack of support for modern display adapters and their closed developer program.

Elbox produces a PCI busboard, not graphic cards. They wrote such drivers which they wanted. You can equally well criticise the Zorro busboard producer for lack of support for better graphic chipsets than S3 Virge (installed in CyberVision 64 3D).

I'm working on the framework for an open source VGA/SVGA 2D driver right now. Whether or not it gets released depends on the licensing restrictions put in place by Elbox, OpenPCI, and Picasso96.

O!? So you have now those potential guilty of your failure in writing these drivers? Are your skills not taken into account here, Trev?

I'm feeling positive about OpenPCI and Picasso96.

Positive feelings about OpenPCI and Picasso96? Why? Because, unlike Elbox, they have done nothing new so far for users of Amiga PCI busboards?

[Trev]

Oh yes? So what Mediator 3dfx drivers if not Warp 3D drivers you had on your mind writing: "The Mediator 3dfx drivers are almost certainly based on stolen intellectual property. [...], and I don't recall Nvidia starting a 3dfx licensing program." and "They were especially closelipped about Glide, their 3D API,[...]?"

I didn't have Warp3D in mind at all. My description of 3dfx's position on their APIs was anecdotal. Let's just consider this one lost in translation and let it go.

Sure, English is not my native language. But I think that these "misunderstandings" result mostly from the fact that you are not well versed in the issue about which you talk so easily.

You have a lot to learn about international communication. Granted, I only speak English, but I'm always aware that what I say and/or write may not be properly interpreted by a non-English speaking individual.

If they put support for all graphic cards for Mediator in one driver and called it Mediatorgraphic.card, would that mean support for one graphic card only? We talk here about the number of supported chipsets (like: VSA-100, Avenger, Banshee, S3 86C375, S3 86C325), not number of driver file names.

*sigh*

"Documentation" doesn't mean Linux sources, right? Documentation as a rule is a pretty thick book (electronic or paper) with descriptions of all registers, chipset operation, etc. Who thinks seriously about writing drivers, shouldn't he know what documentation is?

Actually, souce code does qualify as documentation. In this case, the documentation is written in C. How is that any different from documentation written in English, German, etc.? They're all languages used to communicate ideas. Shall I satisfy your need for troll fodder? Why not. No, I don't know of any publicly available documentation written in a language other than C that details the inner workings of Nvidia's various chipsets.

Elbox produces a PCI busboard, not graphic cards. They wrote such drivers which they wanted. You can equally well criticise the Zorro busboard producer for lack of support for better graphic chipsets than S3 Virge (installed in CyberVision 64 3D).

I agree, but programming information for Zorro busboards is publicly available.

So you have now those potential guilty of your failure in writing these drivers? Are your skills not taken into account here, Trev?

Huh? Maybe you should repeat that in your native language. Your first question is nonsensical.

If the Picasso96 folks say, "No, you can't write open source card and chip drivers for Picasso96," what am I supposed to do? In the US, fair use would allow me to reverse engineer their interfaces, but I'd much rather make some new friends and help support a useful piece of software.

Positive feelings about OpenPCI and Picasso96? Why? Because, unlike Elbox, they have done nothing new so far for users of Amiga PCI busboards?

You're drifting. We're talking about display adpater drivers, remember? And once again, you've misinterpreted my comments. I'm feeling positive about using OpenPCI because their dev kit is now publicly available, and I'm feeling positive about Picasso96 because the authors seem like nice guys interested in helping out the community.

Trev