[Bluez-devel] Porting BlueZ on embedded uClinux

[Bluez-devel] Porting BlueZ on embedded uClinux

[Al]

Hi, there:

     I'm trying to port BlueZ on embedded linux. The followings are
what I've done so far:

=3D=3D=3D=3D=3D=3D=3D=3D For Kernel part =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The embedded linux cannot load modules so I need to make BlueZ as part =
of kernel itself.

1. Change Makefile in linux/drivers/bluetooth
                                                                         =
                                                                      =
-------------------------------------
O_TARGET        :=3D bluetooth.o
                                                                         =
                                                                      =
list-multi      :=3D hci_uart.o
                                                                         =
                                                                      =
obj-y +=3D hci_usb.o
obj-y +=3D hci_vhci.o
                                                                         =
                                                                      =
obj-y +=3D hci_uart.o
uart-y :=3D hci_ldisc.o
uart-y +=3D hci_h4.o
                                                                         =
                                                                      =
obj-y +=3D dtl1_cs.o
obj-y +=3D bt3c_cs.o
obj-y +=3D bluecard_cs.o
                                                                         =
                                                                      =
include $(TOPDIR)/Rules.make
                                                                         =
                                                                      =
hci_uart.o: $(uart-y)
        $(LD) -r -o $@ $(uart-y)
--------------------------------------
2. Add line below in Makefile in linux/drivers
    subdir-y +=3D bluetooth

3. Change Makefile in /linux/net/bluetooth
--------------------------------------------
O_TARGET :=3D bluetooth.o
                                                                         =
      =20
obj-y    :=3D af_bluetooth.o hci_core.o hci_sock.o lib.o syms.o =
hci_conn.o hci_event.o l2cap.o sco.o
                                                                         =
                                                                         =
             =20
include $(TOPDIR)/Rules.make
------------------------------------------

4. Add lines Makefile in linux/net
    subdir-y +=3D bluetooth
    obj-y +=3D bluetooth/bluetooth.o

=3D=3D=3D=3D=3D=3D=3D=3D=3D For User Space (Utility) =
part=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Use embedded compilier to make  "hciconfig" and copy it to embedded =
romdisk.

A CSR USB dongle is used. When I boot up the device and execute
hciconfig.

It prints errors when trying to create bluetooth socket:

"Can't open HCI socket.: Address family not supported by protocol"

if ((ctl =3D socket(AF_BLUETOOTH, SOCK_RAW, BTPROTO_HCI)) < 0)=20
{=09
		perror("Can't open HCI socket.");
		exit(1);
}

It seems like BlueZ is not integrated into kernel, but the object files =
in linux/drivers/bluetooth and linux/net/bluetooth are created without =
errors.

Does anyone have previous experience to port BlueZ on embeded linux and =
not using as modules?
Any advice/comment is appriciated.

Thanks for the helps.

Al









-------------------------------------------------------
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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Porting BlueZ on embedded uClinux

[Peter Wippich]

Hi AL,

first question : what kernel version you are using ??

Second: why you change the Makefile ??? Simply do a make menuconfig or
what ever you prefer and configure that Bluetooth is compiled build in and
not as a module.

Make sure you have basic networking support enabled for your kernel.

I can't see that you compiled in the bluetooth USB driver. So this is
required when you use a USB adapter. But you don't need the *_cs drivers.

Why do you think an embedded system can't support modules ????

Ciao,

Peter


On Fri, 12 Aug 2005, Al wrote:

