From: OpenBMC Patches <patches@stwcx.xyz>
To: openbmc@lists.ozlabs.org
Subject: [PATCH openbmc 2/7] Allow login on ttyS4
Date: Mon, 12 Oct 2015 09:16:35 -0500 [thread overview]
Message-ID: <1444659400-4196-3-git-send-email-patches@stwcx.xyz> (raw)
In-Reply-To: <1444659400-4196-1-git-send-email-patches@stwcx.xyz>
From: Brad Bishop <bradleyb@us.ibm.com>
---
.../recipes-extended/shadow/shadow-securetty/securetty.patch | 10 ++++++++++
.../common/recipes-extended/shadow/shadow-securetty_%.bbappend | 4 ++++
meta-phosphor/common/recipes.txt | 4 +++-
3 files changed, 17 insertions(+), 1 deletion(-)
create mode 100644 meta-phosphor/common/recipes-extended/shadow/shadow-securetty/securetty.patch
create mode 100644 meta-phosphor/common/recipes-extended/shadow/shadow-securetty_%.bbappend
diff --git a/meta-phosphor/common/recipes-extended/shadow/shadow-securetty/securetty.patch b/meta-phosphor/common/recipes-extended/shadow/shadow-securetty/securetty.patch
new file mode 100644
index 0000000..6533e4a
--- /dev/null
+++ b/meta-phosphor/common/recipes-extended/shadow/shadow-securetty/securetty.patch
@@ -0,0 +1,10 @@
+--- a/securetty
++++ b/securetty
+@@ -7,6 +7,7 @@ ttyS0
+ ttyS1
+ ttyS2
+ ttyS3
++ttyS4
+
+ # ARM AMBA SoCs
+ ttyAM0
diff --git a/meta-phosphor/common/recipes-extended/shadow/shadow-securetty_%.bbappend b/meta-phosphor/common/recipes-extended/shadow/shadow-securetty_%.bbappend
new file mode 100644
index 0000000..70ab435
--- /dev/null
+++ b/meta-phosphor/common/recipes-extended/shadow/shadow-securetty_%.bbappend
@@ -0,0 +1,4 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+SRC_URI += "file://securetty.patch"
+
diff --git a/meta-phosphor/common/recipes.txt b/meta-phosphor/common/recipes.txt
index c2c88b7..8ebedf8 100644
--- a/meta-phosphor/common/recipes.txt
+++ b/meta-phosphor/common/recipes.txt
@@ -1 +1,3 @@
-recipes-phosphor - Phosphor OpenBMC applications and configuration
+recipes-extended - Applications which whilst not essential add features compared to the alternatives in
+ core. May be needed for full tool functionality or LSB compliance.
+recipes-phosphor - Phosphor OpenBMC applications and configuration
--
2.6.0
next prev parent reply other threads:[~2015-10-12 14:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 14:16 [PATCH openbmc 0/7] bitbake and package files for host-ipmid OpenBMC Patches
2015-10-12 14:16 ` [PATCH openbmc 1/7] Add kernel-cuimage class OpenBMC Patches
2015-10-12 14:16 ` OpenBMC Patches [this message]
2015-10-12 14:16 ` [PATCH openbmc 3/7] Add recipes-connectivity recipes.txt description OpenBMC Patches
2015-10-12 14:16 ` [PATCH openbmc 4/7] Add linux-obmc kernel recipe OpenBMC Patches
2015-10-12 14:16 ` [PATCH openbmc 5/7] Move Palmetto specific metadata to Palmetto layer OpenBMC Patches
2015-10-12 14:16 ` [PATCH openbmc 6/7] " OpenBMC Patches
2015-10-12 14:16 ` [PATCH openbmc 7/7] bitbake and package files for host-ipmid OpenBMC Patches
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=1444659400-4196-3-git-send-email-patches@stwcx.xyz \
--to=patches@stwcx.xyz \
--cc=openbmc@lists.ozlabs.org \
/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.