All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Bill Nottingham <notting@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH, RFC, BAD IDEA] /proc/tty/console
Date: Fri, 29 Feb 2008 12:49:42 -0800	[thread overview]
Message-ID: <20080229124942.fd402273.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080229150730.GA8209@nostromo.devel.redhat.com>

On Fri, 29 Feb 2008 10:07:30 -0500
Bill Nottingham <notting@redhat.com> wrote:

> Andrew Morton (akpm@linux-foundation.org) said: 
> > > The attached patch adds /proc/tty/console. The contents of it are
> > > simply a description of the current drivers attached to /dev/console.
> > > For example, a boot with 'console=ttyS3,115200n1 console=tty0' would
> > > yield:
> > > 
> > > # cat /proc/tty/console
> > > unknown             /dev/tty0
> > > serial              /dev/ttyS3
> > 
> > I must say that the what-consoles-are-registered problem makes my head spin
> > sometimes too.  Seems a worthy objective.
> > 
> > However I think that a bunch of plain old printks which are emitted when a
> > console is added or removed would suffice?
> 
> We already do that in register_console(), albeit without flags.

oh.

> My concern is I'd like to easily programmatically do something with this
> info - ideally it would be in sysfs so it can easily be used from udev
> or something similar.

That's the sort of information which really must be in the changelog, fully
spelled out.

      reply	other threads:[~2008-02-29 20:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-27 18:18 [PATCH, RFC, BAD IDEA] /proc/tty/console Bill Nottingham
2008-02-27 18:37 ` Randy Dunlap
2008-02-27 18:52   ` Bill Nottingham
2008-02-27 18:56     ` Randy Dunlap
2008-02-29  6:49 ` Andrew Morton
2008-02-29 15:07   ` Bill Nottingham
2008-02-29 20:49     ` Andrew Morton [this message]

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=20080229124942.fd402273.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=notting@redhat.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.