On 7/24/2023 16:24, Martin Kohn wrote:
Hello Lars,
a little background: We are just a company that uses the Quectel modems in our products. So far, I was not able to get more information from Quectel apart from
that it is the same module with a different product ID. Unfortunately, they will stick to the new product ID.
Yes it is the same module but with a different interface layout so you
can not just copy and paste the option driver entry for the old device.
So, my approach was to clone to entry for EM05-G with the old id. With these changes it is working.
It does work as ppp dialup modem which limits its bandwidth to 30-50Mbps
(host dependent) but this is a LTE CAT4 device which is able to transfer
150Mbps down and 50Mbs up, they always have some kind of direct net
interface.
On the EM05Gv2 that is interface #4 which should be reserved in the
option driver and added in the qmi_wwan driver.
The older EM05G had qmi_wwan on interface #6 which is why that
interface was reserved in the option driver.
If you let the option driver bind to the net interface then the net
driver can not bind to that interface, that's why the net interface must
be declared as reserved (RSVD) in the option driver.
But you are right. I removed RSVP(6) option entirely and it also works fine.
I currently trying to get on hold of a module with the old product ID (might be difficult), because I think the driver for the old revision might then also have the same issue.
Please provide any feedback you can, it would be greatly appreciated, our customers are eager to have the modem working in Linux again.
Any changes from your initial patch should have a revision number in the
email header and there should be an explanation in the email body below
the tear line what has changed from revision to revision. Since you did
not revision your previous patches then your next attempt should be a v2
patch.
Greetings,
Martin Kohn
