linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ben@trinity.fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: Announcing s3c64xx XWindows fbdrv w/ XAA+XVideo+HWcursor
Date: Thu, 24 Sep 2009 22:09:58 +0100	[thread overview]
Message-ID: <20090924210958.GI31920@trinity.fluff.org> (raw)
In-Reply-To: <200909241742.n8OHgLHr004520@chronolytics.com>

On Thu, Sep 24, 2009 at 01:42:20PM -0400, David F. Carlson wrote:
> 
> S3C6410 based Xwindows fbdev with
>    o  XAA accelerated fills, lines, expands, blits, offscreen pixmaps/stipples
>    o  Alpha-blended HWCursor 
>    o  XVideo Support (using the Samsung Post-Processor colorspace driver)
>    o  Tested with the Maemo Mer kernel 2.6.24.7 because...
> 
> This is not as off topic as it might seem...
> 
> The XWindows subsystem needs help from the kernel in s3cfb "standards" 
> (support MMIO interface) and configuration (how to configure per-screen 
> offscreen memory), some scheme for accessing the Post-Processor and G2D 
> graphics support.  (And of course, gaining driver support for pp and g2d 
> including suspend/resume.)

Are the necessary changes for the s3cfb postable to the list to start
the review process for them?
 
> This driver is pretty much hardcoded for s3c64xx.  If kernel hooks for 
> describing configuration this driver base could be expanded to 
> support many s3c variants (with g2d and pp).

It would be good to get the discussion about these items going before
we get too much further down the development process.
 
> There is some discussion in the the README.
> 
> http://chronolytics.com/mid/README
> http://chronolytics.com/mid/fbdev_xaa_pp_hwcurs.tgz
> 
> Acknowledgements:
> 
> The most excellent XAA base code was done by 
>    Matan Ziv-Av <matan@svgalib dot org>
> 
> The original XVideo code was done by 
>    Jetta Tang <jetta.tang@hhcn dot com>
> 
> The g2d and pp drivers upon which this code is based were provided by
>    Samsung Semiconductor.  Thanks.
> 
> Time and Materials and Hosting 
>    Chronolytics Inc.  Real-Time Embedded Software  http://chronolytics.com
> 
> David F. Carlson    Chronolytics, Inc.  Rochester, NY
> mailto:dave at chronolytics.com            http://www.chronolytics.com
> 
> "The faster I go, the behinder I get." --Lewis Carroll
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

-- 
-- 
Ben

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

  reply	other threads:[~2009-09-24 21:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-24 17:42 Announcing s3c64xx XWindows fbdrv w/ XAA+XVideo+HWcursor David F. Carlson
2009-09-24 21:09 ` Ben Dooks [this message]
2009-09-25 12:47   ` David F. Carlson
2009-09-26 11:59     ` Ben Dooks
  -- strict thread matches above, loose matches on Subject: below --
2009-09-24 18:38 Maurus Cuelenaere

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=20090924210958.GI31920@trinity.fluff.org \
    --to=ben@trinity.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).