From: Takashi Iwai <tiwai@suse.de>
To: Struan Bartlett <struan.bartlett@gmail.com>
Cc: Andreas Schwab <schwab@suse.de>,
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: Support for netconsole as default tty/console?
Date: Wed, 02 Apr 2014 12:26:36 +0200 [thread overview]
Message-ID: <s5hvbust4bn.wl%tiwai@suse.de> (raw)
In-Reply-To: <CAOte+=YTaq76D22MRUhToFJLcb78P_LNY1p+viMHqyqwkHjLzg@mail.gmail.com>
At Tue, 1 Apr 2014 10:34:27 +0200,
Struan Bartlett wrote:
>
> On 31 March 2014 14:34, Andreas Schwab <schwab@suse.de> wrote:
> > One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk> writes:
> >
> >> It's however implemented and present. The rest is between you and the
> >> relevant Kconfig maintainer. I'm sure you count as an expert ;-)
> >
> > Indeed.
> >
> > http://lists.opensuse.org/opensuse-kernel/2014-03/msg00071.html
>
> I have just completed an implementation of a tty driver for
> netconsole, which I was about to submit as a patch. When the kernel
> command line is set accordingly (console=netcon0), it has the desired
> effect of taking over output to /dev/console when it is loaded. Would
> you say this work is wasted, or that it's worth submitting the patch
> anyway?
>
> There are differences to the ttyprintk approach. ttyprintk is
> currently kernel-only, and not available as a module.
Actually, this can be easily fixed. I'm going to submit a patch (and
another fix patch for the driver's error path).
Note that they don't mean to object against your patching netconsole.
I find also it more convenient to use directly netconsole.
thanks,
Takashi
next prev parent reply other threads:[~2014-04-02 10:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-29 12:22 Support for netconsole as default tty/console? Struan Bartlett
2014-03-29 14:54 ` Andreas Schwab
2014-03-30 8:44 ` Struan Bartlett
2014-03-30 11:39 ` Andreas Schwab
2014-03-31 10:18 ` One Thousand Gnomes
2014-03-31 10:26 ` Andreas Schwab
2014-03-31 12:32 ` One Thousand Gnomes
2014-03-31 12:34 ` Andreas Schwab
2014-04-01 8:34 ` Struan Bartlett
2014-04-02 10:26 ` Takashi Iwai [this message]
2014-03-31 18:33 ` Arkadiusz Miskiewicz
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=s5hvbust4bn.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=schwab@suse.de \
--cc=struan.bartlett@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.