Debian Bug report logs - #860910
screen: support baudrate of 1500000

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: screen: support baudrate of 1500000

Date: Fri, 21 Apr 2017 11:18:17 -0700

[Message part 1 (text/plain, inline)]

Package: screen
Version: 4.5.0-5
Severity: wishlist

When I run:

  screen /dev/ttyUSB2 1500000

All I get is gibberish on the screen.


I'm able to access the same device with cu:

  cu --line=/dev/ttyUSB2 --baud=1500000

And I get expected serial output, so I know the tty device works at
that speed.


Highest speed listed in the source tty.sh (which produces tty.c) is
460800, but it's unclear to me if it also dynamically determines
appropriate values for baud rates somehow...


live well,
  vagrant


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing'), (120, 'unstable'), (1, 'experimental')
Architecture: amd64
 (x86_64)
Foreign Architectures: armhf

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages screen depends on:
ii  libc6      2.24-9
ii  libpam0g   1.1.8-3.5
ii  libtinfo5  6.0+20161126-1

screen recommends no packages.

Versions of packages screen suggests:
pn  byobu | screenie | iselect  <none>
ii  ncurses-term                6.0+20161126-1

-- no debconf information

[signature.asc (application/pgp-signature, inline)]

Message #10 received at 860910@bugs.debian.org (full text, mbox, reply):

From: Axel Beckert <abe@debian.org>

To: Vagrant Cascadian <vagrant@debian.org>, 860910@bugs.debian.org

Subject: Re: Bug#860910: screen: support baudrate of 1500000

Date: Fri, 21 Apr 2017 22:38:54 +0200

Control: tag -1 + moreinfo upstream

Hi Vagrant,

Vagrant Cascadian wrote:
> Highest speed listed in the source tty.sh (which produces tty.c) is
> 460800, but it's unclear to me if it also dynamically determines
> appropriate values for baud rates somehow...

I currently assume that screen doesn't do that. But I'm not sure
either.

Is 1500000 a common baudrate? It doesn't seem to be a multiple of one
of the common baudrates as I would expect.

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Message #17 received at 860910@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@debian.org>

To: Axel Beckert <abe@debian.org>, 860910@bugs.debian.org

Subject: Re: Bug#860910: screen: support baudrate of 1500000

Date: Fri, 21 Apr 2017 14:05:07 -0700

[Message part 1 (text/plain, inline)]

Thanks for the quick response!

On 2017-04-21, Axel Beckert wrote:
> Vagrant Cascadian wrote:
>> Highest speed listed in the source tty.sh (which produces tty.c) is
>> 460800, but it's unclear to me if it also dynamically determines
>> appropriate values for baud rates somehow...
>
> I currently assume that screen doesn't do that. But I'm not sure
> either.

At the very least, it could fail and issue an error with unsupported
baud rates, rather than silently transmitting and recieving garbled
data...


> Is 1500000 a common baudrate? It doesn't seem to be a multiple of one
> of the common baudrates as I would expect.


I don't know how common it is, but I've encountered it with the
firefly-rk3399:

  http://wiki.t-firefly.com/index.php/Firefly-RK3399/Serial_debug/en

There are two boards in the linux-next tree which use it:

  arch/arm/boot/dts/rk1108-evb.dts:               stdout-path = "serial2:1500000n8";
  arch/arm64/boot/dts/rockchip/rk3328-evb.dts:            stdout-path = "serial2:1500000n8";


live well,
  vagrant

[signature.asc (application/pgp-signature, inline)]

Message #22 received at 860910@bugs.debian.org (full text, mbox, reply):

From: Axel Beckert <abe@debian.org>

To: Vagrant Cascadian <vagrant@debian.org>

Cc: 860910@bugs.debian.org

Subject: Re: Bug#860910: screen: support baudrate of 1500000

Date: Fri, 21 Apr 2017 23:33:20 +0200

Control: tag -1 - moreinfo
Control: clone -1 -2
Control: forwarded -1 https://savannah.gnu.org/bugs/?func=detailitem&item_id=45741
Control: retitle -2 screen: Should error out on unsupported baud rates instead of showing garbled data
Control: severity -2 normal

Hi Vagrant,

Vagrant Cascadian wrote:
> > I currently assume that screen doesn't do that. But I'm not sure
> > either.
> 
> At the very least, it could fail and issue an error with unsupported
> baud rates, rather than silently transmitting and recieving garbled
> data...

Granted. But that should probably be a separate bug request. Will file
a separate bug report upstream once I know the number of the cloned
bug report.

> I don't know how common it is, but I've encountered it with the
> firefly-rk3399:

Thanks for the details!

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Message #37 received at 860910-close@bugs.debian.org (full text, mbox, reply):

From: Axel Beckert <abe@debian.org>

To: 860910-close@bugs.debian.org

Subject: Bug#860910: fixed in screen 4.6.0-1

Date: Wed, 28 Jun 2017 22:36:05 +0000

Source: screen
Source-Version: 4.6.0-1

