All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 73081] Fail to setup Bluetooth on Dell Venue 11 Pro
Date: Mon, 03 Aug 2015 20:06:03 +0000	[thread overview]
Message-ID: <bug-73081-62941-uxaG34jEzk@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-73081-62941@https.bugzilla.kernel.org/>

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

Dmitry Khromov <icechrome@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |icechrome@gmail.com

--- Comment #1 from Dmitry Khromov <icechrome@gmail.com> ---
Same here, on Venue 8 Pro.
Actually, the protocol Windows is using is H4, nevertheless, it doesn't work
also.
This snippet from DSDT table (BTH0 entry, DLAC3002) specifies the UART settings
that Windows (supposedly) uses:
UartSerialBus (0x0001C200, DataBitsEight, StopBitsOne, 0xC0, LittleEndian,
ParityTypeNone, FlowControlHardware, 0x0020, 0x0020, "\\_SB.URT1", 0x00,
ResourceConsumer, ,)
URT1 is /dev/ttyS4 in my config, the interesting thing is that there's no bytes
inbound at all - looks like the BT module is simply unpowered, no matter if I
attach an rfkill-gpio (like Jin above), or drive GPIOs manually (via
/sys/bus/gpio).
So, it's unlikely a kernel bug (and may be closed as such).

Jin. had you ever succeed in getting this piece working?

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

       reply	other threads:[~2015-08-03 20:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-73081-62941@https.bugzilla.kernel.org/>
2015-08-03 20:06 ` bugzilla-daemon [this message]
2016-01-30 15:41 ` [Bug 73081] Fail to setup Bluetooth on Dell Venue 11 Pro bugzilla-daemon
2016-01-30 15:42 ` 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-uxaG34jEzk@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.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 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.