[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <ZXTIPS.5HTA0G5SXE7D3@unrealasia.net>
Date: Sat, 04 Jan 2025 00:32:23 +0800
From: Muhammad Nuzaihan <zaihan@...ealasia.net>
To: Sergey Ryazanov <ryazanov.s.a@...il.com>
Cc: netdev@...r.kernel.org, Loic Poulain <loic.poulain@...aro.org>,
Johannes Berg <johannes@...solutions.net>, Andrew Lunn <andrew@...n.ch>,
Slark Xiao <slark_xiao@....com>
Subject: Re: [PATCH] Add NMEA GPS character device for PCIe MHI Quectel Module
to read NMEA statements.
Hi Sergey,
Apparently after a new recompilation the entire kernel and modules
fixes the problem with wwan0nmea0 port get attached at bootup. I had
previously only compiled modules without the kernel during development.
Before that i went to debug several wwan_core.c device wwan_create_port
and wwan_create_dev functions to see what's going on not being loaded
at bootup and seemed that a recompile the entire kernel and module
fixes that. Checked my diffs and saw no changes.
So now, everything works perfectly at bootup and I have to tell
ModemManager to ignore NMEA port type. So booting up with a fresh new
kernel and module gets my 5G working automatically at boot.
No need to unload and reload of the kernel modules and configuring with
AT commands to wwan0at0 with scripts, now everything works seamlessly.
So to ensure ModemManager can work with this setup, i would add a new
udev rule for ModemManager to not probe wwan0nmea0 port (which i think
i will submit this to ModemManger project):
# ModemManager ignore NMEA
ATTRS{vendor}=="0x1eac", ATTRS{device}=="0x1007", ATTR{type}=="NMEA",
ENV{ID_MM_PORT_IGNORE}="1"
I'll submit the "cleaned up" v3 nmea patch later tomorrow, it's a
pretty small patch. (It's 12AM now here in Malaysia)
- Zaihan
On Fri, Jan 3 2025 at 03:15:34 AM +0800, Muhammad Nuzaihan
<zaihan@...ealasia.net> wrote:
> Hi Sergey,
>
>
> On Fri, Jan 3 2025 at 02:05:19 AM +0800, Muhammad Nuzaihan
> <zaihan@...ealasia.net> wrote:
>> Hi Sergey,
>>
Powered by blists - more mailing lists