linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Trueskew" <trueskew@gmail.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: Using bestcomm in an external module (MPC5200B to be exact)
Date: Fri, 16 Jun 2006 21:47:09 -0700	[thread overview]
Message-ID: <4493894e.6d57ffd8.019a.ffff95b9@mx.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]

I'm writing a driver for a TI codec attached to the MPC5200B PSC3 codec
lines on a Lite5200b.  It's an external module, and I'd like to use Bestcomm
with it.  I've already tried a bunch of horrible things to get it to work.
I could say it's close, but by close I mean the FEC still runs, my stuff
doesn't.  
 
1. Can the Bestcomm I/F be used by an external module, or is the module
required to be built in if built-in drivers use Bestcomm?  TasksInitAPI (no
so bad) and TasksLoadImage (yeah, bad) aren't really supposed to be called
more than once from what I've read, and the kernel loads them for ethernet
and ATA (no disk in my system if that matters).  
 
2. If it can be used by an external module, how would I do it?  I've tried
compiling the source into my module and replicating the initialization the
kernel does in addition to my own stuff.  It's not too bad, though I don't
get any interrupts yet.
 
The LTIB from Freescale includes AIC23 and AC97 drivers that use Bestcomm.
I built my kernel with them set as modules, and they had the same unresolved
problems that my driver has on insmod, so I'm pessimistic.  If someone could
put me out of my misery one way or another, I'd appreciate it.
 
Thanks.
Sal
 

[-- Attachment #2: Type: text/html, Size: 2767 bytes --]

             reply	other threads:[~2006-06-17  4:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-17  4:47 Trueskew [this message]
2006-06-17 18:53 ` Using bestcomm in an external module (MPC5200B to be exact) Frank Bennett
2006-06-18  1:26   ` SalQ
  -- strict thread matches above, loose matches on Subject: below --
2006-06-19  7:28 Trueskew
2006-06-19 13:15 ` Andrey Volkov
2006-06-19 14:50   ` Trueskew
2006-06-19 21:32     ` John Rigby
2006-06-20  0:48       ` Trueskew
2006-06-20 19:15         ` Sylvain Munaut
2006-06-28  4:08           ` John Rigby
2006-06-20 19:03     ` Sylvain Munaut
2006-06-30 23:33       ` Benjamin Herrenschmidt
2006-07-17 22:13         ` Sylvain Munaut
2006-07-27 17:30           ` John Rigby
2006-07-27 19:15             ` Sylvain Munaut

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=4493894e.6d57ffd8.019a.ffff95b9@mx.gmail.com \
    --to=trueskew@gmail.com \
    --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).