From: Stefan Strobl <nst@gersys.de>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Lite5200B I2S driver
Date: Mon, 18 Dec 2006 14:47:50 +0100 [thread overview]
Message-ID: <45869C06.5020507@gersys.de> (raw)
In-Reply-To: <200612131356.50092.roman.fietze@telemotive.de>
Hello Roman
I'm interested in your code also though I haven't had a chance to look
at it yet. I am also having a MPC5200 based board running Wolfgang's
kernel 2.4.25.
Roman Fietze wrote:
> The driver uses some modified bestcomm code, because the original
> bestcomm code from Freescale is, ahem, not very well designed, one of
> the reasons for the new design in the 2.6. The changes were done in
> the code image 2. They are a more generic approach for the PSC tasks,
> so I can more easily switch PSC's. You should easily be able to modify
> the kernel part of the driver, to use the bestcomm code from
> Wolfgang's 2.4.25 git kernel tree. If not, please contact me and I
> will send you the sources of my bestcomm/ subdirectory, or anybody
> else of course.
What I am wondering is, how many DMA tasks do you run besides Audio?
I am already using DMA for IDE and FEC so Audio would be my third DMA
task. I remember that it used to be difficult to get more than two tasks
running at the same time.
Would you send me or post your bestcomm sources since I'm not that
proficient in kernel programming.
Thanks
Stefan
next prev parent reply other threads:[~2006-12-18 13:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 15:47 Lite5200B I2S driver Pedro Luis D. L.
2006-12-12 19:22 ` Sylvain Munaut
2006-12-13 9:31 ` Pedro Luis D. L.
2006-12-13 9:10 ` Roman Fietze
2006-12-13 9:39 ` Pedro Luis D. L.
2006-12-13 12:56 ` Roman Fietze
2006-12-18 13:47 ` Stefan Strobl [this message]
2006-12-18 14:46 ` Roman Fietze
2006-12-18 15:10 ` Stefan Strobl
2006-12-13 12:58 ` Roman Fietze
2006-12-13 13:15 ` Roman Fietze
2006-12-13 14:37 ` Pedro Luis D. L.
2006-12-17 8:03 ` Grant Likely
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=45869C06.5020507@gersys.de \
--to=nst@gersys.de \
--cc=linuxppc-embedded@ozlabs.org \
/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).