From: David Jander <david.jander@protonic.nl>
To: Klaus Pedersen <kau@bang-olufsen.dk>
Cc: Linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: MPC5121e, MBX driver, pvr.ko ...
Date: Mon, 16 Feb 2009 08:27:33 +0100 [thread overview]
Message-ID: <200902160827.33338.david.jander@protonic.nl> (raw)
In-Reply-To: <OF4A842FE5.CCF31A69-ONC1257555.0030E2A2-C1257555.0031CBC3@bang-olufsen.dk>
On Friday 06 February 2009 10:03:55 Klaus Pedersen wrote:
> Hi David
>
> I'm also run on a custom board, and using the MBX.
>
> You need to get the device tree file right. You will see the MBX reserved
> the irq 66 in the boot printout.
> Instead of using insmod use modprobe. The are 2 versions of rc.pvr.
Thanks. I'll try that.
Two versions of rc.pvr? Why's that, and where is the other one?
> I a early thread about memcpy for G2/G3 cores, you mentioned that you will
> have a look at the init. of the dram controller and the prio-manager, did
> that give you anything??
Yes it did, and it's a long story, I havn't had persmission to talk about,
sorry. I believe I can now say that there should be a new errata from
Freescale explaining it all. As of now it's not on their web-site, but it
should have been there since last week at least *grrr*.
Btw, it has nothing to do with the prio-manager or the DRAM controller
whatsoever.
Best regards,
--
David Jander
Protonic Holland.
next prev parent reply other threads:[~2009-02-16 7:27 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 [this message]
2009-02-06 19:17 ` Wolfgang Denk
2009-02-16 8:40 ` David Jander
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=200902160827.33338.david.jander@protonic.nl \
--to=david.jander@protonic.nl \
--cc=Linuxppc-dev@ozlabs.org \
--cc=kau@bang-olufsen.dk \
/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).