Hi! The issue is resolved. For anyone who may be interested in the details,
it's as follows:
The problem was that the kernel did not recognize character device major
version 216. It had no drivers for this type of device. I had to configure
RFCOMM protocol support and RFCOMM TTY support under Bluetooth support in
the kernel and recompile it. This step added a driver to the kernel and a
cat of /proc/devices listed "216 rfcomm" as a recognized device.
Not being able to recognize this type of device was also causing ioctl()
function calls which referred to it to fail. After the drivers were loaded,
the ioctl() calls worked properly (which were previously giving errors).
Fahad.
_________________________________________________________________
Take advantage of powerful junk e-mail filters built on patented Microsoft?
SmartScreen Technology.
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines
Start enjoying all the benefits of MSN? Premium right now and get the
first two months FREE*.
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
mknod /dev/rfcomm0 c 216 0
I hope this helps.
Paulo Wollny
Fahad Khowaja wrote:
> Hello list members!
>=20
> I am using Bluez on an Axis Developer Board 82+ running kernel 2.4. I=20
> have everything running fine except when I try to issue "rfcomm bind" o=
r=20
> cat /dev/rfcomm0 or echo "foo" > /dev/rfcomm0 I get a "No such device"=20
> error. A cat of my /proc/devices produces:
>=20
> Character devices:
> 1 mem
> 2 pty
> 3 ttyp
> 4 ttyS
> 5 cua
> 10 misc
> 90 mtd
> 108 ppp
> 120 etrax gpio
> 121 ds1302
> 128 ptm
> 136 pts
> 162 raw
> 180 usb
>=20
> Block devices:
> 1 ramdisk
> 31 mtdblock
>=20
> It seems that the character device with major version 216 is not=20
> recognized by the kernel. Which driver is used for these devices? Which=
=20
> options should I enable in the kernel for it to be included in the=20
> kernel (I don't have module support on the axis board)? It will be an=20
> immense help if someone can give me some pointers!
>=20
> Gratefully yours,
> Fahad.
>=20
> _________________________________________________________________
> Take advantage of powerful junk e-mail filters built on patented=20
> Microsoft=AE SmartScreen Technology.=20
> http://join.msn.com/?pgmarket=3Den-ca&page=3Dbyoa/prem&xAPID=3D1994&DI=3D=
1034&SU=3Dhttp://hotmail.com/enca&HL=3DMarket_MSNIS_Taglines=20
> Start enjoying all the benefits of MSN=AE Premium right now and get th=
e=20
> first two months FREE*.
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by the 'Do More With Dual!' webinar=20
> happening
> July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dua=
l
> core and dual graphics technology at this free one hour event hosted by=
=20
> HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebina=
r
> _______________________________________________
> Bluez-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>=20
>=20
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users