From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [DBUS PATCH] GetServiceClasses
Date: Fri, 24 Feb 2006 03:39:42 +0100 [thread overview]
Message-ID: <1140748782.24721.87.camel@localhost> (raw)
In-Reply-To: <e1effdeb0602231329r446c015bh172515b7eebec548@mail.gmail.com>
Hi Claudio,
> > the patch has been applied. So what have been left?
>
> - GetFeatures
this returns an empty list for now.
> - PinCodeLength
It has been implemented, but it definitely needs more testing. I choose
an extension of the link keys file.
> - EncryptionKeySize
The basic functionality is there, but no backend for the different chips
has been implemented.
> - MinorClassChanged
Done.
> - dbus-test update
I did a small update for my own testing.
Regards
Marcel
-------------------------------------------------------
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
prev parent reply other threads:[~2006-02-24 2:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-23 20:50 [Bluez-devel] [DBUS PATCH] GetServiceClasses Claudio Takahasi
2006-02-23 21:18 ` Marcel Holtmann
2006-02-23 21:29 ` Claudio Takahasi
2006-02-23 21:51 ` Marcel Holtmann
2006-02-24 2:39 ` 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=1140748782.24721.87.camel@localhost \
--to=marcel@holtmann.org \
--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.