[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMZdPi_veiVaQYBcu9o0GqbmUcYtkL4NawOo2AGPKxfmaNrdhg@mail.gmail.com>
Date: Wed, 23 Mar 2022 18:06:03 +0100
From: Loic Poulain <loic.poulain@...aro.org>
To: Sergey Ryazanov <ryazanov.s.a@...il.com>
Cc: "Kumar, M Chetan" <m.chetan.kumar@...ux.intel.com>,
Johannes Berg <johannes@...solutions.net>,
netdev@...r.kernel.org, Jakub Kicinski <kuba@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
"Sudi, Krishna C" <krishna.c.sudi@...el.com>,
Intel Corporation <linuxwwan@...el.com>
Subject: Re: net: wwan: ethernet interface support
On Sat, 19 Mar 2022 at 19:34, Sergey Ryazanov <ryazanov.s.a@...il.com> wrote:
>
> Hello,
>
> On Sat, Mar 19, 2022 at 6:21 PM Kumar, M Chetan
> <m.chetan.kumar@...ux.intel.com> wrote:
> > Release16 5G WWAN Device need to support Ethernet interface for TSN requirement.
> > So far WWAN interface are of IP type. Is there any plan to scale it to support
> > ethernet interface type ?
>
> What did you mean when you talked about supporting interfaces of Ethernet type?
>
> The WWAN subsystem provides an interface for users to request the
> creation of a network interface from a modem driver. At the moment,
> all modem drivers that support the WWAN subsystem integration create
> network interfaces of the ARPHRD_NONE or ARPHRD_RAWIP type. But it is
> up to the driver what type of interface it will create. At any time,
> the driver can decide to create an ARPHRD_ETHER network interface, and
> it will be Ok.
Agree, WWAN does not require a specific type, so you can do whatever
you want in the newlink callback.
Should a modem/driver be able to expose mixed interface types (e.g. ip
+ eth), in that case we probably need to add extra param to newlink.
>
> > Any thought process on TSN requirement support.
>
> Could you please elaborate what specific protocol or feature should be
> implemented for it?
Powered by blists - more mailing lists