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 13:12:14 +0100 [thread overview]
Message-ID: <1068207133.25163.117.camel@pegasus> (raw)
In-Reply-To: <3FAB8963.9070600@zappa.cx>
Hi Andreas,
> This is when I have successfully enabled bluetooth and USB has noticed
> that the dongle has been plugged in.
>
> root@swe248:/proc/acpi/toshiba# cat bluetooth
> bluetooth_available: 15
> wireless_switch: 705
> bluetooth_on: 1
>
> By accident I noticed that when I changed the switched from Off to On it
> went up to 577 so I that is now the highest number I've seen without the
> bluetooth dongle actually working.
don't think of highest number. You should start thinking in which bit is
set and which is not. It seems that the bluetooth_available register
will always be 15 and can be ignored at this point. The important part
is the value of wireless_switch.
It seems that we have some variables to fill in.
The hardware switch on/off
Bluetooth activated/deactivated through software
Bluetooth dongle found/disabled by USB subsystem
So you should make a table with all possible combinations and fill in
the values (in hex) for it. This is what I need to see which bit gets
toggled and which not.
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
next prev parent reply other threads:[~2003-11-07 12:12 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
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 [this message]
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=1068207133.25163.117.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