All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Keith Packard <keithp@keithp.com>
Cc: Gustavo Padovan <gustavo@padovan.org>,
	linux-kernel@vger.kernel.org, linux-bluetooth@vger.kernel.org,
	Johan Hedberg <johan.hedberg@intel.com>
Subject: Re: [PATCH] Revert "Bluetooth: Always enable management interface"
Date: Thu, 29 Mar 2012 05:33:42 +0200	[thread overview]
Message-ID: <1332992022.1870.183.camel@aeonflux> (raw)
In-Reply-To: <86r4wct9q7.fsf@sumi.keithp.com>

Hi Keith,

> > A consequence is that you'll need to use newer version of bluez, at least 4.99.
> > Or call the bluetooth daemon (from a pre 4.99 version) with a parameter to
> > disable the new interface:
> 
> That's not OK -- you're breaking user space with this kernel change. I
> know I get bashed every time I suggest that we 'fix' the kernel and
> require new user space X bits...

I think we actually have a broken user space in this case. I do have a
hunch on what went wrong. It is not the kernel's fault here.

If I am anywhere right, then bluetoothd fails to bring up the device.
That is why you don't see anything with "hcitool dev", but the device
should be present. Check "hciconfig -a".

Check your bluetoothd startup line and add "-P mgmtops". That will
disable the broken plugin.

Regards

Marcel



  reply	other threads:[~2012-03-29  3:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-29  1:19 [PATCH] Revert "Bluetooth: Always enable management interface" Keith Packard
2012-03-29  1:25 ` David Miller
2012-03-29  2:25 ` Marcel Holtmann
2012-03-29  2:28 ` Gustavo Padovan
2012-03-29  2:35   ` Keith Packard
2012-03-29  3:33     ` Marcel Holtmann [this message]
2012-03-29  4:39       ` David Miller
2012-03-29  4:40     ` David Miller
2012-03-30  6:54     ` Gustavo Padovan
2012-04-03 12:29       ` Gustavo Padovan
2012-04-05 22:24       ` Keith Packard
2012-04-06  1:01         ` Gustavo Padovan
2012-03-29  3:48   ` Keith Packard
2012-03-29  4:40   ` David Miller

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=1332992022.1870.183.camel@aeonflux \
    --to=marcel@holtmann.org \
    --cc=gustavo@padovan.org \
    --cc=johan.hedberg@intel.com \
    --cc=keithp@keithp.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@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.