From: Marcel Holtmann <marcel@holtmann.org>
To: Jon Valvatne <jon@valvatne.com>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] hidd --server only finding one device
Date: Fri, 18 Jun 2004 13:49:20 +0200 [thread overview]
Message-ID: <1087559360.4309.116.camel@pegasus> (raw)
In-Reply-To: <1087520970.3103.87.camel@localhost.localdomain>
Hi Jon,
> > I think the problem here is your Bluetooth card. The Nokia card is
> > working fine, but it seems that it has problems when you try to get
> > another device into that piconet in which it is already master. I only
> > own the DTL-1 and so I can't test this, but with a newer card or USB
> > dongle everything should work, because I tested already this case with
> > seven HID devices and it was working perfect.
>
> Ok, thank you very much for your help. I was actually happy when I
> received a Socket card of revision F instead of G, because then I
> wouldn't have to worry about the G card not working with the 2.6 kernel.
> But I guess there's a reason they never supported HID in their windows
> drivers for the previous revisions.
your thought is wrong here. The problem is not that the card don't
supports HID, because you can work with one of your devices. The problem
is that this card is "very old" and in the beginning of Bluetooth not
all chip manufacturers did a good job in implementing all features. Many
of them think to short and in a special case the phone companies. They
made sure that their card works with their phone and from their view
that was mostly an one-to-one communication. The keywords are scatternet
and multi-connection support. Another example is that in most phones you
can't synchronize your phonebook while you are makeing a phone call with
your Bluetooth headset.
Btw I also saw a very new Bluetooth 1.2 chip that don't really like a
piconet full of HID devices :(
> I've just ordered their special upgrade offer, so hopefully in a week or
> two I'll have both the F and the G revision to play with. Maybe I can
> even somehow make the newer card work with 2.6, so I can have both a new
> kernel and working HID. Wish me luck :)
If you find the real problem between hci_uart, serial_cs and 2.6 we will
all thank you.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-06-18 11:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 18:22 [Bluez-users] hidd --server only finding one device Jon Valvatne
2004-06-17 20:29 ` Marcel Holtmann
2004-06-17 21:19 ` Jon Valvatne
2004-06-17 22:19 ` Marcel Holtmann
2004-06-17 22:28 ` Jon Valvatne
2004-06-17 22:38 ` Marcel Holtmann
2004-06-17 22:55 ` Jon Valvatne
2004-06-17 23:01 ` Marcel Holtmann
2004-06-18 1:09 ` Jon Valvatne
2004-06-18 11:49 ` Marcel Holtmann [this message]
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=1087559360.4309.116.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=jon@valvatne.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox