All of lore.kernel.org
 help / color / mirror / Atom feed
From: Itzhak Ben-Akiva <benakiva@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] PCMCIA Bluetooth Card (AnyCom CF - 300) on ARM
Date: Tue, 27 Sep 2005 17:51:47 +0300	[thread overview]
Message-ID: <f6df51f0050927075118d4efe4@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 9068 bytes --]

Hi all,

May I request your help in solving a problem I have with pcmcia
bluetooth card?

I'm working on ARM Integrator/AP platform with Linux 2.6.13. And, I'm
using PCI Bus Card Drive: PCI-IF1/C (32Bit) and PCMCIA Bluetooth Card -
Anycom Blue CF - 300, which uses the driver bluecard_cs.

In my system the device is correctly detected to be usable with the
bluecard_cs driver. It then calls bluecard_attach(), which calls
pcmcia_register_client(). It then calls bluecard_event(), which calls
bluecard_config. bluecard_config, then, calls pcmcia_request_io, which
always returns REQUESTIO: resource in use.

However, cardctl and cardmgr report the card correctly:
~ # cardctl ident
Socket 0:
 product info: "BTCFCARD", "LSE139"
 manfid: 0x0264, 0x000b
 function: 6 (network)


Below is a syslog message:

Linux version 2.6.13-git2 (root@gilnx13-1) (gcc version 3.4.2 (release)
(CodeSourcery ARM Q3 2004)) #14 Mon Sep 26 12:35:25
CPU: ARM920Tid(wb) [41129200] revision 0 (ARMv4T)
Machine: ARM-Integrator
Warning: bad configuration page, trying to continue
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
CPU0: D cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
Built 1 zonelists
Kernel command line: console=ttyAM0,38400n8 mem=126M rw nohalt
root=/dev/nfs ip=10.0.0.11:10 <http://10.0.0.11:10>.0.0.2::::eth0:off
nfsroot=10.k
PID hash table entries: 512 (order: 9, 8192 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 126MB = 126MB total
Memory: 125056KB available (2027K code, 622K data, 96K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
PCI: bus0: Fast back to back transfers disabled
PCI: bus1: Fast back to back transfers enabled
PCI: Bridge: 0000:00:09.0
 IO window: disabled.
 MEM window: disabled.
 PREFETCH window: disabled.
PCI: Bus 2, cardbus bridge: 0000:00:0b.0
 IO window: 00006000-000060ff
 IO window: 00006400-000064ff
 PREFETCH window: 10000000-11ffffff
 MEM window: 00000000-01ffffff
NetWinder Floating Point Emulator V0.97 (double precision)
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Initializing Cryptographic API
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
Serial: AMBA driver $Revision: 1.41 $
ttyAM0 at MMIO 0x16000000 (irq = 1) is a AMBA
ttyAM1 at MMIO 0x17000000 (irq = 2) is a AMBA
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
loop: loaded (max 8 devices)
eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://www.scyld.com/network/eepro100.html
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin
<saw@saw.sw.com.sg> and others
eth0: 0000:00:0a.0, 00:0E:0C:6C:3A:1E, IRQ 14.
 Board assembly 751767-007, Physical connectors present: RJ45
 Primary interface chip i82555 PHY #1.
 Secondary interface chip i82555.
 General self-test: passed.
 Serial sub-system self-test: passed.
 Internal registers self-test: passed.
 ROM checksum self-test: passed (0x3258698e).
PPP generic driver version 2.4.2
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
IP-Config: Guessing netmask 255.0.0.0 <http://255.0.0.0>
IP-Config: Complete:
 device=eth0, addr=10.0.0.11 <http://10.0.0.11>,
mask=255.0.0.0<http://255.0.0.0>,
gw=255.255.255.255 <http://255.255.255.255>,
 host=10.0.0.11 <http://10.0.0.11>, domain=, nis-domain=(none),
 bootserver=10.0.0.2 <http://10.0.0.2>, rootserver=10.0.0.2<http://10.0.0.2>,
rootpath=
Looking up port of RPC 100003/2 on 10.0.0.2 <http://10.0.0.2>
Looking up port of RPC 100005/1 on 10.0.0.2 <http://10.0.0.2>
VFS: Mounted root (nfs filesystem).
yenta_socket: Unknown symbol pccard_nonstatic_ops
PCI: enabling device 0000:00:0b.0 (0140 -> 0143)
Yenta: CardBus bridge found at 0000:00:0b.0 [0000:0000]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:0b.0, mfunc 0x00001c02, devctl 0x62
Yenta: ISA IRQ mask 0x0000, PCI irq 15
Socket status: 30000010
pcmcia: parent PCI bridge Memory window: 0x40000000 - 0x4fffffff
pcmcia: parent PCI bridge Memory window: 0x50000000 - 0x5fffffff
cs: memory probe 0x40000000-0x4fffffff: excluding 0x40000000-0x427fffff
cs: memory probe 0x50000000-0x5fffffff: excluding 0x50000000-0x5fffffff
Bluetooth: Core ver 2.7
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.7
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM ver 1.5
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: HIDP (Human Interface Emulation) ver 1.1-mh1
bluecard_config is about to be called in bluecard_event
pcmcia_resource: pcmcia_socket0: odd IO request: base 0x300 align 0x40
pcmcia_resource: pcmcia_socket0: odd IO request: base 0x340 align 0x40
pcmcia_resource: pcmcia_socket0: odd IO request: base 0x380 align 0x40
pcmcia_resource: pcmcia_socket0: odd IO request: base 0x3c0 align 0x40
pcmcia_resource: pcmcia_socket0: odd IO request: base 0x200 align 0x40
pcmcia_resource: pcmcia_socket0: odd IO request: base 0x240 align 0x40
pcmcia_resource: pcmcia_socket0: odd IO request: base 0x280 align 0x40
pcmcia_resource: pcmcia_socket0: odd IO request: base 0x2c0 align 0x40
pcmcia_resource: pcmcia_socket0: odd IO request: base 0x100 align 0x40
pcmcia_resource: pcmcia_socket0: odd IO request: base 0x140 align 0x40
pcmcia_resource: pcmcia_socket0: odd IO request: base 0x180 align 0x40
pcmcia_resource: pcmcia_socket0: odd IO request: base 0x1c0 align 0x40
pcmcia_resource: pcmcia_socket0: odd IO request: base 0x40 align 0x40
pcmcia_resource: pcmcia_socket0: odd IO request: base 0x80 align 0x40
pcmcia_resource: pcmcia_socket0: odd IO request: base 0xc0 align 0x40
BT_DEBUG: pcmcia_request_io failed in bluecard_config
0.0: RequestIO: Resource in use
Uninitialised timer!
This is just a warning. Your computer is OK
function=0x00000000, data=0x0
[<c0025c84>] (dump_stack+0x0/0x14) from [<c003f598>] (check_timer_failed
+0x4c/0x6c)
[<c003f54c>] (check_timer_failed+0x0/0x6c) from [<c003f6fc>] (del_timer
+0x28/0x80)
 r4 = C79CFC88
[<c003f6d4>] (del_timer+0x0/0x80) from [<bf047da4>] (bluecard_release
+0x2c/0x64 [bluecard_cs])
 r5 = C79CFBE0 r4 = C79CFBE0
[<bf047d78>] (bluecard_release+0x0/0x64 [bluecard_cs]) from [<bf048478>]
(bluecard_event+0x4ec/0x5b4 [bluecard_cs])
 r5 = C79CFBE0 r4 = C79CFBE0
[<bf047f8c>] (bluecard_event+0x0/0x5b4 [bluecard_cs]) from [<bf0153b0>]
(pcmcia_register_client+0x1f4/0x224 [pcmcia])
[<bf0151bc>] (pcmcia_register_client+0x0/0x224 [pcmcia]) from
[<bf047f30>] (bluecard_attach+0xb8/0x114 [bluecard_cs])
[<bf047e78>] (bluecard_attach+0x0/0x114 [bluecard_cs]) from [<bf01431c>]
(pcmcia_device_probe+0x80/0x108 [pcmcia])
 r7 = 00000000 r6 = C7DA423C r5 = C7DA4200 r4 = BF04999C
[<bf01429c>] (pcmcia_device_probe+0x0/0x108 [pcmcia]) from [<c01473c4>]
(driver_probe_device+0x5c/0xa8)
 r7 = BF0499B0 r6 = BF0499B0 r5 = 00000000 r4 = C7DA423C
[<c0147368>] (driver_probe_device+0x0/0xa8) from [<c0147508>]
(__driver_attach+0x4c/0x78)
 r6 = C01474BC r5 = C7C25DBC r4 = C7DA42E4
[<c01474bc>] (__driver_attach+0x0/0x78) from [<c0146ae4>]
(bus_for_each_dev+0x50/0x84)
 r4 = 00000000
[<c0146a94>] (bus_for_each_dev+0x0/0x84) from [<c0147554>]
(driver_attach+0x20/0x28)
 r7 = BF01BB9C r6 = BF049944 r5 = BF0499B0 r4 = BF0499C4
[<c0147534>] (driver_attach+0x0/0x28) from [<c0146f58>] (bus_add_driver
+0x6c/0x138)
[<c0146eec>] (bus_add_driver+0x0/0x138) from [<c014790c>]
(driver_register+0x34/0x38)
[<c01478d8>] (driver_register+0x0/0x38) from [<bf0141d8>]
(pcmcia_register_driver+0xf8/0x114 [pcmcia])
 r4 = BF04999C
[<bf0140e0>] (pcmcia_register_driver+0x0/0x114 [pcmcia]) from
[<bf04b014>] (init_bluecard_cs+0x14/0x1c [bluecard_cs])
 r7 = C02218D0 r6 = BF049A60 r5 = BF049A60 r4 = C02218E0
[<bf04b000>] (init_bluecard_cs+0x0/0x1c [bluecard_cs]) from [<c0051a74>]
(sys_init_module+0x155c/0x16bc)
[<c0050518>] (sys_init_module+0x0/0x16bc) from [<c0020d00>]
(ret_fast_syscall+0x0/0x2c)


Many thanks in advance,
Itzhak

[-- Attachment #2: Type: text/html, Size: 12845 bytes --]

                 reply	other threads:[~2005-09-27 14:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=f6df51f0050927075118d4efe4@mail.gmail.com \
    --to=benakiva@gmail.com \
    --cc=bluez-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.