All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: James Simmons <jsimmons@infradead.org>
Cc: Dmitry Torokhov <dtor@insightbb.com>,
	Miguel Ojeda <maxextreme@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	oLinux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>,
	Luming Yu <Luming.yu@intel.com>,
	Andrew Zabolotny <zap@homelink.ru>,
	linux-acpi@vger.kernel.org, kernel-discuss@handhelds.org,
	lcd4linux-devel@sf.net
Subject: Re: Display class
Date: Sat, 13 Jan 2007 23:55:14 -0800	[thread overview]
Message-ID: <20070114075514.GE10585@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0701132225530.18652@pentafluge.infradead.org>

On Sat, Jan 13, 2007 at 10:40:55PM +0000, James Simmons wrote:
> 
> > Hi,
> > 
> > On Tuesday 05 December 2006 13:03, James Simmons wrote:
> > > +int probe_edid(struct display_device *dev, void *data)
> > > +{
> > > +???????struct fb_monspecs spec;
> > > +???????ssize_t size = 45;
> 
> That code was only for testing. I do have new core code. Andrew could 
> you merge this patch as it is against the -mm tree.
> 
> This new class provides a way common interface for various types of 
> displays such as LCD, CRT, LVDS etc. It is a expansion of the lcd
> class to include other types of displays.

Have you worked with the DRM developers who also need to tie into this
CRT class somehow?

thanks,

greg k-h

  parent reply	other threads:[~2007-01-14  7:55 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-14 19:41 ACPI output/lcd/auxdisplay mess James Simmons
2006-11-14 19:41 ` James Simmons
2006-11-14 22:26 ` Miguel Ojeda
2006-11-15  0:54   ` James Simmons
2006-11-15  0:54     ` James Simmons
2006-11-16  8:45     ` Miguel Ojeda
2006-11-16 15:38       ` James Simmons
2006-11-16 21:48         ` Miguel Ojeda
2006-12-05 18:03     ` Display class James Simmons
2006-12-06  1:14       ` Randy Dunlap
2006-12-06 15:10         ` James Simmons
2006-12-06 18:14           ` Randy Dunlap
2006-12-06 18:14             ` Randy Dunlap
2006-12-06 18:24             ` James Simmons
2006-12-06 18:57               ` Randy Dunlap
2006-12-06 18:57                 ` Randy Dunlap
2006-12-06 19:13                 ` James Simmons
     [not found]           ` <Pine.LNX.4.64.0612061443180.28745-nGpKsS7K33UUkNsaar8edxWb9i9o6OzJ@public.gmane.org>
2006-12-06 20:28             ` Randy Dunlap
2006-12-06 20:28               ` Randy Dunlap
2006-12-06 13:19       ` Miguel Ojeda
2006-12-30  3:32       ` Dmitry Torokhov
2007-01-13 22:40         ` James Simmons
2007-01-13 22:47           ` [Linux-fbdev-devel] " James Simmons
2007-01-14  7:54           ` Greg KH
2007-01-14  7:55           ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-12-06 18:44 Miguel Ojeda Sandonis
2006-12-06 19:06 ` Miguel Ojeda
2006-12-07 15:20 ` James Simmons
2006-12-07 16:21   ` Miguel Ojeda
2006-12-08 11:58   ` Miguel Ojeda

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=20070114075514.GE10585@kroah.com \
    --to=greg@kroah.com \
    --cc=Luming.yu@intel.com \
    --cc=dtor@insightbb.com \
    --cc=jsimmons@infradead.org \
    --cc=kernel-discuss@handhelds.org \
    --cc=lcd4linux-devel@sf.net \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxextreme@gmail.com \
    --cc=zap@homelink.ru \
    /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.