lkml.org 
[lkml]   [2018]   [Jan]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    Date
    SubjectRe: [PATCH] Bluetooth: 6lowpan: Fix disconnect bug in 6lowpan
    Hi,

    2018-01-17 7:15 GMT-05:00 Luiz Augusto von Dentz <luiz.dentz@gmail.com>:
    > Hi,
    >
    > On Wed, Jan 17, 2018 at 1:47 AM, Guo Yi <yi2010.guo@samsung.com> wrote:
    >> This patch fix the bluetooth 6lowpan disconnect fail bug.
    >>
    >> The type of the same address type have different define value in HCI layer
    >> and L2CAP layer.That makes disconnect fail due to wrong network type.User
    >> will not be able to disconnect from console with the network type that used
    >> in connect.
    >>
    >> This patch add a var lookup_type, and covert the channel address type to
    >> HCI address type. By these means, user can disconnect successfuly.
    >>
    >> Signed-off-by: Guo Yi <yi2010.guo@samsung.com>
    >
    > While this fix seems alright the debugfs interface was never meant for
    > production, in fact we are working on a replacement:
    >

    Is the new API fixing the issue that the 6LoWPAN device creation is
    done by iproute e.g.:

    ip link add link wpan0 name lowpan0 type lowpan

    or is there a special bluetooth API call needed, like the current case
    with debugfs.
    I know hcis are not netdevs, but it bothers me that we running into
    two different worlds on how to deal with that and it just requires
    "more" special bluetooth specific handling in user space applications.
    Later more "netdev" capable link layers will maybe support 6LoWPAN and
    then bluetooth might the only subsystem where different handling is
    needed to do such job like that.

    We maybe need to support a special handling in "ip link add" to map to
    bluetooth instead moving that to people in user space?

    - Alex

    \
     
     \ /
      Last update: 2018-01-18 00:21    [W:4.139 / U:0.008 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site