> Hi, there:
>
>      I'm trying to port BlueZ on embedded linux. The followings are
> what I've done so far:
>
> ======== For Kernel part =============
>
> The embedded linux cannot load modules so I need to make BlueZ as part of kernel itself.
>
> 1. Change Makefile in linux/drivers/bluetooth
>                                                                                                                                                -------------------------------------
> O_TARGET        := bluetooth.o
>                                                                                                                                                list-multi      := hci_uart.o
>                                                                                                                                                obj-y += hci_usb.o
> obj-y += hci_vhci.o
>                                                                                                                                                obj-y += hci_uart.o
> uart-y := hci_ldisc.o
> uart-y += hci_h4.o
>                                                                                                                                                obj-y += dtl1_cs.o
> obj-y += bt3c_cs.o
> obj-y += bluecard_cs.o
>                                                                                                                                                include $(TOPDIR)/Rules.make
>                                                                                                                                                hci_uart.o: $(uart-y)
>         $(LD) -r -o $@ $(uart-y)
> --------------------------------------
> 2. Add line below in Makefile in linux/drivers
>     subdir-y += bluetooth
>
> 3. Change Makefile in /linux/net/bluetooth
> --------------------------------------------
> O_TARGET := bluetooth.o
>
> obj-y    := af_bluetooth.o hci_core.o hci_sock.o lib.o syms.o hci_conn.o hci_event.o l2cap.o sco.o
>
> include $(TOPDIR)/Rules.make
> ------------------------------------------
>
> 4. Add lines Makefile in linux/net
>     subdir-y += bluetooth
>     obj-y += bluetooth/bluetooth.o
>
> ========= For User Space (Utility) part===========
> Use embedded compilier to make  "hciconfig" and copy it to embedded romdisk.
>
> A CSR USB dongle is used. When I boot up the device and execute
> hciconfig.
>
> It prints errors when trying to create bluetooth socket:
>
> "Can't open HCI socket.: Address family not supported by protocol"
>
> if ((ctl = socket(AF_BLUETOOTH, SOCK_RAW, BTPROTO_HCI)) < 0)
> {
> 		perror("Can't open HCI socket.");
> 		exit(1);
> }
>
> It seems like BlueZ is not integrated into kernel, but the object files in linux/drivers/bluetooth and linux/net/bluetooth are created without errors.
>
> Does anyone have previous experience to port BlueZ on embeded linux and not using as modules?
> Any advice/comment is appriciated.
>
> Thanks for the helps.
>
> Al
>
>
>
>
>
>
>
>
>
> -------------------------------------------------------
> 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
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>

|	Peter Wippich 			Voice: +49 30 46776411		|
|	G&W Instruments GmbH		fax:   +49 30 46776419		|
|	Gustav-Meyer-Allee 25, Geb. 12	Email: pewi@gw-instruments.de	|
|	D-13355 Berlin  / Germany					|




-------------------------------------------------------
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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

RE: [Bluez-devel] Porting BlueZ on embedded uClinux

[Al]

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

Hi, 
 
      Thanks for reply.
 
     1. kernel version is 2.4.20.
 
     2. I don't really change Makefile. Just make sure all
         BlueZ are enabled and force them to be compiled 
        with kernel. Somehow the original package 
         can't find bluetooth support using make menuconfig.
 
     3. Basic networking support is enabled for sure.
 
     4. I compiled bluetooth USB driver. My email program seems
         to misplace the message.
 
    5. I just think making BlueZ to be part of kernel instead of modules
        should be easier for my embedded platform. (So I don't need 
       commands like modprobe in romdisk, it saves space)
        Can I do this (part of kernel instead of modules) 
        without changing the source codes?
 
regards,
 
Al
 


	Hi AL,
	
	first question : what kernel version you are using ??
	
	Second: why you change the Makefile ??? Simply do a make menuconfig or
	what ever you prefer and configure that Bluetooth is compiled build in and
	not as a module.
	
	Make sure you have basic networking support enabled for your kernel.
	
	I can't see that you compiled in the bluetooth USB driver. So this is
	required when you use a USB adapter. But you don't need the *_cs drivers.
	
	Why do you think an embedded system can't support modules ????
	
	Ciao,
	
	Peter
	
	
	


[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 5180 bytes --]

RE: [Bluez-devel] Porting BlueZ on embedded uClinux

[Peter Wippich]

Hi AL,

On Fri, 12 Aug 2005, Al wrote:

> Hi,
>
>       Thanks for reply.
>
>      1. kernel version is 2.4.20.
Ok, I haven't tried BlueZ embedded with a 2.4 Kernel, only with 2.6. But I
know from some other project that it works well when compiled in and not
as a module with 2.4.x

>      2. I don't really change Makefile. Just make sure all
>          BlueZ are enabled and force them to be compiled
>         with kernel. Somehow the original package
>          can't find bluetooth support using make menuconfig.
Strange ! What "package" are you using ??

>      3. Basic networking support is enabled for sure.
>
>      4. I compiled bluetooth USB driver. My email program seems
>          to misplace the message.
>
>     5. I just think making BlueZ to be part of kernel instead of modules
>         should be easier for my embedded platform. (So I don't need
>        commands like modprobe in romdisk, it saves space)
>         Can I do this (part of kernel instead of modules)
>         without changing the source codes?
It will save you some space on your ramdisk. But if you use busybox for
your standard commands not that much. It depends on your system if it
makes sense that all drivers are always loaded to RAM. In general, all
drivers shall work without sourcecode changes when compiled in.

