OEMInterruptEnable() is not getting called

Tutorials Win: Microsoft Windows Forum

Hi,

currently i am doing wince.net 4.1 porting to 4.2 for xscale . my OS loads
into memory and calls OEMinit And InitClock() but my OEMInterruptEnable()
is not getting called with SYSINTR_SMSC. My code was working for 4.1. do i
need to do any changes to make it work for 4.2. please Help

thanks
shyam
Top

Re: OEMInterruptEnable() is not getting called by ZHAO

ZHAO
Mon Feb 09 03:09:25 CST 2004

shyam wrote:
> Hi,
>
> currently i am doing wince.net 4.1 porting to 4.2 for xscale . my OS loads
> into memory and calls OEMinit And InitClock() but my OEMInterruptEnable()
> is not getting called with SYSINTR_SMSC. My code was working for 4.1. do i
> need to do any changes to make it work for 4.2. please Help
>
> thanks
> shyam
>
>

OEMInterruptDone() will be called to enable interrupt.
OEMInterruptEnable() only be called when a device driver calls the
InterruptInitialize() kernel routine.
Top

Re: OEMInterruptEnable() is not getting called by Leif

Leif
Mon Feb 09 08:46:02 CST 2004

On Mon, 9 Feb 2004 02:39:03 -0600, shyam <er_s> wrote:

> Hi,
>
> currently i am doing wince.net 4.1 porting to 4.2 for xscale . my OS
> loads
> into memory and calls OEMinit And InitClock() but my
> OEMInterruptEnable()
> is not getting called with SYSINTR_SMSC. My code was working for 4.1. do
> i
> need to do any changes to make it work for 4.2. please Help
>
> thanks
> shyam
>
>

It could be that you've ran into the same problems I had when switching my
LAN91C111 driver from 4.1 to 4.2. Search this newsgroup (e.g. using
Google) for "NDIS interrupt handling in 4.1 and 4.2" to find a previous
thread of mine. I hope this will give you a few ideas.

Regards,
Leif O.



--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
Top

Re: OEMInterruptEnable() is not getting called by shyam

shyam
Tue Feb 10 00:48:49 CST 2004

Thanks for your lead Leif, i tried putting some debug msgs in DllEntry and
DriverEntry of NDIS driver but none of them is getting called.Do i need to
make any changes to OAL when doing the migration from 4.1 to 4.2.

Thanks for help in advance.

shyam

"Leif O" <leif_nospam@vmetro.no> wrote in message
news:opr23xy0zik3ldon@msnews.microsoft.com...
> On Mon, 9 Feb 2004 02:39:03 -0600, shyam <er_s> wrote:
>
> > Hi,
> >
> > currently i am doing wince.net 4.1 porting to 4.2 for xscale . my OS
> > loads
> > into memory and calls OEMinit And InitClock() but my
> > OEMInterruptEnable()
> > is not getting called with SYSINTR_SMSC. My code was working for 4.1. do
> > i
> > need to do any changes to make it work for 4.2. please Help
> >
> > thanks
> > shyam
> >
> >
>
> It could be that you've ran into the same problems I had when switching my
> LAN91C111 driver from 4.1 to 4.2. Search this newsgroup (e.g. using
> Google) for "NDIS interrupt handling in 4.1 and 4.2" to find a previous
> thread of mine. I hope this will give you a few ideas.
>
> Regards,
> Leif O.
>
>
>
> --
> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/


Top

Re: OEMInterruptEnable() is not getting called by Leif

Leif
Tue Feb 10 09:48:40 CST 2004

As my previous thread indicates, I had to make some small changes to the
OAL interrupt routines, but that shouldn't affect the calling sequence for
DllEntry and DriverEntry.

Regards,
Leif O.

On Tue, 10 Feb 2004 00:48:49 -0600, shyam <er_s> wrote:

> Thanks for your lead Leif, i tried putting some debug msgs in DllEntry
> and
> DriverEntry of NDIS driver but none of them is getting called.Do i need
> to
> make any changes to OAL when doing the migration from 4.1 to 4.2.
>
> Thanks for help in advance.
>
> shyam
>
> "Leif O" <leif_nospam@vmetro.no> wrote in message
> news:opr23xy0zik3ldon@msnews.microsoft.com...
>> On Mon, 9 Feb 2004 02:39:03 -0600, shyam <er_s> wrote:
>>
>> > Hi,
>> >
>> > currently i am doing wince.net 4.1 porting to 4.2 for xscale . my OS
>> > loads
>> > into memory and calls OEMinit And InitClock() but my
>> > OEMInterruptEnable()
>> > is not getting called with SYSINTR_SMSC. My code was working for 4.1.
>> do
>> > i
>> > need to do any changes to make it work for 4.2. please Help
>> >
>> > thanks
>> > shyam
>> >
>> >
>>
>> It could be that you've ran into the same problems I had when switching
>> my
>> LAN91C111 driver from 4.1 to 4.2. Search this newsgroup (e.g. using
>> Google) for "NDIS interrupt handling in 4.1 and 4.2" to find a previous
>> thread of mine. I hope this will give you a few ideas.
>>
>> Regards,
>> Leif O.
>>
>>
>>
>> --
>> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
>
>



--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
Top