Linux bluetooth development
 help / color / mirror / Atom feed
From: John McCorquodale <mcq@cacr.caltech.edu>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: John McCorquodale <mcq@cacr.caltech.edu>,
	BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Socket G card newbie Q
Date: Sun, 7 Mar 2004 16:21:00 -0800	[thread overview]
Message-ID: <20040308002100.GA19049@viz.cacr.caltech.edu> (raw)
In-Reply-To: <1078704901.15279.6.camel@pegasus>

Marcel> you should use "hciattach ttyS0 bcsp 230400", because the Socket card
Marcel> uses the BCSP transport protocol.

The other day you said:

Marcel> The Socket 2.5 generation (also know as revision G) is a CSR based
Marcel> serial Bluetooth card. Look at the archives for more details.

And the list seems to indicate that the F card is BCSP and the G card is CSR.
That said, using bcsp yields:

  $ hciattach ttyS0 bcsp 230400
  BCSP initialization timed out

Am I mistaken about the F/G distinction?  Am I correct in using the normal
serial_cs driver in the PCMCIA cardmgr?  Is there something I can run directly
at the serial port that will give me a more verbose dialog than "initialization
timed out", which might indicate some level of partial success?  Could it
be that there's a new G card series out there -- these are brand spankin' new
cards?

Cheers, and thanks,

-mcq

  reply	other threads:[~2004-03-08  0:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-07 21:42 [Bluez-users] Socket G card newbie Q John McCorquodale
2004-03-08  0:15 ` Marcel Holtmann
2004-03-08  0:21   ` John McCorquodale [this message]
2004-03-08  0:26     ` Marcel Holtmann
2004-03-08  0:48       ` John McCorquodale
2004-03-08  1:00         ` Marcel Holtmann
2004-03-08  1:11           ` John McCorquodale

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=20040308002100.GA19049@viz.cacr.caltech.edu \
    --to=mcq@cacr.caltech.edu \
    --cc=bluez-users@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