revpi-tools_3.1.1-1+revpi11+1 #57
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Sven Sager <s.sager@kunbus.com>
Currently the lan9614.bin is created in the root of the build directory. This is unusal, as most developers would expect it in the tools directory. Build the lan9514.bin in the tools subdirectory of the build directory. Signed-off-by: Philipp Rosenberger <p.rosenberger@kunbus.com>
The version of ethtool from bullseye gives an error of length is not specified: "offset & length out of bounds" Signed-off-by: Philipp Rosenberger <p.rosenberger@kunbus.com>
We use different network device types (phy/mac). Currently we maintain two scripts to write the mac address into the eeprom of our network devices. In time we will need to support more devices. The major part of the scripts is doing the same stuff. * checking if the mac address is "valid" * use ethtool to write to the eeprom * use ethtool to write the mac address The differences are mostly in the size and name of the image. And the location of the mac address. Unify the scripts into one script and add wrapper scripts to provide backwards compatibility. Signed-off-by: Philipp Rosenberger <p.rosenberger@kunbus.com>
Add support to flash the eeprom of LAN7800 devices to the revpi-set-mac script. Also add a wrapper script like the lan95xx-set-mac script. The lan7800.hex is derived from the 7800eep.bin provided by Microchip with it's lan78xx-windows-command-line-utils. https://www.microchip.com/en-us/product/LAN7800#Software Signed-off-by: Philipp Rosenberger <p.rosenberger@kunbus.com>
The KS8851 uses a different offset, when it comes to writing the mac address with ethtool. Extend revpi-set-mac in order to deal with this and make ks8851-set-mac call the revpi-set-mac script. Signed-off-by: Nicolai Buchwitz <n.buchwitz@kunbus.com>
The internal ethernet interface of CM4 uses a MAC of the Raspberry Pi Trading Ltd. In order to match these addresses with casing, and HAT-EEPROM, they need to be set during boot time. Signed-off-by: Holger Jorra <h.jorra@kunbus.com>
Add two udev rules, for eth0 and wlan0 devices. Signed-off-by: Holger Jorra <h.jorra@kunbus.com>
Since /lib is a symlink to /usr/lib this ought to work here, as well. The /usr prefix can be set by the debianization or the user. Signed-off-by: Holger Jorra <h.jorra@kunbus.com>
The systemd manpage says that "pkg-config systemd --variable=systemdsystemunitdir" should be used to determine the correct path for the unit files. Use the FindPkgConfig module of CMake to check for the package. This means we will get a build time dependecy on systemd as /usr/share/pkgconfig/systemd.pc is part of the systemd package. Fixes: 4ed3411 Signed-off-by: Philipp Rosenberger <p.rosenberger@kunbus.com>
Fixes: 6cb77e2 Co-authored-by: Thomas Böhler <t.boehler@kunbus.com> Signed-off-by: Thomas Böhler <t.boehler@kunbus.com> Signed-off-by: Philipp Rosenberger <p.rosenberger@kunbus.com>
Release 3.1.0
tboehler1
previously approved these changes
May 24, 2023
We are now using pkg-config to determine the location for the system units and udev related files. The configuration for pkg-config for systemd is provided by the systemd package. The same goes for udev with the udev package. Add systemd, udev and pkg-config to the Build-Depends otherwise the installation of the systemd units or the udev related files will fail. Signed-off-by: Philipp Rosenberger <p.rosenberger@kunbus.com>
Signed-off-by: Philipp Rosenberger <p.rosenberger@kunbus.com>
The systemd manpage says that "pkg-config systemd --variable=systemdsystemunitdir" should be used to determine the correct path for the unit files. Use the FindPkgConfig module of CMake to check for the package. This means we will get a build time dependecy on systemd as /usr/share/pkgconfig/systemd.pc is part of the systemd package. Signed-off-by: Philipp Rosenberger <p.rosenberger@kunbus.com>
The firstboot.service file contains both DefaultDependencies=no and Conflicts=shutdown.target directives without Before=shutdown.target. This can lead to problems during shutdown because the service may linger until the very end of shutdown sequence as nothing requests to stop it before (due to DefaultDependencies=no). https://lintian.debian.org/tags/systemd-service-file-shutdown-problems systemd/systemd#11821 Signed-off-by: Philipp Rosenberger <p.rosenberger@kunbus.com>
Release 3.1.1
Signed-off-by: Philipp Rosenberger <p.rosenberger@kunbus.com>
naruxde
approved these changes
May 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.