public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Billionton bluetooth CF: how to make it work
Date: Sat, 14 May 2005 22:17:59 +0200	[thread overview]
Message-ID: <20050514201759.GA3598@elf.ucw.cz> (raw)
In-Reply-To: <1116071705.8886.15.camel@pegasus>

Hi!

> I have no idea what USB have to do with it and why you posted it to
> LKML, but it seems you got it.

Oops, that was typo, I meant "Billionton bluetooth CF". I posted lkml
so that it gets archived on easy-to-search place.

> > Okay, so the magic sequence seems to be:
> > 
> > # Take 2.6.12-rc3-mm3
> > #
> > # PCMCIA config:
> > # card "Cyber-blue Compact Flash Card"
> > #   manfid 0x0279, 0x950b
> > #   bind "serial_cs"
> > #
> > killall hciattach
> > sleep .1
> > setserial /dev/ttyS4 baud_base 921600
> > hciattach -s 921600 /dev/ttyS4 bcsp
> > hciconfig
> > hciconfig hci0 up
> > hciconfig
> 
> Verfied with my card and a 2.6.12-rc4.

Good. [Actually it does *not* work for me in -rc4, but it seems to be
pcmcia problem.]

> hci0:   Type: UART
>         BD Address: 00:10:60:xx:xx:xx ACL MTU: 192:8 SCO MTU: 64:8
>         HCI Ver: 1.1 (0x1) HCI Rev: 0x33c LMP Ver: 1.1 (0x1) LMP Subver: 0x33c
>         Manufacturer: Cambridge Silicon Radio (10)
>         Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
>                 <3-slot packets> <5-slot packets> <encryption> <slot offset> 
>                 <timing accuracy> <role switch> <hold mode> <sniff mode> 
>                 <park state> <RSSI> <channel quality> <SCO link> <HV2 packets> 
>                 <HV3 packets> <u-law log> <A-law log> <CVSD> <paging scheme> 
>                 <power control> <transparent SCO> 
>         HCI 16.14
>         Chip version: BlueCore02-External
>         Max key size: 56 bit
>         SCO mapping:  HCI
> 
> > It took me a hour trying to debug weird stuff before I realized that I
> > need to do hciconfig up... to see some results...
> 
> Or make sure that hcid is running. It will bring up your device.

Yes, I was just confused. I'm normally only starting hcid just before
talking to the phone, and I did not try it when I was BD address of
all zeros.
								Pavel
-- 
Boycott Kodak -- for their patent abuse against Java.

      reply	other threads:[~2005-05-14 20:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050512233902.GA3157@elf.ucw.cz>
     [not found] ` <1115942337.18499.86.camel@pegasus>
     [not found]   ` <20050513004606.GA1957@elf.ucw.cz>
     [not found]     ` <1115975517.18499.100.camel@pegasus>
     [not found]       ` <20050513101739.GI1780@elf.ucw.cz>
2005-05-14  0:10         ` Billionton bluetooth USB: how to make it work Pavel Machek
2005-05-14 11:55           ` Marcel Holtmann
2005-05-14 20:17             ` Pavel Machek [this message]

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=20050514201759.GA3598@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox