From: Henrik Austad <henrik@austad.us>
To: David Miller <davem@davemloft.net>
Cc: gvrose8192@gmail.com, linux-kernel@vger.kernel.org,
richardcochran@gmail.com, haustad@cisco.com,
linux-media@vger.kernel.org, alsa-devel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [TSN RFC v2 0/9] TSN driver for the kernel
Date: Fri, 16 Dec 2016 20:07:59 +0100 [thread overview]
Message-ID: <20161216190759.GA1163@sisyphus.home.austad.us> (raw)
In-Reply-To: <20161216.132057.1771215556712298530.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
On Fri, Dec 16, 2016 at 01:20:57PM -0500, David Miller wrote:
> From: Greg <gvrose8192@gmail.com>
> Date: Fri, 16 Dec 2016 10:12:44 -0800
>
> > On Fri, 2016-12-16 at 18:59 +0100, henrik@austad.us wrote:
> >> From: Henrik Austad <haustad@cisco.com>
> >>
> >>
> >> The driver is directed via ConfigFS as we need userspace to handle
> >> stream-reservation (MSRP), discovery and enumeration (IEEE 1722.1) and
> >> whatever other management is needed. This also includes running an
> >> appropriate PTP daemon (TSN favors gPTP).
> >
> > I suggest using a generic netlink interface to communicate with the
> > driver to set up and/or configure your drivers.
> >
> > I think configfs is frowned upon for network drivers. YMMV.
>
> Agreed.
Ok - thanks!
I will have look at netlink and see if I can wrap my head around it and if
I can apply it to how to bring the media-devices up once the TSN-link has
been configured.
Thanks! :)
--
Henrik Austad
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-12-16 19:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 17:59 [TSN RFC v2 0/9] TSN driver for the kernel henrik
2016-12-16 17:59 ` [TSN RFC v2 1/9] igb: add missing fields to TXDCTL-register henrik
2016-12-16 17:59 ` [TSN RFC v2 2/9] TSN: add documentation henrik
2016-12-16 17:59 ` [TSN RFC v2 3/9] TSN: Add the standard formerly known as AVB to the kernel henrik
2016-12-16 17:59 ` [TSN RFC v2 4/9] Adding TSN-driver to Intel I210 controller henrik
2016-12-16 17:59 ` [TSN RFC v2 5/9] Add TSN header for the driver henrik
2016-12-16 22:09 ` Richard Cochran
2016-12-17 8:53 ` Henrik Austad
2016-12-16 17:59 ` [TSN RFC v2 6/9] Add TSN machinery to drive the traffic from a shim over the network henrik
2016-12-16 17:59 ` [TSN RFC v2 7/9] Add TSN event-tracing henrik
2016-12-16 17:59 ` [TSN RFC v2 8/9] AVB ALSA - Add ALSA shim for TSN henrik
2016-12-16 17:59 ` [TSN RFC v2 9/9] MAINTAINERS: add TSN/AVB-entries henrik
2016-12-16 18:12 ` [TSN RFC v2 0/9] TSN driver for the kernel Greg
2016-12-16 18:20 ` David Miller
2016-12-16 19:07 ` Henrik Austad [this message]
2016-12-16 22:05 ` Richard Cochran
2016-12-17 9:05 ` Henrik Austad
2016-12-17 20:09 ` Richard Cochran
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161216190759.GA1163@sisyphus.home.austad.us \
--to=henrik@austad.us \
--cc=alsa-devel@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=gvrose8192@gmail.com \
--cc=haustad@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).