Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Hailo PCIe driver and firmware for Yellow #3734

Merged
merged 1 commit into from
Dec 12, 2024
Merged

Add Hailo PCIe driver and firmware for Yellow #3734

merged 1 commit into from
Dec 12, 2024

Conversation

sairon
Copy link
Member

@sairon sairon commented Dec 12, 2024

The PCIe card from the RPi AI Kit (and probably other M.2 cards using the Hailo-8 chip) can be used on Yellow - the driver initializes correctly and creates a /dev/hailo0 device on Yellow both with CM4 and CM5.

Summary by CodeRabbit

  • New Features
    • Added support for Hailo 8 firmware.
    • Integrated Hailo PCI capabilities into the build configuration.

The PCIe card from the RPi AI Kit (and probably other M.2 cards using the
Hailo-8 chip) can be used on Yellow - the driver initializes correctly and
creates a /dev/hailo0 device on Yellow both with CM4 and CM5.
@sairon sairon added the board/yellow Home Assistant Yellow label Dec 12, 2024
@sairon sairon requested a review from agners December 12, 2024 11:19
Copy link

coderabbitai bot commented Dec 12, 2024

📝 Walkthrough

Walkthrough

The changes in this pull request involve updates to the yellow_defconfig configuration file within the Buildroot external configurations. Two new packages, BR2_PACKAGE_HAILO8_FIRMWARE and BR2_PACKAGE_HAILO_PCI, have been added and are set to be included in the build. The overall structure and existing parameters of the configuration remain unchanged, continuing to support the Raspberry Pi yellow variant.

Changes

File Path Change Summary
buildroot-external/configs/yellow_defconfig Added BR2_PACKAGE_HAILO8_FIRMWARE=y and BR2_PACKAGE_HAILO_PCI=y

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Buildroot
    participant RaspberryPi

    User->>Buildroot: Request build with yellow_defconfig
    Buildroot->>RaspberryPi: Include HAILO8 firmware and PCI support
    RaspberryPi-->>Buildroot: Build complete
    Buildroot-->>User: Return build output
Loading

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?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Experiment)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7031870 and 5e58c9c.

📒 Files selected for processing (1)
  • buildroot-external/configs/yellow_defconfig (1 hunks)
🔇 Additional comments (2)
buildroot-external/configs/yellow_defconfig (2)

159-160: Verify security considerations for Hailo integration.

Since this introduces new firmware and device access:

  1. Consider if AppArmor profiles need updates for Hailo device access
  2. Ensure firmware package includes verification/signing mechanisms

Let's check for security-related configurations:


159-160: LGTM! Verify kernel configuration for Hailo support.

The addition of Hailo packages looks good. The packages are correctly placed and enabled:

  • BR2_PACKAGE_HAILO8_FIRMWARE=y: Provides the necessary firmware
  • BR2_PACKAGE_HAILO_PCI=y: Provides the PCIe driver

Let's verify the kernel configuration includes necessary Hailo support:

✅ Verification successful

Kernel configuration for Hailo support looks good to proceed

The verification shows that:

  • PCI support is properly configured in the kernel through device-support-pci.config
  • The Hailo PCIe driver (v4.19.0) is being built as a kernel module
  • The firmware package correctly installs the binary at /lib/firmware/hailo/hailo8_fw.bin
  • Since this is a standard PCIe driver that will be built as a module, no additional kernel configurations are required beyond the existing PCI support
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check kernel config fragments for Hailo PCIe support

# Check kernel config fragments for Hailo-related settings
echo "Checking kernel config fragments for Hailo support..."
rg -l "CONFIG_HAILO" "$(BR2_EXTERNAL_HASSOS_PATH)/kernel/v6.6.y/"

# Verify PCI support is properly configured
echo "Verifying PCI configuration..."
rg "CONFIG_PCI" "$(BR2_EXTERNAL_HASSOS_PATH)/kernel/v6.6.y/device-support-pci.config"

Length of output: 705


Script:

#!/bin/bash
# Let's first find the correct paths for kernel configs
echo "Finding kernel config files..."
fd "device-support-pci.config"

echo "Searching for any Hailo-related kernel configs..."
rg -l "CONFIG_HAILO"

echo "Looking for kernel defconfig or fragment files..."
fd "defconfig|\.config" buildroot-external/kernel/

Length of output: 854


Script:

#!/bin/bash
# Now that we have the correct paths, let's check the content of relevant config files
echo "Checking PCI support configuration..."
cat buildroot-external/kernel/v6.6.y/device-support-pci.config

echo -e "\nChecking general device support configuration..."
cat buildroot-external/kernel/v6.6.y/device-support.config

echo -e "\nChecking main kernel configuration..."
cat buildroot-external/kernel/v6.6.y/hassos.config

# Let's also check if there are any Hailo-related patches
echo -e "\nChecking for Hailo-related kernel patches..."
fd -e patch . buildroot-external/kernel/v6.6.y/patches/

Length of output: 9760


Script:

#!/bin/bash
# Let's check if there's a Hailo package definition that might contain kernel config requirements
echo "Checking Hailo package definitions..."
fd "hailo" buildroot-external/package/

echo -e "\nChecking package contents if found..."
find buildroot-external/package/ -type f -name "hailo*" -exec cat {} \;

Length of output: 1988

buildroot-external/configs/yellow_defconfig Show resolved Hide resolved
@sairon sairon merged commit d06aa63 into dev Dec 12, 2024
3 checks passed
@sairon sairon deleted the yellow-add-hailo branch December 12, 2024 19:43
This was referenced Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
board/yellow Home Assistant Yellow cla-signed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants