Skip to content

Configs and Symbols needed for building out of tree drivers.

Notifications You must be signed in to change notification settings

Zykaz/pCP-Kernels

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

25 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Utility for compiling out of tree kernel moduels for pCP Kernels

Start

  • Step 1: Download the two scripts:
  • Step 2: Prepare the kernel source...this will download the source if needed. Note: kernel source is over 220MB, you will likely need about 500MB of free space to perform these tasks.
    • The kernel should be stored on persisitent storage. i.e. USB drive, or if you have expanded your microSD card /mnt/mmcblk0p2/tce/kernelsrc
    • run: pcp_prepare_kernel_src -k <kernel version to build> -s <path to saved pCP kernel source - or where to save it>
      • <kernel version to build> will be in the format. See below for kernel versions for pCP releases.
        • 5.10.xx-pcpCore (If you have a piZero, Pi1)
        • 5.10.xx-pcpCore-v7 (If you have a Pi02,2,3,3B+,CM3)
        • 5.10.xx-pcpCore-v7l (If you have a Pi4, using a 32bit OS)
        • 5.10.xx-pcpCore-v8 (If you have a Pi4, using a 64bit OS)
  • Step 3: Download the driver source, cd to the directory of the driver source and edit Makefile, See Below.
    • Store the driver source on the same persistent disk that you saved the kernel, but not the same folder. i.e. /mnt/mmcblk0p2/tce/realtek-driversrc
  • Step 4: Compile your driver based on notes below, driver source code, and information from step 2.
    • run make KVER=x.x.x-pcpCore-xx -j
  • Step 5: Build the extension that contains the driver.
    • cd
    • Run: pcp_make_module_extension -k -e < extension name >
    • Make sure to run this command from the source directory of your driver.

Recommended repos for Realtek drivers....but there are many. There build options for these packages can be quite different.

Notes: In all cases, you will need to edit Makefile

  • Set all the CONFIG_PLATFORM* = n
  • Then set CONFIG_PLATFORM_ARM_RPI = y (or CONFIG_PLATFORM_ARM64_RPI = y) whichever closest matches your system.
  • Driver specific notes are shown below.

8188eu - https://github.com/aircrack-ng/rtl8188eus [branch "v5.3.9"]

8188fu - https://github.com/kelebek333/rtl8188fu [branch "master"]

8192eu - https://github.com/Mange/rtl8192eu-linux-driver [branch "realtek-4.4.x"]

8812au - https://github.com/aircrack-ng/rtl8812au [branch "v5.6.4.2"]

8822bu - https://github.com/EntropicEffect/rtl8822bu [branch "master"]

8821cu - https://github.com/brektrou/rtl8821CU [branch "master"]

  • This driver utilizes floating point, which is not normal for kernel drivers. The readme at the git repo describes how to edit the kernel source to allow building for rpi.

pCP Kernel Versions

  • pCP 8.0.0
    • Single Core boards (i.e. rpiZero): 5.10.42-pcpCore
    • RPi2B,3,3B,CM3: 5.10.42-pcpCore-v7
    • RPi4 32bit: 5.10.42-pcpCore-v7l
    • RPI4 64bit: 5.10.42-pcpCore-v8
  • pCP 8.1.0
    • Single Core boards (i.e. rpiZero): 5.10.77-pcpCore
    • RPi02,2B,3,3B,3B+,CM3: 5.10.77-pcpCore-v7
    • RPi4 32bit: 5.10.77-pcpCore-v7l
    • RPI02,3B,4 64bit: 5.10.77-pcpCore-v8

About

Configs and Symbols needed for building out of tree drivers.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Shell 100.0%