[Nut-upsdev] [PATCH] New to nut project

[Charles Lepple]

All,

I should have some time in the next few days to look at the patch, but
Arnaud mentioned an ID code- has anyone looked into that? If so, we
might be able to combine all the tripplite code except the SU
protocol.

On Monday, November 9, 2009, Arnaud Quette <aquette.dev at gmail.com> wrote:
> Hi Thomas,
>
> thanks for interfacing with Patrick on this point.
> btw, would you be interested in integrating the team?
>
> I'll leave up to Charles to check the patch.
> I don't know much about Tripplite protocols, but this one seems to be
> a variation of the existing ones (1001 and 3003, so maybe a 4004?!),
> which means that it could possibly be merged in the existing tripplite
> drivers.
> All in all, Charles will hopefully have comments...
>
> @Patrick: do you have a USB port too, or only a serial one?
>
> cheers,
> Arnaud
> --
> Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops
> Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
> Debian Developer - http://www.debian.org
> Free Software Developer - http://arnaud.quette.free.fr/
>
>
> 2009/11/9 Thomas Jarosch:
>> ----------  Forwarded Message  ----------
>>
>> Subject: [PATCH] New to nut project
>> Date: Friday, 6. November 2009
>> From: Patrick Levesque
>> To: Thomas Jarosch
>>
>> As requested, here is my patch file including all my modification to the
>> 2.4.1
>> tarball from the web site.
>>
>> On Friday 06 November 2009 05:41:29 you wrote:
>>> 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
>
> _______________________________________________
> Nut-upsdev mailing list
> Nut-upsdev at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev

-- 
- Charles Lepple