Skip to content
This repository has been archived by the owner on Oct 20, 2023. It is now read-only.

Add serial connection Flow control for Intel's UartSub devices in Windows #2

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

iderzhav
Copy link

In order to initiate serial connection with Intel's UartSub Devices:
ACPI\INT3511 and ACPI\INT3512 following DCB struct fields should be set:
fDtrControl = DTR_CONTROL_DISABLE
fRtsControl = RTS_CONTROL_DISABLE

Added "Disable DTR/RTS" option to Flow control list box of serial
connection settings which add desired functionality to putty.exe

Signed-off-by: Igor Derzhavets [email protected]

…onnection settings in Windows

In order to initiate serial connection with Intel's UartSub Devices:
ACPI\INT3511 and ACPI\INT3512 following DCB struct fields should be set:
fDtrControl = DTR_CONTROL_DISABLE
fRtsControl = RTS_CONTROL_DISABLE

Added "Disable DTR/RTS" option to Flow control list box of serial
connection settings which add desired functionality to putty.exe

Signed-off-by: Igor Derzhavets <[email protected]>
@pavelkryukov
Copy link
Contributor

pavelkryukov commented Mar 23, 2018

Hi Igor @iderzhav

You are submitting request to GitHub mirror of PuTTY repository. I'm not sure if it is monitored by PuTTY's maintainer Simon Tatham, so I advise to approach him directly (e-mail: putty at projects.tartarus.org)

@iderzhav
Copy link
Author

@iderzhav If you can just give it a 'no objections from me', I'll try talking about it to the author over email.

thanks

Hello,
no objections from me!
BR,
iderzhav

rtsp pushed a commit to rtsp7/putty that referenced this pull request Sep 7, 2021
When do_paint breaks up a line of terminal text into contiguous runs
of characters to treat the same, one of the criteria it uses is, 'Does
this character even need redrawing? (or is it already displayed
correctly from the previous redraw?)' When we encounter a character
that matches its previous value, we end the previous run of
characters, so that we can skip the one we've just encountered.

That check was not taking account of the 'truecolour' field of the
termchar it was checking. So it would sometimes falsely believe the
character to be equivalent to its previously drawn value, even when in
fact it was not, and hence insert a run break, anticipating that the
previous character needed drawing and the current one did not.

This didn't cause a _wrong_ redraw, because there's a separate loop
further on which re-checks whether to actually draw things, which
didn't make the same error. So the character that loop github#1 thought
didn't need a redraw, loop github#2 knew _did_ need a redraw, and hence,
everything did get redrawn.

But by the time loop github#2 is running, it's too late to change the run
boundaries. So everything does get redrawn, but in much smaller chunks
than it could have been. The net effect was that if the screen was
filled with text displayed in true colour, and you changed it to the
_same_ text in a different colour, then the whole terminal would be
redrawn in one-character increments instead of the usual behaviour of
folding together runs that can be drawn in one go.

Thanks to Bradley Smith for debugging this very confusing issue!
rtsp pushed a commit to rtsp7/putty that referenced this pull request Dec 28, 2021
Now, we always try an initial CONNECT request with no auth at all, and
wait for the proxy to reject it before sending a second try with
auth.

That way, we can wait to see what _kind_ of authentication the proxy
requests, which will enable us to support something more secure than
Basic, such as HTTP Digest.

(I mean, it would _work_ to try Basic in request github#1 and then retrying
with Digest in github#2 when the proxy asks for it. But if the aim of using
Digest is to avoid sending the password in cleartext, it defeats the
entire purpose to have sent it in cleartext anyway by the time you
realise the server is prepared to do something better!)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants