d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
974351045b
freebsd-skq/sys/mips/conf/RT5350_FDT

75 lines
1.3 KiB
Plaintext
Raw Normal View History

In order to build a kernel with one of these configs the user should do the following: 1. Give the appropriate board dts file to be used by either: 1.1. edit the SoC kernel config required (e.g., MT7620A_FDT) and include the required FDT_DTS_FILE makeoption; or 1.2. simply supply FDT_DTS_FILE="xx.dts" on the command line when building the kernel Of course, the user can also create a completely new kernel config to match the desired board and include the SoC kernel config from within it. If required, edit the MEDIATEK config file, which includes optional drivers and comment out the unneeded ones. 2.1. this would only make sense if kernel size is a concern. Even if we build the kernel with all drivers, if we lzma it and package it as a uImage, its size is still around 1.1MiB. The user will have to choose a dts file (or create a new one) from sys/gnu/dts/mips , where all Mediatek/Ralink dts files will be imported via a later revision. Approved by: adrian (mentor) Sponsored by: Smartcom - Bulgaria AD Differential Revision: https://reviews.freebsd.org/D5966
2016-04-15 15:20:41 +00:00
#
# RT5350_FDT -- Kernel configuration file for FreeBSD/MIPS RT5350 SoC
#
Rework Mediatek/Ralink configuration files Only compile what each SoC needs and get rid of MEDIATEK generic config. Approved by: adrian (mentor) Sponsored by: Smartcom - Bulgaria AD Differential Revision: https://reviews.freebsd.org/D5996
2016-04-21 07:40:03 +00:00
# This includes all the configurable parts of the kernel.
In order to build a kernel with one of these configs the user should do the following: 1. Give the appropriate board dts file to be used by either: 1.1. edit the SoC kernel config required (e.g., MT7620A_FDT) and include the required FDT_DTS_FILE makeoption; or 1.2. simply supply FDT_DTS_FILE="xx.dts" on the command line when building the kernel Of course, the user can also create a completely new kernel config to match the desired board and include the SoC kernel config from within it. If required, edit the MEDIATEK config file, which includes optional drivers and comment out the unneeded ones. 2.1. this would only make sense if kernel size is a concern. Even if we build the kernel with all drivers, if we lzma it and package it as a uImage, its size is still around 1.1MiB. The user will have to choose a dts file (or create a new one) from sys/gnu/dts/mips , where all Mediatek/Ralink dts files will be imported via a later revision. Approved by: adrian (mentor) Sponsored by: Smartcom - Bulgaria AD Differential Revision: https://reviews.freebsd.org/D5966
2016-04-15 15:20:41 +00:00
#
# $FreeBSD$
#
#NO_UNIVERSE
#
# FDT_DTS_FILE should be modified to suit the target board type.
#
Rework Mediatek/Ralink configuration files Only compile what each SoC needs and get rid of MEDIATEK generic config. Approved by: adrian (mentor) Sponsored by: Smartcom - Bulgaria AD Differential Revision: https://reviews.freebsd.org/D5996
2016-04-21 07:40:03 +00:00
#makeoptions FDT_DTS_FILE=DIR-610-A1.dts
In order to build a kernel with one of these configs the user should do the following: 1. Give the appropriate board dts file to be used by either: 1.1. edit the SoC kernel config required (e.g., MT7620A_FDT) and include the required FDT_DTS_FILE makeoption; or 1.2. simply supply FDT_DTS_FILE="xx.dts" on the command line when building the kernel Of course, the user can also create a completely new kernel config to match the desired board and include the SoC kernel config from within it. If required, edit the MEDIATEK config file, which includes optional drivers and comment out the unneeded ones. 2.1. this would only make sense if kernel size is a concern. Even if we build the kernel with all drivers, if we lzma it and package it as a uImage, its size is still around 1.1MiB. The user will have to choose a dts file (or create a new one) from sys/gnu/dts/mips , where all Mediatek/Ralink dts files will be imported via a later revision. Approved by: adrian (mentor) Sponsored by: Smartcom - Bulgaria AD Differential Revision: https://reviews.freebsd.org/D5966
2016-04-15 15:20:41 +00:00
# Start with a base configuration
Rework Mediatek/Ralink configuration files Only compile what each SoC needs and get rid of MEDIATEK generic config. Approved by: adrian (mentor) Sponsored by: Smartcom - Bulgaria AD Differential Revision: https://reviews.freebsd.org/D5996
2016-04-21 07:40:03 +00:00
include "../mediatek/std.mediatek"
In order to build a kernel with one of these configs the user should do the following: 1. Give the appropriate board dts file to be used by either: 1.1. edit the SoC kernel config required (e.g., MT7620A_FDT) and include the required FDT_DTS_FILE makeoption; or 1.2. simply supply FDT_DTS_FILE="xx.dts" on the command line when building the kernel Of course, the user can also create a completely new kernel config to match the desired board and include the SoC kernel config from within it. If required, edit the MEDIATEK config file, which includes optional drivers and comment out the unneeded ones. 2.1. this would only make sense if kernel size is a concern. Even if we build the kernel with all drivers, if we lzma it and package it as a uImage, its size is still around 1.1MiB. The user will have to choose a dts file (or create a new one) from sys/gnu/dts/mips , where all Mediatek/Ralink dts files will be imported via a later revision. Approved by: adrian (mentor) Sponsored by: Smartcom - Bulgaria AD Differential Revision: https://reviews.freebsd.org/D5966
2016-04-15 15:20:41 +00:00
ident RT5350
cpu CPU_MIPS24K
Rework Mediatek/Ralink configuration files Only compile what each SoC needs and get rid of MEDIATEK generic config. Approved by: adrian (mentor) Sponsored by: Smartcom - Bulgaria AD Differential Revision: https://reviews.freebsd.org/D5996
2016-04-21 07:40:03 +00:00
# Don't build any modules by default
makeoptions MODULES_OVERRIDE=""
# Default rootfs device configuration, should be changed to suit target board
options ROOTDEVNAME=\"ufs:md0.uzip\"
# Support geom_uzip(4) compressed disk images
device geom_uzip
options GEOM_UZIP
# Support md(4) and md-based rootfs
device md
options MD_ROOT
# Interrupt controller support
device mtk_intr_v1
# UART device support
nodevice uart_ns8250
device uart_dev_mtk
# SPI and SPI flash support
device mtk_spi_v1
device spibus
device mx25l
# GPIO and gpioled support
device mtk_gpio_v1
device gpio
device gpioled
# USB (ehci, ohci) support
device usb
device mtk_usb_phy
device ehci
device ohci
# USB umass(4) storage and da(4) support
device umass
device da
# CAM support, required if umass(4) is enabled above
device pass
device scbus
# Ethernet, BPF and bridge support
device rt
device bpf
device if_bridge
# Extres
device ext_resources
device clk
Reference in New Issue Copy Permalink