From: Bastien Nocera <hadess@hadess.net>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: dun profile
Date: Thu, 15 Oct 2009 10:38:57 +0100 [thread overview]
Message-ID: <1255599537.3797.63.camel@localhost.localdomain> (raw)
In-Reply-To: <2d5a2c100910141815l3300ee34p12fbbac2dd6a96b6@mail.gmail.com>
On Wed, 2009-10-14 at 22:15 -0300, Luiz Augusto von Dentz wrote:
> Hi List,
>
> Im trying to put an end to this problem of detecting rfcomm port
> properly, so what seems to be missing is to associate the profile to
> the port so that udev can properly announce it as modem in case of dun
> profile. I don't know of any mechanism to attach any profile
> information to the port itself, but in theory we could identify the
> port by name, so instead of using rfcomm# for all ports created by
> Serial interface we could name it dun# for instance, so how about
> that? Also we probably want to make this persistent so once this is
> configured this will be restored in the next boot.
Same questions as Stefan I'm afraid.
In any case, I think the front-ends should be creating the port
themselves, so they would know which one to handle.
See the recent (and less recent) work done in NetworkManager for DUN
support.
Cheers
next prev parent reply other threads:[~2009-10-15 9:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 1:15 dun profile Luiz Augusto von Dentz
2009-10-15 7:02 ` Stefan Seyfried
2009-10-15 9:38 ` Bastien Nocera [this message]
2009-10-15 14:22 ` Luiz Augusto von Dentz
2009-10-15 15:19 ` 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=1255599537.3797.63.camel@localhost.localdomain \
--to=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox