linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [RFC] add class/video to fb drivers - Take 2
Date: Wed, 20 Aug 2003 14:33:31 -0700	[thread overview]
Message-ID: <20030820213331.GA4894@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0308202227490.9662-100000@phoenix.infradead.org>

On Wed, Aug 20, 2003 at 10:28:28PM +0100, James Simmons wrote:
> 
> > Well, it's not "ideal" but it will do for 2.6 to use this patch.  If you
> > look at the tty core, it's the same way that currently works.
> > 
> > Ideally in 2.7 I'd like to convert to have all fb drivers create the
> > fb_info structure dynamically, but that's much to big of a change to do
> > this late in the 2.6 development cycle.
> 
> What is the advantage of creating every fb_info dynamically?

Then we can add a struct class_device into fb_info, which will allow us
to export sysfs attributes for each fb_info device to userspace.  It
will provide the proper lifetime rules for such structures, and allow
the individual drivers a place within sysfs to export different things
they might want to export.  Any /proc files you currently have could
then be removed.

For an example of what needs to be done, see the recent v4l core changes
that were just introduced into the kernel tree.

Again, this is a 2.7 thing (which could easily be backported to 2.6.late
afterwards), nothing I want to attempt to do at this time.

thanks,

greg k-h

      reply	other threads:[~2003-08-20 21:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-19  0:27 [RFC] add class/video to fb drivers Greg KH
2003-08-20 19:10 ` [RFC] add class/video to fb drivers - Take 2 Greg KH
2003-08-20 21:16   ` James Simmons
2003-08-20 21:26     ` Greg KH
2003-08-20 21:28       ` James Simmons
2003-08-20 21:33         ` Greg KH [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=20030820213331.GA4894@kroah.com \
    --to=greg@kroah.com \
    --cc=jsimmons@infradead.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).