* Add to Electronic Cats organization

* Add CatSat Zero

* match the directory name of the org file

* Information correct of Meow Meow

* Add BAB2 PID for CatWAN USB-Stick

* add citizen

- add new TomKeddie org
- add pid 8051 entry

* Add to Electronic Cats organization

* Add CatSat Zero

* match the directory name of the org file

* Information correct of Meow Meow

* Add BAB2 PID for CatWAN USB-Stick

* Escornabot Makech

* Added PD Buddy organization and PID 9DB5

1209:9DB5 - PD Buddy Sink

* Update information for PD Buddy

New URLs and an updated description.

…velopment) (#422)

Add device: 2019

* PID request for dme

* PID request for dme

* org: add foosn

Foosn is an independent spinoff of Kosagi, run by Sean "xobs" Cross.

Signed-off-by: Sean Cross <sean@xobs.io>

* 1209: 5bf0: add fomu

Fomu is an ICE40UP5k FPGA that fits in your USB port.

Signed-off-by: Sean Cross <sean@xobs.io>

* Create index.md

* Create index.md

* 2010 PID request for OpenLink-V1 CMSIS-DAP project

Created PID 7102 for Mini SAM M0 Boards.

* Created PID 7102

Created PID 7102 for Mini SAM M0 Boards.

* Update to Clarify and Cleanup

Updated the title and the site link as well as the source to better reflect PID 2017 is for a Mini SAM M4 board.

* Update with additional info.

Updated Site link and added additional information about my org (me).

* Added Robotics-Masters and the MM1 Hat with it's different software options

* Fixed repository URL after rename

* Remove unused Board PID

* License change, additional PID, certifications

- We changed our licensing from GPLv3 to dual Apache-2.0/MIT
- We would like to apply for a new PID CC1D, for use in an
  smartcard product that is in development
- Added links to our OSHWA certifications

* Retract additional PID application

* Create index.md

* Create index.md

* new org e3w2q and new pid for SU120

* Update index.md

* create organization

* Create VID:1209/PID:CB01

* Create VID:1209/PID:CB02

* Modified "owner" name

* Modified "owner" name

* add new pid

* Update index.md

* Update index.md

* Update project url

* Added Inverse Path and the USB armory

* change Inverse Path PID to reflect allowed policy

* PID request - Kameleon Core 0x7600

* Update index.md for PID 0x7600
Adding FW source code, HW schematic and API doc link

* Created organization entry

* Added product entry

* Requesting PID 0xDF11 for Signet

A USB password manager by Nth Dimension

* Fixing owner name for Signet

* Use a Single source URL for Signet

… spaces (#451)

* Request for 0x1209/0x0BEE VID/PID pair

* Changed PID request to 0x1209/0xBEE5 VID/PID pair

…rom 1955 after reviewer request) (#448)

* Added UNG Software's The GRUB Switch as VID 1209, PID 1955

* Added UNGsoftware's The GRUB Switch as VID 1209, PID 1955 (fixed)

* Changed requested GRUB switch PID from 1955 to 2015

* Added denhac org with 2 of our space projects

* Fixing range of reserved ids

* Created organization entry

* Created product entry

* Organization added

* PIDs for bootloader and firmware

* Update index.md

* Update index.md

* Update index.md

* Update index.md

* Update index.md

* Update index.md

* Update index.md

* Update index.md

* Update index.md

* Update index.md

* Project Gemini is a board aimed to make easier to implement constant speed motor controlling.

* Fix site

* Update Keyboardio org to add a site: key

* Add pid codes for the Atreus 2 Keyboard

# <type>[optional scope]: <description>
# 
# [optional body]
# 
# [optional footer]
# 
# The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.
# 
# 1. Commits MUST be prefixed with a type, which consists of a noun, feat, fix, etc., followed by a colon and a space.
# 
# 2. The type feat MUST be used when a commit adds a new feature to your application or library.
# 
# 3. The type fix MUST be used when a commit represents a bug fix for your application.
# 
# 4. An optional scope MAY be provided after a type. A scope is a phrase describing a section of the codebase enclosed in parenthesis, e.g., fix(parser):
# 
# 5. A description MUST immediately follow the type/scope prefix. The description is a short description of the code changes, e.g., fix: array parsing issue when multiple spaces were contained in string.
# 
# 6. A longer commit body MAY be provided after the short description, providing additional contextual information about the code changes. The body MUST begin one blank line after the description.
# 
# 7. A footer MAY be provided one blank line after the body (or after the description if body is missing). The footer SHOULD contain additional issue references about the code changes (such as the issues it fixes, e.g.,Fixes #13).
# 
# 8. Breaking changes MUST be indicated at the very beginning of the footer or body section of a commit. A breaking change MUST consist of the uppercase text BREAKING CHANGE, followed by a colon and a space.
# 
# 9. A description MUST be provided after the BREAKING CHANGE:, describing what has changed about the API, e.g., BREAKING # CHANGE: environment variables now take precedence over config files.
# 
# 10. The footer MUST only contain BREAKING CHANGE, external links, issue references, and other meta-information.
# 
# 11. Types other than feat and fix MAY be used in your commit messages.

* Request to add Etherkit Empyrean Alpha/Beta

* Add indication of bootloader PIDs on Empyrean