From: Aaron Brice <aaron@embeddedts.com>
To: linux-bluetooth@vger.kernel.org
Cc: Aaron Brice <aaron@embeddedts.com>
Subject: [PATCH BlueZ 0/1] btattach: Update for glibc 2.42 compatability
Date: Thu, 3 Sep 2026 11:27:08 -0700 [thread overview]
Message-ID: <20260903182709.473976-1-aaron@embeddedts.com> (raw)
btattach is not setting the baud rate correctly on systems with newer
glibc such as Ubuntu 26.04. In glibc 2.42 the baud rate termios.h
constants changed value, B115200 was 0x1002 which was the struct
termios c_cflag enum bits, but in 2.42 they changed cfsetspeed() to
accept arbitrary rates and not just the baud enum values, and B115200
was changed to the value 115200. This means you can no longer set the
speed with c_cflag |= B115200 and should use cfsetspeed() to be
compatible with both versions.
Aaron Brice (1):
btattach: Update for glibc 2.42 compatability
tools/btattach.c | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
--
2.53.0
next reply other threads:[~2026-09-03 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 18:27 Aaron Brice [this message]
2026-09-03 18:27 ` [PATCH BlueZ 1/1] btattach: Update for glibc 2.42 compatability Aaron Brice
2026-09-03 21:24 ` Bastien Nocera
2026-09-03 21:25 ` Bastien Nocera
2026-09-03 21:49 ` bluez.test.bot
2026-09-04 20:20 ` [PATCH BlueZ 0/1] " patchwork-bot+bluetooth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260903182709.473976-1-aaron@embeddedts.com \
--to=aaron@embeddedts.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox