[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161216190759.GA1163@sisyphus.home.austad.us>
Date: Fri, 16 Dec 2016 20:07:59 +0100
From: Henrik Austad <henrik@...tad.us>
To: David Miller <davem@...emloft.net>
Cc: gvrose8192@...il.com, linux-kernel@...r.kernel.org,
richardcochran@...il.com, haustad@...co.com,
linux-media@...r.kernel.org, alsa-devel@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [TSN RFC v2 0/9] TSN driver for the kernel
On Fri, Dec 16, 2016 at 01:20:57PM -0500, David Miller wrote:
> From: Greg <gvrose8192@...il.com>
> Date: Fri, 16 Dec 2016 10:12:44 -0800
>
> > On Fri, 2016-12-16 at 18:59 +0100, henrik@...tad.us wrote:
> >> From: Henrik Austad <haustad@...co.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
Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)
Powered by blists - more mailing lists