adding jabberwocky v2 keyboard

[lukeski14]

Description

Adding jabberwocky v2 .json
Reorganizing /jabberwocky/ directory, since v1 already is ported to via

QMK Pull Request

qmk/qmk_firmware#19014

Update to productId PR open here: qmk/qmk_firmware#19611

Checklist

• The VIA support for this keyboard is in QMK master already (MANDATORY)
• The VIA definition follows the guide here: https://caniusevia.com/docs/layouts
• I have tested this keyboard definition using VIA's "Design" tab.
• I have tested this keyboard definition with firmware on a device.
• I have assigned alpha keys and modifier keys with the correct colors.
• The Vendor ID is not 0xFEED

[lukeski14]

Should probably change product ids. Going to address this

[lukeski14]

Updated productId QMK PR here: qmk/qmk_firmware#19611

[yiancar]

please ping once the merge of qmk has been done.

[lukeski14]

@yiancar QMK PR merged

[yiancar]

Hello you have added V1 and V2 here. they both have the same PID/VID, this is not allowed. I presume there is a different firmware in V1 and V2?
Also if the JSON are the same you can just add one...

[lukeski14]

The firmware for v1 and v2 is different. I explicitly changed the pid for v2 so now each version has a unique pid. This is the change merged in the most recent QMK PR.

[yiancar]

Ok I see, however in the V1 and V2 JSONS on this PR, both have

"vendorId": "0x4E50",
 "productId": "0x4A58",

[lukeski14]

In this PR, I added v1 and v2 folders.

These are the productIds for each version as seen in this PR:
v1 productId: "0x4A57"
v2 productId: "0x4A58"

From what I can see, the v1 and v2 productIds are correct. The v1 json already existed so the only change in this PR is a file path change for v1. v2 has the new productId, different from v1.

[yiancar]

sorry I am blind.... I couldnt see the right diff....

cheers and thanks for clarifying