From: "Frédéric Dalleau" <frederic.dalleau@access-company.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [patch] BNEP/PAN Qualification issues
Date: Thu, 17 Jul 2008 11:44:47 +0200 [thread overview]
Message-ID: <487F148F.7030109@access-company.com> (raw)
In-Reply-To: <486A6392.6080008@access-company.com>
Any updates?
Fr=E9d=E9ric DALLEAU
Fr=E9d=E9ric Dalleau wrote:
> Marcel, Luiz
>
>>>> A part of the patch si to move handling of incoming setup_conn_req =
>>>> in kernel. In order to keep pan working with older kernel, some =
>>>> differenciation must be done. How to achieve this ?
>>>> =
>>> I don't know yet. Can we first fix the issues that don't need =
>>> modifications within the kernel. I prefer not modifying the kernel =
>>> at all at the moment. =
>>
>> I understand.
>> My problem is that some tests require grouping several messages into =
>> one. In particular, the setup_conn_req can be sent together with a =
>> control extension TP/BNEP/CTRL/BV-19-C.
>> The current extension processing is to skip everything and I'm not =
>> sure the control message can be handled at application level.
>> =
>
> I wake up this thread,
>
> I'm working at making this easier to integrate but it will makes a =
> bunch of patches.
> Let's start with the small and self contained.
>
> Resend patch for bluez-utils, and network service timeout (after =
> SETUP_CONN_REQ is sent and no answer for 30 sec, disconnect)
>
> Other patch adds a parameter to bnep module for disabling header =
> compression.
>
> Let me know what you think.
> Regards,
>
> Fr=E9d=E9ric DALLEAU
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> ------------------------------------------------------------------------
>
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great priz=
es
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=3D100&url=3D/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-07-17 9:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-17 14:15 [Bluez-devel] [patch] BNEP/PAN Qualification issues Frédéric Dalleau
2008-04-17 18:17 ` Luiz Augusto von Dentz
2008-04-17 18:26 ` Marcel Holtmann
2008-04-17 20:42 ` Claudio Takahasi
2008-04-24 17:42 ` Marcel Holtmann
2008-05-22 11:01 ` Frédéric Dalleau
2008-05-22 11:48 ` Marcel Holtmann
2008-05-22 14:05 ` Frédéric Dalleau
2008-07-01 17:04 ` Frédéric Dalleau
2008-07-17 9:44 ` Frédéric Dalleau [this message]
2008-07-19 15:14 ` Luiz Augusto von Dentz
2008-08-07 22:34 ` Marcel Holtmann
2008-09-08 8:57 ` Frédéric Dalleau
2008-09-08 9:32 ` Marcel Holtmann
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=487F148F.7030109@access-company.com \
--to=frederic.dalleau@access-company.com \
--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 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).