> Yes that is a real argument which I agree totally. > Here is my point of view. If I have a piece of > hardware that does not > work, I will try to find one driver on Internet. > If it works, I am happy, without bothering about how > it is implemented. > On the other hand, if I just > can not find a driver, that annoy me very much. > Solaris already have good driver framework, and a lot > of documents. But > still is lack of drivers. How could > we cultivate an active community for writing drives > without enabling > them to use it ? In the long run, it would > be idea if hardware vendors will provide drivers, or > the community will > do it. But how could we achieve that > without enabling users to use the hardware ? I think > we are here > arguing about solution for that.
Sooner or later, if you want drivers, you or someone else will have to roll up their sleeves and dig into the DDI/DDK documentation on docs.sun.com. There is no way around that, no matter which elaborate schemes (user-mode, la la la) one comes up with. How did Linux get so many drivers? Vendors sure weren't eager to release the specs! So that means *somebody* had to roll up their sleeves, reverse-engineer how the device worked, then figure out how to write a driver that will interface with the Linux kernel and with the device. Why are we actively trying *not to* do the exact same thing on Solaris????? If anything, writing drivers for Solaris should be far easier than for Linux! This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list [email protected]
