8e1c6cfe78
The `gpsmon` tool is really deprecated now, after years of its use being discouraged. The `cgps` tool can be used as a replacement, with the added benefit that it's more power-efficient because it doesn't reparse with a slightly different parses like `gpsmon` did. Drop patch that was applied upstream in https://gitlab.com/gpsd/gpsd/-/merge_requests/406 Upstream changelog: 3.26.1: 17 May 2025 Increment libgps version Update Debian Trixie in build.adoc Fix buffer overrun in cgps. Make gpsmon deprecation slightly more obvious. Fix some *BSD compiler warnings Fix numerous typos. 3.26: 11 May 2025 Handle NTRIPv2 that comes in "chunks". Add many UBX decodes. Mostly in ubxtool, some in gpsd. Improve TSIP and UBX initialization. Gather Antenna Status (ant_stat) and Jamming (jam) and send to JSON. Always build u-blox, RTCM104V2, RTCM104V3 drivers. Add partial support for badly documented ALLYSTAR GNSS messages. Add minimal support for Unicore GNSS messages. Add minimal support for CASIC GNSS messages. Add minimal support for buggy Inertial Sense GNSS messages. Try to work better as non-root using non-standard "capabilities". Add SUBSYSTEM=gnss rule to gpsd.rules Moved ntploggps from NTPSec to GPSD and renamed to gpslogntp. Fix many build, Coverity, and Codacy warnings. Improved Python interface for the lexer. Add support for new BeiDou PRNs and subframes. Officially deprecate gpsmon. Improve support for NMEA 4.11 (a stealthy moving target). Remove Oceanserver IMU support. Never worked well. Always with build ubx, NMEA 103, rtcm104v2 and rtcm104v3 support. Add support for jamming detection. Add Go client example. Add support for RTCM3.2 Note: The new "chunk" code led to a short lived bug that led to CVE-2023-43628, a buffer overrun. That bug never appeared in any gpsd release. Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Khem Raj <raj.khem@gmail.com> |
||
|---|---|---|
| .. | ||
| classes | ||
| conf | ||
| dynamic-layers | ||
| files | ||
| lib/oeqa/selftest/cases | ||
| licenses | ||
| recipes-benchmark | ||
| recipes-bsp | ||
| recipes-connectivity | ||
| recipes-core | ||
| recipes-crypto | ||
| recipes-dbs | ||
| recipes-devtools | ||
| recipes-extended | ||
| recipes-gnome | ||
| recipes-graphics | ||
| recipes-kernel | ||
| recipes-multimedia | ||
| recipes-navigation | ||
| recipes-networking/cyrus-sasl | ||
| recipes-printing | ||
| recipes-security | ||
| recipes-shells | ||
| recipes-support | ||
| recipes-test | ||
| COPYING.MIT | ||
| README.md | ||
| SECURITY.md | ||
meta-oe
This layer depends on:
URI: git://github.com/openembedded/openembedded-core.git branch: master
luajit recipe requires host compiler to be able to generate 32bit code when target is 32bit e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed packages to fullfit this might have different names on different host distributions e.g. on archlinux based distributions install prerequisites like below
pacman -S lib32-gcc-libs lib32-glibc
Ubuntu sudo apt-get install gcc-multilib linux-libc-dev:i386
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'
When sending single patches, please use something like: 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][PATCH"'
You are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded to share your patches, this is preferred for patch sets consisting of more than one patch.
Note, it is discouraged to send patches via GitHub pull request system. Such patches get less attention from developers and can be mishandled or not reviewed properly. Please use emails instead. For exemple, you can use 'git request-pull' to generate an email referencing your git repository.
Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well, 'git fetch ' works the same on all of them. We recommend GitHub because it is free, easy to use, has been proven to be reliable and has a really good web GUI.
Layer maintainer: Khem Raj raj.khem@gmail.com