Re: [RFC][PATCH 0/4] Allow hexadecimal encoded pins

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, May 3, 2011 at 1:32 AM, Bastien Nocera <hadess@xxxxxxxxxx> wrote:
> What are the necessary changes to be made in gnome-bluetooth?
>
> I'm guessing that we should add a "WIIMOTE" type of special casing in
> the pin database, and pass the adapter address as per the above when a
> PIN is requested.

Exactly. If I click on PIN-type in gnome-bluetooth applet, then there
are already several choices I can make. I'd recommend adding a new one
with "use source address as PIN" and one with "use destination address
as PIN".
Then at least all functionalities to pair with a device are
implemented. Additional auto-detection may be added...

> Is there any way to detect which "type" of pairing is made with the
> Wiimote, eg. you say that button 1+2 will only work for temporary
> connections. Can we detect this? Would pairing anyway work?

I guess you mean that you wanna predict which PIN to use? No, I
currently know no way to detect this. However, one may try the first
pin and if that fails the second pin. As far as I know, the wiimote
does not turn off when a wrong PIN is passed so you can try other
PINs. I am still working on reverse-engineering the protocol and maybe
I will find a way, though.

> Cheers

Regards
David
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux