$Id: ipaq-linux-cards.txt,v 1.9 2002/09/29 03:59:37 aoki Exp $

these are just some notes on using various network cards under
Familiar 0.5.2 and 0.5.3 (iPAQ Linux).  this is a supplement to the
contents of:
	http://www.handhelds.org/z/wiki/IpaqHardwareCompatibility
and are not particularly meant to be comprehensible to someone who
doesn't know at least a little about setting up Linux networking.

- Netgear FA411NA (FA411)

  put the following in a .conf file in /etc/pcmcia (e.g., 
  "/etc/pcmcia/fa411.conf"):

  -------------------- cut here --------------------
  device "axnet_cs"
    class "network" module "axnet_cs"

  card "NetGear FA411NA Fast Ethernet"
    version "NETGEAR", "FA411"
    manfid 0x0149, 0x0411
    bind "axnet_cs"
  -------------------- cut here --------------------

  the FA411 can operate as an NE2000-compatible card, so if you point
  it to pcnet_cs instead it will operate more or less correctly.  in
  fact, however, the FA411 uses the Asix Ax88790 chipset, which is not
  100% NE2000-compatible.  after a while, the FA411 will spew the
  dreaded "eth0: interrupt(s) dropped!" message to console and start
  using polled I/O.  if you have the axnet_cs driver, it is better to
  go ahead and use it - it does 100bT autonegotiation and all that
  good stuff as well.

  the axnet_cs driver is currently in pcmcia-modules-<kernel>.ipk.

- SMC 2642W (SMC2642W)
- D-Link DCF-650W

  these are both based on the Intersil Prism2 chipset.  for some
  reason someone broke the out-of-the-box support for the Prism2 cards
  in Familiar 0.5.2 because they put in a /etc/pcmcia/wlan-ng.conf
  that wants the prism2_cs driver, but nobody provides prism2_cs.o, at
  least not in a prepackaged form.  (this has been corrected in later
  unstable feeds and in Familiar 0.6.)

  first, i do the following to disable the wlan stuff:

	cd /etc/pcmcia
	mkdir WLAN.NO
	mv wlan* WLAN.NO

  second, i enable a Prism2 driver that is actually available in 
  binary form.

  i have seen claims that the wvlan_cs or orinoco_cs drivers work ok
  with the Prism2 cards, but this has not been my experience.

  in 0.5.2, they do provide the prism2.o driver.  this is actually an
  old version of the hostap_cs driver.  i put the following in a file
  in /etc/pcmcia (e.g., "/etc/pcmcia/prism2.conf"):

  -------------------- cut here --------------------
  device "prism2"
    class "network" module "prism2"
  
  card "DCF-650W 11Mbps Wireless CF Card"
    version "D-Link", "DCF-650W", ""
    manfid 0xd601, 0x0002
    bind "prism2"
  
  card "SMC2642W 11Mbps Wireless CF Card"
    manfid 0xd601, 0x0005
    bind "prism2"
  -------------------- cut here --------------------

  in 0.5.3, they started providing the hostap_cs driver (look for
  prism2_modules-<kernel>.ipk in the usual ipkg feed).

  you can download an appropriate /etc/pcmcia config file from the
  HostAP CVS repository:
  http://hostap.epitest.fi/cgi-bin/viewcvs.cgi/hostap/driver/etc/hostap_cs.conf
  this file can just be dropped as-is into /etc/pcmcia (this link
  actually shows you the version history, not the latest version -
  click on "View").

  since these cards are 3.3V CF cards, you will need to tell the
  hostap_cs driver that it's ok to ignore the fact that the sleeve
  driver always claims that the cards are 5V.  if you don't, you'll
  get a kernel panic every time you load the hostap_cs driver.  in
  0.5.2, do something like this:
	echo 'options prism2 ignore_cis_vcc=1' >> /etc/modules.conf
  and in 0.5.3, do this instead:
	echo 'options hostap_cs ignore_cis_vcc=1' >> /etc/modules.conf
  it doesn't matter whether you're using a PCCard or CF sleeve - the
  5V "feature" is in the sleeve driver, not the sleeve hardware.

  finally, you need to edit /etc/pcmcia/wireless.opts so that it
  provides the right parameters (network name, encryption key, etc.)
  in response to the card's MAC ("Ethernet" network address).  i can't
  help you too much with this because i don't know how you have your
  network set up.

  usually, you can read the MAC off of a label on the card itself.
  you can always capture the MAC from what the driver prints when you
  boot (the card needs to be recognized by the driver, but the network
  code need not be configured correctly).  finally, here are the MAC 
  ranges i know about:

	Lucent "WaveLAN 11Mb"	*,*,*,00:60:1D:*
	Lucent "Orinoco"	*,*,*,00:02:2D:*
	SMC			*,*,*,00:60:B3:*
	D-Link			*,*,*,00:05:5D:*