| | 1 | [[PageOutline]] |
| | 2 | |
| | 3 | = Video Output on OpenWrt = |
| | 4 | As of [wiki:OpenWrt/building OpenWrt 16.02], we have introduced rudimentary support for display output. Display output for the i.MX IPU was only recently added to the Linux Kernel for HDMI and LVDS. Since our [wiki:OpenWrt/building OpenWrt 16.02] BSP is on a newer 4.4.0 kernel, we were able to take advantage of this. |
| | 5 | |
| | 6 | Please see [wiki:linux/display linux/display] for details on configuring the output for OpenWrt. |
| | 7 | |
| | 8 | == User Interface == |
| | 9 | By default, we provided a simple framebuffer console for a user to interact with. On boot, if HDMI or LVDS displays were detected, OpenWrt will open a getty on it and prompt the user with {{{Please press Enter to activate this console.}}}. After hitting enter on a USB keyboard, the user is able to interact with the OpenWrt serial console. To disable or change this feature, please view [https://github.com/Gateworks/openwrt/commit/abff4b3eaae9c398f2efcfc9c4e04b40476df09e this patch]. The line {{{'tty1::askfirst:/bin/ash --login'}}} may be removed if you want to disable this feature or changed to allow for something else. For a small overview of this, please visit [https://wiki.openwrt.org/doc/techref/process.boot#busybox_init this OpenWrt page]. |
| | 10 | |
| | 11 | For example, if you want to keep the framebuffer console for user interaction, but want to add a login prompt, you will have to follow the advice found here[3]. You will have to add the 'busybox' version of the login utility, then switch whatever TTY's you want to have password protection to using it. |
| | 12 | |
| | 13 | References: |
| | 14 | * [wiki:linux/display Linux Display Page] |
| | 15 | * [wiki:Yocto/Video_Out Yocto Video Out Page] |
| | 16 | * https://wiki.openwrt.org/doc/techref/process.boot#busybox_init |
| | 17 | * https://wiki.openwrt.org/doc/howto/serial.console.password |
