d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
7df85047a4
freebsd-skq/sys/arm/conf/IMX53

121 lines
3.4 KiB
Plaintext
Raw Normal View History

tart to clean up the armv6 kernel configs by reducing the diff between them in the first sections and the later FDT support. Differential Revision: https://reviews.freebsd.org/D1346 Reviewed by: rpaulo (earlier version)
2014-12-21 11:37:00 +00:00
#
Create a common i.MX53 config and use it with the two existing i.MX53 boards. This is just intended to split the common config entries out, further cleanup is expected. Reviewed by: ian@, rpaulo@ (earlier version) Differential Revision: https://reviews.freebsd.org/D731
2014-09-07 08:16:27 +00:00
# Kernel configuration for i.MX53 boards
#
# For more information on this file, please read the config(5) manual page,
# and/or the handbook section on Kernel Configuration Files:
#
Update several more URLs - Primarily http -> https - Primarily FreeBSD project URLs
2017-10-29 08:17:03 +00:00
# https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
Create a common i.MX53 config and use it with the two existing i.MX53 boards. This is just intended to split the common config entries out, further cleanup is expected. Reviewed by: ian@, rpaulo@ (earlier version) Differential Revision: https://reviews.freebsd.org/D731
2014-09-07 08:16:27 +00:00
#
# The handbook is also available locally in /usr/share/doc/handbook
# if you've installed the doc distribution, otherwise always see the
Update several more URLs - Primarily http -> https - Primarily FreeBSD project URLs
2017-10-29 08:17:03 +00:00
# FreeBSD World Wide Web server (https://www.FreeBSD.org/) for the
Create a common i.MX53 config and use it with the two existing i.MX53 boards. This is just intended to split the common config entries out, further cleanup is expected. Reviewed by: ian@, rpaulo@ (earlier version) Differential Revision: https://reviews.freebsd.org/D731
2014-09-07 08:16:27 +00:00
# latest information.
#
# An exhaustive list of options and more detailed explanations of the
# device lines is also present in the ../../conf/NOTES and NOTES files.
# If you are in doubt as to the purpose or necessity of a line, check first
# in NOTES.
#
# $FreeBSD$
ident IMX53
Tag all armv7 kernels as such in their machine config line. Transition all boards that support arm cortex CPUs to armv7. This leaves two armv6 kernels in the tree. RPI-B, which uses the BCM2835 which has a ARM1176 core, and VERSATILEPB, which is a qemu board setup around the time RPI-B went in. Copy std.armv6 to std.armv7, even though that duplicates a lot of stuff. More work needs to be done to sort out the duplication. Differential Revision: https://reviews.freebsd.org/D12027
2017-10-05 23:01:50 +00:00
include "std.armv7"
Create a common i.MX53 config and use it with the two existing i.MX53 boards. This is just intended to split the common config entries out, further cleanup is expected. Reviewed by: ian@, rpaulo@ (earlier version) Differential Revision: https://reviews.freebsd.org/D731
2014-09-07 08:16:27 +00:00
include "../freescale/imx/std.imx53"
Add the SOC_IMX51, SOC_IMX53, and SOC_IMX6 options. These are used to select which SoCs the kernel config will support. Use these options to merge files.imx51 and files.imx53.
2015-04-23 22:20:43 +00:00
options SOC_IMX53
Create a common i.MX53 config and use it with the two existing i.MX53 boards. This is just intended to split the common config entries out, further cleanup is expected. Reviewed by: ian@, rpaulo@ (earlier version) Differential Revision: https://reviews.freebsd.org/D731
2014-09-07 08:16:27 +00:00
options SCHED_4BSD # 4BSD scheduler
Remove "New" label from NFSCL/NFSD now that they are the only NFS client/server. While here, remove duplicate NFSCL from sys/conf/NOTES. Approved by: rmacklem
2015-01-06 16:15:57 +00:00
#options NFSD # Network Filesystem Server
Switch i.MX to use the platform code to help with a single Freescale kernel. Differential Revision: https://reviews.freebsd.org/D1349 Reviewed by: ian, rpaulo
2014-12-24 12:26:43 +00:00
options PLATFORM
Create a common i.MX53 config and use it with the two existing i.MX53 boards. This is just intended to split the common config entries out, further cleanup is expected. Reviewed by: ian@, rpaulo@ (earlier version) Differential Revision: https://reviews.freebsd.org/D731
2014-09-07 08:16:27 +00:00
options INCLUDE_CONFIG_FILE # Include this file in kernel
tart to clean up the armv6 kernel configs by reducing the diff between them in the first sections and the later FDT support. Differential Revision: https://reviews.freebsd.org/D1346 Reviewed by: rpaulo (earlier version)
2014-12-21 11:37:00 +00:00
# kernel/memory size reduction
#options MUTEX_NOINLINE
#options NO_FFS_SNAPSHOT
#options NO_SWAPPING
#options NO_SYSCTL_DESCR
#options RWLOCK_NOINLINE
Create a common i.MX53 config and use it with the two existing i.MX53 boards. This is just intended to split the common config entries out, further cleanup is expected. Reviewed by: ian@, rpaulo@ (earlier version) Differential Revision: https://reviews.freebsd.org/D731
2014-09-07 08:16:27 +00:00
# The `bpf' device enables the Berkeley Packet Filter.
# Be aware of the administrative consequences of enabling this!
# Note that 'bpf' is required for DHCP.
device bpf # Berkeley packet filter
# Pseudo devices.
device loop # Network loopback
device ether # Ethernet support
#device vlan # 802.1Q VLAN support
tun/tap: merge and rename to `tuntap` tun(4) and tap(4) share the same general management interface and have a lot in common. Bugs exist in tap(4) that have been fixed in tun(4), and vice-versa. Let's reduce the maintenance requirements by merging them together and using flags to differentiate between the three interface types (tun, tap, vmnet). This fixes a couple of tap(4)/vmnet(4) issues right out of the gate: - tap devices may no longer be destroyed while they're open [0] - VIMAGE issues already addressed in tun by kp [0] emaste had removed an easy-panic-button in r240938 due to devdrn blocking. A naive glance over this leads me to believe that this isn't quite complete -- destroy_devl will only block while executing d_* functions, but doesn't block the device from being destroyed while a process has it open. The latter is the intent of the condvar in tun, so this is "fixed" (for certain definitions of the word -- it wasn't really broken in tap, it just wasn't quite ideal). ifconfig(8) also grew the ability to map an interface name to a kld, so that `ifconfig {tun,tap}0` can continue to autoload the correct module, and `ifconfig vmnet0 create` will now autoload the correct module. This is a low overhead addition. (MFC commentary) This may get MFC'd if many bugs in tun(4)/tap(4) are discovered after this, and how critical they are. Changes after this are likely easily MFC'd without taking this merge, but the merge will be easier. I have no plans to do this MFC as of now. Reviewed by: bcr (manpages), tuexen (testing, syzkaller/packetdrill) Input also from: melifaro Relnotes: yes Differential Revision: https://reviews.freebsd.org/D20044
2019-05-08 02:32:11 +00:00
#device tuntap # Packet tunnel.
Create a common i.MX53 config and use it with the two existing i.MX53 boards. This is just intended to split the common config entries out, further cleanup is expected. Reviewed by: ian@, rpaulo@ (earlier version) Differential Revision: https://reviews.freebsd.org/D731
2014-09-07 08:16:27 +00:00
device md # Memory "disks"
#device gif # IPv6 and IPv4 tunneling
#device firmware # firmware assist module
# Ethernet
device ffec # Freescale Fast Ethernet Controller
device miibus # Standard mii bus
# Serial (COM) ports
device uart # Multi-uart driver
device ata
device atapci # Only for helper functions
device imxata
device gpio
device gpioled
device fsliic
device iic
device iicbus
# SCSI peripherals
device scbus # SCSI bus (required for ATA/SCSI)
device da # Direct Access (disks)
device cd # CD
device pass # Passthrough device (direct ATA/SCSI access)
# USB support
options USB_HOST_ALIGN=64 # Align usb buffers to cache line size.
device ehci # OHCI USB interface
device usb # USB Bus (required)
device umass # Disks/Mass storage - Requires scbus and da
device uhid # "Human Interface Devices"
#device ukbd # Allow keyboard like HIDs to control console
device ums
# USB Ethernet, requires miibus
#device miibus
#device aue # ADMtek USB Ethernet
#device axe # ASIX Electronics USB Ethernet
#device cdce # Generic USB over Ethernet
#device cue # CATC USB Ethernet
#device kue # Kawasaki LSI USB Ethernet
#device rue # RealTek RTL8150 USB Ethernet
#device udav # Davicom DM9601E USB
# USB Wireless
#device rum # Ralink Technology RT2501USB wireless NICs
# Watchdog timer.
# WARNING: can't be disabled!!!
device imxwdt # Watchdog
# Wireless NIC cards
device wlan # 802.11 support
device wlan_wep # 802.11 WEP support
device wlan_ccmp # 802.11 CCMP support
device wlan_tkip # 802.11 TKIP support
device wlan_amrr # AMRR transmit rate control algorithm
# MMC
#device sdhci # SD controller
#device mmc # SD/MMC protocol
#device mmcsd # SDCard disk device
# Flattened Device Tree
tart to clean up the armv6 kernel configs by reducing the diff between them in the first sections and the later FDT support. Differential Revision: https://reviews.freebsd.org/D1346 Reviewed by: rpaulo (earlier version)
2014-12-21 11:37:00 +00:00
options FDT # Configure using FDT/DTB data
Build modules specific to imx5/imx6 only when building those kernels. This adds sys/modules/imx with a SUBDIR makefile to make the whole collection of modules that are specific to these SoCs. Initially, that "whole collection" consists of the if_ffec and imx_i2c drivers. The if_ffec driver is referenced in its existing home in ../ffec rather than moving it into the imx directory, because it's used by powerpc too, but it is no longer built for all armv6/7 systems. The imx_i2c driver is newly added as a module.
2018-02-18 02:48:54 +00:00
makeoptions MODULES_EXTRA="dtb/imx5 imx"
Move device statements out of std.imx* and into kernel config files. In the armv4/5 world device statements in these files were common, but in the v6/7 world, other socs don't put device statements into those files, so this just brings imx5 and imx6 into line with the current conventions.
2018-07-08 21:09:52 +00:00
device fdt_pinctrl # FDT pinmux driver
Reference in New Issue Copy Permalink