I have a Prolink PH-300 dongle.
With usbserial.ko, NM/MM probe correctly and use /dev/ttyUSB2
With option.ko, NM/MM probe incorrectly and use /devttyUSB1.
The latter is pretty consistent, but once in a while NM/MM will use ttyUSB2
correctly.
See below when it works.
I can dial and connect with ma
This fixes a bug with decoding SMS messages with alphanumeric sender
addresses and some excessive pickiness in decoding the protocol field.
- Nathan
From 9fc44d9d0acac95b079e0ac7211d3092824226b0 Mon Sep 17 00:00:00 2001
From: Nathan Williams
Date: Wed, 25 May 2011 17:08:15 -0400
Subject: [PAT
>D-BUS is not a GUI thing. It is the IPC that NM uses to communicate
>with everything,
>including the daemons it manages (modemmanager, wpa_supplicant, pppd
>etc) and the command-line client. So even if you hacked the source and
>removed d-bus, the resulting
>NetworkManager would not be able to man
On Wed, May 25, 2011 at 2:59 PM, wrote:
> Hi list,
> I am cross-compiling nm for an embedded target. I don't require
> any GNOME/GTK/GUI/applet functionality. Do I still require dbus-glib ? If not,
> how can I remove that from the config ?
D-BUS is not a GUI thing. It is the IPC that NM uses to
Hi list,
I am cross-compiling nm for an embedded target. I don't require
any GNOME/GTK/GUI/applet functionality. Do I still require dbus-glib ? If not,
how can I remove that from the config ?
Also what would be appropriate "--with-distro" string to use for
configure ? ... the target does not use
