- 23 Aug, 2003 8 commits
-
-
David S. Miller authored
-
David S. Miller authored
-
David S. Miller authored
-
David S. Miller authored
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.
-
David S. Miller authored
-
David S. Miller authored
-
David S. Miller authored
- 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.
-
David S. Miller authored
-
- 22 Aug, 2003 15 commits
-
-
David S. Miller authored
-
David S. Miller authored
Bug discovered by Michael Chan @ Broadcom.
-
David S. Miller authored
-
Jeff Garzik authored
-
Jeff Garzik authored
-
Jeff Garzik authored
-
Jeff Garzik authored
- 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
-
Jeff Garzik authored
- 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
-
Jeff Garzik authored
- (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
-
David S. Miller authored
-
Linus Torvalds authored
of requiring users to select SCSI in order to see it.
-
http://nfsclient.bkbits.net/linux-2.5Trond Myklebust authored
into fys.uio.no:/home/linux/bitkeeper/nfsclient-2.5
-
Linus Torvalds authored
From Christoph Hellwig
-
Rusty Russell authored
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.
-
Christoph Hellwig authored
Remove the PCMCIA release timer that got missed in earlier patch. This is required for successful compilation of the driver.
-
- 21 Aug, 2003 17 commits
-
-
http://nfsclient.bkbits.net/linux-2.5Trond Myklebust authored
into fys.uio.no:/home/linux/bitkeeper/nfsclient-2.5
-
Trond Myklebust authored
nfsroot_mount().
-
Trond Myklebust authored
Problem analysis and fix provided by Andries Brouwer. Cleanup of nfs_lookup() by me...
-
Yoshinori Sato authored
o inline assembler funcs cleanup o machine depend header cleanup o interrupt management fix
-
Yoshinori Sato authored
o build script update o interrupt management fix o mtd support fix o signal handling fix
-
http://klibc.bkbits.net/early_userspaceLinus Torvalds authored
into home.osdl.org:/home/torvalds/v2.5/linux
-
bk://cifs.bkbits.net/linux-2.5cifsLinus Torvalds authored
into home.osdl.org:/home/torvalds/v2.5/linux
-
Linus Torvalds authored
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.
-
Bryan O'Sullivan authored
into camp4.serpentine.com:/export/bos/bk/linux-early
-
Bryan O'Sullivan authored
-
Steve French authored
-
http://nfsclient.bkbits.net/linux-2.5Trond Myklebust authored
into fys.uio.no:/home/linux/bitkeeper/nfsclient-2.5
-
Trond Myklebust authored
ESTALE errors.
-
Trond Myklebust authored
resent since you don't know whether the server is replying to the first or the second transmission. However we're currently setting the cutoff point to be the timeout of the first transmission. This patch moves the cutoff point to the actual start of the retransmission.
-
Trond Myklebust authored
in line with what is done for TCP. Signedness corrections when updating RTT. Be conservative when calculating RTO. Round up the residues.
-
Trond Myklebust authored
among other things, for the "soft" mount option.
-
Trond Myklebust authored
that call_encode() may cause rq_rcv_buf to be reset despite the fact that a reply might be delivered at any moment by a softirq. This typically results in 'NFS: server cheating in read reply' error messages. Solve by adding rq_private_buf, which is updated atomically from rq_rcv_buf.
-