<div dir="auto">In the ups.conf section for the device driver, "user or NAS" can specify the "vendorid" and "productid" options (required if "subdriver" is specified and not guessed).<div dir="auto"><br></div><div dir="auto">This allows users to pick an existing driver that best supports their device.</div><div dir="auto"><br></div><div dir="auto">In other news, a recent iteration of the Ablerex subdriver in PR #1035 is heading toward getting merged; a final test on hardware (after fixing issues highlighted by CI) would be beneficial however.</div><div dir="auto"><br></div><div dir="auto">Jim</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jul 27, 2021, 06:24 Johnson-shen <<a href="mailto:johnson-shen@ablerex.com.tw">johnson-shen@ablerex.com.tw</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear Sir,<br>
<br>
Long time no see.<br>
I have a question to consult you about NUT drivers.<br>
If the driver(e.g. Ablerex_nutdrv_qx) needs to be applied to different <br>
PID/VID, how to deal with this situation?<br>
Besides, user or NAS selects the appropriate driver by setting ups.conf. <br>
Is there any other way?<br>
<br>
Regards!~<br>
Johnson<br>
<br>
<br>
<br>
Jim Klimov 於 5/12/2021 8:12 PM 寫道:<br>
> On May 12, 2021 10:45:43 AM UTC, Johnson-shen <<a href="mailto:johnson-shen@ablerex.com.tw" target="_blank" rel="noreferrer">johnson-shen@ablerex.com.tw</a>> wrote:<br>
>> Dear sir,<br>
>><br>
>> I hope you have been well!<br>
>> May I consult with you about nutdrv_qx’s driver?<br>
>> If we upload the new driver to NUT. (ex. Ablerex_nutdrv_qx)<br>
>> That means we have both(blazer_USB and Ablerex_nutdrv_qx) drivers for<br>
>> our UPS and the same PID/VID.<br>
>> Is it correct my understanding?<br>
>> If it is correct, when NAS manufacturers use NUT package to import to<br>
>> their kernel. They don't know which driver to use during UPS plug-in to<br>
>><br>
>> NAS. Because these two drivers have the same PID/VID (NAS vendor told<br>
>> us<br>
>> that they choose the driver by PID/VID).<br>
>> Could you kindly provide more information or experience to us with<br>
>> that?<br>
>><br>
>><br>
>><br>
>> Regards!<br>
>> Johnson<br>
>><br>
>><br>
>><br>
>><br>
>> Johnson-shen 於 4/23/2021 11:55 AM 寫道:<br>
>>> Dear Sirs.<br>
>>><br>
>>> I apologize for my phrase and appreciate your support and assistance<br>
>>> for this. We will research for drivers(nutdrv_qx).<br>
>>><br>
>>> Please Kindly support us again, if we have any questions about<br>
>>> (nutdrv_qx).<br>
>>><br>
>>><br>
>>> Regards!<br>
>>> Johnson<br>
>>><br>
>>><br>
>>> Jim Klimov 於 4/20/2021 6:02 PM 寫道:<br>
>>>> Sorry for another delay,<br>
>>>><br>
>>>> I was looking at recent submissions for the new-architecture<br>
>>>> nutdrv_qx family of drivers to provide examples, and some of those<br>
>>>> submissions needed a bit of cleanup before posing as examples.<br>
>>>> Unfortunately our QX expert did not respond yet, so it took a longer<br>
>>>> while on my side.<br>
>>>><br>
>>>> So now I can suggest looking at two PRs:<br>
>>>> * <a href="https://github.com/networkupstools/nut/pull/638/" rel="noreferrer noreferrer" target="_blank">https://github.com/networkupstools/nut/pull/638/</a><br>
>>>> <<a href="https://github.com/networkupstools/nut/pull/638/" rel="noreferrer noreferrer" target="_blank">https://github.com/networkupstools/nut/pull/638/</a>> adding support<br>
>> for<br>
>>>> "hunnox" - both a USB protocol subdriver (in nutdrv_qx.c) and<br>
>>>> device/HID mapping "hunnox_subdriver" (with sources in<br>
>>>> nutdrv_qx_hunnox.c/.h files), and<br>
>>>> * <a href="https://github.com/networkupstools/nut/pull/1008" rel="noreferrer noreferrer" target="_blank">https://github.com/networkupstools/nut/pull/1008</a><br>
>>>> <<a href="https://github.com/networkupstools/nut/pull/1008" rel="noreferrer noreferrer" target="_blank">https://github.com/networkupstools/nut/pull/1008</a>> adding just an<br>
>>>> "snr" protocol subdriver at this point.<br>
>>>><br>
>>>> They also add documentation updates for the changes they made, but<br>
>>>> this aspect was slightly addressed in your PR already (mention of<br>
>> the<br>
>>>> new subdriver would need to move from docs/man/blazer-common.txt to<br>
>>>> nutdrv_qx.txt though).<br>
>>>><br>
>>>> To remind, my primary concerns about your original submission and<br>
>>>> from later discussion are:<br>
>>>><br>
>>>> * The changes in your PR #979 are targeted for blazer_usb driver<br>
>>>> which would at some point be deprecated and obsoleted in favor of<br>
>>>> nutdrv_qx, so this added support would be lost. While someone in the<br>
>>>> community probably can pick up and port source code lines, it would<br>
>>>> be hard to guarantee without access to hardware that the resulting<br>
>>>> driver actually works. So in fact you are best positioned (and<br>
>>>> incentivised) to initially provide the modern driver that will<br>
>>>> survive in the NUT codebase for long.<br>
>>>><br>
>>>> * Another point is the bold statement that "PID=0000/VID=FFFF of<br>
>>>> blazer_USB is Ablerex’s Identification code." It is not exactly a<br>
>>>> random unique number, and I suppose if the USB-IF authority had a<br>
>>>> *publicly* available registry of the ID numbers they give out - same<br>
>>>> as DNS registry, or IANA TCP/UDP port registry, or MAC address<br>
>> prefix<br>
>>>> registry for networking, or many other such lists in IT - these<br>
>>>> particular numbers would not be there, probably not for anyone.<br>
>> Since<br>
>>>> the USB-IF registry is not public, I can only assume that the other<br>
>>>> mentioned Vendor ID "1cb0" is registered properly and no other<br>
>>>> devices would conflict using it. I understand the technical point<br>
>>>> that these "0000:FFFF" are the uncustomized IDs flashed into the USB<br>
>>>> chips your devices use, but it also means that any other vendor<br>
>> might<br>
>>>> have those spectacularly not-unique ID numbers, with same or even<br>
>>>> unrelated chips. We already do have a practical example of such mess<br>
>>>> with "ATCL" chips that provide USB media connections for otherwise<br>
>>>> unrelated UPSes that talk completely different protocols and have<br>
>>>> different NUT drivers for same Vendor ID + Product ID + Device<br>
>> String<br>
>>>> tuple.<br>
>>>><br>
>>>> * Also, "the modification is only for the addition of Ablerex<br>
>> product<br>
>>>> features, so there is no need to consider the differences of other<br>
>>>> customers" - the wording here may be unfortunate, English is not a<br>
>>>> native language for either of us, but as written this phrase looks<br>
>>>> very concerning :) You are changing an existing driver that supports<br>
>>>> several device families already, and existing users of this driver<br>
>>>> expect that the support is not broken when they upgrade NUT. So *OF<br>
>>>> COURSE* there is a need to consider differences for other customers.<br>
>>>> That said, your original (blazer_usb) submission was quite cleanly<br>
>>>> separated and should not have impacted users... unless they have<br>
>> some<br>
>>>> "0000:FFFF" device that worked before with some subdriver and would<br>
>>>> be detected as "ablerex_ext_command=1" and might stop working now;<br>
>>>> you did not offer any failsafe (addvar() a flag, probably) to<br>
>>>> override your detection and disable ablerex mode in the unlikely<br>
>> case<br>
>>>> it is misdiagnosed and breaks somebody in practice.<br>
>>>><br>
>>>> * Notably, the mapping macro in nutdrv_qx is more elaborate and<br>
>>>> allows to map not just ID numbers but also a string the device<br>
>>>> presents itself with, so detection of proper subdriver can probably<br>
>>>> be made more reliable at that point, and not with a hack to check<br>
>>>> particular IDs in `blazer_initinfo()` as you proposed in current PR.<br>
>>>><br>
>>>> Hope this helps,<br>
>>>> Jim Klimov<br>
>>>><br>
>>>><br>
>>>> On Mon, Apr 12, 2021 at 11:17 AM Johnson-shen<br>
>>>> <<a href="mailto:johnson-shen@ablerex.com.tw" target="_blank" rel="noreferrer">johnson-shen@ablerex.com.tw</a> <mailto:<a href="mailto:johnson-shen@ablerex.com.tw" target="_blank" rel="noreferrer">johnson-shen@ablerex.com.tw</a>>><br>
>> wrote:<br>
>>>> Dear Sir,<br>
>>>><br>
>>>> How’s today?<br>
>>>><br>
>>>> Could you kindly provide your comment about our opinions?<br>
>>>><br>
>>>> Please kindly provide more information, documents or example<br>
>> code<br>
>>>> about the driver that will separate Ablerex's, if you did not<br>
>>>> agree with our opinions.<br>
>>>><br>
>>>><br>
>>>><br>
>>>> Regards!<br>
>>>> Johnson<br>
>>>><br>
>>>><br>
>>>><br>
>>>> Johnson-shen 於 4/6/2021 6:22 PM 寫道:<br>
>>>>> Dear Sir,<br>
>>>>><br>
>>>>> Could you merge our driver for us?<br>
>>>>> Because PID=0000/VID=FFFF of blazer_USB is Ablerex’s<br>
>>>>> Identification code. And this time the modification is only for<br>
>>>>> the addition of Ablerex product features, so there is no need<br>
>> to<br>
>>>>> consider the differences of other customers. Could you agree?<br>
>>>>><br>
>>>>> Regards!<br>
>>>>> Johnson<br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>> Jim Klimov 於 4/4/2021 7:43 PM 寫道:<br>
>>>>>> Hello,<br>
>>>>>><br>
>>>>>> I am really sorry about the delay, I hoped our community<br>
>>>>>> expert on the Qx drivers would recommend the best course of<br>
>>>>>> action, but he did not reply yet.<br>
>>>>>><br>
>>>>>> To me it currently seems that this Pull request:<br>
>>>>>> <a href="https://github.com/networkupstools/nut/pull/638/files" rel="noreferrer noreferrer" target="_blank">https://github.com/networkupstools/nut/pull/638/files</a><br>
>>>>>> <<a href="https://github.com/networkupstools/nut/pull/638/files" rel="noreferrer noreferrer" target="_blank">https://github.com/networkupstools/nut/pull/638/files</a>><br>
>>>>>> represents the modernly desirable addition of a USB protocol<br>
>>>>>> subdriver (in nutdrv_qx.c/.h) and the vendor protocol nuances<br>
>>>>>> subdriver (in separate files).<br>
>>>>>><br>
>>>>>> Sadly, according to comment trail, that particular Pull<br>
>>>>>> request changed a bit of logic in existing functions (around<br>
>>>>>> langid_fix and enabling a hunnox patch, most prominently) and<br>
>>>>>> there were concerns if it is not breaking anything for other<br>
>>>>>> devices that work currently. It would be beneficial if people<br>
>>>>>> running nutdrv_qx today could build that branch and confirm<br>
>>>>>> into PR comments that the updated driver does work well or<br>
>> does<br>
>>>>>> break something after all.<br>
>>>>>><br>
>>>>>> So I think the new ablerex subdriver should carefully take a<br>
>>>>>> similar path. Nutdrv_qx modular code did grow as a refactoring<br>
>>>>>> and merge of earlier drivers including blazer, so your<br>
>> original<br>
>>>>>> code contribution should be easily portable into the new<br>
>> layout.<br>
>>>>>> Thank you very much and really sorry it took longer that I'd<br>
>>>>>> expect,<br>
>>>>>> Jim Klimov<br>
>>>>>><br>
>>>>>><br>
>>>>>> On Mon, Mar 29, 2021, 13:16 Johnson-shen<br>
>>>>>> <<a href="mailto:johnson-shen@ablerex.com.tw" target="_blank" rel="noreferrer">johnson-shen@ablerex.com.tw</a><br>
>>>>>> <mailto:<a href="mailto:johnson-shen@ablerex.com.tw" target="_blank" rel="noreferrer">johnson-shen@ablerex.com.tw</a>>> wrote:<br>
>>>>>><br>
>>>>>> Dear Sir,<br>
>>>>>><br>
>>>>>> Thank you for your reply.<br>
>>>>>><br>
>>>>>> I can not sure what you mean.<br>
>>>>>><br>
>>>>>> May I confirm with you again about it?<br>
>>>>>><br>
>>>>>> You did not recommend that extend the new function from<br>
>>>>>> blazer_usb.c for Ablerex UPS.<br>
>>>>>><br>
>>>>>> You suggest that separate the Ablerex function into a new<br>
>>>>>> driver(.c or .h) independently to avoid vendor nuances.<br>
>>>>>><br>
>>>>>> Until we follow the above rule to modify, It will be<br>
>> upload<br>
>>>>>> and merge the driver.<br>
>>>>>><br>
>>>>>> Is it right?<br>
>>>>>><br>
>>>>>> Please kindly provide more information or explain to us,<br>
>> if<br>
>>>>>> I got you wrong.<br>
>>>>>><br>
>>>>>> Please kindly provide the example for a new structure to<br>
>>>>>> us, I think will help to modify it for reference, if it is<br>
>>>>>> right.<br>
>>>>>><br>
>>>>>> Regards!<br>
>>>>>> Johnson<br>
>>>>>><br>
>>>>>><br>
>>>>>><br>
>>>>>><br>
>>>>>> Jim Klimov 於 3/24/2021 6:26 PM 寫道:<br>
>>>>>>> Hello,<br>
>>>>>>><br>
>>>>>>> Yes, in fact there were two things.<br>
>>>>>>><br>
>>>>>>> One was that a week ago I posted some documentation<br>
>>>>>>> updates into your PR (e.g. for acknowledgements) and<br>
>> asked<br>
>>>>>>> you to confirm they sit well with you, and hoped that's<br>
>> it.<br>
>>>>>>> Unfortunately, I was now reminded that extending the<br>
>>>>>>> blazer_usb driver was not a good approach - it was<br>
>>>>>>> (poorly, fixing that) documented as heading to obsoletion<br>
>>>>>>> and eventual removal from codebase. Various drivers for<br>
>> Qx<br>
>>>>>>> protocols were aggregated in drivers/nutdrv_qx*.{c,h} as<br>
>> a<br>
>>>>>>> common core and clean separate sources for vendor<br>
>> nuances.<br>
>>>>>>> In order for us to maintain support for your device in<br>
>> the<br>
>>>>>>> long run, and not lose it when old redundant drivers do<br>
>>>>>>> get dropped, your code contribution should be relocated<br>
>> to<br>
>>>>>>> this newer structure, and importantly - re-tested with<br>
>>>>>>> your hardware we do not have access to. I hope Daniele<br>
>>>>>>> (CC'ed) can clarify this better if you would need<br>
>> assistance.<br>
>>>>>>> Sorry about not noticing this earlier,<br>
>>>>>>> Jim Klimov<br>
>>>>>>><br>
>>>>>>> On Wed, Mar 24, 2021, 03:58 Johnson-shen<br>
>>>>>>> <<a href="mailto:johnson-shen@ablerex.com.tw" target="_blank" rel="noreferrer">johnson-shen@ablerex.com.tw</a><br>
>>>>>>> <mailto:<a href="mailto:johnson-shen@ablerex.com.tw" target="_blank" rel="noreferrer">johnson-shen@ablerex.com.tw</a>>> wrote:<br>
>>>>>>><br>
>>>>>>> Dear Sir,<br>
>>>>>>><br>
>>>>>>> The status of the project is waiting for the other<br>
>>>>>>> managers to verify and confirm?<br>
>>>>>>><br>
>>>>>>> Please advise me if you have any support for this<br>
>> project.<br>
>>>>>>><br>
>>>>>>> Regards!<br>
>>>>>>><br>
>>>>>>> Johnson<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>><br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> Jim Klimov 於 3/18/2021 8:07 PM 寫道:<br>
>>>>>>>> Hello, thanks for the driver update and sorry that I<br>
>>>>>>>> had to be reminded of the PR by mailing list. I<br>
>>>>>>>> reviewed it last week and added a few points on<br>
>>>>>>>> documentation. Can you please check those, that I<br>
>> did<br>
>>>>>>>> not mistake something, and I think it is good to<br>
>>>>>>>> merge. Thanks again!<br>
>>>>>>>><br>
>>>>>>>> Jim Klimov<br>
>>>>>>>><br>
>>>>>>>> On Thu, Mar 18, 2021, 11:33 Johnson-shen<br>
>>>>>>>> <<a href="mailto:johnson-shen@ablerex.com.tw" target="_blank" rel="noreferrer">johnson-shen@ablerex.com.tw</a><br>
>>>>>>>> <mailto:<a href="mailto:johnson-shen@ablerex.com.tw" target="_blank" rel="noreferrer">johnson-shen@ablerex.com.tw</a>>> wrote:<br>
>>>>>>>><br>
>>>>>>>> Dear Wolfy,<br>
>>>>>>>><br>
>>>>>>>> Please advise me, if you need more information<br>
>>>>>>>> about the new driver.<br>
>>>>>>>> Also please kindly update the status of the new<br>
>>>>>>>> driver for us.<br>
>>>>>>>><br>
>>>>>>>> Regards!<br>
>>>>>>>> Johnson<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> Johnson-shen 於 3/10/2021 6:24 PM 寫道:<br>
>>>>>>>>> Dear Wolfy,<br>
>>>>>>>>><br>
>>>>>>>>> Please refer to the below table for the whole<br>
>>>>>>>>> support list of the UPS Model of the new<br>
>> driver.<br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>> Please kindly advise me if you have any<br>
>> questions.<br>
>>>>>>>>> Regards!<br>
>>>>>>>>> Johnson<br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>> Johnson-shen 於 3/10/2021 9:43 AM 寫道:<br>
>>>>>>>>>> Dear Wolfy,<br>
>>>>>>>>>><br>
>>>>>>>>>> Thank you for the reply to emails quickly, the<br>
>>>>>>>>>> DK+ is our customer model name for ODM.<br>
>>>>>>>>>><br>
>>>>>>>>>> We will provide the whole support list of UPS<br>
>>>>>>>>>> Model of the driver to you tomorrow.<br>
>>>>>>>>>><br>
>>>>>>>>>><br>
>>>>>>>>>><br>
>>>>>>>>>> Regards!<br>
>>>>>>>>>><br>
>>>>>>>>>> Johnson<br>
>>>>>>>>>><br>
>>>>>>>>>><br>
>>>>>>>>>><br>
>>>>>>>>>><br>
>>>>>>>>>><br>
>>>>>>>>>><br>
>>>>>>>>>><br>
>>>>>>>>>><br>
>>>>>>>>>> Manuel Wolfshant 於 3/9/2021 7:11 PM 寫道:<br>
>>>>>>>>>>> On 3/9/21 8:37 AM, John wrote:<br>
>>>>>>>>>>>> Hi,<br>
>>>>>>>>>>>><br>
>>>>>>>>>>>> I'm engineer from Ablere Electronics Co.,<br>
>>>>>>>>>>>> Ltd. (<a href="http://www.ablerex.com.tw/" rel="noreferrer noreferrer" target="_blank">http://www.ablerex.com.tw/</a><br>
>>>>>>>>>>>> <<a href="http://www.ablerex.com.tw/" rel="noreferrer noreferrer" target="_blank">http://www.ablerex.com.tw/</a>>).<br>
>>>>>>>>>>>><br>
>>>>>>>>>>>> I pull request to networkupstools/nut that<br>
>>>>>>>>>>>> Add support for Ablerex Dk+ #979.<br>
>>>>>>>>>>>><br>
>>>>>>>>>>> long time user of an MS3000RT here. where is<br>
>>>>>>>>>>> the DK+ described? I cannot find it on your<br>
>>>>>>>>>>> web site or via google.<br>
>>>>>>>>>>><br>
>>>>>>>>>>><br>
>>>>>>>>>>> wolfy<br>
>>>>>>>>>>><br>
>>>>>>>>>> --<br>
>>>>>>>>>> 盈正豫順電子股份有限公司<br>
>>>>>>>>>><br>
>>>>>>>>>> Ablerex Electronics Co., Ltd.<br>
>>>>>>>>>><br>
>>>>>>>>>> 研發部 / 沈南村<br>
>>>>>>>>>><br>
>>>>>>>>>> <a href="mailto:E-mail%3AJohnson-shen@ablerex.com.tw" target="_blank" rel="noreferrer">E-mail:Johnson-shen@ablerex.com.tw</a><br>
>> <mailto:<a href="mailto:Johnson-shen@ablerex.com.tw" target="_blank" rel="noreferrer">Johnson-shen@ablerex.com.tw</a>><br>
>>>>>>>>>> Tel: 886-7-397-8640 Ext: 894<br>
>>>>>>>>>><br>
>>>>>>>>>> Fax: 886-7-3978641<br>
>>>>>>>>>><br>
>>>>>>>>>> 807-66高雄市三民區水源路157號<br>
>>>>>>>>>><br>
>>>>>>>>>> No.157, Shuiyuan Rd., Sanmin District,<br>
>> Kaohsiung City 807-66, Taiwan<br>
>>>>>>>>>> (R.O.C.)<br>
>>>>>>>>><br>
>>>>>>>>> --<br>
>>>>>>>>> 盈正豫順電子股份有限公司<br>
>>>>>>>>><br>
>>>>>>>>> Ablerex Electronics Co., Ltd.<br>
>>>>>>>>><br>
>>>>>>>>> 研發部 / 沈南村<br>
>>>>>>>>><br>
>>>>>>>>> <a href="mailto:E-mail%3AJohnson-shen@ablerex.com.tw" target="_blank" rel="noreferrer">E-mail:Johnson-shen@ablerex.com.tw</a><br>
>> <mailto:<a href="mailto:Johnson-shen@ablerex.com.tw" target="_blank" rel="noreferrer">Johnson-shen@ablerex.com.tw</a>><br>
>>>>>>>>> Tel: 886-7-397-8640 Ext: 894<br>
>>>>>>>>><br>
>>>>>>>>> Fax: 886-7-3978641<br>
>>>>>>>>><br>
>>>>>>>>> 807-66高雄市三民區水源路157號<br>
>>>>>>>>><br>
>>>>>>>>> No.157, Shuiyuan Rd., Sanmin District,<br>
>> Kaohsiung City 807-66, Taiwan<br>
>>>>>>>>> (R.O.C.)<br>
>>>>>>>><br>
>>>>>>>> --<br>
>>>>>>>> 盈正豫順電子股份有限公司<br>
>>>>>>>><br>
>>>>>>>> Ablerex Electronics Co., Ltd.<br>
>>>>>>>><br>
>>>>>>>> 研發部 / 沈南村<br>
>>>>>>>><br>
>>>>>>>> <a href="mailto:E-mail%3AJohnson-shen@ablerex.com.tw" target="_blank" rel="noreferrer">E-mail:Johnson-shen@ablerex.com.tw</a><br>
>> <mailto:<a href="mailto:Johnson-shen@ablerex.com.tw" target="_blank" rel="noreferrer">Johnson-shen@ablerex.com.tw</a>><br>
>>>>>>>> Tel: 886-7-397-8640 Ext: 894<br>
>>>>>>>><br>
>>>>>>>> Fax: 886-7-3978641<br>
>>>>>>>><br>
>>>>>>>> 807-66高雄市三民區水源路157號<br>
>>>>>>>><br>
>>>>>>>> No.157, Shuiyuan Rd., Sanmin District, Kaohsiung<br>
>> City 807-66, Taiwan<br>
>>>>>>>> (R.O.C.)<br>
>>>>>>>><br>
>>>>>>>> _______________________________________________<br>
>>>>>>>> Nut-upsdev mailing list<br>
>>>>>>>> <a href="mailto:Nut-upsdev@alioth-lists.debian.net" target="_blank" rel="noreferrer">Nut-upsdev@alioth-lists.debian.net</a><br>
>>>>>>>> <mailto:<a href="mailto:Nut-upsdev@alioth-lists.debian.net" target="_blank" rel="noreferrer">Nut-upsdev@alioth-lists.debian.net</a>><br>
>>>>>>>> <br>
>> <a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev" rel="noreferrer noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev</a><br>
>>>>>>>> <br>
>> <<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev" rel="noreferrer noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev</a>><br>
>>>>>>> --<br>
>>>>>>> 盈正豫順電子股份有限公司<br>
>>>>>>><br>
>>>>>>> Ablerex Electronics Co., Ltd.<br>
>>>>>>><br>
>>>>>>> 研發部 / 沈南村<br>
>>>>>>><br>
>>>>>>> <a href="mailto:E-mail%3AJohnson-shen@ablerex.com.tw" target="_blank" rel="noreferrer">E-mail:Johnson-shen@ablerex.com.tw</a><br>
>> <mailto:<a href="mailto:Johnson-shen@ablerex.com.tw" target="_blank" rel="noreferrer">Johnson-shen@ablerex.com.tw</a>><br>
>>>>>>> Tel: 886-7-397-8640 Ext: 894<br>
>>>>>>><br>
>>>>>>> Fax: 886-7-3978641<br>
>>>>>>><br>
>>>>>>> 807-66高雄市三民區水源路157號<br>
>>>>>>><br>
>>>>>>> No.157, Shuiyuan Rd., Sanmin District, Kaohsiung City<br>
>> 807-66, Taiwan<br>
>>>>>>> (R.O.C.)<br>
>>>>>>><br>
>>>>>> --<br>
>>>>>> 盈正豫順電子股份有限公司<br>
>>>>>><br>
>>>>>> Ablerex Electronics Co., Ltd.<br>
>>>>>><br>
>>>>>> 研發部 / 沈南村<br>
>>>>>><br>
>>>>>> <a href="mailto:E-mail%3AJohnson-shen@ablerex.com.tw" target="_blank" rel="noreferrer">E-mail:Johnson-shen@ablerex.com.tw</a><br>
>> <mailto:<a href="mailto:Johnson-shen@ablerex.com.tw" target="_blank" rel="noreferrer">Johnson-shen@ablerex.com.tw</a>><br>
>>>>>> Tel: 886-7-397-8640 Ext: 894<br>
>>>>>><br>
>>>>>> Fax: 886-7-3978641<br>
>>>>>><br>
>>>>>> 807-66高雄市三民區水源路157號<br>
>>>>>><br>
>>>>>> No.157, Shuiyuan Rd., Sanmin District, Kaohsiung City<br>
>> 807-66, Taiwan<br>
>>>>>> (R.O.C.)<br>
>>>>>><br>
>>>>> --<br>
>>>>> 盈正豫順電子股份有限公司<br>
>>>>><br>
>>>>> Ablerex Electronics Co., Ltd.<br>
>>>>><br>
>>>>> 研發部 / 沈南村<br>
>>>>><br>
>>>>> <a href="mailto:E-mail%3AJohnson-shen@ablerex.com.tw" target="_blank" rel="noreferrer">E-mail:Johnson-shen@ablerex.com.tw</a><br>
>> <mailto:<a href="mailto:Johnson-shen@ablerex.com.tw" target="_blank" rel="noreferrer">Johnson-shen@ablerex.com.tw</a>><br>
>>>>> Tel: 886-7-397-8640 Ext: 894<br>
>>>>><br>
>>>>> Fax: 886-7-3978641<br>
>>>>><br>
>>>>> 807-66高雄市三民區水源路157號<br>
>>>>><br>
>>>>> No.157, Shuiyuan Rd., Sanmin District, Kaohsiung City 807-66,<br>
>> Taiwan<br>
>>>>> (R.O.C.)<br>
>>>><br>
>>>> --<br>
>>>> 盈正豫順電子股份有限公司<br>
>>>><br>
>>>> Ablerex Electronics Co., Ltd.<br>
>>>><br>
>>>> 研發部 / 沈南村<br>
>>>><br>
>>>> <a href="mailto:E-mail%3AJohnson-shen@ablerex.com.tw" target="_blank" rel="noreferrer">E-mail:Johnson-shen@ablerex.com.tw</a><br>
>> <mailto:<a href="mailto:Johnson-shen@ablerex.com.tw" target="_blank" rel="noreferrer">Johnson-shen@ablerex.com.tw</a>><br>
>>>> Tel: 886-7-397-8640 Ext: 894<br>
>>>><br>
>>>> Fax: 886-7-3978641<br>
>>>><br>
>>>> 807-66高雄市三民區水源路157號<br>
>>>><br>
>>>> No.157, Shuiyuan Rd., Sanmin District, Kaohsiung City 807-66,<br>
>> Taiwan<br>
>>>> (R.O.C.)<br>
>>>><br>
>>> -- <br>
>>> 盈正豫順電子股份有限公司<br>
>>><br>
>>> Ablerex Electronics Co., Ltd.<br>
>>><br>
>>> 研發部 / 沈南村<br>
>>><br>
>>> <a href="mailto:E-mail%3AJohnson-shen@ablerex.com.tw" target="_blank" rel="noreferrer">E-mail:Johnson-shen@ablerex.com.tw</a><br>
>>><br>
>>> Tel: 886-7-397-8640 Ext: 894<br>
>>><br>
>>> Fax: 886-7-3978641<br>
>>><br>
>>> 807-66高雄市三民區水源路157號<br>
>>><br>
>>> No.157, Shuiyuan Rd., Sanmin District, Kaohsiung City 807-66, Taiwan<br>
>>> (R.O.C.)<br>
> Hello,<br>
><br>
> Ideally, there would be just nutdrv_qx_ablerex.c/.h source, using mostly the same code and data you developed for blazer, and no separate support in blazer at all (and so no confusion).<br>
><br>
> Users (and NAS's) would configure the common nutdrv_qx driver which supports many devices related by use of Qx family of protocols and was architected to make that coexistence and re-use of shared code easy (or easier than with earlier driver codebases).<br>
><br>
> Based on PID and VID and possibly strings reported to a USB query, it can pick the proper subdriver such as "ablerex" by itself, or explicitly follow the option from ups.conf section for the device.<br>
><br>
> Hope this helps, and thanks,<br>
> Jim Klimov<br>
><br>
> --<br>
> Typos courtesy of K-9 Mail on my Android<br>
<br>
<br>
-- <br>
盈正豫順電子股份有限公司<br>
<br>
Ablerex Electronics Co., Ltd.<br>
<br>
研發部 / 沈南村<br>
<br>
E-mail: <a href="mailto:Johnson-shen@ablerex.com.tw" target="_blank" rel="noreferrer">Johnson-shen@ablerex.com.tw</a><br>
<br>
Tel: 886-7-397-8640 Ext: 894<br>
<br>
Fax: 886-7-3978641<br>
<br>
807-66高雄市三民區水源路157號<br>
<br>
No.157, Shuiyuan Rd., Sanmin District, Kaohsiung City 807-66, Taiwan<br>
(R.O.C.)<br>
<br>
</blockquote></div>