Is the USB dongle detected by the USB subsystem ???

>
> Al
>
>
>
> 	Hi AL,
>
> 	first question : what kernel version you are using ??
>
> 	Second: why you change the Makefile ??? Simply do a make menuconfig or
> 	what ever you prefer and configure that Bluetooth is compiled build in and
> 	not as a module.
>
> 	Make sure you have basic networking support enabled for your kernel.
>
> 	I can't see that you compiled in the bluetooth USB driver. So this is
> 	required when you use a USB adapter. But you don't need the *_cs drivers.
>
> 	Why do you think an embedded system can't support modules ????
>
> 	Ciao,
>
> 	Peter
>
>
>
>
>

|	Peter Wippich 			Voice: +49 30 46776411		|
|	G&W Instruments GmbH		fax:   +49 30 46776419		|
|	Gustav-Meyer-Allee 25, Geb. 12	Email: pewi@gw-instruments.de	|
|	D-13355 Berlin  / Germany					|




-------------------------------------------------------
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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

RE: [Bluez-devel] Porting BlueZ on embedded uClinux

[Al]

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

Hi, 

> Strange ! What "package" are you using ??
Yeah, somehow BlueZ is missing in config file. But
other BlueZ stuffs are there in kernel.
It's an ARM7 development toolkit with uClinux ported. 

> Is the USB dongle detected by the USB subsystem ???
Yes, I think so.

I just wonder did I miss any other BlueZ directory in kernel?
1. Protocol stack: linux/net/bluetooth
2. HCI device driver: linux/drivers/bluetooth
3. I haven't put anything in /etc/bluetooth, does it matter for the error?
    I just want to use " hciconfig" to list bluetooth USB dongle now.

Thanks for helps,

Al

	 


[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 3448 bytes --]

RE: [Bluez-devel] Porting BlueZ on embedded uClinux

[Peter Wippich]

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

On Fri, 12 Aug 2005, Al wrote:

> Hi,
>
> > Strange ! What "package" are you using ??
> Yeah, somehow BlueZ is missing in config file. But
> other BlueZ stuffs are there in kernel.
> It's an ARM7 development toolkit with uClinux ported.
>
> > Is the USB dongle detected by the USB subsystem ???
> Yes, I think so.
>
> I just wonder did I miss any other BlueZ directory in kernel?
> 1. Protocol stack: linux/net/bluetooth
> 2. HCI device driver: linux/drivers/bluetooth
> 3. I haven't put anything in /etc/bluetooth, does it matter for the error?
>     I just want to use " hciconfig" to list bluetooth USB dongle now.
>
> Thanks for helps,
>
> Al
>
>
>
>

|	Peter Wippich 			Voice: +49 30 46776411		|
|	G&W Instruments GmbH		fax:   +49 30 46776419		|
|	Gustav-Meyer-Allee 25, Geb. 12	Email: pewi@gw-instruments.de	|
|	D-13355 Berlin  / Germany					|




-------------------------------------------------------
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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

RE: [Bluez-devel] Porting BlueZ on embedded uClinux

[Al]

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

Hi, Peter:

Here is the log:
=========================================================
Linux version 2.4.20-uc0 (icc@AL30) (gcc version 3.0) #220 ?.. 8?.. 15 10:09:055Processor: 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 L2CAP ver 2.1 Copyright (C) 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
BlueZ SCO ver 0.3 Copyright (C) 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
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
Can't open HCI socket.: Address family not supported by protocol
pid 9: failed 256
/>
=========================================================

The last error message is printed from hciconfig.c while trying
to create a socket.
-----------------------------------------------------------
if ((ctl = socket(AF_BLUETOOTH, SOCK_RAW, BTPROTO_HCI)) < 0) 
{	
		perror("Can't open HCI socket.");
		exit(1);
}
------------------------------------------------------------

Thanks for helps,

Al
-----Original Message-----
From:	bluez-devel-admin@lists.sourceforge.net on behalf of Peter Wippich
Sent:	Fri 8/12/2005 8:34 PM
To:	bluez-devel@lists.sourceforge.net
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



[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 4828 bytes --]

RE: [Bluez-devel] Porting BlueZ on embedded uClinux

[Al]

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

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 <maxk@qualcomm.com>");
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 <maxk@qualcomm.com>
BlueZ L2CAP ver 2.1 Copyright (C) 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
BlueZ SCO ver 0.3 Copyright (C) 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
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:	bluez-devel-admin@lists.sourceforge.net on behalf of Peter Wippich
Sent:	Fri 8/12/2005 8:34 PM
To:	bluez-devel@lists.sourceforge.net
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



