From: Aaron Brice <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 897d4c: btattach: Update for glibc 2.42 compatibility
Date: Thu, 03 Sep 2026 16:13:30 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1157441/000000-897d4c@github.com> (raw)
Branch: refs/heads/1157441
Home: https://github.com/bluez/bluez
Commit: 897d4c2f6221c1bc284a8a57ea06085a4d85d088
https://github.com/bluez/bluez/commit/897d4c2f6221c1bc284a8a57ea06085a4d85d088
Author: Aaron Brice <aaron@embeddedts.com>
Date: 2026-09-03 (Thu, 03 Sep 2026)
Changed paths:
M tools/btattach.c
Log Message:
-----------
btattach: Update for glibc 2.42 compatibility
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.
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-09-03 23:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/1157441/000000-897d4c@github.com \
--to=noreply@github.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