Merge pull request #74 from Pi4J/release/2.7.1

DRAFT: Release/2.8.0

Author: FDelporte

content/_index.md

@@ -4,7 +4,7 @@ title: Welcome to Pi4J
 
 ## Welcome to Pi4J
 
-**Latest release: V2.7.0 (2024-10-03, see [Release Notes](/about/release-notes/)).**
+**Latest release: V2.8.0 (2025-01-28, see [Release Notes](/about/release-notes/)).**
 
 This project is intended to provide **a friendly object-oriented I/O API and implementation libraries for Java Programmers** to access the **full I/O capabilities of the Raspberry Pi platform**. This project abstracts the low-level native integration and interrupt monitoring to enable Java programmers to **focus on implementing their application business logic**.
 

content/about/release-notes.md

@@ -5,6 +5,28 @@ weight: 40
 
 All releases of Pi4J V.2 are listed on [github.com/Pi4J/pi4j-v2/releases](https://github.com/Pi4J/pi4j-v2/releases).
 
+## 2025-01-28 - V2.8.0
+
+* Several code and JavaDoc improvements by adding the checkstyle plugin.
+* Improvements in loading the Mock providers to build and test Pi4J on a Raspberry Pi. 
+* Issue [#421](https://github.com/Pi4J/pi4j-v2/issues/421): Unable to detect board type. Several improvements have been integrated in the board detection to prevent errors when reading the board code. 
+* Added to `BoardModel`:
+  * Issue [#406](https://github.com/Pi4J/pi4j-v2/issues/406): Old boards not auto detected. Missing codes have been added for Model 1 boards.
+  * The Raspberry Pi Compute 5. Only the board code `c04180` for the 4Gb has been confirmed by Jeff Geerling. The other types are not documented yet. We assume they are `a04180`, `b04180`, and `d04180`, similar to the Compute 4, but will adjust whenever more info is available.
+  * The Raspberry Pi 500 with the board code `d04190`, again confirmed by Jeff who received an evaluation device.
+  * The Raspberry Pi 5 with 16GB memory with the board code `e04171` (thanks again Jeff).
+* Added to `BoardReading`:
+  * Pull request [#432](https://github.com/Pi4J/pi4j-v2/pull/432): Add Support for Throttled State Parsing and Retrieval
+* Improvements in the LinuxFS provider (for Raspberry Pi 5):
+  * Pull Request [#433](https://github.com/Pi4J/pi4j-v2/pull/433): Enhance LinuxFsI2CBus validation with detailed exception messages and comprehensive Javadocs.
+  * Pull Request [#434](https://github.com/Pi4J/pi4j-v2/pull/434): Add SPI support in LinuxFS. No `sudo` is needed to use SPI.
+
+Thanks to contributions by [@mpilone](https://github.com/mpilone), [@cniesen](https://github.com/cniesen), [@geerlingguy](https://github.com/geerlingguy), [@dariuszzbyrad](https://github.com/dariuszzbyrad), [@taartspi](https://github.com/taartspi), [@eitch](https://github.com/eitch), [@fdelporte](https://github.com/fdelporte).
+
+Special thanks to [Dariusz Zbyrad](https://github.com/dariuszzbyrad) for joining the project and improving the Maven builds with a wrapper for more consistency, for example, in the [pi4j-example-devices repository](https://github.com/Pi4J/pi4j-example-devices), and other contributions. And also special thanks to [Mike Pilone](https://github.com/mpilone) for the initial work for LinuxFS SPI.
+
+All changes: https://github.com/Pi4J/pi4j-v2/compare/2.7.0...2.8.0
+
 ## 2024-10-03 - V2.7.0
 
 * Libraries are loaded depending on the platform, by calling `BoardInfoHelper.runningOnRaspberryPi()`.

content/documentation/providers/linuxfs.md

@@ -4,7 +4,7 @@ weight: 93
 tags: ["LinuxFS", "PWM", "I2C"]
 ---
 
-The current implementation of the LinuxFS plugin implements a file based I2C and PWM provider. The file based I2C provider opens 
+The current implementation of the LinuxFS plugin implements a file based I2C, SPI, and PWM provider. The file based I2C provider opens 
 `/dev/i2c-1` using a `RandomAccessFile` to perform I2C reads and writes. The file based PWM provider opens
 `/sys/class/pwm/pwmchip?` using a `RandomAccessFile` to perform PWM operations.
 
@@ -15,6 +15,7 @@ The Linuxfs provider linuxfs-pwm requires minimum kernel Bullseye 6.1.21 and Boo
 Providers in the LinuxFS plugin:
 
 * linuxfs-i2c
+* linuxfx-spi
 * linuxfs-pwm
 * Under construction
   * linuxfs-digital-input
@@ -40,7 +41,9 @@ To use the LinuxFS provider include the following dependencies:
 </dependency>
 ```
 
-And then one can get access to the I2C provider as follows:
+## I2C 
+
+Example on how to use I2C with LinuxFS:
 
 ``` java
 Context pi4j = Pi4J.newAutoContext();
@@ -60,7 +63,17 @@ try (I2C tca9534Dev = i2CProvider.create(i2cConfig)) {
 pi4j.shutdown();
 ```
 
-And then one can get access to the PWM provider as follows:
+## SPI
+
+The buffer size for this SPI implementation is 4096 bytes. This can be configured in `config.txt`:
+
+* Debian Bullseye OS: `/boot/config.txt`
+* Raspberry Pi OS, based on Debian Bookworm: `/boot/firmware/config.txt`
+
+## PWM
+
+Example on how to use PWM with LinuxFS:
+
 ```java
   /**
      * Builds a new PWM configuration for the buzzer

content/documentation/providers/pigpio.md

@@ -12,7 +12,6 @@ Pi5  At the present time the PiGpio implementation does not support the new Pi5
 - This new Pi5 RP1 chip will require a large development effort. There is no known plan for this develoment.   
 ```
 
-
 Providers in the PiGpio plugin:
 
 * pigpio-digital-input
@@ -33,7 +32,6 @@ WARN com.pi4j.library.pigpio.impl.PiGpioNativeImpl
     - PIGPIO ERROR: PI_INIT_FAILED; pigpio initialisation failed
 ```
 
-
 To use the PiGpio provider include the following dependencies:
 
 ``` xml