Messages in this thread | | | From | Gottfried Haider <> | Date | Mon, 18 Apr 2011 09:34:24 +0200 | Subject | Re: [Regression] Bluetooth pairing does not work anymore in 2.6.39-rc3 (works in 2.6.38.3) |
| |
>> I checked: I have this commit in -rc3, so it must be something else here. > hmm... seems to be working over here with the latest Mainline. one thing I > have notice though is the daemon is not starting during boot(systemd), > manually starting bluetoothd gets me to connect.(system is fedora 15).
It was my fault after all:
I had based my kernel config on 2.6.39-rc2 from Ubuntu's mainline-kernel PPA, and this doesn't have BT_L2CAP..
Case closed.
I am just wondering: is it possible to make BT_L2CAP (and SCO?) default to yes when BT is compiled in or build as a module?
From commit 6427451: "The L2CAP layer is needed by almost all Bluetooth protocols and profiles. There isn't any real use case without having L2CAP loaded." Yet when I am doing oldconfig from a config that had L2CAP build as a module, I am getting these easily overlooked lines:
L2CAP protocol support (BT_L2CAP) [N/y/?] (NEW) SCO links support (BT_SCO) [N/y/?] (NEW)
cheers, gohai -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |