mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Miguel Ojeda" <maxextreme@gmail.com>
To: Franck <vagabon.xyz@gmail.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.19-rc1 full] drivers: add LCD support
Date: Mon, 23 Oct 2006 14:56:56 +0200	[thread overview]
Message-ID: <653402b90610230556y56ef2f1blc923887f049094d4@mail.gmail.com> (raw)
In-Reply-To: <453C8027.2000303@innova-card.com>

On 10/23/06, Franck Bui-Huu <vagabon.xyz@gmail.com> wrote:
> Franck Bui-Huu wrote:
> > Hi
> >
> >
> > sorry for coming lately, I just noticed your patch in -mm tree.
> >
> > Did you took a look at drivers/video/arcfb.c driver ?
> > It seems to be a fb driver for ks108 lcd controller. A lot of code
> > is related to the platform though and the controller is driven
> > through GPIO but have you tried to split the code for sharing
> > controller specific code. Note, I don't say it's a good idea, it's
> > just a question that comes in mind.
> >
> > Also you create driver/auxdisplay directory whereas drivers such
> > the one I mentioned previously is located in drivers/video. Why
> > not putting your driver in driver/video ?
>
> Is this driver is already no more maintained ?
>

The driver is waiting in the -mm tree (-mm2 right now) for being
included in the mainline kernel sometime in the future. If it is
included, I will maintain it as I coded it as it apears in the
MAINTAINERS file. Why are you so worried about it if I can ask? Do you
want some more features or something like that?

I missed the other two questions you wrote few days ago. About the
second one, that was discussed a lot in the past and the people
decided that (it wasn't my idea). About the first one, well, my ks0108
code is the one for the wiring of an auxiliary LCD, so if you read the
discussion you will find the people wanted to split video things and
other auxiliary displays, so I think it is better to split it.
(Anyway, I'm answering quickly, I haven't checked the code you talk
about, but I will anyway).

Thanks,
     Miguel Ojeda

  reply	other threads:[~2006-10-23 12:56 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-13  2:32 Miguel Ojeda Sandonis
2006-10-13 12:43 ` Paulo Marques
2006-10-18 14:55 ` Franck Bui-Huu
2006-10-23  8:41   ` Franck Bui-Huu
2006-10-23 12:56     ` Miguel Ojeda [this message]
2006-10-23 15:35       ` Franck Bui-Huu
2006-10-23 16:21         ` Miguel Ojeda
2006-10-23 16:51           ` Franck Bui-Huu
2006-10-26 14:45             ` Miguel Ojeda
2006-10-27 20:08               ` Franck Bui-Huu
2006-10-27 20:38                 ` Miguel Ojeda
2006-10-30  8:43                   ` Franck Bui-Huu
2006-10-30 13:35                     ` Miguel Ojeda
2006-10-23 16:05       ` Franck Bui-Huu
2006-10-23 16:08         ` Miguel Ojeda
2006-10-23 17:15           ` Franck Bui-Huu
2006-10-26 14:55             ` Miguel Ojeda
2006-10-27 20:03               ` Franck Bui-Huu
2006-10-27 20:25                 ` Miguel Ojeda
2006-10-30  9:26                   ` Franck Bui-Huu
2006-10-30 13:22                     ` Paulo Marques
2006-10-30 14:11                       ` Miguel Ojeda
2006-10-30 15:21                         ` Paulo Marques
2006-10-30 17:32                           ` Miguel Ojeda
2006-10-30 20:45                             ` Paulo Marques
2006-10-31  8:10                       ` Franck Bui-Huu
2006-10-31 14:12                         ` Miguel Ojeda
2006-10-31 14:54                         ` Paulo Marques
2006-10-30 13:47                     ` 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=653402b90610230556y56ef2f1blc923887f049094d4@mail.gmail.com \
    --to=maxextreme@gmail.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vagabon.xyz@gmail.com \
    /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®