Pi-KVM organization and IDs

[mdevaev]

Hi! Pi-KVM is a project to create an open source KVM-over-IP based on Raspberry Pi. All software is distributed under the GPLv3 license, the basic schematic technology is also open.

I'm asking you to allocate two identifiers for different USB emulation devices. They will be used to make it easier for system administrators to distinguish them from generic Arduino and other OTG devices.

https://github.com/pikvm/pikvm

[tannewt]

Where are the hardware files for the V3 HAT?

[mdevaev]

V3 hat is a commerical hardware which uses open source software. This is a separate project.

I'm not asking for a PID for V3, but specifically only for software for V0 and V2 that people already use in their DIY KVM. Schemes V0 and V2 are open. For example. That is, V3 is not needed to use this project. Isn't enough? There is no closed software in it and I do not force people to buy V3.

Thousands of people use their homemade Pi-KVM V0 and V2, and I ask for an PID for their convenience.

[tannewt]

Ok. Please do not use this PID for images meant for the closed, commercial V3 hardware. These PIDs are for open hardware projects only.

[mdevaev]

@tannewt Thanks, but the last thing I want to do is break your rules :) I really can't use this even if the v3 firmware is completely open and the codes are part of it, and not flashed on hardware? Firmware v2 and v3 have no differences on the part of the software and differ only in a couple of lines in the configuration files.

[tannewt]

The goal of pid.codes is to promote open hardware by granting PIDs. You should open source your hardware if you want to use a pid.codes PID on it. If you don't want to because of commercial reasons, then you should be willing to pay for a commercial PID. It's another cost of doing business. Most microcontroller manufacturers will sublicense you one (some for free.)

[mdevaev]

Got it.