When performing devtool check-upgrade-status, UNKNOWN_BROKEN status appears.
On the upstream source repository, releases are not identified by tags. So,
UPSTREAM_CHECK_COMMITS is set to 1, to find the latest upstream update.
Signed-off-by: Alexandre Truong <alexandre.truong@smile.fr>
Reviewed-by: Yoann Congal <yoann.congal@smile.fr>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Support of new kernel features:
-----------------------------------
j1939: make use of new RX UAPI
isotp: rework FRAME_TXTIME handling and buffer size (Linux v5.18+)
isotp: add support for transmission without flow control (Linux v5.19+)
mcp251xfd-dump: add support for dumps created with Linux kernel >= v5.18
can-calc-bit-timing: import bit timing calculation algorithm from v5.19
cangen: add support for SO_TXTIME
includes: update to Linux 6.2 upstream (with CAN XL data structures)
Improvements and features:
--------------------------------
canfdtest: Add extended frame format / message length / FD / BRS support
can-calc-bit-timing: add support for calculation of CAN-FD bit timings
cangen: add option for absolute timeouts
cangen: new generation mode - partially randomized payload (-D)
slcan: increase BTR char limit to 8 for 32bit BTR
log asc converter: support len8_dlc for Classical CAN frames
candump: handle individual logfile name for stdout
cansniffer: add CAN FD support
cansniffer: make ASCII output switchable in CAN FD mode
canplayer: introduce option to limit the number of processed frames
Fixes:
-----------------------
candump: print number of dropped frames as unsigned values
candump: reserve enough space for ctrlmsg
candump: fix accidentally disabled traffic timeout feature
lib: fix seperator in snprintf_error_data
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This patch updates SRC_URIs using git to include branch=master if no branch is set
and also to use protocol=https for github urls as generated by the conversion script
in OE-Core.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This replicates the fix from canutils.bb, for the same issue. See the link
in the comment for details.
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This is the result of automated script (0.9.1) conversion:
oe-core/scripts/contrib/convert-overrides.py .
converting the metadata to use ":" as the override character instead of "_".
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
This now included in kernels 5.10+ so on master and linux-yocto we
really do not need this recipe, but there still might be older kernels
interfaced with meta-oe master, so they can still use it.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
It is needed for 5.2 to 5.10 kernel
Can-isotp is now upstream from kernel 5.10 onwards.
Use kernel config file instead. This is only provided for legacy kernels.
For kernel 5.10 onwards use kernel defconfig option for ISO 15765-2 CAN
transport and do not use can-isotp recipe. You will get "The file
/usr/include/linux/can/isotp.h is installed by both linux-libc-headers
and can-isotp" error using this recipe with kernel >= 5.10
Signed-off-by: Khem Raj <raj.khem@gmail.com>
libsocketcan offers two configuration options.
debug: Compile for debugging. Off by default.
error-log: Logging of error events to stderr. On by default.
Because error-log is on by default the package config option is
no-error-log to retain existing recipe behavior.
Signed-off-by: Mark Jonas <toertel@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
canutils provides applications which conflict with can-utils recipe.
update-alternatives helps fix this when both are installed
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Make sure PNBLACKLIST assignments in recipe files use weak assignment,
so they can be overridden in, for example, local.conf files.
Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Also:
- remove patch applied upstream
- update the hash of the license because the file
now contains a SPDX license identifier
Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Linux Kernel Module for ISO 15765-2:2016 CAN transport protocol.
CAN Transport Protocol offers support for segmented Point-to-Point
communication between CAN nodes via two defined CAN Identifiers. This protocol
driver implements data transfers according to ISO 15765-2.
This recipe provides can-isotp.ko kernel module.
Signed-off-by: Andrea Galbusera <gizero@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
gitorious.org that is hosting can-utils has stopped providing git protocol.
That https is provided instead. This will change protocol to get can-utils
of source code from git to https.
Signed-off-by: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Changes:
- rename SUMMARY with length > 80 to DESCRIPTION
- rename DESCRIPTION with length < 80 to (non present tag) SUMMARY
- drop final point character at the end of SUMMARY string
- remove trailing whitespace of SUMMARY line
Note: don't bump PR
Signed-off-by: Matthieu Crapet <Matthieu.Crapet@ingenico.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
- use git hash instead of tag
- backport "candump: Add error frame's handling"
Signed-off-by: Eric Bénard <eric@eukrea.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
It's not necessary to specify the protocol parameter when it's the
default protocol for the fetcher, e.g. the default protocol for
git fetcher it git, "protocol=git" isn't needed.
Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* This change is only aesthetic (unlike indentation in Python
tasks).
* Some recipes were using tabs.
* Some were using 8 spaces.
* Some were using mix or different number of spaces.
* Make them consistently use 4 spaces everywhere.
* Yocto styleguide advises to use tabs (but the only reason to keep
tabs is the need to update a lot of recipes). Lately this advice
was also merged into the styleguide on the OE wiki.
* Using 4 spaces in both types of tasks is better because it's less
error prone when someone is not sure if e.g.
do_generate_toolchain_file() is Python or shell task and also allows
to highlight every tab used in .bb, .inc, .bbappend, .bbclass as
potentially bad (shouldn't be used for indenting of multiline
variable assignments and cannot be used for Python tasks).
* Don't indent closing quote on multiline variables
we're quite inconsistent wheater it's first character on line
under opening quote or under first non-whitespace character in
previous line.
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Acked-by: Koen Kooi <koen@dominion.thruhere.net>
"beginline" is the correct parameter name. Checksums have been updated
where necessary (i.e. if the beginning line was something other than the
default of 1).
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Alexandre Truong
Khem Raj
Martin Jansa
Wang Mingyu
Richard Purdie
Alexander Kanavin
David Sterling
zangrc
Sean Nyekjaer
zangrc
Mark Jonas
Robert P. J. Day
Denys Dmytriyenko
William A. Kennington III via Openembedded-devel
Oleksandr Kravchuk
Andrea Galbusera
Chen Qi
Christopher Larson
Stefan Müller-Klieser
Nobuhiro Iwamatsu
Lauren Post
Matthieu CRAPET
Eric BENARD
Jackie Huang
Paul Eggleton
Koen Kooi