public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Althoefer <stefan.althoefer@web.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] video: Add new driver for Silicon Motion SM501/SM502 Part 1/2
Date: Sun, 07 Dec 2008 11:07:48 +0100	[thread overview]
Message-ID: <ghg782$ta5$1@ger.gmane.org> (raw)
In-Reply-To: <20081207004728.1FB58834B020@gemini.denx.de>

Dear All,

> Dear Anatolij & Stefan,
> 
> In message <493AD29C.80409@denx.de> you wrote:
>>> Use CONFIG_VIDEO_SM501NEW to enable the driver.
>> not sure if CONFIG_VIDEO_SM501NEW is a good chose here. Maybe
>> we should use s.th. like CONFIG_VIDEO_SM50x. This applies to
>> the file names too: sm50x.h, sm50x.c, etc. Even better would
>> be a merge with the existing driver.
> 
> I agree with Anatolij here. A merge would definitely be best.

Before I start to implement the good suggestions, I'd like
to know how such a merge would look like in your opinion.

Over the long term, I see the old driver vanishing, as it is too
complicated to use (you need to be a video and SMI register
expert). It is not much more than a jump into the board specific
setup routines. However, removing the old driver would break half
a dozen  of boards (inacceptable).

BTW the driver will probably also work with the new SM107,
which as no USB, Keyboard and all this stuff.

-- Stefan

  parent reply	other threads:[~2008-12-07 10:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-04 21:10 [U-Boot] [PATCH] video: Add new driver for Silicon Motion SM501/SM502 Part 1/2 Stefan Althoefer
2008-12-06 19:29 ` Anatolij Gustschin
2008-12-06 22:35   ` Stefan Althoefer
2008-12-07  0:47   ` Wolfgang Denk
2008-12-07  6:33     ` ksi at koi8.net
2008-12-07  9:44       ` Wolfgang Denk
2008-12-07 18:19         ` ksi at koi8.net
2008-12-07 21:23           ` Wolfgang Denk
2008-12-07 22:21             ` ksi at koi8.net
2008-12-07 10:07     ` Stefan Althoefer [this message]
2008-12-08 13:03       ` Anatolij Gustschin

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='ghg782$ta5$1@ger.gmane.org' \
    --to=stefan.althoefer@web.de \
    --cc=u-boot@lists.denx.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