TI SDK supports images with real-time kernel. Add support for building
such images for the `current` release by adding a config file for it.
The RT image is built with the `current-rt` branch.
Signed-off-by: Suhaas Joshi <s-joshi@ti.com>
- BeagleBoard.org boards normally ship with USB cdc enabled to allow
network sharing and ssh support over usb.
- This is specially important for boards like pocketbeagle2 since it
does not have built-in wifi.
Signed-off-by: Ayush Singh <ayush@beagleboard.org>
Change from "y" to "m"
Before
[ 2.423992] rtc-hym8563 1-0051: no valid clock/calendar values available
[ 2.424718] rtc-hym8563 1-0051: registered as rtc0
[ 2.425770] rtc-hym8563 1-0051: no valid clock/calendar values available
[ 2.425789] rtc-hym8563 1-0051: hctosys: unable to read the hardware clock
[ 3.817166] rk808-rtc rk808-rtc.5.auto: registered as rtc1
After
[ 3.790107] rk808-rtc rk808-rtc.5.auto: registered as rtc0
[ 3.801742] rk808-rtc rk808-rtc.5.auto: setting system clock to 2017-08-05T09:48:13 UTC (1501926493)
[ 3.919628] rtc-hym8563 1-0051: registered as rtc1
Signed-off-by: Patrick Yavitz <pyavitz@gmail.com>
Enables kernel options that are important for making armbian viable for use on PocketBeagle 2.
Can now run all examples present in the beagle examples repo: https://github.com/beagleboard/vsx-examples
Signed-off-by: Ayush Singh <ayush@beagleboard.org> Andrei Aldea <andrei@beagleboard.org>
From the Kconfig:
```
Preload default EDID (Extended Display Identification Data)
branded by Linux Foundation that exposes display modes up
to 4k@30Hz, which have best compatibility with HDMI transmitters.
Enabling this option is recommended for a non-production use-cases.
It will make driver usable out-of-the-box.
For a higher display modes you will need to load customized EDID
from userspace using v4l2-ctl tool or by other means.
Without enabling this option driver will be practically
non-functional until EDID will be loaded from userspace.
Which is a wanted behavior when using this driver in a
commercial product that should utilize own branded EDID.
```
When RTL8152 USB network is enabled as build-in, it will throw out warnings such as:
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156b-2.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156a-2.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153c-1.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153b-2.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-4.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-3.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-2.fw for built-in driver r8152
This should prevent this while keep driver as module.
add some missing configs and fix update-initramfs
problems by switching to build-in for some modules
- USB_ONBOARD_DEV now build-in
- ARM_IMX_BUS_DEVFREQ now build-in
Signed-off-by: Martin Schmiedel <Martin.Schmiedel@tq-group.com>