From: Marcel Holtmann <marcel@holtmann.org>
To: "Li, Zhigang" <zhigang.li@intel.com>
Cc: Johan Hedberg <johan.hedberg@nokia.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: RE: To enablue DID in coming bluez release
Date: Wed, 17 Dec 2008 20:59:13 +0100 [thread overview]
Message-ID: <1229543953.10889.16.camel@violet> (raw)
In-Reply-To: <B94C62E7C2870743865418621F040C1303B80C87@pdsmsx502.ccr.corp.intel.com>
Hi Zhigang,
so first things first. NO top-posting on this mailing list.
> Updated:
> --- a/main.c Tue Dec 16 17:43:24 2008 +0800
> +++ b/main.c Wed Dec 17 11:57:47 2008 +0800
> @@ -174,6 +174,17 @@ static void parse_config(GKeyFile *confi
> main_opts.inqmode = val;
> }
>
> + str = g_key_file_get_string(config, "General",
> + "DeviceID", &err);
> + if (err) {
> + debug("%s", err->message);
> + g_clear_error(&err);
> + } else {
> + debug("deviceid=%s", str);
> + strncpy(main_opts.deviceid, str, sizeof(main_opts.deviceid));
> + g_free(str);
> + }
> +
> main_opts.link_mode = HCI_LM_ACCEPT;
>
> main_opts.link_policy = HCI_LP_RSWITCH | HCI_LP_SNIFF |
I always need patches against the latest GIT tree. Otherwise I can't
merge them and submitting them in a proper format helps me to apply
them.
> diff -r 65556502911d main.conf
> --- a/main.conf Tue Dec 16 17:43:24 2008 +0800
> +++ b/main.conf Tue Dec 17 11:57:51 2008 +0800
> @@ -28,3 +28,9 @@ OffMode = NoScan
> # Discover scheduler interval used in Adapter.DiscoverDevices
> # The value is in seconds. Defaults is 0 to use controller scheduler
> DiscoverSchedulerInterval = 0
> +
> +
> +# User verndor and product and version information are used in DID profile
> +# ":" to identify the value. FFFF is reserved for VendorId by default.
> +DeviceID = 1234:5678:abcd
So the option should be commented out by default since otherwise every
installation now uses vendor id 1234 and that is actually a valid one.
Also the description above makes no sense.
I committed a patch by myself to the GIT tree now that should fix this.
However there is one thing missing. The DID supports USB based vendor
ids and Bluetooth based ones. So we need to support both. Feel free to
come up with something.
Regards
Marcel
next prev parent reply other threads:[~2008-12-17 19:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 1:52 To enablue DID in coming bluez release Li, Zhigang
2008-12-12 1:55 ` Marcel Holtmann
2008-12-16 7:55 ` Li, Zhigang
2008-12-16 9:59 ` Li, Zhigang
2008-12-16 10:29 ` Johan Hedberg
2008-12-17 2:17 ` Li, Zhigang
2008-12-17 2:25 ` David Sainty
2008-12-17 2:38 ` Marcel Holtmann
2008-12-17 3:10 ` Li, Zhigang
2008-12-17 19:59 ` Marcel Holtmann [this message]
2008-12-18 5:55 ` Li, Zhigang
2008-12-19 19:01 ` 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=1229543953.10889.16.camel@violet \
--to=marcel@holtmann.org \
--cc=johan.hedberg@nokia.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=zhigang.li@intel.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