All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sir Graham (Terra)" <sir__graham@terra.es>
To: <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Problem With the Inquiry and RFCOMM conexions
Date: Mon, 13 Mar 2006 15:15:47 +0100	[thread overview]
Message-ID: <00f101c646a8$b02e9250$0300a8c0@akira> (raw)
In-Reply-To: 1142256728.4622.1.camel@aeonflux.holtmann.net

Hi Marcel,

Thanks very much for you answer....

"limitation of the hardware"..?   I use modules BT 2.0 for this ....

Info of hciconfig hci0 version:

hci0:   Type: UART
        BD Address: 00:07:80:XX:XX:XX ACL MTU: 384:8 SCO MTU: 64:8
        HCI Ver: 2.0 (0x3) HCI Rev: 0xa42 LMP Ver: 2.0 (0x3) LMP Subver:=20
0xa42
        Manufacturer: Cambridge Silicon Radio (10)


The inquiry and the RFCOMM in blueZ have diferent handles. I understand t=
he=20
calls hci to module don=C2=B4t mixed ....

Why if I send data over RFCOMM channels the inquiry don=C2=B4t find any d=
evice?
I don=C2=B4t send any data, mantaint the conexion, the inquiry works with=
 any=20
problem.... =C2=BF=C2=BF???

The Inquiry works in a independient thread, and every conexion RFCOMM hav=
e=20
his own thread also....

Any idea?

Regards,
Sir Graham.




----- Original Message -----=20
From: "Marcel Holtmann" <marcel@holtmann.org>
To: <bluez-devel@lists.sourceforge.net>
Sent: Monday, March 13, 2006 2:32 PM
Subject: Re: [Bluez-devel] Problem With the Inquiry and RFCOMM conexions


Hi,

> I have a problem with make a Inquiry and RFCOMM conexions at the same
> time and don=C2=B4t understand why.....(with BlueZ).

this is a limitation of the hardware. What does "hciconfig hci0 version"
tell you?

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting langua=
ge
that extends applications into web and mobile media. Attend the live webc=
ast
and join the prime developer group breaking into this new coding territor=
y!
http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=110944&bid$1720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel=20



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-03-13 14:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-13  9:52 [Bluez-devel] Problem With the Inquiry and RFCOMM conexions Sir Graham (Terra)
2006-03-13 13:32 ` Marcel Holtmann
2006-03-13 14:15   ` Sir Graham (Terra) [this message]
2006-03-17 12:58     ` Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2006-03-15  9:08 Sir Graham (Terra)
2006-03-11  9:31 Sir Graham (Terra)
2006-03-17 12:56 ` 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='00f101c646a8$b02e9250$0300a8c0@akira' \
    --to=sir__graham@terra.es \
    --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.