public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] AmbiCom BT2000C works with hciattach
Date: Wed, 23 Jun 2004 09:14:15 -0700	[thread overview]
Message-ID: <20040623161414.GA9129@atomide.com> (raw)
In-Reply-To: <1087976062.4209.61.camel@pegasus>

* Marcel Holtmann <marcel@holtmann.org> [040623 00:34]:
> Hi Tony,
> 
> > Just FYI, there was some discussion here a while back on the 
> > AmbiCom BT2000C, which is different from the earlier BT2000 
> > models.
> > 
> > Well turns out it works fine with serial_cs + hciattach:
> > 
> > hciattach /dev/ttyS1 csr -s 57600 57600
> > or
> > hciattach /dev/ttyS1 csr -s 57600 460800
> > hciconfig hci0 up
> > hcitool scan
> > ...
> > 
> > Sorry if this was already old news :) Please CC me on any 
> > replies, I'm not subscribing.
> 
> how good these news are actually depends on what kernel you are using ;)

Using 2.6.7.

> Send me the output of "dump_cis" and I will add a line to hciattach for
> that. What is "hciconfig -a" saying?

Here you are:

# dump_cis
Socket 0:
  dev_info
    no_info
  vers_1 7.1, "AmbiCom BT2000C", "Bluetooth PC/CF Card", "", ""
  manfid 0x022d, 0x2000
  funcid serial_port
  serial_interface
    uart 16550 [space/mark/odd/even] [5/6/7/8] [1/1.5/2]
  config base 0x00f8 mask 0x000f last_index 0x03
  cftable_entry 0x01 [default]
    [rdybsy] [audio] [pwrdown]
    Vcc Vnom 3300mV Vmin 3V Vmax 3600mV Iavg 300mA
    Ipeak 300mA Idown 10mA
    io 0x02f8-0x02ff [lines=3] [8bit] [range]
    irq mask 0x86bc [level] [pulse] [shared]
  cftable_entry 0x02
    io 0x03e8-0x03ef [lines=3] [8bit] [range]
  cftable_entry 0x03
    io 0x02e8-0x02ef [lines=3] [8bit] [range]
# hciattach /dev/ttyS1 csr -s 57600 460800
CSR build ID 0x02-0x0D
# hciconfig hci0 up
# hciconfig -a
hci0:   Type: UART
        BD Address: 00:10:xx:xx:xx:xx ACL MTU: 192:8  SCO MTU: 64:8
        UP RUNNING PSCAN ISCAN 
        RX bytes:79 acl:0 sco:0 events:8 errors:0
        TX bytes:39 acl:0 sco:0 commands:8 errors:0
        Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
        Link policy: 
        Link mode: SLAVE ACCEPT 
        Name: 'tony laptop (0)'
        Class: 0x000000
        Service Classes: Unspecified
        Device Class: Miscellaneous, 
        HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP
	Subver: 0x20d
        Manufacturer: Cambridge Silicon Radio (10)

  reply	other threads:[~2004-06-23 16:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-23  3:11 [Bluez-devel] AmbiCom BT2000C works with hciattach Tony Lindgren
2004-06-23  7:34 ` Marcel Holtmann
2004-06-23 16:14   ` Tony Lindgren [this message]
2004-06-23 16:26     ` Marcel Holtmann
2004-06-23 16:45       ` Tony Lindgren

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=20040623161414.GA9129@atomide.com \
    --to=tony@atomide.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --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