[Keyboard] Add MIIIW BlackIO98

[ArthurCyy]

Description

Add MIIIW BlackIO98. This is another version of BlackIO83.

Types of Changes

• [ ] Core
• [ ] Bugfix
• [ ] New feature
• [ ] Enhancement/optimization
• [x] Keyboard (addition or update)
• [x] Keymap/layout/userspace (addition or update)
• [ ] Documentation

Issues Fixed or Closed by This PR

Checklist

• [x] My code follows the code style of this project: C, Python
• [ ] I have read the PR Checklist document and have made the appropriate changes.
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [x] I have read the CONTRIBUTING document.
• [ ] I have added tests to cover my changes.
• [x] I have tested the changes and verified that they work and don't break anything (as well as I can manage).

[lokher]

The keyboard advertises bluetooth and wireless support, but code seems doesn't .

[ArthurCyy]

The keyboard advertises bluetooth and wireless support, but code seems doesn't .

https://github.com/qmk/qmk_firmware/issues/18485

[tzarc]

The keyboard advertises bluetooth and wireless support, but code seems doesn't .

#18485

#18485 says that Wireless builds including QMK are bound by GPL. It does not say "you are free to release open-source code without wireless", especially if you're still using QMK internally.

Providing sources to everything except Wireless when using QMK does not comply with GPL, and as such the manufacturer is in breach of QMK's licensing. Providing full sources including Wireless bindings is required.

---

TL;DR:

• Did you use QMK to build and distribute a wired keyboard? Manufacturer must provide entire source code.
• Did you use QMK to build and distribute a wireless keyboard? Manufacturer must provide entire source code.
• Did you use any portion of QMK to build and distribute any kind of keyboard? Manufacturer must provide entire source code.

The last point includes things such as taking and modifying via.c and hosting it in another keyboard firmware.

[ArthurCyy]

The keyboard advertises bluetooth and wireless support, but code seems doesn't .

#18485

#18485 says that Wireless builds including QMK are bound by GPL. It does not say "you are free to release open-source code without wireless", especially if you're still using QMK internally.

Providing sources to everything except Wireless when using QMK does not comply with GPL, and as such the manufacturer is in breach of QMK's licensing. Providing full sources including Wireless bindings is required.

TL;DR:

• Did you use QMK to build and distribute a wired keyboard? Manufacturer must provide entire source code.
• Did you use QMK to build and distribute a wireless keyboard? Manufacturer must provide entire source code.
• Did you use any portion of QMK to build and distribute any kind of keyboard? Manufacturer must provide entire source code.

The last point includes things such as taking and modifying and hosting it in another keyboard firmware.via.c

1. I am just a user of this keyboard, not the manufacturer.
2. It seems that the wireless function of this keyboard is controlled by another main control chip and firmware (not QMK), and a physical switch on the keyboard can be flipped to switch it to wireless mode and access another firmware. I also found some information from the official firmware updater given for the wireless function, the wireless solution provider is SY Tech. Co., Ltd.
3. Since I am not the manufacturer of this keyboard and do not have access to the source code for the wireless part, I can do nothing about the wireless part, but can only make sure that the wired part works properly. If this does not meet your requirements, I will close this PR, and I'm sorry for causing you any trouble.

[github-actions[bot]]

Thank you for your contribution! This pull request has been automatically marked as stale because it has not had activity in the last 45 days. It will be closed in 30 days if no further activity occurs. Please feel free to give a status update now, or re-open when it's ready. For maintainers: Please label with bug, awaiting review, breaking_change, in progress, or on hold to prevent the issue from being re-flagged.