Re: [Bluez-users] Re: PROBLEM: Apple powerbook, Apple BT keyboard, keyboard does not reconnect on reboot

[Matthew Grant <grantma@anathoth.gen.nz>]

[-- Attachment #1: Type: text/plain, Size: 2595 bytes --]

Marcel,

Just got debug going.  Going to put printks into hidp_get_connlist to
see what is happening.

Your comment on the big endian bug in the L2CAP you noticed below, and
some of the debug I have seen with the other BT problems make it look
like I am having endianess issues. 

I am going to print the kernel code tonight and read it through as it is
obvious I have to understand the stack if I am get things fixed - you
don't have access to an Apple machine to test things on.  In the past I
was a commercial router programmer, doing OSPF and IPX development.

Any good places to find protocol specs?  I especially need
specifications on the endianess of the incoming BT data so I can audit
and check the debug for that sort of thing.

Cheers,

Matthew Grant

On Sun, 2004-11-07 at 15:38, Marcel Holtmann wrote:
> Hi Matthew,
> 
> > > and what does /proc/bluetooth/l2cap show you?
> > > 
> > 
> > root@sharon:/usr/src/bluetooth/bluez-utils-2.10#
> > # cat /proc/bluetooth/l2cap
> > A7:FF:10:93:0D:00 49:0B:3B:95:0A:00 1 4864 0x0041 0x0041 48 672 0x1
> > A7:FF:10:93:0D:00 49:0B:3B:95:0A:00 1 4352 0x0040 0x0040 48 672 0x1
> > A7:FF:10:93:0D:00 61:DF:16:61:07:00 1 4864 0x0041 0x004d 48 48 0x1
> > A7:FF:10:93:0D:00 61:DF:16:61:07:00 1 4352 0x0040 0x004c 48 48 0x1
> > 00:00:00:00:00:00 00:00:00:00:00:00 4 4864 0x0000 0x0000 48 48 0x1
> > 00:00:00:00:00:00 00:00:00:00:00:00 4 4352 0x0000 0x0000 48 48 0x1
> > 00:00:00:00:00:00 00:00:00:00:00:00 4 256 0x0000 0x0000 672 0 0x0
> > 00:00:00:00:00:00 00:00:00:00:00:00 4 768 0x0000 0x0000 1024 0 0x0
> > 
> > The above bluetooth addresses are all in reverse byte order!!!
> > 
> > Apple Keyboard is 00:0A:95:3B:0B:49
> > Logitech Mx900 Mouse is 00:07:61:16:DF:61
> > computer hci0 is 00:0D:93:10:FF:A7
> 
> the address order is ok, but the column for the PSM has a big endian
> bug. This needs to be fixed.
> 
> However you are connected to the mouse and the keyboard. This is
> actually working fine.
> 
> > > You can enable the DEBUG in the hidp driver or add some printk calls be
> > > yourself to see where the ioctl fails.
> > > 
> > I will give this a go latter on this afternoon.
> 
> Try to find the reason why and where the ioctl fails.
> 
> Regards
> 
> Marcel
> 
-- 
===============================================================================
Matthew Grant        /\  ^/\^   grantma@anathoth.gen.nz      /~~~~\
A Linux Network Guy /~~\^/~~\_/~~~~~\_______/~~~~~~~~~~\____/******\
===GPG KeyID: 2EE20270  FingerPrint: 8C2535E1A11DF3EA5EA19125BA4E790E2EE20270==


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]