From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [PATCH v3 0/3] Add command to display or save Linux PStore dumps
Date: Fri, 20 Mar 2020 09:08:42 +0100 [thread overview]
Message-ID: <20200320080842.7DF4524003E@gemini.denx.de> (raw)
In-Reply-To: <a1b7a877-e950-b09a-a0f6-2c9c9cb7e1fb@gmx.de>
Dear Heinrich,
In message <a1b7a877-e950-b09a-a0f6-2c9c9cb7e1fb@gmx.de> you wrote:
>
> > To me this sounds very much like what you are adding here (plus a
> > few features more). Does it make sense to unify such code?
>
> It seems you are relating to
> https://lore.kernel.org/lkml/844oyrqvvb.fsf at sauna.l.org/t/
No, I'm not. I was talking of my own code from many, many years
ago.
> ramoops in Linux is exactly doing what was suggested in 2009. You can
> find the Documentation/admin-guide/ramoops.rst
We had this in U-Boot long before that time. It was a key
requirement when we added POST support in 2002.
> git grep -GHrn 'shared log' finds nothing in U-Boot. So if any part of
> the old implementation in U-Boot exists, could you, please, point us to
> the coding.
The shared log buffer support was added by commit 56f94be3ef63:
commit 56f94be3ef63732384063e110277ed89701b6471 (tag: LABEL_2002_11_05_1735)
Author: Wolfgang Denk <wdenk>
Date: Tue Nov 5 16:35:14 2002 +0000
* Add support for log buffer which can be passed to Linux kernel's
syslog mechanism; used especially for POST results.
* Patch by Klaus Heydeck, 31 Oct 2002:
Add initial support for kup4k board
The code was mainly in common/cmd_log.c, but this got heahily
rewritten and is now in cmd/log.c ; apparently this got lost (like
the original copyright, sic!) when Simon modified / rewrote this
driver.
For history, try: git log --follow -- common/cmd_log.c
> If the original design never made it into Linux and there is an
> established Linux interface since 2011, I would plead to eliminate any
> remaining non-compliant coding from U-Boot should it exist.
I understand what Linus has is one-way, only focussing on crash
dump, i. e. it does not allow to pass information from U-Boot to Linux?
Also, my understanding is that the changes needed in Linux are
pretty small.
Maybe Heiko can comment on that...
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Ken Dodd?s dad?s dog?s dead.
next prev parent reply other threads:[~2020-03-20 8:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 17:57 [PATCH v3 0/3] Add command to display or save Linux PStore dumps Frédéric Danis
2020-03-19 17:57 ` [PATCH v3 1/3] cmd: " Frédéric Danis
2020-03-19 17:57 ` [PATCH v3 2/3] test: Add PStore command tests Frédéric Danis
2020-03-19 20:39 ` Wolfgang Denk
2020-03-19 17:57 ` [PATCH v3 3/3] cmd: Fixup DT to pass PStore Ramoops parameters Frédéric Danis
2020-03-19 19:14 ` Heinrich Schuchardt
2020-03-19 20:37 ` [PATCH v3 0/3] Add command to display or save Linux PStore dumps Wolfgang Denk
2020-03-19 22:30 ` Heinrich Schuchardt
2020-03-20 8:08 ` Wolfgang Denk [this message]
2020-03-20 8:57 ` Heiko Schocher
2020-03-20 10:13 ` Frédéric Danis
2020-03-20 10:35 ` Wolfgang Denk
2020-03-20 11:19 ` Frédéric Danis
2020-03-20 11:29 ` Wolfgang Denk
2020-03-23 15:37 ` Simon Glass
2020-03-23 15:46 ` Tom Rini
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=20200320080842.7DF4524003E@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.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