Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Andreas Sundstrom <sunkan@zappa.cx>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] 2.6.0-test9 SiW works sometimes
Date: Fri, 07 Nov 2003 12:25:14 +0100	[thread overview]
Message-ID: <1068204314.25163.104.camel@pegasus> (raw)
In-Reply-To: <3FAB6E18.2070601@zappa.cx>

Hi Andreas,

> Ok, first of all I want to say that it works ok for me. I have tried
> everything except the "keys" proc entry.

this is good to hear, so I don't break anything else ;)

> Which means that when you have learnd how they function you should be
> able to guess what to do with the bluetooth entry if it for example
> looked like this:
> #cat bluetooth
> bluetooth_available:     15
> wireless_switch:         512
> bluetooth_on:            0
> 
> I have here changed the parameter to echo into "bluetooth" from
> bluetooth to bluetooth_on, and added an entry that shows the status of
> it. This makes it easy to guess that "echo bluetooth_on:1 > bluetooth"
> should enable the device if you know how the other entris work.
> Without this you want be able to guess that "bluetooth:1/0" is used
> for enabling/disabling the device.

The problem here are the information about these values. Try to play a
little bit with the switch on your notebook and get the values of the
wireless_switch and bluetooth_available registers for Bluetooth on/off
and Wirless LAN on/off.

Maybe this register could also be used to switch the Wireless LAN card
on/off and so I tend to rename the complete proc entry to wireless and
redo some parts of the patch.

Regards

Marcel





-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2003-11-07 11:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-05 11:06 [Bluez-users] 2.6.0-test9 SiW works sometimes Andreas Sundstrom
2003-11-05 11:22 ` Marcel Holtmann
2003-11-05 12:07   ` Andreas Sundstrom
2003-11-05 12:18     ` Marcel Holtmann
2003-11-05 12:54       ` Andreas Sundstrom
2003-11-05 14:15         ` Marcel Holtmann
2003-11-05 14:33           ` Andreas Sundstrom
2003-11-06 23:48             ` Marcel Holtmann
2003-11-07 10:04               ` Andreas Sundstrom
2003-11-07 11:25                 ` Marcel Holtmann [this message]
2003-11-07 11:34                   ` Andreas Sundstrom
2003-11-07 11:41                     ` Marcel Holtmann
2003-11-07 12:00                       ` Andreas Sundstrom
2003-11-07 12:12                         ` Marcel Holtmann
2003-11-07 13:22                           ` Andreas Sundstrom
2003-11-07 15:27                           ` Andreas Sundstrom
2003-11-07 18:50                           ` Andreas Sundstrom
2003-11-05 13:49       ` Andreas Sundstrom
2003-11-05 14:03         ` Marcel Holtmann
2003-11-05 14:31           ` Andreas Sundstrom
2003-11-08  9:53           ` Andreas Sundstrom

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=1068204314.25163.104.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=sunkan@zappa.cx \
    /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