Re: CE5.0: PCCard Socket Numbers

From: mobilevil (kccheng_at_kachun-youknowwhat.com)
Date: 02/17/05


Date: Thu, 17 Feb 2005 13:11:32 +0800

well this numbering thing is happening in maistone 2 bsp. it came with pb5
itself.

"bb" <bb@discussions.microsoft.com> wrote in message
news:794F7BD2-FB0B-49C0-A4D2-8C7853A19559@microsoft.com...
>I have ported our CE4.2 PCMCIA socket driver to the new 'bus agnostic'
>pccard
> model in CE5.0. Functionally, everything works fine under CE5, however I
> have a questions regarding the socket numbering.
>
> Under CE4.2, if an unknown card is plugged in, the UI window gives a
> prompt
> along the lines of 'unknown card in socket 1' or 'unknown card in socket
> 2'
> depending on which CF slot is being used. In CE5, the socket number seems
> to
> be treated as a reference rather than having any linkage to the physical
> slot. As a result, if I take an 'unknown card' and insert and remove it a
> few times (say 5 for example), the UI window says 'unknown card in socket
> 5'.
> This is a little confusing when there are only two CF slots on the device.
>
> I see that the number reference comes from the MDD portion of the driver
> where a global card reference is incremented each time a card is inserted
> (g_dwCardRef). I'm curious to know why this reference is used rather than
> the actual slot number?? The PDD passes the slot number into the MDD, so
> it
> is available.
>
> I could pull the public code into our platform and make some changes, but
> it'd be good to have a better understanding of this before doing anything
> rash...
>
> In a recent CE Chat, it was noted that there's not a lot of documentation
> regarding the socket implementation with the response that we should stay
> tuned to MSDN for a white paper or the like. Any progress on that?
>
> Thanks for your time,
> bb.
>



Relevant Pages

  • CE5.0: PCCard Socket Numbers
    ... I have ported our CE4.2 PCMCIA socket driver to the new 'bus agnostic' pccard ... Functionally, everything works fine under CE5, however I ... Under CE4.2, if an unknown card is plugged in, the UI window gives a prompt ... I see that the number reference comes from the MDD portion of the driver ...
    (microsoft.public.windowsce.platbuilder)
  • Re: "invalid handle", sockets, threads and garbage collector
    ... your IntPtr value happens to coincide with a reference. ... The exception contains "invalid handle" message. ... Socket constructor problem ... finalization means closing the handle to resource. ...
    (microsoft.public.dotnet.framework.clr)
  • Re: passing this object
    ... Sock which extends CSocketComm. ... Once the socket class processed the data, ... reference of CVirtualScreen - screen.setMessage function ...
    (microsoft.public.vc.language)
  • Re: passing this object
    ... Sock which extends CSocketComm. ... Once the socket class processed the data, ... reference of CVirtualScreen - screen.setMessage function ...
    (microsoft.public.vc.language)
  • Re: passing this object
    ... Sock which extends CSocketComm. ... Once the socket class processed the data, ... reference of CVirtualScreen - screen.setMessage function ...
    (microsoft.public.vc.language)