linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <syrjala@sci.fi>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Robert Whaley <rwhaley@applieddata.net>
Subject: Re: SM501 framebuffer driver
Date: Fri, 6 Oct 2006 21:55:35 +0300	[thread overview]
Message-ID: <20061006185535.GA7649@sci.fi> (raw)
In-Reply-To: <452691A2.2020209@anagramm.de>

On Fri, Oct 06, 2006 at 07:25:54PM +0200, Clemens Koller wrote:
> Hello, Bill,
> 
> > Sorry about starting a new thread, but I was referred to this 
> > list/thread by a colleague just a few minutes ago.  (OT: it isn't in the 
> > archives in SF, either!).
> 
> Okay, fine! I'll be glad to join the party because we are using the SM501
> on PCI of an MPC8540 embedded PowerPC.

I'm using an ARM board. The CPU is an Atmel AT91RM9200, and the SM501 is 
connected to it via a CPLD.

> > I hate to play "me too!", but I also have an SM501 framebuffer driver in 
> > a partial state of development.  I'd love to collaborate with others to 
> > get a good version pushed upstream.
> 
> Great! Where shall we collect the code?
> I have some 
> 
> - a working fb driver kernel module
> 	(I did lots of code cleanup, but still needs a lot)

Me too here :) My changes to the original sm501 fb driver include:
 - Use dev_dbg instead of custom macro
 - video= command line parsing
 - Better checking in check_var
 - Started to implement setcolreg and panning, not finished
 - Removed duplicated code
 - Tried to make code more readable :)
 - Maybe something else (I didn't keep track

I also started to write an ALSA driver for the audio part. I wrote the 
basic driver skeleton, and my next step was going to be the 8051, but 
then I got distracted by other stuff. My plan was to start off with some 
very simple code for the 8051 which would just issue an interrupt at 
some interval so I could just see how the CPU<->8051 communication 
works. I'll try dig up the code in case someone wants to take a look.

Like I mentioned in the other thread I also wrote a DirectFB gfxdriver. 
It does basic blitting and filling for now. I tried to make it draw 
lines too but that caused the chip to lock up, and I tried to use alpha 
bleded blits but those seem to make the chip really sluggish to respond.

-- 
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  parent reply	other threads:[~2006-10-06 18:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06 16:11 SM501 framebuffer driver Bill Gatliff
2006-10-06 16:26 ` Ben Dooks
2006-10-06 19:19   ` Bill Gatliff
2006-10-10  6:01   ` Andrey Volkov
2006-10-10 12:06     ` Bill Gatliff
2006-10-11 15:17       ` Clemens Koller
2006-10-06 17:25 ` Clemens Koller
2006-10-06 18:04   ` Bill Gatliff
     [not found]     ` <4526A37F.6040002@anagramm.de>
2006-10-06 19:03       ` Bill Gatliff
2006-10-06 18:14   ` Alex Deucher
2006-10-06 18:55   ` Ville Syrjälä [this message]
2006-10-13 12:11   ` Paul Mundt
2006-10-13 13:12     ` [Sm5xx-devel] " Andrey Volkov
2006-10-13 13:35       ` Paul Mundt
2006-10-13 13:12     ` Clemens Koller
2006-10-13 13:18       ` Andrey Volkov
2006-10-15 17:34     ` Bill Gatliff
2006-10-16  3:01       ` [Sm5xx-devel] " Paul Mundt
2006-10-16 19:28         ` Bill Gatliff
2006-10-16 19:40           ` Robert Whaley
2006-10-16 19:48             ` Bill Gatliff
  -- strict thread matches above, loose matches on Subject: below --
2007-01-15  1:31 Ben Dooks
2007-01-22  7:55 ` Manuel Lauss
2007-01-23 10:17   ` Ben Dooks
2007-01-23 15:13     ` Manuel Lauss

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=20061006185535.GA7649@sci.fi \
    --to=syrjala@sci.fi \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=rwhaley@applieddata.net \
    /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).