RaspberryPi: Update kernel to 6.6.51 - stable_20241008 #3662
Conversation
* buildroot 2ffac68a74...19027bc796 (1): > package/rpi-firmware: bump to version 1.20241008 for kernel 6.6.51
sairon
added
board/raspberrypi
|
Related buildroot PR: home-assistant/buildroot#58 |
📝 WalkthroughWalkthroughThe changes in this pull request include updates to the kernel version numbers for various Raspberry Pi models and the Home Assistant Yellow board in the documentation, changing the version from 6.6.31 to 6.6.51. Additionally, the configuration files for several Raspberry Pi platforms have been modified to point to a newer Linux kernel tarball dated 20241008, replacing the previous tarball dated 20240529. The subproject commit reference in the buildroot has also been updated to reflect a new state of the subproject. Changes
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (9)
✅ Files skipped from review due to trivial changes (7)
🔇 Additional comments (3)buildroot-external/configs/rpi3_64_defconfig (2)Line range hint The overall configuration remains well-structured with:
The URL update for the kernel tarball looks correct, pointing to the official Raspberry Pi repository. Let's verify the tarball URL and kernel version: ✅ Verification successfulKernel tarball and version verification successful ✓ Tarball URL is accessible (HTTP 200) 🏁 Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Description: Verify kernel tarball accessibility and version
# Test 1: Check if the URL is accessible
echo "Checking tarball URL accessibility..."
curl -I "https://github.com/raspberrypi/linux/archive/stable_20241008.tar.gz"
# Test 2: Verify kernel version matches PR title (6.6.51)
echo "Checking kernel version..."
curl -sL "https://raw.githubusercontent.com/raspberrypi/linux/stable_20241008/Makefile" | \
awk '/^VERSION =|^PATCHLEVEL =|^SUBLEVEL =/ {print $3}' | \
paste -sd "."
# Test 3: Check for consistency across other platform configs
echo "Checking consistency across platform configs..."
fd -e defconfig . | xargs grep -l "stable_20241008"
Length of output: 4827 Script: #!/bin/bash
# Let's try a different approach to verify the version and consistency
# Test 1: Check if the URL redirects properly and the tarball exists
echo "Verifying tarball accessibility..."
curl -sLI "https://github.com/raspberrypi/linux/archive/stable_20241008.tar.gz" | grep "HTTP/"
# Test 2: Check kernel version using grep instead of paste
echo "Checking kernel version..."
curl -sL "https://raw.githubusercontent.com/raspberrypi/linux/stable_20241008/Makefile" | \
grep -E "^VERSION = |^PATCHLEVEL = |^SUBLEVEL = "
# Test 3: Check other platform configs for consistency
echo "Checking RPi platform configs..."
find buildroot-external/configs -type f -name "*rpi*defconfig" -exec grep "BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION" {} \;
Length of output: 1308 buildroot-external/configs/rpi4_defconfig (1)
The update from stable_20240529 to stable_20241008 aligns with the kernel version bump from 6.6.31 to 6.6.51. This is a patch version update that should bring security fixes and stability improvements while maintaining backward compatibility. Let's verify this is the latest stable kernel version: ✅ Verification successfulKernel version verified as latest stable The verification confirms that 🏁 Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Description: Verify if this is the latest stable kernel for Raspberry Pi
# Expected: stable_20241008 should be the latest stable tag
# Check the latest stable tag from the Raspberry Pi Linux repository
gh api repos/raspberrypi/linux/tags --paginate | jq -r '.[].name' | grep -E '^stable_[0-9]{8}$' | sort -r | head -n 1
Length of output: 135 Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
Warning Rate limit exceeded@sairon has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 27 minutes and 24 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
Warning Rate limit exceeded@sairon has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 27 minutes and 23 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
📝 WalkthroughWalkthroughThe changes in this pull request involve updates to kernel version numbers and configuration files across various Raspberry Pi models and the Home Assistant Yellow board. The kernel version has been uniformly updated from 6.6.31 to 6.6.51 in the documentation. Additionally, configuration files for several Raspberry Pi models have been modified to reference a new Linux kernel tarball dated 20241008, replacing the previous tarball dated 20240529. The changes primarily affect documentation and configuration settings without altering the overall structure or functionality. Changes
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (9)
✅ Files skipped from review due to trivial changes (9)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
📝 WalkthroughWalkthroughThe pull request includes updates to the documentation and configuration files for various Raspberry Pi models and the Home Assistant Yellow board. The kernel version numbers for the Raspberry Pi models and Home Assistant Yellow have been changed from 6.6.31 to 6.6.51. Additionally, the configuration files for multiple Raspberry Pi models have been updated to point to a new Linux kernel tarball URL dated 20241008, replacing the previous URL dated 20240529. The subproject commit reference in the buildroot has also been updated. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Documentation
participant Buildroot
participant Configs
User->>Documentation: Request kernel version info
Documentation-->>User: Provide updated versions (6.6.51)
User->>Buildroot: Request subproject commit info
Buildroot-->>User: Provide updated commit reference
User->>Configs: Request kernel tarball location
Configs-->>User: Provide updated URLs (20241008)
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (9)
✅ Files skipped from review due to trivial changes (8)
🔇 Additional comments (2)buildroot-external/configs/rpi3_64_defconfig (2)
The update to the stable kernel tarball from 20240529 to 20241008 is consistent with the PR objective of updating to kernel 6.6.51.
The kernel config fragments are referenced from the v6.6.y directory. Let's verify they are compatible with the new kernel version. Also applies to: 22-22 ✅ Verification successfulThe output shows that the kernel config fragments are actually located at Based on the output, I can see that the kernel config fragments exist in the correct location at Kernel config fragments are compatible with the new kernel version. The fragments were freshly added as part of the Buildroot update that includes the kernel version change, ensuring their compatibility. 🏁 Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Description: Verify kernel config fragments exist and haven't changed significantly
# Check if the kernel config fragments exist
echo "Checking kernel config fragments..."
for fragment in "hassos.config" "docker.config" "device-support.config" "device-support-wireless.config"; do
if ! [ -f "kernel/v6.6.y/$fragment" ]; then
echo "Error: Missing kernel config fragment: $fragment"
exit 1
fi
done
# Check git history for recent changes to kernel config fragments
echo -e "\nChecking recent changes to kernel configs..."
git log --since="2024-05-29" --name-only --oneline kernel/v6.6.y/*.config
Length of output: 352 Script: #!/bin/bash
# Let's first check if the kernel config fragments are in a different location
echo "Searching for kernel config fragments across the repository..."
fd -t f -e config
# Also check if there are any .fragment files
echo -e "\nSearching for .fragment files..."
fd -t f -e fragment
# Let's also check the buildroot-external directory structure
echo -e "\nChecking buildroot-external directory..."
ls -R buildroot-external/
Length of output: 23211 Script: #!/bin/bash
# Check the content of kernel config fragments
echo "Content of kernel config fragments in v6.6.y:"
for fragment in hassos.config docker.config device-support.config device-support-wireless.config; do
echo -e "\n=== $fragment ==="
cat "buildroot-external/kernel/v6.6.y/$fragment"
done
# Check git history for recent changes
echo -e "\nRecent changes to kernel config fragments:"
git log -p --since="2024-05-29" buildroot-external/kernel/v6.6.y/*.config
Length of output: 133932 Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Summary by CodeRabbit
New Features
Documentation
Configuration Updates