From: "Bjørn Mork" <bjorn@mork.no>
To: Stefan x Nilsson <stefan.x.nilsson@axis.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
<netdev@vger.kernel.org>, <linux-usb@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <kernel@axis.com>
Subject: Re: [PATCH net-next] qmi_wwan: Add rawip module param
Date: Tue, 12 Sep 2023 11:45:36 +0200 [thread overview]
Message-ID: <874jjzafnj.fsf@miraculix.mork.no> (raw)
In-Reply-To: <42522712-b739-3db4-9111-a4b378a65809@axis.com> (Stefan x. Nilsson's message of "Tue, 12 Sep 2023 09:44:26 +0200")
Stefan x Nilsson <stefan.x.nilsson@axis.com> writes:
> Would a quirk on the affected modem be an better/acceptable solution?
More acceptable but still needs justification.
I'm probably missing something, but I don't see the described issue even
if I assume a device crashing if it sees an ethernet header.
The netdev and associated chardev are created when a USB device is
connected. The device knows nothing about this. It answers a few USB
descriptor requests and that's it. The host is free to switch the
netdev to raw-ip framing before bringing it up. There is no need to
send any frames with eithernet header. There is no relationship between
framing and the QMI control channel. But the host is in complete
control of any communication there too, so it wouldn't be a problam if
there were.
Bjørn
prev parent reply other threads:[~2023-09-12 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 7:04 Stefan x Nilsson
2023-09-12 7:22 ` Bjørn Mork
2023-09-12 7:44 ` Stefan x Nilsson
2023-09-12 9:45 ` Bjørn Mork [this message]
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=874jjzafnj.fsf@miraculix.mork.no \
--to=bjorn@mork.no \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel@axis.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stefan.x.nilsson@axis.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
all inboxes | Powered by JetHome®