For
DeveloppementGPL , here are some requirements we have, in the spirit of GPL. Matter of factly, that has a (great) impact on free distribution of the driver.
Those are mostly "wish to have" and should be taken as simply this. We do not make anything compulsory, but try to identify the importance and identify the impacts (if not accepted, particularly).
Both organizational and functional requirements are identified for the eagle-usb driver.
C closed
O open
Short term requirements
#ST001 : C : free distribution of driver
- status : 20041008 proposed 20041010 done
- Importance : high
ADI currently must accept that we distribute freely and publicly their current driver adi.zip. The licence states the contrary in some doc files or is not precised. I could remove doc and files without licence.
- Answer : yes "all the files in adi.zip file can be distributed. "
- Impact if no : no public distribution of their current driver. We may accept restrictions (add a warning not to redistribute in the current state and replace with newer version for public distribution and redistribution)
#ST002 : C : ADI accepts to work with us
- status : 20041008 proposed 20041010 done
- Importance : high
We need e-mails of our co-workers and a description of their role / what they expect from us or can give us. The exchanges will be done on a public mailing-list. Currently eagleusb-dev at gna dot org
This wiki pages list what we have currently identified. Any question is welcome.
- answer : yes + e-mails and description (currently privately but public ML can be used by ADI / Sagem)
- impact if no : to be identified depending on the condition of work proposed
#ST003 : C : Sagem accepts to work with us
- status : 20041008 accepted
- Importance : high
Sagem accepts to work with us. Sagem subscribes to the ML and provides what they can.
#ST004 : C : appropriate values for OPTNxx
- status : 20041008 proposed 20041025 done
- Importance : high
Current values do not work mostly with Fast 800 E2L, see
http://forum.eagle-usb.org. We use bnm files from windows sagem driver 2.0.31.
We could use new BNM files (necessary for Fast 800 E3) if we are confirmed that they are compatible with
this list of modems (interwiki) (a longer list would be a plus)
- answer : list of values for POTS / ISDN + (backward) compatibility of new BNM files
Longer term requirements
Those are requirements that are not completely necessary in the short term or need to be better defined before they can be accepted.
#LT001 : O : approve the naming of the eagle-usb driver
- status : 20041008 proposed
- importance : high
We have renamed the adiusbadsl driver to eagle-usb. Is this a problem ? Are we authorized by ADI to use it ?
#LT002 : O : provide documentation about CMV
- status : 20041008 proposed
- importance : medium
Provide list of CMV that work
Their signification would be a plus
#LT003 : O : provide specification about CMV
- status : 20041008 proposed
- importance : medium
Provide specification of how to use CMV. That's a document that is currently proprietary, we can obtain it only from ADI, if they accept.
- answer : yes / no + documentation
#LT004 : O : provide specification of interfaces
- status : 20041008 proposed
- importance : medium
Provide specification of functions that can be accessed externally, with the parameters needed.
- answer : yes / no + documentation
#LT005 : O : provide specification of internal functions
- status : 20041008 proposed
- importance : medium
Provide specification of functions that are internal to the modem.
- answer : yes / no + documentation
#LT006 : O : provide source code for firmware
- status : 20041008 proposed
- importance : medium
Provide source code for firmware. It is written in 8051 language. This is a requirement of GPL.
- answer : yes / no + source code
#LT007 : O : provide source code for BNM
- status : 20041008 proposed
- importance : medium
Provide source code for BNM which is DSP code. It is written in 8051 language. This is a requirement of GPL.
- answer : yes / no + source code
#LT008 : O : full GPL ?
- status : 20041008 proposed / to be completed
- importance : medium
All files must have a header stating a copyright and a licence (preferably the GPL).
to be defined more precisely as there are still changing opinions today (see
Debian Social Contract & Linus opinion on firmware to be included in the kernel)
- answer : yes / no + list of accepted modifications
#LT009 : O : add a GPL header to bnm files
- status : 20041008 proposed
- importance : medium
Technically, a header / description could be added to BNM files : format
s-record motorola see
http://home.socal.rr.com/awi/srecords.htm
The proposed patch is to put :
to be defined in the S0 record (text is available ? the example does not show this)
A text file included in the same directory as bnm files could identify the copyright and licence chosen for all files included in this directory.
