Return-Path: Date: Mon, 22 Aug 2011 20:49:32 +0100 From: Dave Higton To: linux-bluetooth@vger.kernel.org Subject: Re: Arguments to PIN Code Request Response Message-ID: References: <7b86640552.davehigton@dsl.pipex.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: In message Ash K wrote: > Hi Dave, > > If you see specification the PIN_Code parameter for > PIN_Code_request_reply command, it says > > Value > ---- > 0xXXXXXXXXXX > XXXXXXXXXXX > XXXXXXXXXXX > ?Parameter Description > ---- > PIN code for the device that is to be connected. The Host should > ensure that strong PIN Codes are used. PIN Codes can be up to a > maximum of 128 bits. Note: The PIN_Code Parameter is a string > parameter. Endianess does therefore not apply to the PIN_Code > Parameter. The first octet of the PIN code should be transmitted first. > Which means, even if your PIN code of 4 byte length you have to send > 16 byte length of PIN code to controller. And controller uses initial > bytes from the 16byte PIN code, the length of the PIN code is defined > by length parameter. > What you are looking at is correct, after 4 bytes of PIN code, you > have some junk/host selected data which is of no interest to > controller. Many thanks for your explanation, Ash. Dave