From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: Vinicius Gomes <vinicius.gomes@openbossa.org>,
BlueZ <linux-bluetooth@vger.kernel.org>
Subject: Re: BlueZ GSoC 2010
Date: Mon, 22 Mar 2010 18:14:37 +0200 [thread overview]
Message-ID: <2d5a2c101003220914m41188e22ha0872104d4c6db4f@mail.gmail.com> (raw)
In-Reply-To: <1269259999.21548.3330.camel@localhost.localdomain>
Hi Bastien,
On Mon, Mar 22, 2010 at 2:13 PM, Bastien Nocera <hadess@hadess.net> wrote:
> Hey,
>
> On Thu, 2010-03-18 at 22:50 -0300, Vinicius Gomes wrote:
>> Hi,
>>
>> BlueZ just got accepted as an organization for this year's Google
>> Summer of Code.
>>
>> There is a small list of project ideas here[1], for the next days we
>> need to polish it and add more content. Any help is appreciated.
>>
>> We are also looking for mentors, if this idea interests you, please
>> contact me off-list or go to #bluez-gsoc at freenode, this is also
>> where most of the discussion regarding GSoC will take place, in case
>> you just want to follow it.
>>
>> As always, patches and suggestions are welcome ;-)
>
> A couple of comments:
> - Is AVRCP 1.4 support really a full Summer's work? Could be with
> PulseAudio or application integration?
Some avrcp 1.4 needs some integration so I guess it is ok.
> - The "any" adapter work is a waste of resources, as I've mentioned in
> the past on the list.
Well if it eliminates one round trip for most application I guess it
is worth adding, and we might add other tricks as storage and API
simplifications on top of it.
> - The VDP support probably needs kernel-level hacking as well, to avoid
> being constrained to one of the supported frameworks, and create a
> user-space driver for the device (using CUSE?)
It could be considerate, but if that is a good idea to vdp it would
also be for a2dp, there is also the problem that avdtp is currently
implemented in bluetoothd so I wonder if we should start changing
things or just implement vdp on top of the existing avdtp code.
> I'd be happy to do testing and some integration work for both the VDP
> and DUN works.
>
> I could also add:
> - Port gnome-user-share to obexd, instead of obex-data-server (easy)
> - Port osso-gwobex test suite and extend it (medium)
> (Those 2 could be combined into one project)
> - Printer (initial) setup integration in gnome-bluetooth (medium)
I guess those are too gnome related for being in BlueZ, expect maybe
gwobex, of course we could help/co/mentor projects under gnome
organization.
> - Extended hostname support (using xdg-hostname) (medium)
> - Kernel driver and user-space changes for Sixaxis joypad (including
> rumble). The bdaddr assignment would be done in the kernel, with a
> helper in bluetoothd, extra functionality would be added in the kernel
> for the other features (medium)
Great ideas and those fits perfectly as bluez organization projects.
--
Luiz Augusto von Dentz
Computer Engineer
next prev parent reply other threads:[~2010-03-22 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 1:50 BlueZ GSoC 2010 Vinicius Gomes
2010-03-22 12:13 ` Bastien Nocera
2010-03-22 16:14 ` Luiz Augusto von Dentz [this message]
2010-03-22 17:27 ` Bastien Nocera
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=2d5a2c101003220914m41188e22ha0872104d4c6db4f@mail.gmail.com \
--to=luiz.dentz@gmail.com \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=vinicius.gomes@openbossa.org \
/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;
as well as URLs for NNTP newsgroup(s).