From: Marcel Holtmann <marcel@holtmann.org>
To: Neil Fenemor <Neil@OnDrugs.co.nz>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Logitech MX900 Hub + i-mate smartphone2
Date: Thu, 24 Jun 2004 01:19:13 +0200 [thread overview]
Message-ID: <1088032753.4296.23.camel@pegasus> (raw)
In-Reply-To: <1088032096.3703.32.camel@localhost.localdomain>
Hi Neil,
> The standard Fedora 2.6.5 kernel, I'm just doing a compile of the
> kernel again, making sure I've got all the options I need.
maybe you should install 2.6.7-mh1.
> However, if I use a different phone (in fact I've tried two other
> phones) I can create a L2CAP link, and even use it happily.
Run "hcidump -w <dumpfile>" as root and send us the binary dump file. I
must compare the timestamps.
> Maybe the Windows phone just doesn't like playing nice with Linux ;)
Actually the L2CAP and RFCOMM layers of BlueZ behave like the Bluetooth
specification say they should ;)
Regards
Marcel
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-06-23 23:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 22:22 [Bluez-devel] Logitech MX900 Hub + i-mate smartphone2 Neil Fenemor
2004-06-23 22:38 ` Marcel Holtmann
2004-06-23 22:49 ` Neil Fenemor
2004-06-23 22:59 ` Marcel Holtmann
2004-06-23 23:08 ` Neil Fenemor
2004-06-23 23:19 ` Marcel Holtmann [this message]
[not found] ` <1088033524.3703.34.camel@localhost.localdomain>
2004-06-23 23:41 ` Marcel Holtmann
2004-06-23 23:58 ` Neil Fenemor
2004-06-23 22:50 ` Neil Fenemor
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=1088032753.4296.23.camel@pegasus \
--to=marcel@holtmann.org \
--cc=Neil@OnDrugs.co.nz \
--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.