From: "Miguel Ojeda" <maxextreme@gmail.com>
To: jsimmons@infradead.org
Cc: linux-kernel@vger.kernel.org, Luming.yu@intel.com,
zap@homelink.ru, randy.dunlap@oracle.com,
kernel-discuss@handhelds.org
Subject: Re: Display class
Date: Wed, 6 Dec 2006 20:06:24 +0100 [thread overview]
Message-ID: <653402b90612061106i2071ba75ka1a14de6829c85b5@mail.gmail.com> (raw)
In-Reply-To: <20061206194442.422c60d3.maxextreme@gmail.com>
On 12/6/06, Miguel Ojeda Sandonis <maxextreme@gmail.com> wrote:
> Ok, here is the patch (against git7+displayclass) which moves auxdisplay/*
> to video/display/* and start using the display class.
>
> It is just a draft, but there isn't much code changed from -mm2.
>
> - I would remove "struct device *dev, void *devdata" of display_device_register()
> Are they neccesary for other display drivers? I have to pass NULL right now.
>
> - I would add a paramtere ("char *name") to display_device_register() so we
> set the name when registering. Right now I have to set my name after inited,
> and this is a Linux module and not a person borning, right? ;)
>
> - I would add a read/writeable attr called "rate" for set/unset the refresh rate
> of a display.
>
> - I was going to maintain the drivers/auxdisplay/* tree.
> Are you going to maintain the driver? I think so, just for being sure.
I meant display driver (display/*).
>
> P.S.
>
> When I was working at 2.6.19-rc6-mm2 it worked all fine, but now
> I have copied it to git7 I'm getting some weird segmentation faults
> (oops) when at cfag12864bfb_init, at mutex_lock() in
> display_device_unregister module... I think unrelated (?), but I will
>
I meant display_device_unregister function of display-sysfs.c
--
The changes have been made in driver/video/display/cfag12864bfb.c, so
please focus the review on it.
Thanks
next prev parent reply other threads:[~2006-12-06 19:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 18:44 Miguel Ojeda Sandonis
2006-12-06 19:06 ` Miguel Ojeda [this message]
2006-12-07 15:20 ` James Simmons
2006-12-07 16:21 ` Miguel Ojeda
2006-12-08 11:58 ` Miguel Ojeda
-- strict thread matches above, loose matches on Subject: below --
2006-11-14 19:41 ACPI output/lcd/auxdisplay mess James Simmons
2006-11-14 22:26 ` Miguel Ojeda
2006-11-15 0:54 ` James Simmons
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:24 ` James Simmons
2006-12-06 18:57 ` Randy Dunlap
2006-12-06 19:13 ` James Simmons
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-14 7:54 ` Greg KH
2007-01-14 7:55 ` Greg KH
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=653402b90612061106i2071ba75ka1a14de6829c85b5@mail.gmail.com \
--to=maxextreme@gmail.com \
--cc=Luming.yu@intel.com \
--cc=jsimmons@infradead.org \
--cc=kernel-discuss@handhelds.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®