Hi,
I am writing a gigabit ethernet driver for one of the
NICs.My hardware is capable of computing the checksum
and hence I am enabling per-packet handling of
TCP/IP/UDP checksum offload in transmit side.I would
like to know if there is a way by which I can tell the
upperguy that I will not be
Why are IP options not passed to userland on a udp socket?
(and on all other transport protocols for that matter)
We created such an implementation by just returning it in the ancillary
data control message. (Only for IP timestamps which we needed but this
could be easily done for all IP
* shubha mr [EMAIL PROTECTED] [020717 03:50] wrote:
Hi,
I am writing a gigabit ethernet driver for one of the
NICs.My hardware is capable of computing the checksum
and hence I am enabling per-packet handling of
TCP/IP/UDP checksum offload in transmit side.I would
like to know if there is a
Pointers to interface and arpcom are clearly equivalent as arpcom contains
the interface structure. The one definition for the combined structure
makes it very safe. However, there are many definitions of the softc
structure. Requiring arpcom to be at the beginning of all softc structs
Any driver that uses miibus_attach() is broken if struct arpcom is not at
the beginning of the softc structure. There was some discussion of this
more than a year ago when this bug showed up in the wx driver.
Jim
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
On Wed, 17 Jul 2002 10:58:12 -0700 (PDT), Bill Baumann [EMAIL PROTECTED] said:
Why bother with a if_softc field when the interface and softc pointer are
supposed to be the same? Also, the very old Lance driver (lnc) has this
problem. It makes me wonder how true we are to TCP/IP
Fortunately, none of the offending drivers (awi,lnc,pdq,ray) use mii.
On Wed, 17 Jul 2002, Jim McGrath wrote:
Any driver that uses miibus_attach() is broken if struct arpcom is not at
the beginning of the softc structure. There was some discussion of this
more than a year ago when this bug
