Guilhem Bonnefille wrote: > An other significant bug, IMHO, is the #2766373: GPS on ttyUSB3 is not > accessable > https://sourceforge.net/tracker/?func=detail&aid=2766373&group_id=83870&atid=570954 > > One solution is to change the current PARAM_PORT parameter nature. > Currently, it is an integer, used as index for a predefined list of > ports. I suggest to replace it with raw string, storing the effective > port value ("/dev/ttyUSB3" for example). > > Such change will brake compatibility between versions. Perhaps can we > find a way to stay ascendant compatible.
Do we need that at all? If I remember right you should be able to request a list of known devices from gpsd - you could display these then. Configuring gpsd properly to use devices is nothing viking should need to do. See http://gpsd.berlios.de/gpsd.html - the command is ?DEVICES for the new protocol. Actually I'm not sure if theres a proper replacement for that in the old protocol, also I think it doesn't make much sense to be backward compatible forever, so probably just drop the device selection when building viking with an old libgps, instead just use the data as it comes from gpsd without any filtering by device. -- Bernd Zeimetz Debian GNU/Linux Developer http://bzed.de http://www.debian.org GPG Fingerprints: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79 ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
