Imported Upstream version 2.7.1

This commit is contained in:
Laurent Bigonville 2013-11-24 16:00:12 +01:00
parent a1fa151fc7
commit 0121794af9
451 changed files with 41339 additions and 10887 deletions

View file

@ -15,18 +15,18 @@ Be sure to also read the <<footnotes,footnotes>>.
ifdef::website[]
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
<fieldset id="support-level-legend">
<legend>Support level legend</legend>
<dl style="list-style: none; padding: 0;">
<dt><span class="red hcl-legend-level">1</span></dt><dd>protocol based on reverse engineering</dd>
<dt><span class="orange hcl-legend-level">2</span></dt><dd>based on fragments of publicly available protocol</dd>
<dt><span class="yellow hcl-legend-level">3</span></dt><dd>based on publicly available protocol</dd>
<dt><span class="blue hcl-legend-level">4</span></dt><dd>vendor provided protocol</dd>
<dt><span class="green hcl-legend-level">5</span></dt><dd>vendor provided protocol and hardware</dd>
</dl>
</fieldset>
<fieldset id="filters-set">
<legend>Filters</legend>
<fieldset id="support-level-legend">
<legend>Support level legend</legend>
<dl style="list-style: none; padding: 0;">
<dt><span class="red">*</span></dt><dd>protocol based on reverse engineering</dd>
<dt><span class="orange">**</span></dt><dd>based on fragments of publicly available protocol</dd>
<dt><span class="yellow">***</span></dt><dd>based on publicly available protocol</dd>
<dt><span class="blue">****</span></dt><dd>vendor provided protocol</dd>
<dt><span class="green">*****</span></dt><dd>vendor provided protocol and hardware</dd>
</dl>
</fieldset>
<table>
<tbody>
<tr>
@ -105,8 +105,8 @@ You may find that it "just works" or mostly works.
In either case, send in a report so this list and the driver can be improved.
Next, if you don't find any match, there are a few drivers that have a good
chance of working on random hardware. These are indicated in the *Various*
entries above.
chance of working on random hardware. These are indicated in the
link:stable-hcl.html?manufacturer=Various[Various] entries above.
After doing that, if those aren't working, you might try running other ones
from the set to see if anything works. Sometimes you get lucky. Finally, if
@ -116,35 +116,40 @@ we will see what we can do for you.
In general, if a driver does not exist, that's due to the lack of overlap
between the set of developers and the set of owners of that hardware.
The way to fix it is to turn a developer into an owner or an owner into a
The way to fix it is to turn a developer into an owner, or an owner into a
developer.
*Report new devices, omissions or errors*
There is a lot of power devices hardware for sale, and it's possible
There are a lot of power devices hardware for sale, and it's possible
that we have missed listing some that are supported, or made an error.
So that this list can be as accurate as possible, please report any
omissions to the
link:http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev[NUT Developers]
mailing list, including the following information:
link:http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev[NUT Developers] mailing list
or the NUT link:https://github.com/networkupstools/nut/issues/new[issue tracker on GitHub],
including the following information:
- mail subject: [HCL] <Manufacturer> <Device> supported by <driver>
- or tag the issue "HCL" and title it: <Manufacturer> <Device> supported by <driver>
replacing Manufacturer, Device and driver by your specific values,
- mail body:
- mail or issue body:
- Device manufacturer and name,
- upsc output (upsrw and upscmd outputs are also welcome),
- link:docs/user-manual.chunked/ar01s06.html#Shutdown_design[shutdown sequence]
testing results,
- a link to an online description is also appreciated.
testing results: a statement that you have actually tested it successfully is
enough for now,
- a link to the manufacturer's online description of the device is also appreciated.
*Pointing the present HCL*
*Linking to the HCL*
You can create direct link to the present HCL, speficying some filters within
the URL. This allows to select devices that matches some specific criteria,
like a connexion type, a manufacturer, ... All filters available on the page
itself are also available for use in the URL.
You can create a direct link to the HCL, specifying some filters within the URL
(JavaScript must be enabled in the browser for this to work). This allows you
to select devices that matches some specific criteria, like a connection type
or a manufacturer. All filters available on the page itself are also available
for use in the URL.
The form of the URL is the following:
@ -166,7 +171,7 @@ The form of the URL is the following:
- 'Network'
|===================================================================
You can finally combine multiple filters, using ampersand (*&*).
You can combine multiple filters, using ampersand (*&*).
For example, if you only want to select USB units from Eaton, use: