From: bernhard@bwalle.de
To: ptxdist@pengutronix.de
Cc: Bernhard Walle <walle@corscience.de>
Subject: [ptxdist] [PATCH] Add sp-oops-extract package
Date: Wed, 21 Mar 2012 16:24:06 +0100 [thread overview]
Message-ID: <1332343446-22595-1-git-send-email-bernhard@bwalle.de> (raw)
From: Bernhard Walle <walle@corscience.de>
sp-oops-extract is a simple userspace program to extract kernel oopses
saved on raw MTD with the CONFIG_MTD_OOPS driver. See the comment in
Kconfig for more information on how to use the driver/the tool.
Signed-off-by: Bernhard Walle <walle@corscience.de>
---
...the-Makefile-more-cross-compiler-friendly.patch | 19 +++++++
| 4 ++
| 15 ++++++
| 56 ++++++++++++++++++++
4 files changed, 94 insertions(+)
create mode 100644 patches/sp-oops-extract-0.0.7/0001-Make-the-Makefile-more-cross-compiler-friendly.patch
create mode 100644 patches/sp-oops-extract-0.0.7/series
create mode 100644 rules/sp-oops-extract.in
create mode 100644 rules/sp-oops-extract.make
diff --git a/patches/sp-oops-extract-0.0.7/0001-Make-the-Makefile-more-cross-compiler-friendly.patch b/patches/sp-oops-extract-0.0.7/0001-Make-the-Makefile-more-cross-compiler-friendly.patch
new file mode 100644
index 0000000..df363f7
--- /dev/null
+++ b/patches/sp-oops-extract-0.0.7/0001-Make-the-Makefile-more-cross-compiler-friendly.patch
@@ -0,0 +1,19 @@
+From: Bernhard Walle <walle@corscience.de>
+Date: Wed, 21 Mar 2012 15:55:06 +0100
+Subject: [PATCH] Make the Makefile more cross-compiler friendly
+
+Signed-off-by: Bernhard Walle <walle@corscience.de>
+---
+ src/Makefile | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/Makefile b/src/Makefile
+index cf5b550..c221c83 100644
+--- a/src/Makefile
++++ b/src/Makefile
+@@ -9,4 +9,4 @@ distclean: clean
+ $(RM) $(TARGETS)
+
+ sp-oops-extract: oopslog.c
+- gcc -Wall -s -o $@ $^
++ $(CROSS_COMPILE)$(CC) -Wall -s -o $@ $^
--git a/patches/sp-oops-extract-0.0.7/series b/patches/sp-oops-extract-0.0.7/series
new file mode 100644
index 0000000..6053a64
--- /dev/null
+++ b/patches/sp-oops-extract-0.0.7/series
@@ -0,0 +1,4 @@
+# generated by git-ptx-patches
+#tag:base --start-number 1
+0001-Make-the-Makefile-more-cross-compiler-friendly.patch
+# 1e23689ed7181ffae1913ee9c0c2db54 - git-ptx-patches magic
--git a/rules/sp-oops-extract.in b/rules/sp-oops-extract.in
new file mode 100644
index 0000000..fea83a5
--- /dev/null
+++ b/rules/sp-oops-extract.in
@@ -0,0 +1,15 @@
+## SECTION=debug_tools
+
+config SP_OOPS_EXTRACT
+ tristate
+ prompt "sp-oops-extract"
+ help
+ Tool to extract oopses generated with mtd-oops.ko driver.
+
+ To use that mechanism, just select CONFIG_MTD_OOPS in the kernel
+ configuration and add 'mtdoops.mtddev=<devno>' to your boot command
+ line where '<devno>' is the MTD device number you want to use to save
+ kernel oopses. Alternatively, load the 'mtdoops' module with
+ 'mtddev=<devno>' as module parameter. To extract that oops, just use
+ 'sp-oops-extract /dev/mtd<devno>'.
+
--git a/rules/sp-oops-extract.make b/rules/sp-oops-extract.make
new file mode 100644
index 0000000..265bcdf
--- /dev/null
+++ b/rules/sp-oops-extract.make
@@ -0,0 +1,56 @@
+# -*-makefile-*-
+#
+# Copyright (C) 2012 by Bernhard Walle <walle@corscience.de>
+#
+# See CREDITS for details about who has contributed to this project.
+#
+# For further information about the PTXdist project and license conditions
+# see the README file.
+#
+
+#
+# We provide this package
+#
+PACKAGES-$(PTXCONF_SP_OOPS_EXTRACT) += sp-oops-extract
+
+#
+# Paths and names
+#
+SP_OOPS_EXTRACT_VERSION := 0.0.7
+SP_OOPS_EXTRACT_MD5 := b4e3ff7716c249e3446758582a1cae12
+SP_OOPS_EXTRACT := sp-oops-extract-$(SP_OOPS_EXTRACT_VERSION)
+SP_OOPS_EXTRACT_SUFFIX := tar.gz
+SP_OOPS_EXTRACT_ARCHIVE := sp-oops-extract_$(SP_OOPS_EXTRACT_VERSION)-1.$(SP_OOPS_EXTRACT_SUFFIX)
+SP_OOPS_EXTRACT_URL := http://repository.maemo.org/pool/fremantle/free/s/sp-oops-extract/$(SP_OOPS_EXTRACT_ARCHIVE)
+SP_OOPS_EXTRACT_SOURCE := $(SRCDIR)/$(SP_OOPS_EXTRACT_ARCHIVE)
+SP_OOPS_EXTRACT_DIR := $(BUILDDIR)/$(SP_OOPS_EXTRACT)
+SP_OOPS_EXTRACT_LICENSE := unknown
+
+# ----------------------------------------------------------------------------
+# Prepare
+# ----------------------------------------------------------------------------
+
+SP_OOPS_EXTRACT_CONF_TOOL := NO
+SP_OOPS_EXTRACT_MAKE_ENV := $(CROSS_ENV)
+SP_OOPS_EXTRACT_MAKEVARS := $(CROSS_ENV)
+
+# ----------------------------------------------------------------------------
+# Target-Install
+# ----------------------------------------------------------------------------
+
+$(STATEDIR)/sp-oops-extract.targetinstall:
+ @$(call targetinfo)
+
+ @$(call install_init, sp-oops-extract)
+ @$(call install_fixup, sp-oops-extract,PRIORITY,optional)
+ @$(call install_fixup, sp-oops-extract,SECTION,base)
+ @$(call install_fixup, sp-oops-extract,AUTHOR,"Bernhard Walle <walle@corscience.de>")
+ @$(call install_fixup, sp-oops-extract,DESCRIPTION,missing)
+
+ @$(call install_copy, sp-oops-extract, 0, 0, 0755, -, /usr/bin/sp-oops-extract)
+
+ @$(call install_finish, sp-oops-extract)
+
+ @$(call touch)
+
+# vim: syntax=make
--
1.7.9.4
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2012-03-21 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 15:24 bernhard [this message]
2012-03-24 9:50 ` Michael Olbrich
2012-03-26 10:49 ` [ptxdist] [PATCH v2] " Bernhard Walle
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=1332343446-22595-1-git-send-email-bernhard@bwalle.de \
--to=bernhard@bwalle.de \
--cc=ptxdist@pengutronix.de \
--cc=walle@corscience.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox