I have tried to support a TrippLite Internet350SER UPS using a serial cable (The only connection on this model) using the 2.4 code branch. It uses the Protocol 1004 from the tripplite specification that can be use either used on serial or USB device. Since my device was only serial, I worked only on the serial integration. Since I found nothing in tripplite.c, tripplite-hid.c, tripplitesu.c to support my model, I have done trippliteser.c in order to support my unit. Not all the functionality are there but the core functionality is there. Since it is licence as GPLv2, I just want to push back my modifs to the community but really don't know the procedure. thank for the help Patrick Levesque This electronic message may contain proprietary and confidential information of Verint Systems Inc., its affiliates and/or subsidiaries. The information is intended to be for the use of the individual(s) or entity(ies) named above. If you are not the intended recipient (or authorized to receive this e-mail for the intended recipient), you may not use, copy, disclose or distribute to anyone this message or any information contained in this message. If you have received this electronic message in error, please notify us by replying to this e-mail. -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 19001 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20091104/ff2959c3/attachment-0001.bin>
Hello Patrick, On Wednesday, 4. November 2009 14:12:09 Levesque, Patrick wrote:> I have tried to support a TrippLite Internet350SER UPS using a serial > cable (The only connection on this model) using the 2.4 code branch. It > uses the Protocol 1004 from the tripplite specification that can be use > either used on serial or USB device. Since my device was only serial, I > worked only on the serial integration. Since I found nothing in > tripplite.c, tripplite-hid.c, tripplitesu.c to support my model, I have > done trippliteser.c in order to support my unit. Not all the > functionality are there but the core functionality is there. Since it > is licence as GPLv2, I just want to push back my modifs to the community > but really don't know the procedure.Do you know how diff/patch works? Just send your changes as unified diff (diff -u) to the devel list. Might be a good idea to prefix your mail subject with "[PATCH]". If possible, try to prevent winmail.dat attachments on the mailing list, so people with a normal email client can open the attachment. Cheers, Thomas