All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: David Stockwell <dstockwell@frequency-one.com>
Cc: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Moving towards a new API for BlueZ 4.0
Date: Thu, 20 Mar 2008 14:50:14 +0100	[thread overview]
Message-ID: <1206021014.7678.7.camel@californication> (raw)
In-Reply-To: <039f01c88a15$a848aaa0$6701a8c0@freqonedev>

Hi David,

> Thanks for all of the great effort, especially in moving toward the DBus model.
> 
> I am currently going through the work done to date in audio/control.c (the implementation of AVRCP), and am trying to apply that to 
> an application connecting with an AVRCP on CSR's BlueLab 4.0 framework (implements BT2.1+).  I have some ideas, although I am still 
> making sure I understand what has been done to this point, and would like to participate in further development (although I am not 
> the best C developer).
> 
> As things stand, it appears we could use more functions and callbacks to support UnitInfo, SubUnitInfo, Passthrough, and 
> VendorDependent (wherein Metadata resides), etc., and at the same time, I think we should not constrain the use cases to the simple 
> 10-button remote that has been implemented to date.
> 
> At any rate, I would like to get involved, as I have immediate interest in moving this forward.  I do have the official Bluetooth 
> specs and the CSR IDE, so I think I could contribute from that front.
> 
> Any interest?  Who should I communicate with?

go ahead and do so. Patches are always welcome. However, please start a
new thread for it.

Regards



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2008-03-20 13:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-13 20:32 [Bluez-devel] Moving towards a new API for BlueZ 4.0 Marcel Holtmann
2008-03-14 10:23 ` Manuel Naranjo
2008-03-14 12:23   ` Marcel Holtmann
2008-03-14 13:44     ` Manuel Naranjo
2008-03-14 14:00       ` Marcel Holtmann
2008-03-14 14:15         ` Manuel Naranjo
2008-03-14 14:20         ` Robert Rawlins
2008-03-19 23:04 ` David Stockwell
2008-03-20 13:50   ` Marcel Holtmann [this message]
2008-03-20 14:49   ` Johan Hedberg

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=1206021014.7678.7.camel@californication \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=dstockwell@frequency-one.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 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.