Mailinglist Archive: opensuse-factory (542 mails)
| < Previous | Next > |
Re[2]: 2.6.16 serious consequences / GPL_EXPORT_SY MBOL / USB drivers of major vendor excluded
- From: Christoph Weidmann <c_weidmann@xxxxxx>
- Date: Sun, 19 Feb 2006 16:53:55 +0100
- Message-id: <154368267@xxxxxx>
Hi,
I want to reply to a message which was sent to list when I wasn't subscriped to it. So I send my reply now as a new message, I hope it will not break the thread structure to much. Sorry!
I'm very pleased for explanation of details in the mail from s.schmidt@xxxxxx about the closed-source driver problem. I can understand that a leading company like AVM can't open source its intellectual property and know-how. I understand that its easier und more flexible to do some functionality in software than in hardware. But what about putting this algorythms in the upgradeable firmware of the devices? Ok, I can understand that current devices are not prepared for doing this, but could this be a solution for future products? Things like fax or modem emulation could be done in the binary firmware of the device an the drivers could be kept simple an open source. You have to open no know-how to public or competitors because it will stay closed in the device's firmware.
I'm currently not affected by the disscussion because although am using ISDN as primary net-access, I'm using a Bluefritz USB in combination with Bluefritz AP-X that seemes to work with open-source drivers. All ISDN-related things seemed to be done by firmware and I think this could be a solution for other devices.
I've to clearify that I'm not a programmer, hardware designer or ISDN-expert (so I may be completely wrong), I'm just a very pleased user of AVM's devices who's hoping that a solution will be found. I can understand both sides: Having closed source in kernel will cause some problems but opening the software is inacceptable for AVM...
regards
Christoph Weidmann
______________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
I want to reply to a message which was sent to list when I wasn't subscriped to it. So I send my reply now as a new message, I hope it will not break the thread structure to much. Sorry!
I'm very pleased for explanation of details in the mail from s.schmidt@xxxxxx about the closed-source driver problem. I can understand that a leading company like AVM can't open source its intellectual property and know-how. I understand that its easier und more flexible to do some functionality in software than in hardware. But what about putting this algorythms in the upgradeable firmware of the devices? Ok, I can understand that current devices are not prepared for doing this, but could this be a solution for future products? Things like fax or modem emulation could be done in the binary firmware of the device an the drivers could be kept simple an open source. You have to open no know-how to public or competitors because it will stay closed in the device's firmware.
I'm currently not affected by the disscussion because although am using ISDN as primary net-access, I'm using a Bluefritz USB in combination with Bluefritz AP-X that seemes to work with open-source drivers. All ISDN-related things seemed to be done by firmware and I think this could be a solution for other devices.
I've to clearify that I'm not a programmer, hardware designer or ISDN-expert (so I may be completely wrong), I'm just a very pleased user of AVM's devices who's hoping that a solution will be found. I can understand both sides: Having closed source in kernel will cause some problems but opening the software is inacceptable for AVM...
regards
Christoph Weidmann
______________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
| < Previous | Next > |