Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: digger vermont <dv_mlist@verizon.net>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [Bluez-users] Config for Socket CF card
Date: Wed, 21 Jan 2004 16:22:25 +0100	[thread overview]
Message-ID: <1074698544.7088.102.camel@pegasus> (raw)
In-Reply-To: <1074697933.3020.19.camel@myrna>

Hi Digger,

> Ahh, then I'm back to square one.  Before I added the configuration to
> config.opts  cardmgr was  trying to start serial_cs and I was getting
> the error:
> 
> Jan 19 16:14:50 [cardmgr] + WARNING: Error inserting 8250
> (/lib/modules/2.6.1-ben1/kernel/drivers/serial/8250.ko): Device or
> resource busy
> 
> I didn't understand it was because the internal serial ports were using
> ttyS0 and ttyS1. With the ports disabled the card is now starting. 
> 
> Should cardmgr, serial_cs.ko, or 8250.ko been able to see that the ports
> were already used?  (The powerbook uses pmaczilog.ko) If not where can
> that be configured.  Also, a config definition for the card doesn't seem
> to be needed.  Should I put one in config.opts?

I don't have any experiences with Apple machines. Ask Benjamin
Herrenschmidt about this specific problem.

> Forward to step two.
> 
> > After that you can use "hciattach <dev> socket" to init the Bluetooth
> > chip on this card.
> 
> running "hciattach /dev/tts/0 socket" I get:
> 
> BCSP initialization timed out
> 
> I built and tried a 2.4.24 kernel and the command works fine.   I would
> prefer to stay with the 2.6 kernel.  I there anything I can try? If its
> of any help there's lofiles, etc below.

My Com1 card uses also BCSP and I will try it later with 2.6.2-rc1.
Please check again with this kernel, too.

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-01-21 15:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-20  2:37 [Bluez-users] Config for Socket CF card digger vermont
2004-01-20 11:22 ` Marcel Holtmann
2004-01-21 15:12   ` digger vermont
2004-01-21 15:22     ` Marcel Holtmann [this message]
2004-01-21 21:29       ` Benjamin Herrenschmidt
2004-01-22  5:34       ` digger vermont
2004-01-22 10:16         ` Marcel Holtmann
2004-01-22 12:50         ` Marcel Holtmann
2004-01-22 23:38           ` digger vermont
2004-01-23  0:11             ` Marcel Holtmann
2004-01-23  0:44               ` Max Krasnyansky
2004-01-23  0:58                 ` Marcel Holtmann
2004-01-23  1:12                   ` Benjamin Herrenschmidt
2004-01-23  1:26                     ` Marcel Holtmann
2004-01-23  4:32                   ` digger vermont
2004-01-23 13:41                     ` Marcel Holtmann

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=1074698544.7088.102.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=benh@kernel.crashing.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=dv_mlist@verizon.net \
    /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