From: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
To: "Bjørn Mork" <bjorn@mork.no>, "Daniele Palmas" <dnlplm@gmail.com>
Cc: Dan Williams <dcbw@redhat.com>, netdev@vger.kernel.org
Subject: Re: Qualcomm rmnet driver and qmi_wwan
Date: Mon, 11 Jun 2018 17:00:20 -0600 [thread overview]
Message-ID: <095a8f087276ead358d6534b29300f02@codeaurora.org> (raw)
In-Reply-To: <87zi01w753.fsf@miraculix.mork.no>
> both patches work properly for me.
>
> Maybe it could be helpful in the first patch to add a print when
> pass-through setting fails if raw-ip has not been set, just to let the
> user know what is happening.
>
Thanks for testing Daniele.
I can add an error message there when pass through mode setting fails.
Will you be submitting the patch for iproute2. Otherwise, I can do so
a bit later.
> Maybe rmnet_is_real_dev_registered(dev->net) instead, since we use that
> elsewhere in this function?
>
> Like Daniele said: It would be good to have some way to know when the
> rawip condition fails. Or even better: Automatically force rawip mode
> when the rmnet driver attaches. But that doesn't seem possible? No
> notifications or anything when an rx handler is registered?
>
> Hmm, looking at this I wonder: Is the rawip check really necessary?
> You
> skip all the extra rawip code in the driver anyway, so I don't see how
> it matters. But maybe the ethernet header_ops are a problem?
>
> And I wonder about using skb->dev here. Does that really work? I
> didn't think we set that until later. Why not use dev->net instead?
>
>
Hi Bjørn
Yes, I will switch to using dev->net.
There doesnt seem to be a net device notifier event when the rx
registration
happens.
If the dev type is ethernet, rmnet driver will try to remove the first
14
bytes since it assumes an ethernet header is present in the packet.
Hence the
need for raw ip mode in qmi_wwan.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2018-06-11 23:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 11:38 Qualcomm rmnet driver and qmi_wwan Daniele Palmas
2018-02-21 19:47 ` Subash Abhinov Kasiviswanathan
2018-02-22 10:44 ` Daniele Palmas
2018-06-05 9:38 ` Daniele Palmas
2018-06-05 14:54 ` Dan Williams
2018-06-05 17:38 ` Subash Abhinov Kasiviswanathan
2018-06-08 10:21 ` Daniele Palmas
2018-06-08 17:19 ` Subash Abhinov Kasiviswanathan
2018-06-08 19:10 ` Bjørn Mork
2018-06-09 2:19 ` Subash Abhinov Kasiviswanathan
2018-06-09 7:22 ` Daniele Palmas
2018-06-09 17:55 ` Subash Abhinov Kasiviswanathan
2018-06-11 14:30 ` Daniele Palmas
2018-06-11 17:43 ` Bjørn Mork
2018-06-11 23:00 ` Subash Abhinov Kasiviswanathan [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=095a8f087276ead358d6534b29300f02@codeaurora.org \
--to=subashab@codeaurora.org \
--cc=bjorn@mork.no \
--cc=dcbw@redhat.com \
--cc=dnlplm@gmail.com \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.