From: Bill Gatliff <bgat@billgatliff.com>
To: Paul Mundt <lethal@linux-sh.org>
Cc: Robert Whaley <rwhaley@applieddata.net>,
sm5xx-devel@lists.berlios.de,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [Sm5xx-devel] SM501 framebuffer driver
Date: Mon, 16 Oct 2006 14:28:27 -0500 [thread overview]
Message-ID: <4533DD5B.4020804@billgatliff.com> (raw)
In-Reply-To: <20061016030154.GA6301@linux-sh.org>
Paul:
Paul Mundt wrote:
>Hi Bill, fancy seeing you in this thread ;-)
>
>
Heh, you need to talk to the guy at the door. He'll let anyone in, I'm
proof! :)
>We want the 8051 blob in userspace if anything, there's little reason to
>tie this in to the module specifically, and it's handy to expose the
>interface for people that are specifically interested in loading in
>alternate code on the 8051.
>
>As far as including source for the 8051 code itself, that would be nice
>to have, but I doubt it's something the majority of users are going to
>care about. I've certainly never seen any.
>
>
I totally agree on all points. But I hate blobs. If the source code is
around, I'd love to have it recorded somewhere even though we all know
that Kbuild and most users won't know what to do with it. Just In Case.
Do we even know where this blob came from originally?
>On that note, do you have a pointer to some of the various ALSA
>implementations that are floating around? I've only seen the OSS driver
>we had in CVS, and that provides a rather dysmal starting point..
>
>
Whaley sent me one just last week (hi Robert!). Given that, I don't
suppose he'd mind my forwarding the patch on. What makes it tricky to
do so is that the patch is against his highly-evolved sm501 driver
stack, so there will be some mending required.
Yet another reason why we've all got to get all this stuff together.
The SM501 is a decent chip, and there's too few of us to go around
re-inventing the wheel.
b.g.
--
Bill Gatliff
bgat@billgatliff.com
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2006-10-16 19:27 UTC|newest]
Thread overview: 21+ 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
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 [this message]
2006-10-16 19:40 ` Robert Whaley
2006-10-16 19:48 ` Bill Gatliff
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=4533DD5B.4020804@billgatliff.com \
--to=bgat@billgatliff.com \
--cc=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).