All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@buildroot.org
Cc: Gerome Burlats <gerome.burlats@smile.fr>,
	Romain Naour <romain.naour@gmail.com>
Subject: [Buildroot] [PATCH 1/3] configs/qemu_aarch64_virt_defconfig: don't hard code getty port
Date: Sat, 22 Jan 2022 16:37:11 +0100	[thread overview]
Message-ID: <20220122153714.26991-1-peter@korsgaard.com> (raw)

The Linux defconfig both has VT and serial port support, so it makes more
sense to run getty on /dev/console instead of hard coding the serial port.

Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
---
 configs/qemu_aarch64_virt_defconfig | 1 -
 1 file changed, 1 deletion(-)

diff --git a/configs/qemu_aarch64_virt_defconfig b/configs/qemu_aarch64_virt_defconfig
index e6b72d8838..0caf38112d 100644
--- a/configs/qemu_aarch64_virt_defconfig
+++ b/configs/qemu_aarch64_virt_defconfig
@@ -4,7 +4,6 @@ BR2_cortex_a53=y
 
 # System
 BR2_SYSTEM_DHCP="eth0"
-BR2_TARGET_GENERIC_GETTY_PORT="ttyAMA0"
 
 # Filesystem
 BR2_TARGET_ROOTFS_EXT2=y
-- 
2.20.1

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2022-01-22 15:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-22 15:37 Peter Korsgaard [this message]
2022-01-22 15:37 ` [Buildroot] [PATCH 2/3] configs/qemu_aarch64_virt_defconfig: linux.config: enable fb/input support Peter Korsgaard
2022-01-22 15:37 ` [Buildroot] [PATCH 3/3] configs/qemu_aarch64_virt_defconfig: bump Linux kernel to 5.15.16 Peter Korsgaard
2022-01-23 10:56   ` Romain Naour
2022-01-23 14:48     ` Peter Korsgaard
2022-01-23 15:48       ` Romain Naour
2022-01-22 19:10 ` [Buildroot] [PATCH 1/3] configs/qemu_aarch64_virt_defconfig: don't hard code getty port Yann E. MORIN

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220122153714.26991-1-peter@korsgaard.com \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=gerome.burlats@smile.fr \
    --cc=romain.naour@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.