From: Marcel Holtmann <marcel@holtmann.org>
To: Matthew Grant <grantma@anathoth.gen.nz>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [Bluez-users] Re: PROBLEM: Apple powerbook, Apple BT keyboard, keyboard does not reconnect on reboot
Date: Sat, 06 Nov 2004 13:34:51 +0100 [thread overview]
Message-ID: <1099744491.6919.39.camel@pegasus> (raw)
In-Reply-To: <1099721547.5132.70.camel@localhost>
Hi Matthew,
> Finally figured out what is wrong. There is definitely a Powerpc
> problem with the BT HIDPGETCONNLIST ioctl on the powerpc arch.
>
> The HID ioctl HIDPGETCONNLIST is not returning any HID device entries
> from the kernel on the Powerpc architecture, even when a blue-tooth
> keyboard and mouse are working.
>
> In Debian's boot scripts hidd --killall is used to nicely close the
> connections so that the devices will reconnect cleanly on next boot.
> This is not working for me as the above ioctl is not returning a list if
> addresses to be acted on.
>
> Work around for me will be to explicitly kill each device address before
> stopping hidd, as hidd --kill <device address> works. Does this mean
> that the devices are registering in the hidp module, but there is a
> problem in passing the list back out of the kernel?
does "hidd --show" works?
> Do you have access to a powerpc machine to test this on? Could you give
> me any instructions on getting the hidp.ko module to produce the debug
> that would be useful?
>
> It would be good to get this one solved, as I would like to look at
> shallower bugs which I can knock off myself. First look at the hidp code
> with this one freaked me out a bit.
I don't have access to a PowerPC machine. What Apple is this?
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users/listinfo/bluez-users
next prev parent reply other threads:[~2004-11-06 12:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-24 21:45 PROBLEM: Apple powerbook, Apple BT keyboard, keyboard does not reconnect on reboot Matthew Grant
2004-10-24 22:07 ` [Bluez-users] " Matthew Grant
2004-10-25 3:56 ` Marcel Holtmann
2004-10-25 3:55 ` [Bluez-users] " Marcel Holtmann
2004-10-25 8:59 ` Matthew Grant
2004-10-26 10:34 ` [Bluez-users] " Matthew Grant
2004-11-06 6:12 ` Matthew Grant
2004-11-06 12:34 ` Marcel Holtmann [this message]
2004-11-06 20:11 ` Matthew Grant
2004-11-06 21:31 ` Marcel Holtmann
[not found] ` <1099788984.4543.5.camel@localhost>
2004-11-07 2:38 ` Marcel Holtmann
2004-11-08 19:38 ` Matthew Grant
2004-11-08 19:53 ` Marcel Holtmann
2004-11-10 19:34 ` Matthew Grant
2004-11-13 3:39 ` Matthew Grant
2004-11-13 6:09 ` Matthew Grant
2004-11-13 12:53 ` Marcel Holtmann
2004-11-13 18:52 ` Matthew Grant
2004-11-13 19:05 ` Marcel Holtmann
2004-11-13 19:55 ` Matthew Grant
2004-11-13 20:01 ` Marcel Holtmann
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=1099744491.6919.39.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=dwmw2@infradead.org \
--cc=grantma@anathoth.gen.nz \
/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