From: Greg KH <gregkh@suse.de>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/5] VT binding: Add sysfs support
Date: Fri, 9 Jun 2006 15:08:03 -0700 [thread overview]
Message-ID: <20060609220803.GB7636@suse.de> (raw)
In-Reply-To: <448933D7.6040301@gmail.com>
On Fri, Jun 09, 2006 at 04:39:51PM +0800, Antonino A. Daplas wrote:
> Add sysfs attributes for binding and unbinding VT console drivers. The
> attributes are located in /sys/class/tty/console and are namely:
>
> A. backend - list registered drivers in the following format:
>
> "I C: Description"
No, this violates the "one value per file" issue with sysfs. How do you
know you will not overflow the buffer passed to you?
>
> Where: I = ID number of the driver
> C = status of the driver which can be:
>
> S = system driver
> B = bound modular driver
> U = unbound modular driver
>
> Description - text description of the driver
>
> B. bind - binds a driver to the console layer
>
> echo <ID> > /sys/class/tty/console/bind
>
> C. unbind - unbinds a driver from the console layer
>
> echo <ID> > /sys/class/tty/console/unbind
>
> The tty layer does nothing to these attributes except create them and punt all
> requests to the VT layer.
Why is this needed? What is wrong with the current scheme of binding
ttys to the console?
thanks,
greg k-h
next prev parent reply other threads:[~2006-06-09 22:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 8:39 [PATCH 2/5] VT binding: Add sysfs support Antonino A. Daplas
2006-06-09 22:08 ` Greg KH [this message]
2006-06-10 0:38 ` Antonino A. Daplas
2006-06-10 4:37 ` Greg KH
2006-06-10 5:56 ` Antonino A. Daplas
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=20060609220803.GB7636@suse.de \
--to=gregkh@suse.de \
--cc=adaplas@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).