diff options
author | Ming Liu <ming.liu@toradex.com> | 2023-05-08 17:01:34 +0200 |
---|---|---|
committer | Ming Liu <ming.liu@toradex.com> | 2023-05-23 10:12:23 +0200 |
commit | d34345da77bc1b2812bcfd0ac2385ffba0a4d3ba (patch) | |
tree | a7e5471a17cbff6dfdbf2a47e082d57d1293e9c1 /recipes-core | |
parent | 9e788821467e599fb78e95bf2e4eae1ac272af68 (diff) |
libusbgx: drop recipe
Let's use the libusbgx recipe from meta-openembedded, move Toradex
related g1.schema to libusbgx-config recipe.
The following fixes have been made to libusbgx-config:
- Add 'idProduct' and 'serialnumber' to /etc/usbgx/g1.schema by
pkg_postinst_ontarget function, it would runs only once at the first
boot, no need to write them to /sys/kernel/config/usb_gadget/g1
everytime in ExecStartPost.
With these meta-openembedded MRs:
https://patchwork.yoctoproject.org/project/oe/patch/20230516133052.2071705-1-liu.ming50@gmail.com/
https://patchwork.yoctoproject.org/project/oe/patch/20230516133257.2072092-1-liu.ming50@gmail.com/
https://patchwork.yoctoproject.org/project/oe/patch/20230509113620.786170-4-liu.ming50@gmail.com/
https://patchwork.yoctoproject.org/project/oe/patch/20230509113620.786170-3-liu.ming50@gmail.com/
https://patchwork.yoctoproject.org/project/oe/patch/20230509113620.786170-2-liu.ming50@gmail.com/
the following changes have been made:
- Drop '/sbin/modprobe libcomposite' and
'/bin/mount -t configfs configfs /sys/kernel/config' from
ExecStartPre, they are redundant since libcomposite would be
automatically loaded during system starting up due to the following
setting in linux-toradex recipe:
KERNEL_MODULE_AUTOLOAD += "libcomposite", insteadly, now let
usbgx.service require and run after sys-kernel-config.mount.
- Since we have "WantedBy=usb-gadget.target" in systemd service, that
ensures when udev trigger UDC rules, usbgx.service would run as well
so the "Before=systemd-networkd.service" condition could be dropped
from usbgx.service of meta-oe, since that is a ETH gadget specific
condition.
- Use "Type=simple" rather than "Type=oneshot", this ensures
usbgx.service would not hang on failures, failures could happen in
many conditions, like if the end user has manually configured
something in configfs, or start usbgx.service twice, or someting
wrong in /etc/default/usbgx or /etc/usbgx/*.schema.
Signed-off-by: Ming Liu <ming.liu@toradex.com>
Diffstat (limited to 'recipes-core')
0 files changed, 0 insertions, 0 deletions