Re: WLAN CF card (NDIS) driver - CF bus enumeration

From: Shehan (shehan_at_rediffmail.com)
Date: 03/24/04 

Date: 24 Mar 2004 01:58:14 -0800

Hi Seung Yi,

Thank you for the prompt response.

Instead of the NE 2000 sample, I am using the Cisco 802.11 PC Card
driver sample provided with PB 4.0. I assume PC card driver and PCMCIA
driver follow the same architecture. So, being a WLAN PC card driver,
the Cisco 802.11 driver is more similar to the CF WLAN driver I have
to implement. Isn't it?

Moreover, it implements some 802_11 OIDs also in its QueryInformation
function.

Thank you again

Shehan

Seung Yi <seungyi@codetelligence NOSPAMMERS .com> wrote in message news:<opr5bxzmr6swt9p6@localhost>...
> Yes CF and PCMCIA are the same with regard to Plug and Play on Windows
>
> CE. They use the same bus type.
>
> The NDIS/PCMCIA implementation is a little strange, but you should start
>
>
> with the NE2000 sample driver which has the necessary registry keys and
>
> card services calls you will need. The way it works today is that NDIS
> is
>
> fairly intimate with PC Card services, your PNP registry keys will
>
> actually point card services to load NDIS.DLL. NDIS will then find your
>
> miniport and through some NDIS configuration calls, you can get a card
>
> services handle to your card. From there you allocate resources,
>
> interrupts etc.. and off you go. Since you are a WLAN card, there are
>
> some specific OIDs you need to implement for zero-config.
>
>
>
> On 23 Mar 2004 04:11:45 -0800, Shehan <shehan@rediffmail.com> wrote:
>
> > Hi
> >
> > I am new to WinCE driver development and now in the process of writing
>
> > a PocketPC 2003 device driver for a CF Type-1 WLAN card.
> >
> > As per WinCE PB documentation, the WINCE network driver development
> > must follow the NDIS specifications, which is similar to that of
> > Windows 2000.....Well and good.
> >
> > But how to handle the CF card enumeration and that kind of stuff. The
> > NDIS INTERFACE TYPE network adapter bus enum in WinCE has support for
> > only ISA, PCI and PCMCIA buses. I have read somewhere that CF and
> > PCMCIA are the same except for the mechanical interface spec. Does
> > that mean CF WLAN driver and PCMCIA WLAN driver follow the same type
> > of architecture?
> >
> > Thanks in advance.
> >
> > Shehan

Relevant Pages

  • Re: Linux Wifi laptop guidance requested.
    ... do you lnow if it is running a 'native' driver or the NDIS ... > wrapper. ... Xterasys card in the machine. ...
    (alt.internet.wireless)
  • Re: D-Link Wireless card
    ... Since the card is not supported, I fetched and built the ... > driver with ndis which built and installed ok. ... I've scoured the ndis manpages and everything seems ...
    (freebsd-questions)
  • ndis troubles - whats my next debugging step?
    ... I followed the instructions, and everything loads fine, but the card ... I ran ndis and generated the driver as specified, ... Another site suggested pciconf -la to determine what cards are found, ...
    (freebsd-net)
  • RE: [UPDATED PATCH] EFI support for ia32 kernels
    ... >> reuse a single driver image for multiple architectures assuming there ... As one of the people responsible for the EFI Specification and our ... Perhaps the UNDI network card interface that Intel developed ... BIOS can't shadow that much ROM code. ...
    (Linux-Kernel)
  • Re: Question about FILE_OBJECT
    ... NDIS IM is a driver that fully conforms to the model, ... I.E. every time they allocated a new context object they ...
    (microsoft.public.win32.programmer.kernel)