diff options
author | André Erdmann <dywi@mailerd.de> | 2014-10-09 15:58:02 +0200 |
---|---|---|
committer | Peter Korsgaard <peter@korsgaard.com> | 2014-10-12 15:37:01 +0200 |
commit | c95bf441a6e13d74a67bef95cc12ec5ae80ebbca (patch) | |
tree | 5fe8f11fd7c072e97d31af2e04de46e126a37aea /package/opencv/opencv-0001-core-fix-x86-PIC-code-compilation.patch | |
parent | 3c25f6e6c0a57daac4786dbdf2f0242273641566 (diff) | |
download | buildroot-c95bf441a6e13d74a67bef95cc12ec5ae80ebbca.tar.gz buildroot-c95bf441a6e13d74a67bef95cc12ec5ae80ebbca.zip |
package/systemd: fix getty setup
When trying to run a buildroot system configured with
BR2_TARGET_GENERIC_GETTY_PORT="tty1" (x86_64), the boot process hangs
with the following message:
"A start job is running for dev-tty1.device (<time> / 1min 30s)"
Replacing /etc/systemd/system/getty.target.wants/serial-getty@tty1.service
(linking to serial-getty@) with getty@tty1.service (-> getty@) fixes the issue.
This patch adds a check that "detects" the tty type by removing digits at the
end of BR2_TARGET_GENERIC_GETTY_PORT and comparing the resulting base name.
An instance of getty@service gets created if the name matches "tty",
otherwise serial-getty@ gets instantiated (as before).
So, tty1,tty2,... are created as links getty@tty1.service -> getty@,
while ttyS0, ttyAMA0, ... are created as instances of serial-getty@.
[Peter: simplify logic]
Signed-off-by: André Erdmann <dywi@mailerd.de>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Diffstat (limited to 'package/opencv/opencv-0001-core-fix-x86-PIC-code-compilation.patch')
0 files changed, 0 insertions, 0 deletions