Re: Odd l2cap_sock.c Code?

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

Subject: Re: Odd l2cap_sock.c Code?
From: Dylan Taft <dylanetaft@xxxxxxxxx>
Date: Mon, 12 Nov 2018 00:25:52 -0500
In-reply-to: <CAKz1w-kFDGH-zfYu1GjoJqfs+9uvHvxnG=qwgj8EscAidDNd1w@mail.gmail.com>
References: <CAKz1w-==yXd4EL39ULE6bcYU3fTpZB9D0EqdgRhq4L38kVzYEg@mail.gmail.com> <CAKz1w-kFDGH-zfYu1GjoJqfs+9uvHvxnG=qwgj8EscAidDNd1w@mail.gmail.com>

I think I was able to figure my own confusion out after browsing the
bluez userspace tools.  The kernel does not handle anything above the
L2CAP layer.  This is ATT and that negotiation is in user space,
nothing to do with sockopts!

Follow-Ups:
- Re: Odd l2cap_sock.c Code?
  - From: Luiz Augusto von Dentz

References:
- Odd l2cap_sock.c Code?
  - From: Dylan Taft
- Re: Odd l2cap_sock.c Code?
  - From: Dylan Taft

Prev by Date: Re: Odd l2cap_sock.c Code?
Next by Date: Re: Odd l2cap_sock.c Code?
Previous by thread: Re: Odd l2cap_sock.c Code?
Next by thread: Re: Odd l2cap_sock.c Code?
Index(es):
- Date
- Thread

[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