linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: Samsung SoCs framebuffer re-work
Date: Tue, 18 May 2010 03:50:58 +0100	[thread overview]
Message-ID: <20100518025058.GL27571@trinity.fluff.org> (raw)
In-Reply-To: <AANLkTinThrLrsxBYHs-1xPqIaRiK1HH-YZkcloKHnzkx@mail.gmail.com>

On Tue, May 18, 2010 at 08:59:29AM +0900, Kyungmin Park wrote:
> Hi Ben,
> 
> Currently there's only one fb drivers for samsung SocS. but it's based
> on s3c24xx and a part of s3c64xx.

Your statement is incorrect, we have the s3c2410-fb driver which deals
with the 2410/2440/2412 style hardware and s3c-fb which is for the newer
devices.

> As you can see the s5pc110 (aka s5pv210) spec, It has more features
> and interconnection between FIMC and FIMD.
> So current fb driver can't handle these features well. So LSI make a
> own fb drivers and use it. You can see the code at their git repo.
> 
> Now we are re-implement or change it for s5pc110 and for future usages.
> How do you think?

I've already got updates for s3c-fb to work on 2416,2443 and the c110/v210
systems. I am talking with the relevant people at System.LSI to get our
drivers closers together, possibly we can get this done for the current
merge window.

-- 
Ben

Q:      What's a light-year?
A:      One-third less calories than a regular year.

  parent reply	other threads:[~2010-05-18  2:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-17 23:59 Samsung SoCs framebuffer re-work Kyungmin Park
2010-05-18  1:41 ` Kukjin Kim
2010-05-18  2:50 ` Ben Dooks [this message]
2010-05-18  3:09   ` Kyungmin Park
2010-05-18  5:53     ` Ben Dooks
2010-05-18  6:54       ` Pawel Osciak
2010-05-18  7:16         ` Ben Dooks
2010-05-18  7:58           ` Pawel Osciak

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=20100518025058.GL27571@trinity.fluff.org \
    --to=ben-linux@fluff.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).