Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
To: EXT-Somil.Asthana@nokia.com
Cc: Max Krasnyansky <maxk@qualcomm.com>,
	tomi@virago.in-chemnitz.de,
	BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: RE: [Bluez-users] DB aliases (wishlist)
Date: 10 Apr 2003 16:32:31 +0200	[thread overview]
Message-ID: <1049985158.7671.25.camel@pegasus.local> (raw)
In-Reply-To: <E320A8529CF07E4C967ECC2F380B0CF9013E84C7@bsebe001.americas.nokia.com>

Hi Somil,

>   Just a thought !! Do you really think this is necessary feature because I added a simple cmd in hcitool -i hciX lname <local_name> which calls issues HCI_CMD to write local name. It was nothing more than cut & paste from hcid/main.c file which writes local name...

we don't need this, because you can use

	hciconfig hci0 name <local-name>

and I don't see what this have to do with the mail from Paul. Such an
aliases, hosts or devices file is for the remote devices, not the local
ones.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2003-04-10 14:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-10 13:26 [Bluez-users] DB aliases (wishlist) EXT-Somil.Asthana
2003-04-10 14:32 ` Marcel Holtmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-15 14:40 EXT-Somil.Asthana

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=1049985158.7671.25.camel@pegasus.local \
    --to=marcel@rvs.uni-bielefeld.de \
    --cc=EXT-Somil.Asthana@nokia.com \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=maxk@qualcomm.com \
    --cc=tomi@virago.in-chemnitz.de \
    /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