Linux bluetooth development
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 73081] Fail to setup Bluetooth on Dell Venue 11 Pro
Date: Sat, 13 Jun 2026 03:24:14 +0000	[thread overview]
Message-ID: <bug-73081-62941-snespIpojX@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-73081-62941@https.bugzilla.kernel.org/>

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

--- Comment #7 from Dmitry Khromov (icechrome@gmail.com) ---
If memory serves, the MMIO-mapped UART requires
CONFIG_SERIAL_DEV_CTRL_TTYPORT=y for a port to be picked up by BlueZ. This, in
turn, requires CONFIG_SERIAL_DEV_BUS=y, but most desktop distros ship a kernel
with CONFIG_SERIAL_DEV_BUS=m.

Long story short, I was successful in bringing Bluetooth up and running on
Venue 8 Pro back in the day, so try compiling a kernel with the configuration
flags mentioned. No further action should be required -- BlueZ should
automatically pick the port up and attach the HCI.

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

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

  parent reply	other threads:[~2026-06-13  3:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-73081-62941@https.bugzilla.kernel.org/>
2015-08-03 20:06 ` [Bug 73081] Fail to setup Bluetooth on Dell Venue 11 Pro bugzilla-daemon
2016-01-30 15:41 ` bugzilla-daemon
2016-01-30 15:42 ` bugzilla-daemon
2026-06-12 12:16 ` bugzilla-daemon
2026-06-12 13:56 ` bugzilla-daemon
2026-06-12 21:34 ` bugzilla-daemon
2026-06-13  3:24 ` bugzilla-daemon [this message]
2026-06-13  6:32 ` bugzilla-daemon
2026-06-13  6:57 ` bugzilla-daemon

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-73081-62941-snespIpojX@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