[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45a44e481001041614i35ceef84q5f12a068e2f0b97b@mail.gmail.com>
Date: Tue, 5 Jan 2010 08:14:12 +0800
From: Jaya Kumar <jayakumar.lkml@...il.com>
To: Pavel Machek <pavel@....cz>
Cc: "Rick L. Vinyard, Jr." <rvinyard@...nmsu.edu>,
Jiri Kosina <jkosina@...e.cz>, linux-kernel@...r.kernel.org,
krzysztof.h1@...pl, Andrew Morton <akpm@...ux-foundation.org>,
linux-usb@...r.kernel.org, Oliver Neukum <oliver@...kum.org>,
linux-input@...r.kernel.org
Subject: Re: [PATCH] Logitech G13 driver (fixed cc list --- ignore others)
On Tue, Jan 5, 2010 at 6:48 AM, Pavel Machek <pavel@....cz> wrote:
>
> Ok, but I guess you should cc auxdisplay people in future.
Hi Pavel,
I just looked at the drivers/auxdisplay directory and got a bit
confused. The reason I got confused is because auxdisplay is actually
an fbdev driver but it is outside of the drivers/video directory. It
looks like there has only been 1 commit and that was for the Samsung
KS0108 controller. It also sort of uses platform support but the way
it is abstracted is odd to my thinking. The controller is ks0108, so
in my mind that would be the code that would be platform independent,
and then that would use a board specific IO driver to push data (eg:
parport or gpio or usb). I think in the long term it would probably
make sense to write a cleaner approach with a drivers/video/ks0108.c
which is cleanly platform independent (and back within fbdev proper)
and then a board specific driver in the appropriate location that
handles the IO.
Thanks,
jaya
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists