d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
0b5af5520d
freebsd-dev/sys/dev/ed
History
Warner Losh 84e924047d When reading via memory, read in (amount + 1) / 2 (to properly round 
up) rather than amount + 1 / 2, which is the same as amount, or 2x too
many words which leads to data corruption.

# This fixes the sbdrop panics I was seeing with the Toshiba LANCT00A.
2009-03-28 06:22:11 +00:00
..
ax88x90reg.h MFp4: 2005-10-05 05:21:07 +00:00
dl100xxreg.h MFp4: 2005-10-05 05:21:07 +00:00
if_ed98.h
if_ed_3c503.c Have a function pointer to the routine to call for writing an mbuf 2006-01-27 19:10:13 +00:00
if_ed_cbus.c o break newbus api: add a new argument of type driver_filter_t to 2007-02-23 12:19:07 +00:00
if_ed_hpp.c Have a function pointer to the routine to call for writing an mbuf 2006-01-27 19:10:13 +00:00
if_ed_isa.c o break newbus api: add a new argument of type driver_filter_t to 2007-02-23 12:19:07 +00:00
if_ed_novell.c MFp4: 2006-06-12 04:30:42 +00:00
if_ed_pccard.c It turns out that the Toshiba LANCT00A PC Card is really like the 2009-03-28 04:56:56 +00:00
if_ed_pci.c Add Winbond W89C940F to the list. Also, stub in some entries for two 2007-12-31 03:29:02 +00:00
if_ed_rtl80x9.c Add missing 'sc->chip_type ==' to an ugly switch statement expression 2007-12-31 03:27:21 +00:00
if_ed_sic.c Have a function pointer to the routine to call for writing an mbuf 2006-01-27 19:10:13 +00:00
if_ed_wd80x3.c It turns out that the Toshiba LANCT00A PC Card is really like the 2009-03-28 04:56:56 +00:00
if_ed.c When reading via memory, read in (amount + 1) / 2 (to properly round 2009-03-28 06:22:11 +00:00
if_edreg.h MFp4: 2005-10-05 05:21:07 +00:00
if_edvar.h It turns out that the Toshiba LANCT00A PC Card is really like the 2009-03-28 04:56:56 +00:00
rtl80x9reg.h MFp4: 2005-10-05 05:21:07 +00:00
tc5299jreg.h MFp4: 2005-10-05 05:21:07 +00:00