Virtual serial is not documented

[iFreilicht]

We have a virtual serial port available since 2016 (#677), and the stenography features are using it, yet it doesn't seem to be documented anywhere and only one keymap is using the virtser_recv for receiving commands from the PC, something that seems to be asked about every now and then.

It seems it's as easy as adding VIRTSER_ENABLE = yes to rules.mk, a line that is not present in any example file, and then defining virtser_recv in your keymap.c.

If I got the structure of the docs right, this new page should go into the "Software Features" section.

[drashna]

Yup to just about all of that. The send/receive stuff should work very much like how the raw HID does. So a lot of the code should be convertible.

[stale]

This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed in the next 30 days unless it is tagged properly or other activity occurs.
For maintainers: Please label with bug, in progress, on hold, discussion or to do to prevent the issue from being re-flagged.

[stapelberg]

@Stale: this issue is still relevant

[iFreilicht]

I'll have a go at this in two months, until then I'm hard pressed for time. 22 Aug 2020 20:25:45 Michael Stapelberg <notifications@github.com>:

…

@Stale[https://github.com/Stale]: this issue is still relevant — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub[#9131 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ACKKSK3O3PDJ25ETCDWYYY3SCAESPANCNFSM4NEI7ZNQ]. [https://github.com/notifications/beacon/ACKKSK2LD7LDGRMZ4JESLELSCAESPA5CNFSM4NEI7ZN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFBZ4FPY.gif]

[stale]

This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed in the next 30 days unless it is tagged properly or other activity occurs.
For maintainers: Please label with bug, in progress, on hold, discussion or to do to prevent the issue from being re-flagged.

[stapelberg]

@Stale: this issue is still relevant

[stale]

This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed in the next 30 days unless it is tagged properly or other activity occurs.
For maintainers: Please label with bug, in progress, on hold, discussion or to do to prevent the issue from being re-flagged.

[stapelberg]

@Stale: this issue is still relevant

[stale]

This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed in the next 30 days unless it is tagged properly or other activity occurs.
For maintainers: Please label with bug, in progress, on hold, discussion or to do to prevent the issue from being re-flagged.

[danshick]

@Stale This issue is still relevant.

[zvecr]

This issue has been automatically closed because it has not had any recent activity.
If this issue is still valid, re-open the issue and let us know.

[iFreilicht]

@zvecr This issue is not fixed yet and it is still active. The missing documentation has not been written.

[keyboard-magpie]

I'll have a go at this in two months, until then I'm hard pressed for time. 22 Aug 2020 20:25:45 Michael Stapelberg notifications@github.com:
…
@Stale[https://github.com/Stale]: this issue is still relevant — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub[#9131 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ACKKSK3O3PDJ25ETCDWYYY3SCAESPANCNFSM4NEI7ZNQ]. [https://github.com/notifications/beacon/ACKKSK2LD7LDGRMZ4JESLELSCAESPA5CNFSM4NEI7ZN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFBZ4FPY.gif]

If it's not happened in 2 years, is it going to happen at all? Issues shouldn't remain open indefinitely and this was closed as part of a cleanup.

[PeterHindes]

I'll see if I can figure out how it works. No promises though.