[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 5012 bytes --]

Re: [Bluez-devel] Porting BlueZ on embedded uClinux

[Paul Webster]

>      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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

RE: [Bluez-devel] Porting BlueZ on embedded uClinux

[Al]

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

Hi,

     "hciconfig -a hci0" results the same.
-------------------------------------------------
/> new USB device :801aaa04-174d60
hub.c: new USB device 1, assigned address 2
usb.c: USB device 2 (vend/prod 0x1131/0x1001) is not claimed by any active driv.                                                                                
/>
/> hciconfig -a hci0
                                                                                
Can't get device info: No such device
pid 9: failed 256
/>

---------------------------------------------------
      I think bluetooth drivers are not integrated to kernel correctly. hci_usb_init() in hci_usb.c is not run since I can't read the printout in embedded linux while the printout can be read in PC RH9 linux.

int hci_usb_init(void)
{
	int err;

	BT_INFO("BlueZ HCI USB driver ver %s Copyright (C) 2000,2001 Qualcomm Inc",  
		VERSION);
	BT_INFO("Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>");

	if ((err = usb_register(&hci_usb_driver)) < 0)
		BT_ERR("Failed to register HCI USB driver");

	return err;
}

-----Original Message-----
From:	bluez-devel-admin@lists.sourceforge.net on behalf of Paul Webster
Sent:	Mon 8/15/2005 1:38 PM
To:	bluez-devel@lists.sourceforge.net
Cc:	
Subject:	Re: [Bluez-devel] Porting BlueZ on embedded uClinux
>      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.

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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel




[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 3600 bytes --]

Re: [Bluez-devel] Porting BlueZ on embedded uClinux

[durai]

Hi Al,
I recently ported bluez stack in a embedded linux running 2.4.18 kernel.
First I downloaded the MH patch from  http://www.holtmann.org/linux/kernel/. 
and
applied it. Now both statically compiled driver as well as modules are 
working correctly.
You can also try finding an appropriate patch and patch it with your kernel. 
But what is
surprising for me is, though your kernel is 2.4.21 and you are not able to 
find the options in
make menuconfig.  I guess something  is messed up in your package.

Can you find "hci_usb_init" in your System.map? Is it integrated correctly?
regards
durai
----- Original Message ----- 
From: "Al" <Al_chane@issc.com.tw>
To: <bluez-devel@lists.sourceforge.net>
Sent: Monday, August 15, 2005 11:43 AM
Subject: RE: [Bluez-devel] Porting BlueZ on embedded uClinux


Hi,

     "hciconfig -a hci0" results the same.
-------------------------------------------------
/> new USB device :801aaa04-174d60
hub.c: new USB device 1, assigned address 2
usb.c: USB device 2 (vend/prod 0x1131/0x1001) is not claimed by any active 
driv.
/>
/> hciconfig -a hci0

Can't get device info: No such device
pid 9: failed 256
/>

---------------------------------------------------
      I think bluetooth drivers are not integrated to kernel correctly. 
hci_usb_init() in hci_usb.c is not run since I can't read the printout in 
embedded linux while the printout can be read in PC RH9 linux.

int hci_usb_init(void)
{
int err;

BT_INFO("BlueZ HCI USB driver ver %s Copyright (C) 2000,2001 Qualcomm Inc",
VERSION);
BT_INFO("Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>");

if ((err = usb_register(&hci_usb_driver)) < 0)
BT_ERR("Failed to register HCI USB driver");

return err;
}

-----Original Message-----
From: bluez-devel-admin@lists.sourceforge.net on behalf of Paul Webster
Sent: Mon 8/15/2005 1:38 PM
To: bluez-devel@lists.sourceforge.net
Cc:
Subject: Re: [Bluez-devel] Porting BlueZ on embedded uClinux
>      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.

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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel






-------------------------------------------------------
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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

RE: [Bluez-devel] Porting BlueZ on embedded uClinux

[Al]

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

Hi,

     I resolved the problem of integrating HCI driver. I can now use
"hciconfig hci0 up" to bring up the device. MAC address can be read
correctly. Kernel porting seems ok so far.

    But when I use "hciconfig -a", it has problem to read "Name", "Class",
and so on from /etc/bluetooth/hcid.conf (which I created already in the 
embedded
ramdisk). Any dependancy among those utilities? For example, if I need to 
use "hciconfig",
"hcid" is needed?