We believe that the bug you reported is fixed in the latest version of
screen, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 860910@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Axel Beckert <abe@debian.org> (supplier of updated screen package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 29 Jun 2017 00:10:57 +0200
Source: screen
Binary: screen screen-udeb
Architecture: source amd64
Version: 4.6.0-1
Distribution: experimental
Urgency: low
Maintainer: Axel Beckert <abe@debian.org>
Changed-By: Axel Beckert <abe@debian.org>
Description:
 screen     - terminal multiplexer with VT100/ANSI terminal emulation
 screen-udeb - terminal multiplexer with VT100/ANSI terminal emulation - udeb (udeb)
Closes: 846396 860910
Changes:
 screen (4.6.0-1) experimental; urgency=low
 .
   * New upstream release.
     + Supports many more baud rates, including 1500000. (Closes: #860910)
     + Updates Unicode wide tables to 9.0. (Closes: #846396)
     + Drop 62-fix-texinfo-syntax-error.patch, fixed differently.
     + Drop 64-fix-garbage-on-serial-terminal.patch, applied upstream.
     + Refresh patches where necessary.
   * Retroactively mention #355942 in 4.5.1-1's changelog entry.
   * Add patch to fix spelling errors found by lintian.
Checksums-Sha1:
 35626e2d376ec8db6585a6d993d5e497356248ab 2125 screen_4.6.0-1.dsc
 a707be2abae99e6df521746f39952a669c53e53e 849062 screen_4.6.0.orig.tar.gz
 917027f74357980d09b88181d2345685b63fa8de 45108 screen_4.6.0-1.debian.tar.xz
 6b7f4f38980b80379b3772bf13087ca19b2e5fea 462014 screen-dbgsym_4.6.0-1_amd64.deb
 3827b233d656e9f6402aefabefe4e8496707eade 392750 screen-udeb_4.6.0-1_amd64.udeb
 26baac957153c02f814bb0f4faa5dd198c697322 6339 screen_4.6.0-1_amd64.buildinfo
 63034cf570fb9105d74b963c8e31dc781d5ed73e 592200 screen_4.6.0-1_amd64.deb
Checksums-Sha256:
 f64e97ebaffdfc1a2cd0b832f0d81e125d6b6ffbfafdfc5f4750e79a299d90a1 2125 screen_4.6.0-1.dsc
 9433706b653e941cc4c745f28e252e57be2a141eded923e61cc2c4a09768fed4 849062 screen_4.6.0.orig.tar.gz
 315017e2f1aafe972d79f1688a0ac3e33daa153a379e97829eb2b4135d83dd12 45108 screen_4.6.0-1.debian.tar.xz
 384c9b705e2cc301c8c00ae9aa21a23ff33b51a4f6692d08c402ff702f36f4bb 462014 screen-dbgsym_4.6.0-1_amd64.deb
 8c43ebe07e77473a1132e746a3af3c6951f5443dfef34ab8297e683d9cf545b1 392750 screen-udeb_4.6.0-1_amd64.udeb
 7c1d42385d0cc23431222b1c3769450b47f9a9c88d6498c87c7da23d03063451 6339 screen_4.6.0-1_amd64.buildinfo
 fc7de76c59f5bd6089c376ba82c019df6807f1c3366ce4f9a1038c89c5604da9 592200 screen_4.6.0-1_amd64.deb
Files:
 d8a015358f2e2546651d665d4293e912 2125 misc standard screen_4.6.0-1.dsc
 af60f716c4ec134712b923ef6cd93848 849062 misc standard screen_4.6.0.orig.tar.gz
 cfdf40d00e51dd79623e8275ae46a8a1 45108 misc standard screen_4.6.0-1.debian.tar.xz
 01546592f573732021673048f7534be8 462014 debug extra screen-dbgsym_4.6.0-1_amd64.deb
 eebfa31c804cf3ebf108532f1e8f64fb 392750 debian-installer extra screen-udeb_4.6.0-1_amd64.udeb
 d8c64119e6b49eabc022b4b7fa441095 6339 misc standard screen_4.6.0-1_amd64.buildinfo
 7e17a23d151a3e002343124b7b1dc2dc 592200 misc standard screen_4.6.0-1_amd64.deb

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEERoyJeTtCmBnp12Ema+Zjx1o1yXUFAllUKd4ACgkQa+Zjx1o1
yXWM9A/+IIrkD3tLZVvbNfZSwewEhkqOaTbHLYvcivDIamqrcVvoLjrOLt/7JCTO
rHXTrX5b+CrRTZ6yzdLVyFBZa2/Uv9MEuZx2vNXAzlVsaCmtYuSnIteOnYLd6riI
CeZgXigAbZ+EsksAXac9T/qkGarijByI/QyqKstyYH4x7AjpX51ipmSbtd1ognzJ
c93arVKneQeWG1kKMrWzfAY/2//1l8XrqR3M5AGBugjkdkhkpsq/4BoT1naNnguD
nV+gIG55Lg2znKCdEd9yGy9HO445wfpWt9Wkbm4oGC2kcWlPtc+hww/mx2Oo2mjb
ppeGNMp6c+ASJ0VgMT+YV81SJfcUW+Ed49pmmPNlAGBV6cVCBFXaqAhUlK21aqdA
U671q7ELoto1v60VWu/zu8QPEhqln+eOpEddiZDne1Jqp62YTUhvqjgBHaSkeTN2
UcqItUNQpzUMImXxqMC1QsO7s3EhL6LxqPt4+q0/U2gPaewWgXPaiJsoKS1Y22cY
JD2Oe98MvPXNj/Mtalen529oL8ENchye0H4NzAl/DNxEr2viNZ5rT7tjXUxLvWjb
qxr0GMDzBhdX23CuOVuxqsCGJeSneN723gks61g41w9VnnzoHpqfkzHbVhg+fC0Y
6UcBRTdhlC1Z1+3zONDxWL5oZEDgUO/ZBTJ5ZbI9e3MnQII98pA=
=PHVr
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.