[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230607104350.03a51711@kernel.org>
Date: Wed, 7 Jun 2023 10:43:50 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
Cc: davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com,
mhi@...ts.linux.dev, linux-arm-msm@...r.kernel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
loic.poulain@...aro.org
Subject: Re: [PATCH v2 0/2] Add MHI Endpoint network driver
On Wed, 7 Jun 2023 22:41:53 +0530 Manivannan Sadhasivam wrote:
> > In any case, I'm opposed to reuse of the networking stack to talk
> > to firmware. It's a local device. The networking subsystem doesn't
> > have to cater to fake networks. Please carry:
> >
> > Nacked-by: Jakub Kicinski <kuba@...nel.org>
> >
> > if there are future submissions.
>
> Why shouldn't it be? With this kind of setup one could share the data connectivity
> available in the device with the host over IP tunneling. If the IP source in the
> device (like modem DSP) has no way to be shared with the host, then those IP
> packets could be tunneled through this interface for providing connectivity to
> the host.
>
> I believe this is a common usecase among the PCIe based wireless endpoint
> devices.
We can handwave our way into many scenarios and terrible architectures.
I don't see any compelling reason to merge this.
Powered by blists - more mailing lists