Moving from Binary Drivers to Open Source?
GerryGilmore asks: "We are a division, specializing in telecommunications equipment, of a very large hardware manufacturer. Our equipment, DSP and PSTN boards, has been supported under Linux through a set of binary driver modules and binary libraries implementing our API set. We are in the process of migrating to a completely open source-based software infrastructure to be more in sync with the rest of the Linux industry. However, not having any real experience with moving from proprietary to an open source model, we wanted to see if the Slashdot crowd has any similar experiences to share: The Good; The Bad; The Ugly; and how best to avoid the most common pitfalls."
Sorry... I have no experience in this!
eWeek is reporting that IE 7's weakest link will be its CSS 2 support.
yay
bitch
go gnaa
male nurses? You mean murses?
I've just heard that IE7's biggest weakness will be it's lack of CSS2 support.6 943,00.as p
That is what should be on the front page of Slashdot, not this stuff about drivers that I don't understand.
Eweek has an article about it here...
http://www.eweek.com/article2/0,1759,177
...dont fix it.
:)
I am just asking myself why would you want to do that? I think you must ask yourself theses first questions.
1- Are your current drivers free? : If yes, why bother to change?
2- Are your current drivers working? : Look at the title.
And I would strongly you to have a test environnement
No sig for now.
As you post said you are in the telecommunciations *business*, not the Linux "industry". How does making your drivers open sores add value for your business shareholders who ultimately sign you paycheck?