From: Fredrik Noring <noring@nocrew.org>
To: Achim Bohnet <ach@mpe.mpg.de>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] Bluetooth address specific device configuration
Date: Thu, 29 Jan 2004 19:29:17 +0100 [thread overview]
Message-ID: <1075400957.22564.42.camel@akka.yeti.nocrew.org> (raw)
In-Reply-To: <200401290016.05166.ach@mpe.mpg.de>
Hi Achim,
tor 2004-01-29 klockan 00.16 skrev Achim Bohnet:
> I've a laptop with buildin bt and an external bt stick. It depends on the
> order I switch internal one on or connect the stick what interface is
> assigned to the same hardware. If there is a need (no idea yet I'm
> a bt newbie) for this feature selection by bdaddr is therefore useful
> to support. Selection by interface would be useless for me.
I think combining all three possibilities is the best:
device <bdaddr>
{
# This is the configuration for all
# devices that have matching bdaddr:s.
}
device <hci interface>
{
# This is the configuration for all devices
# that have matching interfaces but no matching
# bdaddr.
}
device
{
# This is the configuration for all devices
# that don't match anything else: the default.
}
This way one can mix and move devices around and hcid will do its
best to configure things properly.
Having a utility (e.g. config-bluetooth) managing all these
configurations simpifies things, of course.
> On the other hand if I ever take the another identical stick with me
> by accident, bdaddr would be different and the settings would not
> apply without a notice. Maybe a
>
> device default
> {
> complain loudly
> }
>
> is useful ;)
Well, simply having
device
{
# Default configuration.
}
already works today. :)
Fredrik
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-01-29 18:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 18:56 [Bluez-devel] [PATCH] Bluetooth address specific device configuration Fredrik Noring
2004-01-28 19:24 ` Fredrik Noring
2004-01-28 23:16 ` Achim Bohnet
2004-01-29 18:29 ` Fredrik Noring [this message]
2004-01-29 5:52 ` Marcel Holtmann
2004-01-29 19:39 ` Fredrik Noring
2004-01-29 19:58 ` Fredrik Noring
2004-01-31 15:30 ` Marcel Holtmann
2004-01-31 15:49 ` Fredrik Noring
2004-01-31 15:59 ` Marcel Holtmann
2004-01-31 16:15 ` Fredrik Noring
2004-01-31 18:09 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2004-01-29 10:38 Nosve
2004-01-31 19:04 ` Marcel Holtmann
2004-02-03 13:32 ` Fredrik Noring
2004-02-01 19:20 nosve
2004-02-01 23:27 ` 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=1075400957.22564.42.camel@akka.yeti.nocrew.org \
--to=noring@nocrew.org \
--cc=ach@mpe.mpg.de \
--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