OpenIPC
/
wiki
mirror of https://github.com/OpenIPC/wiki.git
1
0
Fork 0
Code Activity

housekeeping

pull/70/head
Paul Philippov 2022-12-30 00:57:32 -05:00 committed by GitHub
parent 2504a9605f
commit e834d7336f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 15 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

45
en/hardware-wifi-ah-huge-ic → en/hardware-wifi-ah-huge-ic.md
View File

@ -1,10 +1,13 @@
# OpenIPC Wiki
[Table of Content](../index.md)
OpenIPC - Add new Wifi drivers for Ingenic T31 OpenIPC - Add new Wifi drivers for Ingenic T31
For basic users like me, advanced users can ignore this document altogether. ----------------------------------------------
For basic users like myself, advanced users can ignore this document altogether.
This document describes how to add Huge-IC's AH Halow wifi drivers to OpenIPC This document describes how to add Huge-IC's AH Halow wifi drivers to OpenIPC
### Obtain driver source and edit Makefile
1 Obtain driver source and Edit Makefile
Obtain source file of the drivers so you can compile those drivers and upload to your camera system. So that when the hardware is connected, camera (host) can identify the hardware and connect with it. Its like, when you connect an USB dongle to your computer, it loads the driver. Your microprocessor does not load drivers like your PC, so you need to do it yourself. Obtain source file of the drivers so you can compile those drivers and upload to your camera system. So that when the hardware is connected, camera (host) can identify the hardware and connect with it. Its like, when you connect an USB dongle to your computer, it loads the driver. Your microprocessor does not load drivers like your PC, so you need to do it yourself.
@ -14,65 +17,47 @@ ARCH,
COMPILER AND; COMPILER AND;
LINUX_KERNEL_PATH LINUX_KERNEL_PATH
Ingenic uses ‘mips’ architecture so use it for ARCH ‘ARCH := mips’ Ingenic uses ‘mips’ architecture so use it for ARCH ‘ARCH := mips’
For COMPILER and Kernel Path, it is will be a cross compilation – kind of dependent on what you got in the OpenIPC. To enlighten yourself further, read this: https://blukat.me/2017/12/cross-compile-arm-kernel-module/ For COMPILER and Kernel Path, it is will be a cross compilation – kind of dependent on what you got in the OpenIPC. To enlighten yourself further, read this: https://blukat.me/2017/12/cross-compile-arm-kernel-module/
We can now move onto download and extract OpenIPC firmware, its extracted file will provide us the paths for Compiler and Kernal. We can now move onto download and extract OpenIPC firmware, its extracted file will provide us the paths for Compiler and Kernal.
Download OpenIPC Firmware ### Download OpenIPC Firmware
```
cd cd
git clone git@github.com:OpenIPC/firmware.git git clone git@github.com:OpenIPC/firmware.git
cd firmware cd firmware
./building.sh t31_ultimate ./building.sh t31_ultimate
```
(t31_ultimate because ultimate comes with support for wireless devices. lite is stripped of those to save space.) (t31_ultimate because ultimate comes with support for wireless devices. lite is stripped of those to save space.)
Now you can change the Compiler and Kernel path in driver source Makefile: Now you can change the Compiler and Kernel path in driver source Makefile:
```
#Driver Compilation for Ingenic T31 #Driver Compilation for Ingenic T31
ARCH := mips ARCH := mips
COMPILER := ~/firmware/output/host/bin/mipsel-linux- COMPILER := ~/firmware/output/host/bin/mipsel-linux-
LINUX_KERNEL_PATH := ~/firmware/output/build/linux-3.10.14 LINUX_KERNEL_PATH := ~/firmware/output/build/linux-3.10.14
```
### Now run ‘make fmac’
2 Now run ‘make fmac’
(here FMAC or any other relevant name for your drivers) (here FMAC or any other relevant name for your drivers)
If all went to plan, you should have one script file and one or more .ko extension files. Those .ko extension files are your drivers and the script file includes instructions for your host microcontroller to find and activate the drivers. If all went to plan, you should have one script file and one or more .ko extension files. Those .ko extension files are your drivers and the script file includes instructions for your host microcontroller to find and activate the drivers.
### Time to upload the drivers to camera system
3 Time to upload the drivers to camera system
IF the files are small and Ingenic having extra space available, you can sideload the drivers. IF the files are small and Ingenic having extra space available, you can sideload the drivers.
Upload the .ko (drivers) and FMAC (your script file can have a different name) script file to the folder of your choosing. Please make sure to edit the corresponding paths in the (FMAC) script file if required. Upload the .ko (drivers) and FMAC (your script file can have a different name) script file to the folder of your choosing. Please make sure to edit the corresponding paths in the (FMAC) script file if required.
### Test
4 Test
Test it with your wifi hardware to ensure that it works. Test it with your wifi hardware to ensure that it works.
5 Next, create a Package ### Next, create a package
Once you have learned how to create a package, please share it with the OpenIPC admin team members. They may agree to include your driver package to the repo. Once included as a package, next time you can use it by simply uncommenting and activating the package within the OpenIPC config file. Once you have learned how to create a package, please share it with the OpenIPC admin team members. They may agree to include your driver package to the repo. Once included as a package, next time you can use it by simply uncommenting and activating the package within the OpenIPC config file.