Re: [PATCH RFC] Bluetooth: Add generic support for vendor HCI frames
Luiz Augusto von Dentz <[email protected]>
| Newsgroups | org.kernel.vger.linux-bluetooth,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <CABBYNZJn2VvcNZq4xE2XS8ZZ5auVPTwB4W7q_Xpr9eNUALsfGw@mail.gmail.com> |
Hi Zijun, On Tue, Jul 21, 2026 at 3:40 PM Zijun Hu <[email protected]> wrote: > > On 7/21/2026 10:22 PM, Luiz Augusto von Dentz wrote: > >> Could you please give me a clear direction > >> Solution A or is_vendor()? > > There might be a simpler approach, just consider anything other then > > the known packets a vendor packet, so it is automatically stamped with > > HCI_VENDOR_PKT then push it back to driver from processing. > > For this simpler approach: > in TX, userspace send data to kernel by 0x31[inidicator] .... > > in RX, how does kernel send data to userspace > by 0xff, 0x34(indicator).... > OR 0x34(indicator) without 0xff ? For the user channel I would say it would be better to always include 0xff. That way, it remains agnostic and it won't suddenly match a different packet type if you change the vendor or something like that. -- Luiz Augusto von Dentz