From: digger vermont <dv_mlist@verizon.net>
To: bluez-users <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] Config for Socket CF card
Date: Mon, 19 Jan 2004 21:37:08 -0500 [thread overview]
Message-ID: <1074566227.3670.24.camel@myrna> (raw)
Hello All,
I give up. Its time to look for help. After too much time I discovered
that I was trying to use the wrong module (dtl1_cs) and for all the
threads in the mailing list archives I haven't been able to figure it
out. Also keep in mind that anything I've done are wild guesses due to
desperation :)
Here's the card I have:
-------------------------------------------
product info: "Socket", "CF+ Personal Network Card Rev 2.5"
manfid: 0x0104, 0x0096
function: 2 (serial)
-----------------------------------------
I believe that means I have the infamous revision G.
My laptop is a powerbook G4. The kernel is 2.6.1-ben1 using devfs.
Cardmgr seems to starting correctly. Pcmcia had no config for this card
or for the hci_uart so I added an entry to /etc/pcmcia/config.opts. I
also changed the port and memory settings for the powerbook. Is this
correct?
----------------------------------
device "hci_uart"
class "bluetooth" module "hci_uart"
card "Socket Bluetooth Card"
version "Socket", "CF+ Personal Network Card Rev 2.5"
manfid 0x0104, 0x0096
bind "hci_uart"
include port 0x100-0x4ff, port 0x800-0x8ff, port 0xc00-0xcff
include memory 0x80080000-0x8008ffff
-------------------------------------
When I insert the card this is what I get in the log:
----------------------------------------------------
Jan 19 21:24:34 [cardmgr] initializing socket 0
Jan 19 21:24:34 [cardmgr] socket 0: Socket Bluetooth Card
Jan 19 21:24:34 [cardmgr] product info: "Socket", "CF+ Personal Network
Card Rev 2.5"
Jan 19 21:24:34 [cardmgr] manfid: 0x0104, 0x0096 function: 2 (serial)
Jan 19 21:24:34 [cardmgr] executing: 'modprobe hci_uart'
Jan 19 21:24:34 [kernel] Bluetooth: HCI UART driver ver 2.1
Jan 19 21:24:34 [kernel] Bluetooth: HCI H4 protocol initialized
Jan 19 21:24:34 [cardmgr] bind 'hci_uart' to socket 0 failed: Invalid
argument
------------------------------------------------------------
Any help, or directions to where I can find it, would be greatly
appreciated.
Thanks,
digger
-------------------------------------------------------
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
next reply other threads:[~2004-01-20 2:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 2:37 digger vermont [this message]
2004-01-20 11:22 ` [Bluez-users] Config for Socket CF card Marcel Holtmann
2004-01-21 15:12 ` digger vermont
2004-01-21 15:22 ` Marcel Holtmann
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=1074566227.3670.24.camel@myrna \
--to=dv_mlist@verizon.net \
--cc=bluez-users@lists.sourceforge.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