public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: umeshyv <umeshyv@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] enabling/disabling in response to ThinkPad hotkey
Date: Sat, 5 Jan 2008 10:01:12 +0530	[thread overview]
Message-ID: <b5c34db00801042031s4564c190sc9cc5ff0718cc188@mail.gmail.com> (raw)
In-Reply-To: <477E9A32.8080908@cs.wisc.edu>


[-- Attachment #1.1: Type: text/plain, Size: 1802 bytes --]

Hi to all,
I use suse linux 10.1 and i connected bluetooth usb dongle and enabled
bluetooth server and i removed mouse from my system and i own sony erricsion
(K750i) mobile and it contains remote control application in it and using
that i am able to access desktop in windows  vista and is this possible to
do in linux.please send your valuable comments

Regards
Umesh

On Jan 5, 2008 2:12 AM, Ben Liblit <liblit@cs.wisc.edu> wrote:

> Marcel Holtmann wrote:
> > The reason for this is that the Bluetooth on/off switches are all
> > different and HAL and rfkill is the way to abstract it into a common
> > interface. It is not the job of hcid to abstract this.
>
> OK, I see your point.  HAL is supposed to keep other daemons from having
> to worry about such things.  I've conveyed your reply back to the HAL
> mailing list.
>
> That said, it's unfortunate that the end result is an Fn+F5 key which
> does *nothing* useful out of the box.  Even if different users would
> want it to do slightly different things, right now it does *nothing* by
> default.  I'm savvy enough to write my own script that runs as root,
> hooks into HAL D-BUS signals, and responds accordingly.  Most users
> won't do that, so for them, this key is useless.
>
> Oh well.  Between HAL and Bluez, things are much better now than they
> ever were before.  We're not done yet, but at least we're making progress.
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>

[-- Attachment #1.2: Type: text/html, Size: 2433 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2008-01-05  4:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-03  5:05 [Bluez-users] enabling/disabling in response to ThinkPad hotkey Ben Liblit
2008-01-03  5:21 ` Marcel Holtmann
2008-01-04 20:42   ` Ben Liblit
2008-01-05  4:31     ` umeshyv [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=b5c34db00801042031s4564c190sc9cc5ff0718cc188@mail.gmail.com \
    --to=umeshyv@gmail.com \
    --cc=bluez-users@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