Hi, Peter:
You are right about BlueZ was not initilized. After I force define MODULE in af_bluetooth.c , creating bluetooth socket using hciconfig is OK. But command "hciconfig -a" still can't read the bluetooth USB dongle information.
thanks,
Al
-----------------------
#define MODULE //Al add
#ifdef MODULE
module_init(bluez_init);
module_exit(bluez_cleanup);
MODULE_AUTHOR("Maxim Krasnyansky <[email protected]>");
MODULE_DESCRIPTION("BlueZ Core ver " VERSION);
MODULE_LICENSE("GPL");
#endif
-----------------------
log:
========================================================
Linux version 2.4.20-uc0 (icc@AL30) (gcc version 3.0) #225 ?.. 8?.. 15 12:56:425Processor: Winbond W90N740 revision 1
Architecture: W90N740
On node 0 totalpages: 2048
zone(0): 0 pages.
zone(1): 2048 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/rom0
Calibrating delay loop... 39.83 BogoMIPS
Memory: 7MB = 7MB total
Memory: 5792KB available (987K code, 205K data, 48K init)
Dentry cache hash table entries: 1024 (order: 1, 8192 bytes)
Inode cache hash table entries: 512 (order: 0, 4096 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 2048 (order: 1, 8192 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
Winbond W90N740 Serial driver version 0.9 (2001-12-27) with no serial options edttyS00 at 0xfff80000 (irq = 6) is a W90N740
Blkmem copyright 1998,1999 D. Jeff Dionne
Blkmem copyright 1998 Kenneth Albanowski
Blkmem 1 disk images:
0: 700000-7CABFF [VIRTUAL 700000-7CABFF] (RO)
RAMDISK driver initialized: 16 RAM disks of 1024K size 1024 blocksize
loop: loaded (max 8 devices)
Regiter EMC 1 W90N740
Winbond NATA1 ver0.2
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
Linux video capture interface: v1.00
AM29LV160 Flash Detected
usb.c: registered new driver hub
add a static ohci host controller device
: USB OHCI at membase 0xfff05000, IRQ 9
hc_alloc_ohci
usb-ohci.c: AMD756 erratum 4 workaround
hc_reset
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
bluetooth.c: USB Bluetooth support registered
usb.c: registered new driver bluetty
bluetooth.c: USB Bluetooth tty driver v0.13
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 512 bind 1024)
ip_conntrack version 2.0 (56 buckets, 448 max) - 348 bytes per conntrack
In URL Filter conntrack init
ip_ct_http: registering helper for port 53
Spec conntrack init successfully ########
Register NAT spec successfully
ip_tables: (C) 2000-2002 Netfilter core team
BlueZ Core ver 2.2 Copyright (C) 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <[email protected]>
BlueZ L2CAP ver 2.1 Copyright (C) 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <[email protected]>
BlueZ SCO ver 0.3 Copyright (C) 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <[email protected]>
VFS: Mounted root (romfs filesystem) readonly.
Freeing init memory: 48K
Shell invoked to run file: /bin/init
Sash command shell (version 1.1.1)
/> new USB device :801e7a04-171d60
hub.c: new USB device 1, assigned address 2
bluetooth.c: USB Bluetooth converter detected
bluetooth.c: Bluetooth converter now attached to ttyUB0 (or usb/ttub/0 for devf)
/> hciconfig -a
/> hciconfig hci0 up
Can't get device info: No such device
pid 10: failed 256
/>
=========================================================
-----Original Message-----
From: [email protected] on behalf of Peter Wippich
Sent: Fri 8/12/2005 8:34 PM
To: [email protected]
Cc:
Subject: RE: [Bluez-devel] Porting BlueZ on embedded uClinux
Hi Al,
when I remember your original posting right the error message was
something like "protokoll family not registered...". This may be the case
when the BlueZ is not initialized. Do you get some start up message from
BlueZ when your system boots up ??
Ciao,
Peter
> You are right about BlueZ was not initilized. After I force define M=
ODULE in
> af_bluetooth.c , creating bluetooth socket using hciconfig is OK. But com=
mand "hciconfig
> -a" still can't read the bluetooth USB dongle information.
What about "hciconfig -a hci0"?
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel