This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: PowerPC FEC interrupt handler problem
- From: Wolfgang Heppner <hep at iis dot fhg dot de>
- To: eCos-discuss <ecos-discuss at sources dot redhat dot com>
- Date: Thu, 11 Jul 2002 10:16:14 +0200
- Subject: Re: [ECOS] PowerPC FEC interrupt handler problem
- Organization: FhG-IIS-A
Hi,
sorry, but i did not dive far enough into the interrupt handling,
because the API functions worked for me (even when i wrote my own
drivers!).
I have only one hint: The FEC driver only installs an interrupt handler,
if _FEC_USE_INTS is defined, so check this first.
Regards
Wolfgang
Khasim wrote:
>
> Hi .
> Thanks for your kind responce. I have one more doudbt
>
> See When an interrupt comes the control should go to 0x500 location and then
> it has to branch to the appropriate handler based on the interrupt.
>
> I dont find any such code which is doing this . Please tell me how interrupt
> handler registration is done here.
> I saw the function cyg_drv_interrupt_create
>
> Which is creating an interrupt object but how this will be used when an
> interrupt occurs.
>
> What all parts of the code I need to change If I have to incorparate the
> changes required for my board compared to viper board.
>
> Thanks in anticipation
>
> Khasim
--
Wolfgang Heppner
High Speed Kamerasysteme - Abt. Bildsensorik (ESY-B)
High Speed Camera Systems - Dept. Electronic Imaging (ESY-B)
Fraunhofer
Institut Integrierte Schaltungen
Angewandte Elektronik
Am Wolfsmantel 33
91058 Erlangen
(Germany)
Tel: +49 (0) 9131 776 528
Fax: +49 (0) 9131 776 598
email: hep@iis.fhg.de
web: http://www.iis.fhg.de
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss