From: David Jander <david.jander@protonic.nl>
To: linuxppc-dev@lists.ozlabs.org
Cc: "Kári Davíðsson" <kari.davidsson@marel.com>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
"Paul Gibson" <paul.gibson2074@gmail.com>,
"Wolfgang Denk" <wd@denx.de>
Subject: Re: MPC5121 CAN and USB
Date: Mon, 19 Oct 2009 08:46:51 +0200 [thread overview]
Message-ID: <200910190846.51906.david.jander@protonic.nl> (raw)
In-Reply-To: <20091015231005.D2CE9F15432@gemini.denx.de>
On Friday 16 October 2009 01:10:05 am Wolfgang Denk wrote:
> Dear Paul,
>
> In message <26b052040910151603y8fc9b00g678d6a873083f1e7@mail.gmail.com> you
wrote:
> > > The "ltib-mpc5121ads-20090602" branch reflects the exact state of the
> > > kernel contained in the LTIB with this name (dated July 2009, despite
> > > the name; based at 2.6.24.6, i. e. 7+ kernel versions behind).
> >
> > I have diff'ed this and it is very similar to the ltib in the BSP.
> > The MBX patches may be missing though. These patches can be obtained
> > via the Freescale SDK for the OpenGL on the MPC5121e webpage.
>
> Who cares. This code is about 8 (!) kernel releases behind. Scrap
> it.
I would love to, but as it stands, this is still the best we can get for the
MPC5121e :-(
I took that branch, merged the MBX patch in from the LTIB and ported the new
NFC driver from the 'mpc512x' branch back to this one, since the original
driver is buggy.
The latest OpenGL-ES libraries and MBX drivers released are closed-source,
buggy, but stable and seem to work well if your program doesn't do the kinds
of things that make it crash.
If you know the limitations of this and can live with it, it might be
bearable... I don't have any other option :-(
Best regards,
--
David Jander
Protonic Holland.
next prev parent reply other threads:[~2009-10-19 7:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 10:54 UBIFS problem on MPC8536DS Felix Radensky
2009-10-14 12:36 ` Adrian Hunter
2009-10-14 13:02 ` Felix Radensky
2009-10-14 13:21 ` Felix Radensky
2009-10-14 16:44 ` Adrian Hunter
2009-10-14 17:48 ` Felix Radensky
2009-10-14 18:13 ` Scott Wood
2009-10-14 20:12 ` Felix Radensky
2009-10-15 20:07 ` Scott Wood
2009-10-16 5:01 ` Felix Radensky
2009-10-16 15:31 ` Scott Wood
2009-10-18 9:38 ` Felix Radensky
2009-10-19 15:40 ` Scott Wood
2009-10-19 19:39 ` Felix Radensky
2009-10-19 19:47 ` Scott Wood
2009-10-19 20:19 ` Felix Radensky
2009-10-20 15:30 ` Felix Radensky
2009-10-22 8:20 ` Felix Radensky
2009-10-22 16:07 ` Scott Wood
2009-10-15 9:54 ` Norbert van Bolhuis
2009-10-15 10:45 ` MPC5121 CAN and USB Kári Davíðsson
2009-10-15 11:20 ` Paul Gibson
2009-10-15 11:36 ` Kári Davíðsson
2009-10-15 18:30 ` Wolfgang Denk
2009-10-15 23:03 ` Paul Gibson
2009-10-15 23:10 ` Wolfgang Denk
2009-10-19 6:46 ` David Jander [this message]
2009-10-16 13:53 ` Kári Davíðsson
2009-10-15 12:49 ` UBIFS problem on MPC8536DS Felix Radensky
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=200910190846.51906.david.jander@protonic.nl \
--to=david.jander@protonic.nl \
--cc=kari.davidsson@marel.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paul.gibson2074@gmail.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).