From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [PATCH] Set D-BUS signal paths according to local device
Date: Fri, 14 Oct 2005 00:51:40 +0200 [thread overview]
Message-ID: <1129243900.5057.14.camel@localhost.localdomain> (raw)
In-Reply-To: <20051013180202.GA24902@localhost.localdomain>
Hi Johan,
> > I didn't analized all the patch content, but I guess it's possible change
> > the signature of the functions passing the dev id instead of receive the BT
> > address and convert it.
> >
> > What do you think?
>
> Yes, that would also be one possibility. However, it requires some
> changes to security.c (where those functions are being called from).
> Also, if we decide to start using the device address (instead of the id)
> in the object paths, there's no point in changing the function
> parameters. Maybe Marcel has an opinion about this?
I applied your patch to get it started. However for the final solution
we should send around a string inside the hcid API that will maybe
"hci0" or also an alias. For example you can rename Ethernet interfaces
and at some point I like to rename Bluetooth HCI interfaces, too.
Internally it will still use an id number, but that is only inside the
kernel.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-10-13 22:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-13 17:20 [Bluez-devel] [PATCH] Set D-BUS signal paths according to local device Johan Hedberg
2005-10-13 17:36 ` Claudio Takahasi
2005-10-13 18:02 ` Johan Hedberg
2005-10-13 22:51 ` Marcel Holtmann [this message]
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=1129243900.5057.14.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--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