* BT LMP
@ 2012-07-05 6:00 victor yeo
2012-07-05 7:20 ` Marcel Holtmann
0 siblings, 1 reply; 6+ messages in thread
From: victor yeo @ 2012-07-05 6:00 UTC (permalink / raw)
To: linux-bluetooth
Hi,
Anyone know which part of linux kernel processes the LMP au_rand and
LMP not_accepted event?
I want to modify the Bluetooth kernel code so that when it receives
LMP not_accepted event, it will do re-pairing.
Thanks,
Victor
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: BT LMP
2012-07-05 6:00 BT LMP victor yeo
@ 2012-07-05 7:20 ` Marcel Holtmann
2012-07-05 7:42 ` victor yeo
0 siblings, 1 reply; 6+ messages in thread
From: Marcel Holtmann @ 2012-07-05 7:20 UTC (permalink / raw)
To: victor yeo; +Cc: linux-bluetooth
Hi Victor,
> Anyone know which part of linux kernel processes the LMP au_rand and
> LMP not_accepted event?
>
> I want to modify the Bluetooth kernel code so that when it receives
> LMP not_accepted event, it will do re-pairing.
LMP is implemented in the Bluetooth chip's firmware and not the kernel.
Regards
Marcel
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: BT LMP
2012-07-05 7:20 ` Marcel Holtmann
@ 2012-07-05 7:42 ` victor yeo
2012-07-05 8:25 ` Keren, Doron
0 siblings, 1 reply; 6+ messages in thread
From: victor yeo @ 2012-07-05 7:42 UTC (permalink / raw)
To: Marcel Holtmann; +Cc: linux-bluetooth
Hi Marcel,
When LMP_not_accepted is received by Bluetooth Chip's firmware, it
will send a HCI event to the linux kernel bluetooth portion. Do i
understand correctly? What is the HCI event name?
Thanks,
Victor
On Thu, Jul 5, 2012 at 3:20 PM, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Victor,
>
>> Anyone know which part of linux kernel processes the LMP au_rand and
>> LMP not_accepted event?
>>
>> I want to modify the Bluetooth kernel code so that when it receives
>> LMP not_accepted event, it will do re-pairing.
>
> LMP is implemented in the Bluetooth chip's firmware and not the kernel.
>
> Regards
>
> Marcel
>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: BT LMP
2012-07-05 7:42 ` victor yeo
@ 2012-07-05 8:25 ` Keren, Doron
2012-07-05 9:10 ` victor yeo
0 siblings, 1 reply; 6+ messages in thread
From: Keren, Doron @ 2012-07-05 8:25 UTC (permalink / raw)
To: victor yeo; +Cc: linux-bluetooth
Hi Victor,
The LMP not_accepted event will lead to Authentication failure.
Some devices will then initiate disconnection with error code :
Authentication Failure error code (0x05).
Thanks,
Doron Keren
Texas Instruments
> -----Original Message-----
> From: linux-bluetooth-owner@vger.kernel.org [mailto:linux-bluetooth-
> owner@vger.kernel.org] On Behalf Of victor yeo
> Sent: Thursday, July 05, 2012 10:43 AM
> To: Marcel Holtmann
> Cc: linux-bluetooth@vger.kernel.org
> Subject: Re: BT LMP
>
> Hi Marcel,
>
> When LMP_not_accepted is received by Bluetooth Chip's firmware, it
> will send a HCI event to the linux kernel bluetooth portion. Do i
> understand correctly? What is the HCI event name?
>
> Thanks,
> Victor
>
> On Thu, Jul 5, 2012 at 3:20 PM, Marcel Holtmann <marcel@holtmann.org>
> wrote:
> > Hi Victor,
> >
> >> Anyone know which part of linux kernel processes the LMP au_rand and
> >> LMP not_accepted event?
> >>
> >> I want to modify the Bluetooth kernel code so that when it receives
> >> LMP not_accepted event, it will do re-pairing.
> >
> > LMP is implemented in the Bluetooth chip's firmware and not the kernel.
> >
> > Regards
> >
> > Marcel
> >
> >
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: BT LMP
2012-07-05 8:25 ` Keren, Doron
@ 2012-07-05 9:10 ` victor yeo
2012-07-05 10:19 ` Keren, Doron
0 siblings, 1 reply; 6+ messages in thread
From: victor yeo @ 2012-07-05 9:10 UTC (permalink / raw)
To: Keren, Doron; +Cc: linux-bluetooth
On Thu, Jul 5, 2012 at 4:25 PM, Keren, Doron <doronkeren@ti.com> wrote:
> Hi Victor,
>
> The LMP not_accepted event will lead to Authentication failure.
> Some devices will then initiate disconnection with error code :
> Authentication Failure error code (0x05).
>
> Thanks,
> Doron Keren
> Texas Instruments
>
>> -----Original Message-----
>> From: linux-bluetooth-owner@vger.kernel.org [mailto:linux-bluetooth-
>> owner@vger.kernel.org] On Behalf Of victor yeo
>> Sent: Thursday, July 05, 2012 10:43 AM
>> To: Marcel Holtmann
>> Cc: linux-bluetooth@vger.kernel.org
>> Subject: Re: BT LMP
>>
>> Hi Marcel,
>>
>> When LMP_not_accepted is received by Bluetooth Chip's firmware, it
>> will send a HCI event to the linux kernel bluetooth portion. Do i
>> understand correctly? What is the HCI event name?
>>
>> Thanks,
>> Victor
>>
>> On Thu, Jul 5, 2012 at 3:20 PM, Marcel Holtmann <marcel@holtmann.org>
>> wrote:
>> > Hi Victor,
>> >
>> >> Anyone know which part of linux kernel processes the LMP au_rand and
>> >> LMP not_accepted event?
>> >>
>> >> I want to modify the Bluetooth kernel code so that when it receives
>> >> LMP not_accepted event, it will do re-pairing.
>> >
>> > LMP is implemented in the Bluetooth chip's firmware and not the kernel.
>> >
>> > Regards
>> >
>> > Marcel
>> >
>> >
>> --
Hi Doron,
Will the hci_auth_complete_evt() function in net/bluetooth/hci_event.c
handle the hci error code?
Thanks,
Victor
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: BT LMP
2012-07-05 9:10 ` victor yeo
@ 2012-07-05 10:19 ` Keren, Doron
0 siblings, 0 replies; 6+ messages in thread
From: Keren, Doron @ 2012-07-05 10:19 UTC (permalink / raw)
To: victor yeo; +Cc: linux-bluetooth
> -----Original Message-----
> From: victor yeo [mailto:victoryeo1974@gmail.com]
> Sent: Thursday, July 05, 2012 12:10 PM
> To: Keren, Doron
> Cc: linux-bluetooth@vger.kernel.org
> Subject: Re: BT LMP
>
> On Thu, Jul 5, 2012 at 4:25 PM, Keren, Doron <doronkeren@ti.com> wrote:
> > Hi Victor,
> >
> > The LMP not_accepted event will lead to Authentication failure.
> > Some devices will then initiate disconnection with error code :
> > Authentication Failure error code (0x05).
> >
> > Thanks,
> > Doron Keren
> > Texas Instruments
> >
> >> -----Original Message-----
> >> From: linux-bluetooth-owner@vger.kernel.org [mailto:linux-bluetooth-
> >> owner@vger.kernel.org] On Behalf Of victor yeo
> >> Sent: Thursday, July 05, 2012 10:43 AM
> >> To: Marcel Holtmann
> >> Cc: linux-bluetooth@vger.kernel.org
> >> Subject: Re: BT LMP
> >>
> >> Hi Marcel,
> >>
> >> When LMP_not_accepted is received by Bluetooth Chip's firmware, it
> >> will send a HCI event to the linux kernel bluetooth portion. Do i
> >> understand correctly? What is the HCI event name?
> >>
> >> Thanks,
> >> Victor
> >>
> >> On Thu, Jul 5, 2012 at 3:20 PM, Marcel Holtmann <marcel@holtmann.org>
> >> wrote:
> >> > Hi Victor,
> >> >
> >> >> Anyone know which part of linux kernel processes the LMP au_rand and
> >> >> LMP not_accepted event?
> >> >>
> >> >> I want to modify the Bluetooth kernel code so that when it receives
> >> >> LMP not_accepted event, it will do re-pairing.
> >> >
> >> > LMP is implemented in the Bluetooth chip's firmware and not the
> kernel.
> >> >
> >> > Regards
> >> >
> >> > Marcel
> >> >
> >> >
> >> --
>
> Hi Doron,
>
> Will the hci_auth_complete_evt() function in net/bluetooth/hci_event.c
> handle the hci error code?
>
> Thanks,
> Victor
Hi Victor,
As I can read in the code the hci_auth_complete_evt() call mgmt_auth_failed() on failure. The mgmt_auth_failed() function just prints
The fail status number. You can add your own code to do re-pairing several times.
Thanks,
Doron
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2012-07-05 10:19 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-07-05 6:00 BT LMP victor yeo
2012-07-05 7:20 ` Marcel Holtmann
2012-07-05 7:42 ` victor yeo
2012-07-05 8:25 ` Keren, Doron
2012-07-05 9:10 ` victor yeo
2012-07-05 10:19 ` Keren, Doron
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.