Re: Linux stifles innovation...
> > For example, if there were six different companies that marketed ethernet > drivers for the eepro100, you'd have a choice of which one to buy..perhaps > with different "features" that were of value to you. Instead, you have > crappy GPL code that locks up under load, and its not worth spending > corporate dollars to fix it because you have to give away your work for > free under GPL. And since there is a "free" driver that most people can > use, its not worth building a better mousetrap either because the market is > too small. So, the handful of users with problems get to "fit it > themselves", most of whom cant of course. > Assuming I am a corporate entity and I need to spend a few bucks to fix a GPL driver, just because I fix it and deploy my fix on my corporation's internal network machines -- and quite possibly benefit the hell out of myself and my company -- that does not mean that I have to release my work for free under the GPL. Of course, the *nice* thing to do would be to release it under the GPL even if I was only using the fix internally -- but I am under no obligation to do that, if, say, I just wanted to keep ahead of my competitors. Maybe I was planning to wait awhile so I could get ahead in my market. Maybe I'm just an IP freak and I want to keep my code to myself. Whatever. My understanding is that the only restrictions I have is that I can't sell or distribute the darned thing. If, say for example I needed to fix that driver so that it would work on my new WhizBang 2001 Corporate Server that is about to hit the market, then I would be making money on the hardware, and as an added bonus my company looks good because it has an "open" driver for its server. (no matter that it "had" to under the GPL) Mike Pontillo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux stifles innovation...
For example, if there were six different companies that marketed ethernet drivers for the eepro100, you'd have a choice of which one to buy..perhaps with different "features" that were of value to you. Instead, you have crappy GPL code that locks up under load, and its not worth spending corporate dollars to fix it because you have to give away your work for free under GPL. And since there is a "free" driver that most people can use, its not worth building a better mousetrap either because the market is too small. So, the handful of users with problems get to "fit it themselves", most of whom cant of course. Assuming I am a corporate entity and I need to spend a few bucks to fix a GPL driver, just because I fix it and deploy my fix on my corporation's internal network machines -- and quite possibly benefit the hell out of myself and my company -- that does not mean that I have to release my work for free under the GPL. Of course, the *nice* thing to do would be to release it under the GPL even if I was only using the fix internally -- but I am under no obligation to do that, if, say, I just wanted to keep ahead of my competitors. Maybe I was planning to wait awhile so I could get ahead in my market. Maybe I'm just an IP freak and I want to keep my code to myself. Whatever. My understanding is that the only restrictions I have is that I can't sell or distribute the darned thing. If, say for example I needed to fix that driver so that it would work on my new WhizBang 2001 Corporate Server that is about to hit the market, then I would be making money on the hardware, and as an added bonus my company looks good because it has an "open" driver for its server. (no matter that it "had" to under the GPL) Mike Pontillo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Support for 802.11 cards?
Hmm, this is interesting... I know that the kernel can be set to try to detect PCI devices on its own, without the help of the BIOS. Is there any reason why that feature wouldn't work with this particular type of card? Thanks, Mike Pontillo On 29 Jan 2001, Bryan O'Sullivan wrote: > m> The ISA bridge also works on the 2.4 kernels but I have not > m> retested the PCI bridge on 2.4. > > The Lucent PCI-to-Cardbus bridge only works on machines that have a > recent PCI BIOS. Any motherboard more than about 16 months old simply > won't find the bridge card, and hence neither will Linux. > >- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Support for 802.11 cards?
Hello, I was wondering what 802.11 PCI cards anyone knows of that run under Linux-2.4. (or 2.2 for that matter) I have looked at Documentation/Configure.help and done a quick grep of all the documentation for "802.11" without much luck. I can't seem to find anything related to the aironet cards that are mentioned in ./Configure.help -- it would be a matter of guesswork for me to figure out which, if any, Cisco card is the same one that the kernel supports. Does anyone know if anyone has released (working) drivers for their 802.11 cards that have not been incorporated into the kernel? I know D-Link has some 802.11 cards out right now, but I haven't seen any mention of support for Linux. I know other D-Link devices are supported; does anyone know if someone is working on a driver for their card? If not, have they been receptive to requests for documentation? Thanks! Mike Pontillo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Support for 802.11 cards?
Hello, I was wondering what 802.11 PCI cards anyone knows of that run under Linux-2.4. (or 2.2 for that matter) I have looked at Documentation/Configure.help and done a quick grep of all the documentation for "802.11" without much luck. I can't seem to find anything related to the aironet cards that are mentioned in ./Configure.help -- it would be a matter of guesswork for me to figure out which, if any, Cisco card is the same one that the kernel supports. Does anyone know if anyone has released (working) drivers for their 802.11 cards that have not been incorporated into the kernel? I know D-Link has some 802.11 cards out right now, but I haven't seen any mention of support for Linux. I know other D-Link devices are supported; does anyone know if someone is working on a driver for their card? If not, have they been receptive to requests for documentation? Thanks! Mike Pontillo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
