[Coco] Coco to PC cable

[John W. Linville]

On Thu, Mar 12, 2009 at 12:03:41AM -0400, Gene Heskett wrote:
> On Wednesday 11 March 2009, John W. Linville wrote:
> >On Wed, Mar 11, 2009 at 06:50:41PM -0400, Gene Heskett wrote:
> >> On Wednesday 11 March 2009, John W. Linville wrote:
> >> >On Wed, Mar 11, 2009 at 03:42:43PM -0400, Gene Heskett wrote:
> >> >> On a secondary note, the usb bluetooth keys have arrived, and I'm a bit
> >> >> confused as the kernel doesn't seem to recognize the makers code &
> >> >> doesn't load the right drivers for it.
> >> >
> >> >Doh!  That sucks...  What is the USB ID?
> >>
> >> Bus 002 Device 005: ID 0e5e:6622
> >>
> >> >John
> >>
> >> Thanks John, specially if you can figure an alias. :)
> >
> >It looks like the btusb driver claims support for that.
> 
> I enabled that for the last build too.
> 
> >It is
> >selected by CONFIG_BT_HCIBTUSB, which is turned-on by default in
> >Fedora kernels.  This is the newer HCI USB Bluetooth driver, which
> >supercedes the older hci_usb driver (selected by CONFIG_BT_HCIUSB).
> >
> >Are you using a stock Fedora kernel?  If not, make sure you are using
> >CONFIG_BT_HCIBTUSB (and not CONFIG_BT_HCIUSB) in your .config file.
> >
> >Hth!
> >
> A step in the right direction I believe.
> 
> >John
> 
> >From the 2.6.29-rc7/.config
> [root at coyote linux-2.6.29-rc7]# grep CONFIG_BT_HCIBTUSB .config
> CONFIG_BT_HCIBTUSB=m
> 
> In fact:
> [root at coyote linux-2.6.29-rc7]# grep CONFIG_BT .config
> CONFIG_BT=m
> CONFIG_BT_L2CAP=m
> CONFIG_BT_SCO=m
> CONFIG_BT_RFCOMM=m
> CONFIG_BT_RFCOMM_TTY=y
> CONFIG_BT_BNEP=m
> CONFIG_BT_BNEP_MC_FILTER=y
> CONFIG_BT_BNEP_PROTO_FILTER=y
> CONFIG_BT_HIDP=m
> CONFIG_BT_HCIBTUSB=m
> CONFIG_BT_HCIBTSDIO=m
> CONFIG_BT_HCIUART=m
> CONFIG_BT_HCIUART_H4=y
> CONFIG_BT_HCIUART_BCSP=y
> CONFIG_BT_HCIUART_LL=y
> CONFIG_BT_HCIBCM203X=m
> CONFIG_BT_HCIBPA10X=m
> CONFIG_BT_HCIBFUSB=m
> CONFIG_BT_HCIVHCI=m
> # CONFIG_BTRFS_FS is not set
> 
> Humm, looks like I missed one.  Or did I, is it even related
> to bluetooth stuffs?  Sounds like one of those specialty filesystems.

BTRFS is a new filesystem, hoping to eventually replace EXT4.

> And on the reboot, it did create 2 more /dev/hidraw (1 & 2) devices, but no
> /dev/hci* are to be found.  Am I looking for the wrong device?

You should be running hciconfig, looking for output similar to this:

hci0:	Type: USB
	BD Address: 00:1F:3A:32:45:71 ACL MTU: 1021:8 SCO MTU: 64:1
	UP RUNNING PSCAN 
	RX bytes:966 acl:0 sco:0 events:62 errors:0
	TX bytes:3390 acl:0 sco:0 commands:62 errors:0

FWIW, my device seems to disappear with 2.6.29-rc7-wl, but I can see
it when running the stock F10 kernel, 2.6.27.19-170.2.35.fc10.x86_64.
Perhaps it has been broken upstream, or perhaps my 2.6.29-rc7-wl config
is lacking some magic, dunno.  In any case, I'd advise you to try to
get things working with a stock Fedora kernel and then proceed from
there. :-)

Hth!

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville at tuxdriver.com			might be all we have.  Be ready.