linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Volkov <avolkov@varma-el.com>
To: Wolfgang Denk <wd@denx.de>
Cc: linuxppc-dev@ozlabs.org, surendra.yadav@softdel.com
Subject: Re: [F]Framebuffer driver using SM501 hardware.
Date: Wed, 17 Aug 2005 14:11:13 +0400	[thread overview]
Message-ID: <43030D41.3000508@varma-el.com> (raw)
In-Reply-To: <20050816194825.A62AC353AB5@atlas.denx.de>

I (now :)) working on it too.

Unfortunately, due to terrible SM docos/examples,
I rewrite/write some parts from scratch :(
(mainly based on Applied Data Systems drivers for PXA).
Currently my driver(s) in prerelease stage. It provide:

- PCI/bus infra.
- CRT or LCD fb (dual head in progress,
  I hope, on next week it will be done).
- hwd cursor
- hwd accel (bitblit/fill rect/color expand)
- I2C/DDC (software, due to silicon bug in SM501)
- CI (Command List Interpreter) partially supported
  (problems in PCI mode: when it work as master with
   MPC5200, some data are lost, needed investigation).

Todo:
- 16 bpp colormap (needed reverse endian support in fbcon/fbmem)
- Alpha (have not ideas how to use it in fb/X)
- Video (same as above)
- Platform driver (it will not too hard to write it,
  but all boards, which I have, are PCI based)
- USB host (in progress)
- USB slave
- Full CI support.
- UART/SPI/AC97....

To whom it is interesting, I could send my current code
(not too little). And, if smb will wish fix/expand...,
I could (temporally) create cvs on sf.net.

Wolfgang Denk wrote:
> In message <43022F05.3050409@anagramm.de> you wrote:
> 
>>I was working with the SM501 framebuffer for a while on
>>linux-2.6.
> 
> 
> ...and we did in the context of our 2.4 kernel.
> 
> 
>>There is a color-mapping issue left (RGB is swapped on powerpc)
>>and it needs lots of code cleanup or a complete rewrite.
> 
> 
> I think we fixed some of these problems, and I have a couple of other
> patches sitting in my queue. Anybody interested can (1) have  a  look
> at our tree and (2) mail me.
> 
> Best regards,
> 
> Wolfgang Denk
----------------
> 
> In message <BPEMKMADCCCPHPEDDKOOMEHFCFAA.surendra.yadav@softdel.com> you wrote:
> 
>>> 
>>> I am writing framebuffer driver using SM501. This graphics driver chip can
> 
> 
> Why are you re-inventing the wheel?
Because I (for ex.) don't use nor QT, nor X :) and I use 2.6 kernel.
Also I need USB/AC97... support.

-- 
Regards
Andrey Volkov

  reply	other threads:[~2005-08-17 10:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16 13:34 Framebuffer driver using SM501 hardware Surendra Yadav
2005-08-16 16:38 ` Dan Malek
2005-08-16 18:23 ` Clemens Koller
2005-08-16 19:48   ` Wolfgang Denk
2005-08-17 10:11     ` Andrey Volkov [this message]
2005-08-17 11:04       ` [F]Framebuffer " Clemens Koller
2005-08-17 11:50         ` Matej Kupljen
2005-08-17 12:37           ` Andrey Volkov
2005-08-17 11:18       ` Geert Uytterhoeven
2005-08-17 12:15         ` Andrey Volkov
2005-08-17 12:42           ` Geert Uytterhoeven
2005-08-17 14:23             ` Andrey Volkov
2005-08-17 14:31             ` Clemens Koller
2005-08-17 14:52               ` Andrey Volkov
2005-08-16 19:42 ` Framebuffer " Wolfgang Denk

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=43030D41.3000508@varma-el.com \
    --to=avolkov@varma-el.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=surendra.yadav@softdel.com \
    --cc=wd@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;
as well as URLs for NNTP newsgroup(s).