linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Robert Whaley <rwhaley@applieddata.net>, sm5xx-devel@lists.berlios.de
Subject: Re: SM501 framebuffer driver
Date: Fri, 13 Oct 2006 21:11:38 +0900	[thread overview]
Message-ID: <20061013121138.GA21744@linux-sh.org> (raw)
In-Reply-To: <452691A2.2020209@anagramm.de>

On Fri, Oct 06, 2006 at 07:25:54PM +0200, Clemens Koller wrote:
> 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)
> 
There's at least half a dozen of these floating around, with some
disagreement on the actual implementation. We had one in the old SH tree
that specifically registered a different framebuffer device for each
plane, which we had some code in DirectFB and mplayer for making use of
for overlays and so on.

There's also another framebuffer driver for this in the Linux/MIPS tree
that's reasonably clean and might make a better starting point. The main
issue is supporting both PCI and platform device handling from the same
driver, since there seem to be just as many in both configurations
floating around.

> - kernel code for an functional complete(?) SM501 implementation for
> 	an RTS7751R2D Renesas SH-4 Board running Linux.
> 
It's largely complete, yes, but most of the code is fairly messy, or
against outdated APIs. It might make a good reference point, but little
else. The OHCI and i2c drivers are probably the "cleanest" out of these,
though I haven't gotten around to tidying them up and merging them in to
mainline as of yet. It might be beneficial to get these in to your sm5xx
tree though, before we end up having even more duplication (it seems
there already is with i2c..).

The OHCI thing was a bit of a mess since the DMA requests need to be in
the 8051 address space via the accessible SRAM there. You can see our
lame allocator for that in arch/sh/cchips/voyagergx/consistent.c.

> Oh, I will need to get the AC97 working, too :-/
> (my hardware is more or less ready to test some software)
> 
We also have an OSS driver for SM501, but it contains a lot of 8051
microcode that needs to be shoved in to userspace, and it needs to be
reworked for ALSA.

It should be fairly trivial to rework this for the mfd approach and work
from there, which I'll look at doing if no one beats me to it and I
finish some more pressing matters first.

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

  parent reply	other threads:[~2006-10-13 12:12 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ä
2006-10-13 12:11   ` Paul Mundt [this message]
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=20061013121138.GA21744@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=rwhaley@applieddata.net \
    --cc=sm5xx-devel@lists.berlios.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).