From: David Jander <david.jander@protonic.nl>
To: Wolfgang Denk <wd@denx.de>
Cc: Linuxppc-dev <Linuxppc-dev@ozlabs.org>,
John Rigby <jrigby@freescale.com>
Subject: Re: MPC5121e, MBX driver, pvr.ko ...
Date: Mon, 16 Feb 2009 09:40:46 +0100 [thread overview]
Message-ID: <200902160940.46783.david.jander@protonic.nl> (raw)
In-Reply-To: <20090206191710.C16B78322908@gemini.denx.de>
On Friday 06 February 2009 20:17:10 Wolfgang Denk wrote:
> Dear David,
>
> In message <200902060824.06851.david.jander@protonic.nl> you wrote:
> > I decided to try out Application Note AN3793 from Freescale (3D Graphics
> > on the ADS512101 Board Using OpenGL ES).
> >
> > I started trying to load the provided (binary!) kernel modules into our
> > kernel, but I am geeting errors inserting the modules using
>
> The binary kernel modules are a mess. Not only they are a pretty
> clear GPL license violation (and I wonder what Freescale is going to
> do to sort this out), but it effectively always locks you down to the
Sorry if this starts to get a little off-topic to this list...
IANAL, so I won't argue about a binary-driver being by definition a
GPL-violation or not, or if those "gray areas" that Linus mentioned in the
past, apply in this case.
Besides that, do you have another reason why this is a clear GPL-violation?
> specific LTIB kernel version (and probably even to a specific DTS)
> they were built against. Open source? Forget it.
I never expected this driver to be Open-Source. I always supposed that we'd
never be able to use the MBX because of this, and use the AXE instead (One of
our applications needs some form of hardware accelerated image-scaling). But
since I saw that application note, I couldn't resist trying it out, just to
see how hard it is to actually use it. The point is made: Leaving aside the
possible legal implications of the driver's existance, it still is an
undoable job to get this working in a maintainable fashion.
What could Freescale possibly do about this?... beats me. I don't know about
the legal implications (again, IANAL), but what if there was a driver like
NVidia's video drivers (i.e. binary object with a re-compileable shell around
it to adapt it to other kernels)? Otherwise, I guess Freescale can just as
well stop making the MPC5121e and just make MPC5123's instead (which
continues to be an awesome chip nevertheless) :-)
Best regards,
--
David Jander
Protonic Holland.
prev parent reply other threads:[~2009-02-16 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 7:24 MPC5121e, MBX driver, pvr.ko David Jander
2009-02-06 9:03 ` Klaus Pedersen
2009-02-16 7:27 ` David Jander
2009-02-06 19:17 ` Wolfgang Denk
2009-02-16 8:40 ` David Jander [this message]
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=200902160940.46783.david.jander@protonic.nl \
--to=david.jander@protonic.nl \
--cc=Linuxppc-dev@ozlabs.org \
--cc=jrigby@freescale.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).