--- /dev/null
+Your account
+<p>
+If you want to edit something or just receive notifications about changes, you need an account.
+If you want to only view and browse information here, you do not need one.
+<p>
+The account contains your email address and password.
+If you want, you can provide a login name and xmpp address as well.
+<p>
+Email and xmpp addresses will be used to send you notifications about changes (if you request them).
+Email address can be used to reset your password, if you forget it.
+Neither your email nor your xmpp address will be showed to anybody but you and admins.
+<p>
+Login name is used for your convenience during login (you can log in by either email or login name) and
+it is showed with discussion submits you wrote.
+
+<h2>Obtaining an account</h2>
+<p>
+It is possible you account has been created already.
+It is created if you submit something using email.
+And we created accounts for all submits imported from previous version of this site.
+In that case, you need to <a href='$AC_URL$respass'>reset your password</a> (because exists no password for you).
+<p>
+If you do not have an account, go to <a href='$AC_URL$register'>register</a> item in menu (you can find it, when you visit <a href='$AC_URL$login'>Log in</a> page) and fill your email address.
+A message containing confirmation link will be sent to it.
+After you follow the link and fill in the rest, your account is ready for use.
+
+<h2>Reseting password</h2>
+<p>
+If your account was created automatically or you forget your password, you need to reset it.
+Enter your email address into the <a href='$AC_URL$respass'>reset password</a> page.
+A message with confirmation link will be sent to you.
+When you follow it, you will be provided with a form where you can change the password.
+
+<h2>Logging in</h2>
+<p>
+When you want to edit some information here or alter your own settings, you need to be logged in.
+Fill the form on the <a href='$AC_URL$login'>log in</a> page.
+You can provide either your email address or your login name, they both work.
+<p>
+After successful login, you will be redirected either to <a href='$HELP_URL$list'>ID browsing</a> or to any action you tried to perform and it required login.
+<p>
+You can log out again by <a href='$AC_URL$logout'>log out</a> menu item.
+You will be logged out automatically if you do not do anything in a long time (approx. 30 minutes) or close your browser.
+
+<h2>Actions requiring login</h2>
+<ul class='navigation'>
+ <li><a href='$HELP_URL$profile'>Configuring your profile</a>
+ <li><a href='$HELP_URL$notifications'>Editing your notifications</a>
+ <li><a href='$HELP_URL$newitem'>Submitting a new item</a>
+ <li><a href='$HELP_URL$newhistory'>Entering a discussion</a>
+</ul>
+
+<h2>Accounts with additional rights</h2>
+<p>
+There are accounts with additional rights, like deleting whole items or approving history comments.
+If you have one, you probably know it already.
+If you think you should have one, contact owners of this site.
--- /dev/null
+Administration interface
+
+<h2>Layout</h2>
+<p>
+Each item requiring administration has it's own rectangle with few lines.
+The first line (either white or grey, depending on the current ID status) contains its path.
+The second line (green), if it is present, specifies current name.
+<p>
+The following gray lines are new discussion comments.
+<p>
+The last, yellow, line is for submitting answer.
+
+<h2>Actions</h2>
+<h3>Deletes</h3>
+<p>
+The last column (with square check-boxes) is for deleting.
+To delete the whole item, use red one in the first line (present only if it is possible to delete this item).
+Each discussion comment has it's own one.
+The delete checkbox in the yellow line will delete name of the current item (eg. the history is preserved, but it will not appear in pci.ids or other exports).
+
+<h3>Selecting</h3>
+<p>
+The round boxes (on the left side of the deleting ones) is for selecting active history comment, which specifies the name of the item.
+If you leave it as it is, on the first line, nothing changes.
+If you select the green one, the name does not change, but the whole history of the item is marked as seen and won't appear again in the administration interface (until someone writes some more).
+If you select any history comment, it will become active.
+
+<h3>Commenting</h3>
+<p>
+The yellow line act's similarly to <a href='$HELP_URL$newietm>new item</a> form.
+If you provide only the text (the large box), it will just appear in the history.
+If you specify a name, it will become active (even if you specified any other active by a round box).
+All comments from administration interface are marked as seen, so you do not have to approve them.
+<p>
+You can use predefined answers to save you some typing. Just select it from the box on the left side.
+If you have javascript enabled, it will appear in the text box and you can view and modify it.
+If your browser does not run javascript, nothing appears, but the combo box overrides the text in the box when in non-default position.
+
+<h3>Seen history</h3>
+<p>
+If you perform any action on an item, all it's history will become marked as seen (will appear in white box in <a href='$HELP_URL$list'>browsing</a> and will not appear in administration interface</a>).
+If you do not want to change anything about the item, just use the green selection box to read the history.
--- /dev/null
+Help index
+<h2>Read only operations</h2>
+<ul class='navigation'>
+ <li><a href='$HELP_URL$list'>Browsing</a>
+ <li><a href='$HELP_URL$jump'>Jumping</a>
+</ul>
+<h2>Account based operations</h2>
+<ul class='navigation'>
+ <li><a href='$HELP_URL$account'>Account creation & login</a>
+ <li><a href='$HELP_URL$notifications'>Notifications</a>
+ <li><a href='$HELP_URL$profile'>Profile</a>
+</ul>
+<h2>Editing database</h2>
+<ul class='navigation'>
+ <li><a href='$HELP_URL$newitem'>Submitting new item</a>
+ <li><a href='$HELP_URL$newhistory'>Discussion</a>
+ <li><a href='$HELP_URL$mailsubmit'>Mail submit</a>
+</ul>
+<h2>Information about ID types</h2>
+<ul class='navigation'>
+ <li><a href='$HELP_URL$pci'>PCI devices</a>
+ <li><a href='$HELP_URL$pci_class'>PCI device classes</a>
+</ul>
--- /dev/null
+Jumping
+The jump box (little text box with 'Jump' button by its side) has two functions.
+
+<h2>Direct ID jump</h2>
+<p>
+If you enter an ID and press Jump (or Enter), you are sent directly to that ID.
+<p>
+You can use both slashes ('/') and colons (':') as ID segment separators.
+If the ID starts with an ID type prefix (eg. 'PC'), it is considered absolute.
+If it starts with a segment separator, it is considered absolute inside current ID tree (eg. PCI devices).
+Absolute addresses are tried first, if they do not exist, relative search is done.
+Otherwise, it is relative and is appended to current ID, then to its parent and so on, until some exists or a root of tree is reached.
+
+<h2>Name search</h2>
+<p>
+If direct ID jump does not succeed, names of items are searched for it.
+By default only names of the same ID type are searched (if you browse PCI devices, you will not get results from device classes).
+If you want to search all names, prefix the search with an asterisk ('*').
+<p>
+If you want to turn off name search in your query, prefix the query with '#'.
+
+<h2>Examples</h2>
+<p>
+All examples are searches from within ID 'PC:0000:0000'.
+<ul>
+ <li><tt>PD:00</tt> ‒ jumps to <tt>PD:00</tt>, if it exist.
+ <li><tt>:1234</tt> ‒ jumps to <tt>PC:1234</tt>, if it exist.
+ <li><tt>abcd</tt> ‒ tries <tt>PC:0000:0000:abcd</tt>, then <tt>PC:0000:abcd</tt>, then <tt>PC:abcd</tt>. Then searches in names.
+ <li><tt>#abcd</tt> ‒ same as above, but does not continue searching in names.
+ <li><tt>Some text</tt> ‒ all id searches will fail, names of PCI devices are searched for <tt>Some text</tt>.
+ <li><tt>*Some text</tt> ‒ same, but the search is trough all devices in database.
+</ul>
--- /dev/null
+Browsing ID list
+<p>
+You can examine the current list of IDs.
+The IDs are organized into a tree.
+<h2>Page anatomy</h2>
+<p>
+Page is divided into parts:
+<ul>
+ <li><strong>Menu</strong> ‒ you can perform actions, both in connection with current item (like <a href='$HELP_URL$newitem'>adding a new sub-item</a>, in top left corner) and global (<a href='$HELP_URL$profile'>editing your profile</a>, in top right corner).
+ <li><strong>Hierarchy</strong> ‒ lists all parental items.
+ <li><strong>Item status</strong> ‒ contains current name and comment.
+ <li><strong>Discussion</strong> ‒ contains history of suggested names, notes and general talk about current item.
+ <li><strong>List of sub-items</strong> ‒ all direct sub-items are listed here and you can browse into them.
+</ul>
+
+You can find menu and hierarchy in most other pages and they have the same function.
+
+<h2>Colors</h2>
+Colors are used both in discussion and list of sub-items to mark status of discussion comments and sub-items respectively.
+<span class='main-history'>Green entries</span> are discussion comments which provide current item name.
+<span class='unseen-history'>Grey ones</span> are entries with some problem. They are either items without any assigned name (discussion about non-existing item, new item which was not yet approved by an admin) or discussion comments not yet seen by an admin.
+<span class='history'>White ones</span> are the rest, usual discussion and valid items.
+
+<h2>Example</h2>
+<div class='help-example'>
+<div class='top'>
+<div class='lmenu'><ul>
+ <li><a href='$HELP_URL$newitem'>Add item</a>
+ <li><a href='$HELP_URL$newhistory'>Discuss</a>
+ <li><form class='jump' method='POST' action='$HELP_URL$jump'><p><input type='text' class='jump' disabled='disabled'><input type='submit' value='Jump'></form>
+</ul></div>
+<div class='rmenu'><ul>
+ <li><a href='$HELP_URL$account'>Log in</a>
+</ul></div>
+<h1>ID 0000</h1>
+<div class='clear'></div></div>
+<div class='path'><p><a href='$HELP_URL$index'>Main page</a> -> <a href='$HELP_URL$index'>Parent</a></div>
+<h2>ID 0000</h2>
+<div class='name'><p>Name: ID name</div>
+<div class='discussion'><h2>Discussion</h2>
+<div class='main-history'>
+ <p class='itemname'>Name: ID name
+ <p class='discussion-text'>This item is here just as an example.
+ <p class='author'>Author
+ <p class='time'>1900-01-01 00:00
+</div>
+</div>
+<h2>Sub-items</h2>
+<table class='subnodes'><col class='id-col'><col class='name-col'><col class='note-col'>
+<th>Id<th>Name<th>Note
+<tr class='item'><td>1234<td>Sub-item<td>This is just example
+</table>
+</div>
--- /dev/null
+Mail submit
+<p>
+PCI IDs can be submited and edited using email.
+There is a robot at address <a href='mailto:pci-ids@ucw.cz'>pci-ids@ucw.cz</a>, which accepts patches sent to it.
+Please use unified diffs (<tt>diff -u</tt>) against the current <a href='/static/pci.ids'>pci.ids</a> file (preferably the one just downloaded from this page, but the robot tries hard to recognize older versions as well).
+Avoid base64 encoding and mail agents converting tabs to spaces, breaking lines and so on.
+<p>
+If you do not have an <a href='$HELP_URL$account'>account</a> yet, one is created for your email address.
+You will get subscribed to notifications about all the items you changed (if you like to tweak the notifications, look at their <a href='$HELP_URL$notifications'>documentation</a>.
+<p>
+Please note, the robot understands only PCI IDs. Other types of IDs must be entered by the web interface.
--- /dev/null
+Discussion
+<p>
+If you think some information here is wrong, you know better or want to say something about some item, you can enter discussion.
+Browse to the item and click the <a href='$AC_URL$newhistory'>discuss</a> link.
+<p>
+If you do not want to alter current name or note, provide only text.
+If you want to change name, provide that one too (in that case, you do not have to provide text, but it is recommended to say why you think the new version is better).
+Changing note alone is not possible, you can change it with name only.
+If you change just note, enter the same name as before.
+<p>
+You can request item deletion here, too.
+
+<h2>Approval</h2>
+<p>
+All submissions are checked by an admin for errors.
+Please try to provide valid information.
+You should check specific help for corresponding ID type:
+<ul class='navigation'>
+ <li><a href='$HELP_URL$pci'>PCI devices</a>
+ <li><a href='$HELP_URL$pci_class'>PCI device classes</a>
+</ul>
+
+<h2>Notification subscription</h2>
+<p>
+If the subscribe checkbox is checked, a notification on the new item will be created for you.
+For more information about notifications look at <a href='$HELP_URL$notifications'>their documentation</a>.
+<p>
+The checkbox is present only unless you have a notification covering this item already.
+
+<h2>See also</h2>
+<p>
+You can create <a href='$HELP_URL$newitem'>new items</a>.
+<p>
+If you want to know about changes in some item, set up <a href='$HELP_URL$notifications'>a notification</a>.
--- /dev/null
+Add a new item
+<p>
+If you know about an ID not present here, you can submit it.
+Browse to the item which should contain it and click <a href='$AC_URL$newitem'>add item</a> link.
+<p>
+You need to fill in the ID and its name.
+The ID is just the last part (without parent part, for example if you have PCI device <tt>1234:5678</tt> and the vendor <tt>1234</tt> already exists, you enter only <tt>5678</tt>).
+If you know chip name, it is preferred over marketing name.
+<p>
+You can add some note to the name, for example, if the ID is not really owned by the company using it.
+You can add a discussion comment to it (why you think it is correct).
+The difference between note and discussion is that note is additional information to name, while discussion is administrative.
+Also, note is sometimes distributed, while discussion isn't.
+<p>
+Both note and discussion is optional.
+<p>
+After you submit it, it will wait approval of an admin.
+
+<h2>Approval</h2>
+<p>
+Each item is checked and approved by an admin.
+It is because not all submissions are correct.
+<p>
+If you want to it to get approved, please check you enter valid information into correct place (eg. not an USB ID into PCI devices, Device into its vendor).
+You should check help specific for each tree:
+<ul class='navigation'>
+ <li><a href='$HELP_URL$pci'>PCI devices</a>
+ <li><a href='$HELP_URL$pci_class'>PCI device classes</a>
+</ul>
+
+<h2>Notification subscription</h2>
+<p>
+If the subscribe checkbox is checked, a notification on the new item will be created for you.
+For more information about notifications look at <a href='$HELP_URL$notifications'>their documentation</a>.
+
+<h2>See also</h2>
+<p>
+Once item is submitted, it is not sealed for ever. You can <a href='$HELP_URL$newhistory'>discuss</a> existing items and suggest them new names.
+<p>
+If you are interested in changes in some item (or its whole subtree), you can let the system send you <a href='$HELP_URL$notifications'>notifications</a>.
--- /dev/null
+Notifications
+<p>
+If you are interested in any changes in some item, you can set up a notification to get informed.
+Browse to the item and click <a href='$AC_URL$notifications'>notifications</a> link (it is visible only when you are <a href='$HELP_URL$account'>logged in</a>.
+You can set these things:
+<ul>
+ <li><strong>Effect range</strong> ‒ which IDs are considered by this notification. If the notification is not recursive, only the current ID is taken into account. Recursive notifications work on the given ID and its whole subtree (sub-items, their sub-items, …).
+ <li><strong>Notification level</strong> ‒ how serious even needs to happen to trigger the notification. None means the notification never happens (it does not exist, you can delete it by setting it to it), main comment means whenever admin approves change of a name, sub-item is when someone submits new item with this one as a parent, suggestion is when someone suggests a new name for the item (but is not yet approved) and discussion is whenever someone writes anything.
+ All the more common notifications contain the less common (when you check discussion and an admin approves a name change, it is triggered too, but not the other way around).
+ <li><strong>Notification way</strong> ‒ the way the notification gets to you.
+</ul>
+
+<h2>Existing notifications</h2>
+<p>
+There is a list of currently existing notifications at the bottom of page.
+You can switch to them by clicking on them.
+
+<h2>See also</h2>
+<p>
+This is all your own configuration. You can <a href='$HELP_URL$account'>get an account</a> so you can set it up.
+<p>
+You can set up various things (like address, where the notifications are sent) in your <a href='$HELP_URL$profile'>profile</a>.
--- /dev/null
+PCI devices
+<h2>Vendors</h2>
+<p>
+The top level of hierarchy is a vendor list.
+Each vendor has a 2-byte long id, stored in database as 4 hexadecimal digits (with lowercase letters).
+They can be browsed <a href='/read/PC'>here</a>.
+
+<h2>Devices</h2>
+<p>
+Each vendor contains a list of its devices.
+Each device in the list has a 2-byte long id, stored the same way as vendor id (4 hexadecimal letters).
+
+<h2>Subsystems</h2>
+A device can consist of more sub-systems.
+Each sub-system has 4-byte long id, stored as 8 hexadecimal letters, split in the middle by a space (for example <tt>1234 abcd</tt> could be a sub-system id).
+The first quad of digits is considered a vendor id (from the same list of vendors). The vendor of the sub-system can be different than vendor of the device.
+
+<h2>See also</h2>
+<p>
+You can have a look at <a href='$HELP_URL$pci_class'>PCI device classes</a>.
--- /dev/null
+PCI device classes
+<h2>Device classes</h2>
+<p>
+Device class is identified by a single byte. It is stored as 2 hexadecimal digits (all in lowercase).
+They can be examined <a href='/read/PD'>here</a>.
+
+<h2>Device subclasses</h2>
+<p>
+A device class is divided into subclasses.
+Each subclass is identified in a same way as a device class, by single byte represented by 2 hexadecimal letters.
+
+<h2>Program interface</h2>
+<p>
+A subclass can have different program interfaces.
+An interface is identified by a single byte represented by 2 hexadecimal letters.
+
+<h2>See also</h2>
+You can have a look at <a href='/read/PC'>PCI devices</a>.
--- /dev/null
+User profile
+<p>
+When you are logged in, you can find a <a href='$AC_URL$profile'>profile</a> link.
+You can set various information about your account.
+<ul>
+ <li><strong>Email</strong> ‒ this is the address email notifications about changes in database will be sent.
+ It is used for resetting password and you can log in using it.
+ <li><strong>Login</strong> ‒ you can log in using this one instead of your email address.
+ Furthermore, it is showed with discussion comments you wrote.
+ <li><strong>Xmpp</strong> ‒ you can get notifications using xmpp (aka jabber) as well as email.
+ <li><strong>Password</strong> ‒ if you want to set new password, fill in both new password and confirm password boxes.
+ <li><strong>Batch times</strong> ‒ if you want to group notifications together, so you receive less messages.
+ This is the time in minutes, for how long the system will gather notifications before it sends them by email or xmpp respectively.
+</ul>
+
+<h2>Password protected values</h2>
+<p>
+Email, login and new password are protected by the old password.
+If you want to change any of these, you must provide the old password to unlock them.
+
+<h2>See also</h2>
+<p>
+You can get a profile by <a href='$HELP_URL$account'>registering it</a>.
+<p>
+To receive any notifications, you need to <a href='$HELP_URL$notifications'>set them up</a>.
+++ /dev/null
-Your account
-<p>
-If you want to edit something or just receive notifications about changes, you need an account.
-If you want to only view and browse information here, you do not need one.
-<p>
-The account contains your email address and password.
-If you want, you can provide a login name and xmpp address as well.
-<p>
-Email and xmpp addresses will be used to send you notifications about changes (if you request them).
-Email address can be used to reset your password, if you forget it.
-Neither your email nor your xmpp address will be showed to anybody but you and admins.
-<p>
-Login name is used for your convenience during login (you can log in by either email or login name) and
-it is showed with discussion submits you wrote.
-
-<h2>Obtaining an account</h2>
-<p>
-It is possible you account has been created already.
-It is created if you submit something using email.
-And we created accounts for all submits imported from previous version of this site.
-In that case, you need to <a href='$AC_URL$respass'>reset your password</a> (because exists no password for you).
-<p>
-If you do not have an account, go to <a href='$AC_URL$register'>register</a> item in menu (you can find it, when you visit <a href='$AC_URL$login'>Log in</a> page) and fill your email address.
-A message containing confirmation link will be sent to it.
-After you follow the link and fill in the rest, your account is ready for use.
-
-<h2>Reseting password</h2>
-<p>
-If your account was created automatically or you forget your password, you need to reset it.
-Enter your email address into the <a href='$AC_URL$respass'>reset password</a> page.
-A message with confirmation link will be sent to you.
-When you follow it, you will be provided with a form where you can change the password.
-
-<h2>Logging in</h2>
-<p>
-When you want to edit some information here or alter your own settings, you need to be logged in.
-Fill the form on the <a href='$AC_URL$login'>log in</a> page.
-You can provide either your email address or your login name, they both work.
-<p>
-After successful login, you will be redirected either to <a href='$HELP_URL$list'>ID browsing</a> or to any action you tried to perform and it required login.
-<p>
-You can log out again by <a href='$AC_URL$logout'>log out</a> menu item.
-You will be logged out automatically if you do not do anything in a long time (approx. 30 minutes) or close your browser.
-
-<h2>Actions requiring login</h2>
-<ul class='navigation'>
- <li><a href='$HELP_URL$profile'>Configuring your profile</a>
- <li><a href='$HELP_URL$notifications'>Editing your notifications</a>
- <li><a href='$HELP_URL$newitem'>Submitting a new item</a>
- <li><a href='$HELP_URL$newhistory'>Entering a discussion</a>
-</ul>
-
-<h2>Accounts with additional rights</h2>
-<p>
-There are accounts with additional rights, like deleting whole items or approving history comments.
-If you have one, you probably know it already.
-If you think you should have one, contact owners of this site.
+++ /dev/null
-Administration interface
-
-<h2>Layout</h2>
-<p>
-Each item requiring administration has it's own rectangle with few lines.
-The first line (either white or grey, depending on the current ID status) contains its path.
-The second line (green), if it is present, specifies current name.
-<p>
-The following gray lines are new discussion comments.
-<p>
-The last, yellow, line is for submitting answer.
-
-<h2>Actions</h2>
-<h3>Deletes</h3>
-<p>
-The last column (with square check-boxes) is for deleting.
-To delete the whole item, use red one in the first line (present only if it is possible to delete this item).
-Each discussion comment has it's own one.
-The delete checkbox in the yellow line will delete name of the current item (eg. the history is preserved, but it will not appear in pci.ids or other exports).
-
-<h3>Selecting</h3>
-<p>
-The round boxes (on the left side of the deleting ones) is for selecting active history comment, which specifies the name of the item.
-If you leave it as it is, on the first line, nothing changes.
-If you select the green one, the name does not change, but the whole history of the item is marked as seen and won't appear again in the administration interface (until someone writes some more).
-If you select any history comment, it will become active.
-
-<h3>Commenting</h3>
-<p>
-The yellow line act's similarly to <a href='$HELP_URL$newietm>new item</a> form.
-If you provide only the text (the large box), it will just appear in the history.
-If you specify a name, it will become active (even if you specified any other active by a round box).
-All comments from administration interface are marked as seen, so you do not have to approve them.
-<p>
-You can use predefined answers to save you some typing. Just select it from the box on the left side.
-If you have javascript enabled, it will appear in the text box and you can view and modify it.
-If your browser does not run javascript, nothing appears, but the combo box overrides the text in the box when in non-default position.
-
-<h3>Seen history</h3>
-<p>
-If you perform any action on an item, all it's history will become marked as seen (will appear in white box in <a href='$HELP_URL$list'>browsing</a> and will not appear in administration interface</a>).
-If you do not want to change anything about the item, just use the green selection box to read the history.
+++ /dev/null
-Help index
-<h2>Read only operations</h2>
-<ul class='navigation'>
- <li><a href='$HELP_URL$list'>Browsing</a>
- <li><a href='$HELP_URL$jump'>Jumping</a>
-</ul>
-<h2>Account based operations</h2>
-<ul class='navigation'>
- <li><a href='$HELP_URL$account'>Account creation & login</a>
- <li><a href='$HELP_URL$notifications'>Notifications</a>
- <li><a href='$HELP_URL$profile'>Profile</a>
-</ul>
-<h2>Editing database</h2>
-<ul class='navigation'>
- <li><a href='$HELP_URL$newitem'>Submitting new item</a>
- <li><a href='$HELP_URL$newhistory'>Discussion</a>
- <li><a href='$HELP_URL$mailsubmit'>Mail submit</a>
-</ul>
-<h2>Information about ID types</h2>
-<ul class='navigation'>
- <li><a href='$HELP_URL$pci'>PCI devices</a>
- <li><a href='$HELP_URL$pci_class'>PCI device classes</a>
-</ul>
+++ /dev/null
-Jumping
-The jump box (little text box with 'Jump' button by its side) has two functions.
-
-<h2>Direct ID jump</h2>
-<p>
-If you enter an ID and press Jump (or Enter), you are sent directly to that ID.
-<p>
-You can use both slashes ('/') and colons (':') as ID segment separators.
-If the ID starts with an ID type prefix (eg. 'PC'), it is considered absolute.
-If it starts with a segment separator, it is considered absolute inside current ID tree (eg. PCI devices).
-Absolute addresses are tried first, if they do not exist, relative search is done.
-Otherwise, it is relative and is appended to current ID, then to its parent and so on, until some exists or a root of tree is reached.
-
-<h2>Name search</h2>
-<p>
-If direct ID jump does not succeed, names of items are searched for it.
-By default only names of the same ID type are searched (if you browse PCI devices, you will not get results from device classes).
-If you want to search all names, prefix the search with an asterisk ('*').
-<p>
-If you want to turn off name search in your query, prefix the query with '#'.
-
-<h2>Examples</h2>
-<p>
-All examples are searches from within ID 'PC:0000:0000'.
-<ul>
- <li><tt>PD:00</tt> ‒ jumps to <tt>PD:00</tt>, if it exist.
- <li><tt>:1234</tt> ‒ jumps to <tt>PC:1234</tt>, if it exist.
- <li><tt>abcd</tt> ‒ tries <tt>PC:0000:0000:abcd</tt>, then <tt>PC:0000:abcd</tt>, then <tt>PC:abcd</tt>. Then searches in names.
- <li><tt>#abcd</tt> ‒ same as above, but does not continue searching in names.
- <li><tt>Some text</tt> ‒ all id searches will fail, names of PCI devices are searched for <tt>Some text</tt>.
- <li><tt>*Some text</tt> ‒ same, but the search is trough all devices in database.
-</ul>
+++ /dev/null
-Browsing ID list
-<p>
-You can examine the current list of IDs.
-The IDs are organized into a tree.
-<h2>Page anatomy</h2>
-<p>
-Page is divided into parts:
-<ul>
- <li><strong>Menu</strong> ‒ you can perform actions, both in connection with current item (like <a href='$HELP_URL$newitem'>adding a new sub-item</a>, in top left corner) and global (<a href='$HELP_URL$profile'>editing your profile</a>, in top right corner).
- <li><strong>Hierarchy</strong> ‒ lists all parental items.
- <li><strong>Item status</strong> ‒ contains current name and comment.
- <li><strong>Discussion</strong> ‒ contains history of suggested names, notes and general talk about current item.
- <li><strong>List of sub-items</strong> ‒ all direct sub-items are listed here and you can browse into them.
-</ul>
-
-You can find menu and hierarchy in most other pages and they have the same function.
-
-<h2>Colors</h2>
-Colors are used both in discussion and list of sub-items to mark status of discussion comments and sub-items respectively.
-<span class='main-history'>Green entries</span> are discussion comments which provide current item name.
-<span class='unseen-history'>Grey ones</span> are entries with some problem. They are either items without any assigned name (discussion about non-existing item, new item which was not yet approved by an admin) or discussion comments not yet seen by an admin.
-<span class='history'>White ones</span> are the rest, usual discussion and valid items.
-
-<h2>Example</h2>
-<div class='help-example'>
-<div class='top'>
-<div class='lmenu'><ul>
- <li><a href='$HELP_URL$newitem'>Add item</a>
- <li><a href='$HELP_URL$newhistory'>Discuss</a>
- <li><form class='jump' method='POST' action='$HELP_URL$jump'><p><input type='text' class='jump' disabled='disabled'><input type='submit' value='Jump'></form>
-</ul></div>
-<div class='rmenu'><ul>
- <li><a href='$HELP_URL$account'>Log in</a>
-</ul></div>
-<h1>ID 0000</h1>
-<div class='clear'></div></div>
-<div class='path'><p><a href='$HELP_URL$index'>Main page</a> -> <a href='$HELP_URL$index'>Parent</a></div>
-<h2>ID 0000</h2>
-<div class='name'><p>Name: ID name</div>
-<div class='discussion'><h2>Discussion</h2>
-<div class='main-history'>
- <p class='itemname'>Name: ID name
- <p class='discussion-text'>This item is here just as an example.
- <p class='author'>Author
- <p class='time'>1900-01-01 00:00
-</div>
-</div>
-<h2>Sub-items</h2>
-<table class='subnodes'><col class='id-col'><col class='name-col'><col class='note-col'>
-<th>Id<th>Name<th>Note
-<tr class='item'><td>1234<td>Sub-item<td>This is just example
-</table>
-</div>
+++ /dev/null
-Mail submit
-<p>
-PCI IDs can be submited and edited using email.
-There is a robot at address <a href='mailto:pci-ids@ucw.cz'>pci-ids@ucw.cz</a>, which accepts patches sent to it.
-Please use unified diffs (<tt>diff -u</tt>) against the current <a href='/static/pci.ids'>pci.ids</a> file (preferably the one just downloaded from this page, but the robot tries hard to recognize older versions as well).
-Avoid base64 encoding and mail agents converting tabs to spaces, breaking lines and so on.
-<p>
-If you do not have an <a href='$HELP_URL$account'>account</a> yet, one is created for your email address.
-You will get subscribed to notifications about all the items you changed (if you like to tweak the notifications, look at their <a href='$HELP_URL$notifications'>documentation</a>.
-<p>
-Please note, the robot understands only PCI IDs. Other types of IDs must be entered by the web interface.
+++ /dev/null
-Discussion
-<p>
-If you think some information here is wrong, you know better or want to say something about some item, you can enter discussion.
-Browse to the item and click the <a href='$AC_URL$newhistory'>discuss</a> link.
-<p>
-If you do not want to alter current name or note, provide only text.
-If you want to change name, provide that one too (in that case, you do not have to provide text, but it is recommended to say why you think the new version is better).
-Changing note alone is not possible, you can change it with name only.
-If you change just note, enter the same name as before.
-<p>
-You can request item deletion here, too.
-
-<h2>Approval</h2>
-<p>
-All submissions are checked by an admin for errors.
-Please try to provide valid information.
-You should check specific help for corresponding ID type:
-<ul class='navigation'>
- <li><a href='$HELP_URL$pci'>PCI devices</a>
- <li><a href='$HELP_URL$pci_class'>PCI device classes</a>
-</ul>
-
-<h2>Notification subscription</h2>
-<p>
-If the subscribe checkbox is checked, a notification on the new item will be created for you.
-For more information about notifications look at <a href='$HELP_URL$notifications'>their documentation</a>.
-<p>
-The checkbox is present only unless you have a notification covering this item already.
-
-<h2>See also</h2>
-<p>
-You can create <a href='$HELP_URL$newitem'>new items</a>.
-<p>
-If you want to know about changes in some item, set up <a href='$HELP_URL$notifications'>a notification</a>.
+++ /dev/null
-Add a new item
-<p>
-If you know about an ID not present here, you can submit it.
-Browse to the item which should contain it and click <a href='$AC_URL$newitem'>add item</a> link.
-<p>
-You need to fill in the ID and its name.
-The ID is just the last part (without parent part, for example if you have PCI device <tt>1234:5678</tt> and the vendor <tt>1234</tt> already exists, you enter only <tt>5678</tt>).
-If you know chip name, it is preferred over marketing name.
-<p>
-You can add some note to the name, for example, if the ID is not really owned by the company using it.
-You can add a discussion comment to it (why you think it is correct).
-The difference between note and discussion is that note is additional information to name, while discussion is administrative.
-Also, note is sometimes distributed, while discussion isn't.
-<p>
-Both note and discussion is optional.
-<p>
-After you submit it, it will wait approval of an admin.
-
-<h2>Approval</h2>
-<p>
-Each item is checked and approved by an admin.
-It is because not all submissions are correct.
-<p>
-If you want to it to get approved, please check you enter valid information into correct place (eg. not an USB ID into PCI devices, Device into its vendor).
-You should check help specific for each tree:
-<ul class='navigation'>
- <li><a href='$HELP_URL$pci'>PCI devices</a>
- <li><a href='$HELP_URL$pci_class'>PCI device classes</a>
-</ul>
-
-<h2>Notification subscription</h2>
-<p>
-If the subscribe checkbox is checked, a notification on the new item will be created for you.
-For more information about notifications look at <a href='$HELP_URL$notifications'>their documentation</a>.
-
-<h2>See also</h2>
-<p>
-Once item is submitted, it is not sealed for ever. You can <a href='$HELP_URL$newhistory'>discuss</a> existing items and suggest them new names.
-<p>
-If you are interested in changes in some item (or its whole subtree), you can let the system send you <a href='$HELP_URL$notifications'>notifications</a>.
+++ /dev/null
-Notifications
-<p>
-If you are interested in any changes in some item, you can set up a notification to get informed.
-Browse to the item and click <a href='$AC_URL$notifications'>notifications</a> link (it is visible only when you are <a href='$HELP_URL$account'>logged in</a>.
-You can set these things:
-<ul>
- <li><strong>Effect range</strong> ‒ which IDs are considered by this notification. If the notification is not recursive, only the current ID is taken into account. Recursive notifications work on the given ID and its whole subtree (sub-items, their sub-items, …).
- <li><strong>Notification level</strong> ‒ how serious even needs to happen to trigger the notification. None means the notification never happens (it does not exist, you can delete it by setting it to it), main comment means whenever admin approves change of a name, sub-item is when someone submits new item with this one as a parent, suggestion is when someone suggests a new name for the item (but is not yet approved) and discussion is whenever someone writes anything.
- All the more common notifications contain the less common (when you check discussion and an admin approves a name change, it is triggered too, but not the other way around).
- <li><strong>Notification way</strong> ‒ the way the notification gets to you.
-</ul>
-
-<h2>Existing notifications</h2>
-<p>
-There is a list of currently existing notifications at the bottom of page.
-You can switch to them by clicking on them.
-
-<h2>See also</h2>
-<p>
-This is all your own configuration. You can <a href='$HELP_URL$account'>get an account</a> so you can set it up.
-<p>
-You can set up various things (like address, where the notifications are sent) in your <a href='$HELP_URL$profile'>profile</a>.
+++ /dev/null
-PCI devices
-<h2>Vendors</h2>
-<p>
-The top level of hierarchy is a vendor list.
-Each vendor has a 2-byte long id, stored in database as 4 hexadecimal digits (with lowercase letters).
-They can be browsed <a href='/read/PC'>here</a>.
-
-<h2>Devices</h2>
-<p>
-Each vendor contains a list of its devices.
-Each device in the list has a 2-byte long id, stored the same way as vendor id (4 hexadecimal letters).
-
-<h2>Subsystems</h2>
-A device can consist of more sub-systems.
-Each sub-system has 4-byte long id, stored as 8 hexadecimal letters, split in the middle by a space (for example <tt>1234 abcd</tt> could be a sub-system id).
-The first quad of digits is considered a vendor id (from the same list of vendors). The vendor of the sub-system can be different than vendor of the device.
-
-<h2>See also</h2>
-<p>
-You can have a look at <a href='$HELP_URL$pci_class'>PCI device classes</a>.
+++ /dev/null
-PCI device classes
-<h2>Device classes</h2>
-<p>
-Device class is identified by a single byte. It is stored as 2 hexadecimal digits (all in lowercase).
-They can be examined <a href='/read/PD'>here</a>.
-
-<h2>Device subclasses</h2>
-<p>
-A device class is divided into subclasses.
-Each subclass is identified in a same way as a device class, by single byte represented by 2 hexadecimal letters.
-
-<h2>Program interface</h2>
-<p>
-A subclass can have different program interfaces.
-An interface is identified by a single byte represented by 2 hexadecimal letters.
-
-<h2>See also</h2>
-You can have a look at <a href='/read/PC'>PCI devices</a>.
+++ /dev/null
-User profile
-<p>
-When you are logged in, you can find a <a href='$AC_URL$profile'>profile</a> link.
-You can set various information about your account.
-<ul>
- <li><strong>Email</strong> ‒ this is the address email notifications about changes in database will be sent.
- It is used for resetting password and you can log in using it.
- <li><strong>Login</strong> ‒ you can log in using this one instead of your email address.
- Furthermore, it is showed with discussion comments you wrote.
- <li><strong>Xmpp</strong> ‒ you can get notifications using xmpp (aka jabber) as well as email.
- <li><strong>Password</strong> ‒ if you want to set new password, fill in both new password and confirm password boxes.
- <li><strong>Batch times</strong> ‒ if you want to group notifications together, so you receive less messages.
- This is the time in minutes, for how long the system will gather notifications before it sends them by email or xmpp respectively.
-</ul>
-
-<h2>Password protected values</h2>
-<p>
-Email, login and new password are protected by the old password.
-If you want to change any of these, you must provide the old password to unlock them.
-
-<h2>See also</h2>
-<p>
-You can get a profile by <a href='$HELP_URL$account'>registering it</a>.
-<p>
-To receive any notifications, you need to <a href='$HELP_URL$notifications'>set them up</a>.
under the terms of either the <a href="http://www.opensource.org/licenses/gpl-license.php">GNU General Public License</a> (version 2 or later)
or of the <a href="http://www.opensource.org/licenses/bsd-license.php">3-clause BSD License.</a>
- <p>You may want to read <a href='/?action=help?help=index'>help</a> before you start using this site.
+ <p>You may want to read <a href='/read/?action=help?help=index'>help</a> before you start using this site.
<h2>How to submit new data</h2>
<p>If you have any device not listed in our database, we'll be glad to hear
(especially why are you changing an existing entry), please add a discussion comment.
<p>
-You may submit them on this site (for help see <a href='/?action=help?help=newitem'>this</a>) or
+You may submit them on this site (for help see <a href='/read/?action=help?help=newitem'>this</a>) or
send a patch to <a href='/pci.ids'>pci.ids</a> file to address <a href='mailto:pci-ids@ucw.cz'>pci-ids@ucw.cz</a>.
-See <a href='/?action=help?help=mailsubmit'>mail submit help</a>.
+See <a href='/read/?action=help?help=mailsubmit'>mail submit help</a>.
</body></html>
projects / pciids.git / commitdiff