thanks for helps,

Al

----- Original Message ----- 
From: "durai" <durai@isofttech.com>
To: <bluez-devel@lists.sourceforge.net>
Sent: Monday, August 15, 2005 3:22 PM
Subject: Re: [Bluez-devel] Porting BlueZ on embedded uClinux

-----Original Message----- 
From: bluez-devel-admin@lists.sourceforge.net 代理 durai 
Sent: 2005/8/15 [星期一] 下午 03:22 
To: bluez-devel@lists.sourceforge.net 
Cc: 
Subject: Re: [Bluez-devel] Porting BlueZ on embedded uClinux



	Hi Al,
	I recently ported bluez stack in a embedded linux running 2.4.18 kernel.
	First I downloaded the MH patch from  http://www.holtmann.org/linux/kernel/.
	and
	applied it. Now both statically compiled driver as well as modules are
	working correctly.
	You can also try finding an appropriate patch and patch it with your kernel.
	But what is
	surprising for me is, though your kernel is 2.4.21 and you are not able to
	find the options in
	make menuconfig.  I guess something  is messed up in your package.
	
	Can you find "hci_usb_init" in your System.map? Is it integrated correctly?
	regards
	durai
	


[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 4680 bytes --]

RE: [Bluez-devel] Porting BlueZ on embedded uClinux

[Peter Wippich]

Hi AL,

I think you will need hcid anyway to do anything usefull.

Ciao,

Peter

On Mon, 15 Aug 2005, Al wrote:

> Hi,
>
>      I resolved the problem of integrating HCI driver. I can now use
> "hciconfig hci0 up" to bring up the device. MAC address can be read
> correctly. Kernel porting seems ok so far.
>
>     But when I use "hciconfig -a", it has problem to read "Name", "Clas=
s",
> and so on from /etc/bluetooth/hcid.conf (which I created already in the
> embedded
> ramdisk). Any dependancy among those utilities? For example, if I need =
to
> use "hciconfig",
> "hcid" is needed?
>
> thanks for helps,
>
> Al
>
> ----- Original Message -----
> From: "durai" <durai@isofttech.com>
> To: <bluez-devel@lists.sourceforge.net>
> Sent: Monday, August 15, 2005 3:22 PM
> Subject: Re: [Bluez-devel] Porting BlueZ on embedded uClinux
>
> -----Original Message-----
> From: bluez-devel-admin@lists.sourceforge.net =A5N=B2z durai
> Sent: 2005/8/15 [=ACP=B4=C1=A4@] =A4U=A4=C8 03:22
> To: bluez-devel@lists.sourceforge.net
> Cc:
> Subject: Re: [Bluez-devel] Porting BlueZ on embedded uClinux
>
>
>
> 	Hi Al,
> 	I recently ported bluez stack in a embedded linux running 2.4.18 kerne=
l.
> 	First I downloaded the MH patch from  http://www.holtmann.org/linux/ke=
rnel/.
> 	and
> 	applied it. Now both statically compiled driver as well as modules are
> 	working correctly.
> 	You can also try finding an appropriate patch and patch it with your k=
ernel.
> 	But what is
> 	surprising for me is, though your kernel is 2.4.21 and you are not abl=
e to
> 	find the options in
> 	make menuconfig.  I guess something  is messed up in your package.
>
> 	Can you find "hci_usb_init" in your System.map? Is it integrated corre=
ctly?
> 	regards
> 	durai
>
>
>

|	Peter Wippich 			Voice: +49 30 46776411		|
|	G&W Instruments GmbH		fax:   +49 30 46776419		|
|	Gustav-Meyer-Allee 25, Geb. 12	Email: pewi@gw-instruments.de	|
|	D-13355 Berlin  / Germany					|




-------------------------------------------------------
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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Porting BlueZ on embedded uClinux

[Al]

Hi, durai:

     I port hcid to embedded uClinux (2.4.20). But it has problem to
fork(), fork() return -1. Did you have fork() problem in your embedded
linux?

thanks a lot,

Al

----- Original Message -----=20
From: "durai" <durai@isofttech.com>
To: <bluez-devel@lists.sourceforge.net>
Sent: Monday, August 15, 2005 3:22 PM
Subject: Re: [Bluez-devel] Porting BlueZ on embedded uClinux


> Hi Al,
> I recently ported bluez stack in a embedded linux running 2.4.18 =
kernel.
> First I downloaded the MH patch from=20
> http://www.holtmann.org/linux/kernel/. and
> applied it. Now both statically compiled driver as well as modules are =

