On 04/18/2011 12:34 AM, Gottfried Haider wrote:
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.
thats alright...(your human!!!)
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?
tweaking the kconfig can do this.
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
Justin P. Mattock
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
