public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Miguel Ojeda <maxextreme@gmail.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.19-rc1 V9] drivers: add LCD support
Date: Mon, 9 Oct 2006 00:07:22 +0200	[thread overview]
Message-ID: <20061008220722.GG4152@elf.ucw.cz> (raw)
In-Reply-To: <653402b90610081436w34d692ecv2dd9801c451ab490@mail.gmail.com>

Hi!

> >Yep... but when we have /dev/fbcfag12864b ... do we need
> >/dev/cfag12864bX ? I think it is useless at that point.
> 
> Well, because cfag12864b is the generic one I think it should be in
> the /dev directory (whatever if you use or don't it / whatever if it
> is useless or not).

I do not understand, both /dev/fbcfag12864b and /dev/cfag12864bX are
in /dev/...

What is advantage of /dev/cfag12864bX over /dev/fbcfag12864b ?

(And I guess you should invent better name... /dev/fbaux0?)

> >/dev/fbcfag12864b is very easy to "manipulate by hand" too.
> 
> Yep, IMO we should add a Kconfig option instead of mixing both by
> default (cfag12864b and fbcfag12864b); anyway I think having
> cfag12864b & fbcfag12864b is better than mixing it all in one
> module.

I do not think we need a Kconfig option, and I do not think we need
/dev/cfag12864bX . Just use /dev/fbaux0, always.

> modules as they are now and add the fbcfag12864b later in time: I'm
> waiting them to get into one of the -rcs without more radical changes.

I do not think it is suitable for -rc at this point, and it does not
have chance before 2.6.20-rc1, anyway.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2006-10-08 22:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06  0:29 [PATCH 2.6.19-rc1 V9] drivers: add LCD support Miguel Ojeda Sandonis
2006-10-08 18:24 ` Pavel Machek
2006-10-08 18:37   ` Miguel Ojeda
2006-10-08 19:12     ` Pavel Machek
     [not found]       ` <653402b90610081312m32fcf7ecx9929ae9dc4768c17@mail.gmail.com>
     [not found]         ` <20061008211550.GE4152@elf.ucw.cz>
2006-10-08 21:36           ` Miguel Ojeda
2006-10-08 22:07             ` Pavel Machek [this message]
2006-10-08 22:45               ` Miguel Ojeda
2006-10-09 13:33                 ` Stefan Richter
2006-10-09 13:56                   ` Miguel Ojeda
2006-10-10 10:37                 ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2006-10-05 16:26 Miguel Ojeda Sandonis

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=20061008220722.GG4152@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxextreme@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