Re: PC Card gurus..please help..

Tech-Archive recommends: Speed Up your PC by fixing your registry

:) .. okey .. should have asked clearly...

I wanted reference for the PDD layer implementation when only one IRQ
is available....as to whether they have implemented other mechanism
than IISR....

thanks anyways..

regards,
joseph.



On Oct 18, 5:39 am, "Bruce Eitman [eMVP]"
<beitman.nos...@xxxxxxxxxxxxxxxxxxxxxx> wrote:
if( IRQ == MY_PCCARD_IRQ )
{
if( *Status == MY_FIRST_INTERRUPT_SOURCE )
return SYSINTR_FIRST;
else if( *Status == MY_SECOND_INTERRUPT_SOURCE )
return SYSINTR_SECOND;

}

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

<joseph.garibal...@xxxxxxxxx> wrote in message

news:1192686658.960801.164780@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



hey guys.,

thanks for your response...

named events are ruled out....because PCMCIA.dll is the one
creating the event and i have no control over the parameters to
that...The flow is actually like card interrupt occurs->Socket
Service's IST runs->This IST triggers an event->PCMCIA.dll's IST runs
and calls Client drivers callback->client callback runs and sents an
internal event. I am stuck up in the part where Socket Service's IST
communicates to PCMCIA.dll's IST.....

I am edging towards an Installable ISR......

do you guys know of any reference code which is for a hw having
only one IRQ for the PC Card (as opposed to one for the Card Status
Change interrupt and one function interrupt for the function
driver)....Some code which uses SOCK_CAP_ONLY_SYSINTR...I couldn't
locate any

regards,
joseph

On Oct 17, 9:55 am, "Bruce Eitman [eMVP]"
<beitman.nos...@xxxxxxxxxxxxxxxxxxxxxx> wrote:
This sounds like you should do it in the ISR. It is not uncommon to have
one CPU interrupt that is handled in the ISR by reading a status register
and returning the appropriate SYSINTR.

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

<joseph.garibal...@xxxxxxxxx> wrote in message

news:1192607749.193395.104350@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Hi,

My PC card hardware has only one interrupt (for CF IO interrupt as
well as RDY signal change from CF)....I am using the PC card stack
(with ATADISK) that is provided with WinCE 5.0.

For the client drivers to use interrupt, I thought I can use
SOCK_CAP_ONLY_SYSINTR capability of the socket. This way, ATADISK can
use the SYSINTR returned from my Socket Services directly and (the
event corresponding to) this SYSINTR can be triggered from my Socket
Service IST (i can differentiate whether it is an IO interrupt or RDY
signal by probing the CF card registers).

In order to do so from the Socket service's IST, i have to set the
event corresponding to the SYSINTR which has been passed on to the
client driver. Problem is that only the SYSINTR number is known, not
the event of the client driver. So, functionality in tunes of
SetInterruptEvent() is required. But from what I read, this cannot be
used in other than power APIs context. I cannot try to export the
event as done in this thread:

http://groups.google.com/group/microsoft.public.windowsce.platbuilder...

Is there any way I can accomplish this? Or is there any other
method to do the same?

regards,
joseph.- Hide quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -


.

Relevant Pages

  • Re: PC Card gurus..please help..
    ... I am stuck up in the part where Socket Service's IST ... only one IRQ for the PC Card (as opposed to one for the Card Status ... Change interrupt and one function interrupt for the function ... and returning the appropriate SYSINTR. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Installable Interrupt on PCI
    ... How can the second card claim the interrupt? ... After deleting the hive registry everything works fine. ... Have you accidentally set the same SysIntr value for both interrupts? ...
    (microsoft.public.windowsce.platbuilder)
  • PC Card gurus..please help..
    ... My PC card hardware has only one interrupt (for CF IO interrupt as ... SOCK_CAP_ONLY_SYSINTR capability of the socket. ... event corresponding to) this SYSINTR can be triggered from my Socket ...
    (microsoft.public.windowsce.platbuilder)
  • Re: PC Card gurus..please help..
    ... This sounds like you should do it in the ISR. ... and returning the appropriate SYSINTR. ... My PC card hardware has only one interrupt (for CF IO interrupt as ... SOCK_CAP_ONLY_SYSINTR capability of the socket. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: IDE to CF Card Issue
    ... Good CF Card information: ... ATA Card ... CQueuedPipe::CheckForDoneTransfers - failure on TD 0x2e5960, ... Interrupt still delayed; status ...
    (microsoft.public.windowsce.embedded)