linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 217663] Bluetooth GPS modules profile unavailable
Date: Wed, 12 Jul 2023 06:54:06 +0000	[thread overview]
Message-ID: <bug-217663-62941-FXlfelPH6k@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217663-62941@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=217663

--- Comment #1 from Dice Wasser (dicetrash@gmail.com) ---
As seen in
https://btprodspecificationrefs.blob.core.windows.net/assigned-numbers/Assigned%20Number%20Types/Assigned_Numbers.pdf#3.3.3
bluetooth assigned numbers it is part of 3.3 SDP Service Class and Profile
Identifiers
See Bluetooth Core Specification [Vol 3] Part B, Section 5.1.2
as a serial port,

I would expect that connecting to it would create a /dev/tty serial port

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

      reply	other threads:[~2023-07-12  6:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-12  6:29 [Bug 217663] New: Bluetooth GPS modules profile unavailable bugzilla-daemon
2023-07-12  6:54 ` bugzilla-daemon [this message]

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=bug-217663-62941-FXlfelPH6k@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).