| 01:12.33 | *** join/#openmoko Wuzzy (~Wuzzy@p5B0DFD74.dip0.t-ipconnect.de) |
| 01:35.08 | *** join/#openmoko Wuzzy (~Wuzzy@p5B0DFCD2.dip0.t-ipconnect.de) |
| 07:01.09 | *** join/#openmoko Q-Master^Work (~q-master@78-106-182-103.broadband.corbina.ru) |
| 08:35.53 | *** join/#openmoko geaaru (~geaaru@host170-152-static.43-88-b.business.telecomitalia.it) |
| 11:11.42 | *** join/#openmoko yokel (~yokel@unaffiliated/contempt) |
| 11:54.37 | *** join/#openmoko amarsh04 (~amarsh04@ppp121-45-33-160.bras2.adl4.internode.on.net) |
| 16:19.38 | *** join/#openmoko Wuzzy (~Wuzzy@p5B0DFCD2.dip0.t-ipconnect.de) |
| 18:27.28 | *** join/#openmoko skullY (zwhite@darkstar.frop.org) |
| 19:14.21 | *** join/#openmoko jackhumbert (b8124f24@gateway/web/freenode/ip.184.18.79.36) |
| 19:15.57 | skullY | hello, a group of us are working on a keyboard firmware <https://github.com/qmk/qmk_firmware> and so far our vid/pid's have basically been made up (a legacy of the codebase we originally forked.) Given how much our usage has grown it seems like we need to get a better handle on our vid/pid usage. We currently have a little over 100 supported keyboards, with varrying degrees of involvement from the pcb manufacturers. |
| 19:16.03 | skullY | Our concern with sharing a single vid/pid among all QMK devices is that it's tricky to locate the right device in (EG) lsusb when you have several connected. Additionally, windows has a habit of caching enumerated endpoints based on vid/pid, and our firmware lets users turn on or off several possible endpoints (keyboard, mouse, midi, serial, etc.) |
| 19:16.20 | skullY | Is assigning a block of VID's in a situation like this something openmoko is open to? In either case, do you have any advice for us on how best to manage this situation? |
| 19:19.30 | skullY | sorry, s/VID's/PID's/ |
| 19:19.39 | skullY | (not sure how I missed that :) |
| 19:40.17 | PaulFertser | skullY: I think a block is good in this case |
| 19:40.29 | PaulFertser | skullY: such as one was assigned to Rockbox. |
| 19:45.56 | skullY | how would you recommend we divide it up? that could affect how large a block we need |
| 19:47.04 | skullY | if we assign a unique pid per device that's easiest, but that's also basically reserving 8 bits for this. I don't know how ok that would be |
| 19:49.54 | PaulFertser | skullY: well, rockbox got 8 bits |
| 19:50.45 | skullY | seems like a reasonable place to start then :) |
| 19:51.46 | skullY | I assume from here sending email per http://wiki.openmoko.org/wiki/USB_Product_IDs#Conditions is the next best step? |
| 19:53.15 | PaulFertser | skullY: yes |
| 19:53.55 | skullY | awesome, we'll get that put together. thanks for the feedback! |
| 19:55.29 | skullY | as an aside from whoever runs chanserv here, your welcome message has a link to http://freenode.net/faq.shtml#nicksetup which 404's now, the new link is http://freenode.net/kb/answer/registration#nickname-setup |
| 19:55.36 | skullY | s/from/for/ |
| 20:13.01 | PaulFertser | skullY: thanks! |
| 21:45.56 | *** join/#openmoko Rjs- (~user@kekkonen.niksula.hut.fi) |