public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Andrey Volkov <avolkov@varma-el•com>
To: Trueskew <trueskew@gmail•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: Using bestcomm in an external module (MPC5200B to be exact)
Date: Mon, 19 Jun 2006 17:15:15 +0400	[thread overview]
Message-ID: <4496A363.8080802@varma-el.com> (raw)
In-Reply-To: <44965226.33b91fca.1abe.ffffd120@mx.gmail.com>

Trueskew wrote:
> I should've let you all know, I'm more of a 2.4 person than a 2.6 person.
> So I read what I could on 2.6 difference with 2.4, and it looked like my
> easiest choice was to modify the bestcomm code to export a couple tables and
> its API functions.  I found that kallsyms has almost all of the functions I
> needed to resolve (with 'T' next to them), but they were still not working.
> I added EXPORT_MODULE(TaskBDReset) and similar declarations in the bestcomm
> api code, but that still didn't do the trick for me.  So what is the trick?
> I think I'm on the right track, I can insmod a module that my driver needs,
> see kallsyms get updated, and access the functions directly in my driver.  I
> hope I'm close to doing something similar with the bestcomm functions, can
> anyone offer me some advice on what else I need to do?
> 
> Thanks.
Please, check Sylvain's patchset (http://www.246tNt.com/mpc52xx/)
_before_ you will do anithing. If be more shortly - Freescale's
BestcommAPI _deprecated_ and will _not_ included to 2.6.xxx.

--
Regards
Andrey Volkov


> 
> ________________________________
> 
> From: Trueskew [mailto:trueskew@gmail•com] 
> Sent: Friday, June 16, 2006 9:47 PM
> To: 'linuxppc-embedded@ozlabs•org'
> Subject: Using bestcomm in an external module (MPC5200B to be exact)
> 
> 
> 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
> 
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs•org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 

  reply	other threads:[~2006-06-19 13:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19  7:28 Using bestcomm in an external module (MPC5200B to be exact) Trueskew
2006-06-19 13:15 ` Andrey Volkov [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2006-06-17  4:47 Trueskew
2006-06-17 18:53 ` Frank Bennett
2006-06-18  1:26   ` SalQ

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=4496A363.8080802@varma-el.com \
    --to=avolkov@varma-el$(echo .)com \
    --cc=linuxppc-embedded@ozlabs$(echo .)org \
    --cc=trueskew@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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