From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, Greg KH <greg@kroah.com>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/5] VT binding: Add new doc file describing the feature
Date: Sun, 11 Jun 2006 12:36:22 +0800 [thread overview]
Message-ID: <448B9DC6.8030109@gmail.com> (raw)
In-Reply-To: <9e4733910606102027o8438d55webf938dfc8495ea8@mail.gmail.com>
Jon Smirl wrote:
> On 6/10/06, Antonino A. Daplas <adaplas@gmail.com> wrote:
>> My point is: 'Multiple active drivers feature' is a natural consequence
>> of the evolution of the code, but the only way to take advantage of it
>> is if we provide a means for the user to use it. And we are not
>> providing the means.
>
> I'd rather not provide the means and defer this capability to a user
> space implementation where we can achieve true multi-user,
> multi-adapter and multi-head support. The more features we add to the
> VT layer today, the harder it will be to replace it in the future.
No, I'm not adding any new features. We have bind capability, the only
added feature is unbind, that's it.
>
> I'd like to keep the sysfs attributes as simple as possible because if
> they get too complex and flexible no one is going to know how to set
> them. But you're writing the code and you'll do what you think is
> best.
I'm just trying to evolve the code, with the least amount or no breakage.
There's nothing revolutionary here.
Tony
next prev parent reply other threads:[~2006-06-11 4:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 8:40 [PATCH 5/5] VT binding: Add new doc file describing the feature Antonino A. Daplas
2006-06-10 5:53 ` Jon Smirl
2006-06-10 13:27 ` Antonino A. Daplas
2006-06-10 16:16 ` Jon Smirl
2006-06-10 17:01 ` Jon Smirl
2006-06-10 17:22 ` Jon Smirl
2006-06-10 21:26 ` Antonino A. Daplas
2006-06-10 23:44 ` Jon Smirl
2006-06-11 0:21 ` Antonino A. Daplas
2006-06-11 0:49 ` Jon Smirl
2006-06-11 1:05 ` Jon Smirl
2006-06-11 1:44 ` Antonino A. Daplas
2006-06-11 2:26 ` Jon Smirl
2006-06-11 3:05 ` Antonino A. Daplas
2006-06-12 8:31 ` Geert Uytterhoeven
2006-06-11 1:16 ` Antonino A. Daplas
2006-06-11 2:05 ` Jon Smirl
2006-06-11 3:03 ` Antonino A. Daplas
2006-06-11 3:27 ` Jon Smirl
2006-06-11 4:36 ` Antonino A. Daplas [this message]
2006-06-11 4:46 ` Antonino A. Daplas
2006-06-11 20:59 ` Jon Smirl
2006-06-11 22:04 ` Antonino A. Daplas
2006-06-11 3:09 ` Randy.Dunlap
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=448B9DC6.8030109@gmail.com \
--to=adaplas@gmail.com \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=jonsmirl@gmail.com \
--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).