> working correctly.
> You can also try finding an appropriate patch and patch it with your=20
> kernel. But what is
> surprising for me is, though your kernel is 2.4.21 and you are not =
able to=20
> find the options in
> make menuconfig.  I guess something  is messed up in your package.
>
> Can you find "hci_usb_init" in your System.map? Is it integrated=20
> correctly?
> regards
> durai



-------------------------------------------------------
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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Porting BlueZ on embedded uClinux

[durai]

Hi Al,
In uClinux there is no fork, only vfork is available. You have to change 
your fork to vfork in uClinux.
Please refer 
http://www.ucdot.org/article.pl?sid=03/12/12/0317219&mode=thread.
regards
durai
----- Original Message -----
Subject: Re: [Bluez-devel] Porting BlueZ on embedded uClinux
Date: Wed, 17 Aug 2005 10:28:54 +0800
From: "Al" <Al_chane@issc.com.tw>

Hi, durai:

     I port hcid to embedded uClinux (2.4.20). But it has problem to
fork(), fork() return -1. Did you have fork() problem in your embedded
linux?

thanks a lot,

Al

----- Original Message ----- 
From: "durai" <durai@isofttech.com>
To: <bluez-devel@lists.sourceforge.net>
Sent: Monday, August 15, 2005 3:22 PM
Subject: Re: [Bluez-devel] Porting BlueZ on embedded uClinux


> Hi Al,
> I recently ported bluez stack in a embedded linux running 2.4.18 kernel.
> First I downloaded the MH patch from
> http://www.holtmann.org/linux/kernel/. and
> applied it. Now both statically compiled driver as well as modules are
> working correctly.
> You can also try finding an appropriate patch and patch it with your
> kernel. But what is
> surprising for me is, though your kernel is 2.4.21 and you are not able to
> find the options in
> make menuconfig.  I guess something  is messed up in your package.
>
> Can you find "hci_usb_init" in your System.map? Is it integrated
> correctly?
> regards
> durai



-------------------------------------------------------
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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel 



-------------------------------------------------------
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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

RE: [Bluez-devel] Porting BlueZ on embedded uClinux

[Al]

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

Hi, durai:
 
      Yes, vfork() works ok.
      I also found it at http://www.uclinux.org/pub/uClinux/FAQ.shtml#2-5
     "uClinux does not implement fork();  instead it implements vfork()."
               
     For the HCI utility on user space part, I first have /hci-lib and /hcid
compiled to hcid. Then have /hci-lib and /hciconfig compiled to hciconfig.
Copy two applications, hcid and hciconfig, to ramdisk. Also I have hcid.conf
copied to ramdisk /etc/bluetooth/
 
     After boot up, run hcid, then hciconfig hci0 up to bring up the device.
MAC address is read correctly. But when running hciconfig -a, it can't read local name correctly.
Did I miss something?
 
thanks,
 
Al
 
---------------------------------------------------------------

/> hcid
/> hciconfig hci0 up
/> hciconfig -a
hci0:   Type: USB
        BD Address: 00:11:67:03:DB:62 ACL MTU: 678:8 SCO MTU: 48:10
        UP RUNNING PSCAN ISCAN
        RX bytes:323 acl:0 sco:0 events:9 errors:0
        TX bytes:33 acl:0 sco:0 commands:9 errors:0
        Features: 0xff 0xff 0x8d 0x78 0x08 0x18 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy:
        Link mode: SLAVE ACCEPT


Can't read local name on hci0: Connection timed out (110)
pid 17: failed 256
/>
-------------------------------------------------------------------------------------------

	-----Original Message----- 
	From: bluez-devel-admin@lists.sourceforge.net 代理 durai 
	Sent: 2005/8/17 [星期三] 下午 12:32 
	To: bluez-devel@lists.sourceforge.net 
	Cc: 
	Subject: Re: [Bluez-devel] Porting BlueZ on embedded uClinux
	
	


	Hi Al,
	In uClinux there is no fork, only vfork is available. You have to change
	your fork to vfork in uClinux.
	Please refer
	http://www.ucdot.org/article.pl?sid=03/12/12/0317219&mode=thread.
	regards
	durai
	


[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 5944 bytes --]

Re: [Bluez-devel] Porting BlueZ on embedded uClinux

[durai]

-------------------------------------------------------
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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Porting BlueZ on embedded uClinux

[durai]

-------------------------------------------------------
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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel