search for: blzr

Daniele, Thanks again for your work on both the voltronic and blzr drivers. To get the most exposure to new drivers, what we have typically done in the past is to rename the existing driver as *-old, so that users get the new driver by default when they upgrade (but the old driver is still available if there are regressions). This is how we are incorporating Micha...

On Nov 1, 2013, at 9:03 AM, Charles Lepple wrote: > But if blzr supersedes both voltronic and blazer, I propose we rename blazer_{ser,usb} to blazer_{ser,usb}_old, then rename blzr* to blazer*, and revert the voltronic merge. Dan, The pull request against master looks good - thanks! What do you think about the renaming of blazer to blazer_old, and making blz...

In my opinion, there might be just one problem: the blzr driver doesn't provide anymore two splitted drivers (serial and usb), so this isn't going to be a 'silent update' for those using these drivers (should we provide symlinks or the like?). If this doesn't sound like a problem to you, I'll take care of the rename. Plus, if you...

Daniele, I was going to try and put a comment on GitHub, but apparently there isn't a pull request open for your new 'blzr' branch. This line is tripping up the Debian build: https://github.com/zykh/nut/blob/69d79a65789cf479ceb2d6173de4c5b5315ccc50/drivers/blzr_voltronic.c#L2827 http://buildbot.networkupstools.org/public/nut/builders/Debian-x64-gcc/builds/57 ../../drivers/blzr_voltronic.c: In function ?voltroni...

Hi, They say one should never argue with people that know more than you, so please bear with me. On 2013/10/24 09:47 PM, hyouko at gmail.com wrote: > The driver is expecting either 'ACK' or no reply at all in case of > success and the command itself echoed back in case of errors. > On the other hand, your UPS replies '(ACK' in case of success and > '(NAK' on