All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pauli Virtanen <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] b793ab: bthost: fragment when sending ISO packets
Date: Wed, 23 Jul 2025 11:50:02 -0700	[thread overview]
Message-ID: <bluez/bluez/push/refs/heads/985227/000000-765a05@github.com> (raw)

  Branch: refs/heads/985227
  Home:   https://github.com/bluez/bluez
  Commit: b793abf0afa527c148557f6a962102afbdd20a0d
      https://github.com/bluez/bluez/commit/b793abf0afa527c148557f6a962102afbdd20a0d
  Author: Pauli Virtanen <pav@iki.fi>
  Date:   2025-07-23 (Wed, 23 Jul 2025)

  Changed paths:
    M emulator/bthost.c
    M emulator/bthost.h
    M emulator/hciemu.c

  Log Message:
  -----------
  bthost: fragment when sending ISO packets

Support fragmentation to controller MTU when sending ISO packets.
By default, fragment when exceeding btdev iso_mtu.


  Commit: 765a05f8b639e076949908e5ca8e3919b56d8bb3
      https://github.com/bluez/bluez/commit/765a05f8b639e076949908e5ca8e3919b56d8bb3
  Author: Pauli Virtanen <pav@iki.fi>
  Date:   2025-07-23 (Wed, 23 Jul 2025)

  Changed paths:
    M tools/iso-tester.c
    M tools/tester.h

  Log Message:
  -----------
  iso-tester: add tests for hardware RX timestamps

Add tests for HW RX timestamping.  Also add test that sends large
packets to test ISO fragmentation.

Add tests:

ISO Receive - HW Timestamping
ISO Receive Fragmented - Success
ISO Receive Fragmented - HW Timestamping


Compare: https://github.com/bluez/bluez/compare/b793abf0afa5%5E...765a05f8b639

To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications

                 reply	other threads:[~2025-07-23 18:50 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/985227/000000-765a05@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.