From: Ben Dooks <ben-linux@fluff.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Robert Whaley <rwhaley@applieddata.net>
Subject: Re: SM501 framebuffer driver
Date: Fri, 6 Oct 2006 17:26:44 +0100 [thread overview]
Message-ID: <20061006162644.GA15499@home.fluff.org> (raw)
In-Reply-To: <45268042.8050207@billgatliff.com>
On Fri, Oct 06, 2006 at 11:11:46AM -0500, Bill Gatliff wrote:
> Guys:
>
>
> 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!).
>
> 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.
>
> One of the challenges I've encountered with this chip is dealing with
> all the "other stuff" it has onboard. In my driver, I addressed that by
> creating a whole new bus similar to what Nico did for the UCB1400. I
> was in the process of getting AC97 working when I figured out that that
> part of the chip is so braindead, it isn't worth using--- at least on
> ARM platforms that don't have DMA (which was my case).
>
> In an upcoming project I need to use the USBH, so I'll be revisiting
> this issue again soon. I have also cc'd others who have worked with me
> on this chip.
>
> I'd be happy to post code if that makes sense. Or to host a CVS repo or
> something.
We have a solution based on an central device in drivers/mfd
which creates a set of sub-devices that are used by the invidicual
drivers
--
Ben (ben@fluff.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2006-10-06 16:27 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 [this message]
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
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=20061006162644.GA15499@home.fluff.org \
--to=ben-linux@fluff.org \
--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).