tg3_init_rings() happens in tg3_init_hw(), so zap every other
occurance.

- Use ethtool_op_{get,set}_tso().
- Avoid partial byte enables on DMA writes, this upsets several
  non-x86 PCI controllers.

Also, include TSO support code when NETIF_F_TSO is available
but do not enable TSO by default even on capable cards.  User
can turn it on via ethtool.

- Do not set RDMAC_MODE_FIFO_LONG_BURST on 5788
- Do not set WDMAC_MODE_RX_ACCEL on 5788
- Note that 5788 cannot use tagged irq status.
- 5788 cannot do TSO
- 5788 cannot do NETIF_F_HIGHDMA.
- 5901 is 10/100 only.
- Update TSO firmware, add 5705 specific TSO firmware.
- Update TSO packet handling in ->hard_start_xmit() to
  match updated TSO firmware.
- TSO is still off by default until more perf analysis is done.

Bug discovered by Michael Chan @ Broadcom.

- call set-wire-speed phy function from tg3_phy_reset, not just _phy_probe
- disable set-wire-speed usage on certain chips, per bcm5700 driver

- do not zero stats/status block on 5705, they don't exist
  (in controller memory, at least)
- define TG3_MAX_MTU macro such that it takes a (tp) pointer arg,
  because the value varies between 5705 and non-5705
- use the macro to simply tg3_change_mtu

- (major) status block DMA address wasn't being set, for 5705. whoops. :)
- (minor) pass 5705-specific RX_STD_MAX_SIZE
- (minor) don't program RCVBDI_JUMBO_THRESH reg on 5705
- (very minor) re-order *THRESH, HOSTCC* regs per bcm570x driver order

of requiring users to select SCSI in order to see it.

into fys.uio.no:/home/linux/bitkeeper/nfsclient-2.5

From Christoph Hellwig

From David Mosberger:

> We definitely are seeing some strange crashes in get_ksymbol_core().
> I think the reason is the lack of iterator initialization.

Yes, looks good: reset the iterator at allocation.

Remove the PCMCIA release timer that got missed in earlier patch.  This
is required for successful compilation of the driver.

into fys.uio.no:/home/linux/bitkeeper/nfsclient-2.5

nfsroot_mount().

Problem analysis and fix provided by Andries Brouwer.
Cleanup of nfs_lookup() by me...

o inline assembler funcs cleanup
o machine depend header cleanup
o interrupt management fix

o build script update
o interrupt management fix
o mtd support fix
o signal handling fix

into home.osdl.org:/home/torvalds/v2.5/linux

into home.osdl.org:/home/torvalds/v2.5/linux

a valid SEP bit. The errata has it right: you have to have at
least model 3, stepping 3. Not "model >= 3 or stepping >= 3".

Fix the test accordingly.

into camp4.serpentine.com:/export/bos/bk/linux-early

into fys.uio.no:/home/linux/bitkeeper/nfsclient-2.5