linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: MPC823 and LCD?
Date: Wed, 01 Oct 2003 11:35:41 -0400	[thread overview]
Message-ID: <3F7AF44D.4040101@embeddededge.com> (raw)
In-Reply-To: 3F7A7C9F.4050001@imc-berlin.de


Steven Scholz wrote:

> Ok. So we could move the code into a drivers/video/lcd823.c (or
> mpc823fb.c), put your Copyrigth back in and make it available to all
> MPC823 boards.

How different are these drivers?  You mentioned Wolfgang's version
is "more generic"?  I know lots of people have touched this driver
since the beginning of time, and I think Scott Anderson actually
made it look pretty :-)  I think if the driver remains LCD only,
we need to keep that as part of the name (like lcd823fb.c).  If someone
merges the LCD and YUV video into one driver, then call it something
like mpc823fb.c....I don't care so much about the copyright update
as the loss of the history of people that have worked on it.


Thanks.


	-- Dan


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-10-01 15:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-29 15:59 MPC823 and LCD? Steven Blakeslee
2003-09-30 11:17 ` Steven Scholz
2003-09-30 15:54   ` Dan Malek
2003-10-01  7:05     ` Steven Scholz
2003-10-01 15:35       ` Dan Malek [this message]
2003-10-01 15:37         ` Steven Scholz
2003-10-03 22:57         ` Scott Anderson
  -- strict thread matches above, loose matches on Subject: below --
2003-09-30 12:52 Steven Blakeslee
2003-09-29 15:51 Steven Scholz
2003-09-29 16:09 ` Tom Rini
2003-09-30 12:21 ` Wolfgang Grandegger

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=3F7AF44D.4040101@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=steven.scholz@imc-berlin.de \
    /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;
as well as URLs for NNTP newsgroup(s).