From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: barebox@lists.infradead.org
Subject: [PATCH 0/9 v5] introduction of dmesg support
Date: Thu, 7 Mar 2013 22:25:23 +0100 [thread overview]
Message-ID: <20130307212523.GK4401@game.jcrosoft.org> (raw)
HI,
v5: rebase on master
add missing kern_levels.h
v4: remove a debug info
v3: add more swtich
we currently have 2 fifo at comsole level one for input one for output
we fill the output fifo before any console is registered and then
empty it
Now we introduce a new mecanism as in the kernel dmesg
we will always fill the dmesg kfifo with drivers output
as in barebox we have 2 world
device/drivers and applicaiotn (commands)
the verbositty of the printk can be selected at runtime and
compilation
so for now on drivers will have to use pr_xxx and dev_xxx and
application will use printf
dmesg will print the kfifo at any time
we will extend this later with more control of what the drivers output
on the console or just in the fifo
This new feature is optionnal if dmes is disable we continue as before
The following changes since commit 092bfd5eb55d1b2d7ed098aa9723a2fa63b86192:
fix another brown paper bag bug introduced with compile time loglevel (2013-03-06 23:53:04 +0100)
are available in the git repository at:
git://git.jcrosoft.org/barebox.git delivery/dmesg
for you to fetch changes up to 2ed2d3d1c481302eea186d5639022aedc1bd6e28:
barebox_banner: switch to pr_info (2013-03-08 05:21:39 +0800)
----------------------------------------------------------------
Jean-Christophe PLAGNIOL-VILLARD (9):
kfifo: introduce kfifo_dump_str to dump the fifo
console: switch to kfifo_dump_str
intoduce dmesg to print the barebox printk to dmesg ring buffer
startup: switch to pr_xxx
at91: clock switch to pr_info
meminfo: switch to pr_xxx
net/console: switch to pr_xxx
startup: switch to pr_xxx
barebox_banner: switch to pr_info
arch/arm/mach-at91/clock.c | 2 +-
commands/Kconfig | 19 +++++++++++++++++++
common/console.c | 125 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++---
common/meminfo.c | 6 +++---
common/startup.c | 12 ++++++------
common/version.c | 4 ++--
drivers/base/driver.c | 18 ++++++++++++------
include/kfifo.h | 2 ++
include/linux/barebox-wrapper.h | 11 -----------
include/linux/kern_levels.h | 25 +++++++++++++++++++++++++
include/printk.h | 59 ++++++++++++++++++++++++++++++++++++++++++-----------------
lib/kfifo.c | 21 +++++++++++++++++++++
net/netconsole.c | 4 ++--
13 files changed, 257 insertions(+), 51 deletions(-)
create mode 100644 include/linux/kern_levels.h
Best Regards,
J.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
reply other threads:[~2013-03-07 21:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130307212523.GK4401@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox