Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 27 Feb 2003 11:15:02 -0300
From:      "Daniel C. Sobral" <dcs@tcoip.com.br>
To:        "Daniel C. Sobral" <dcs@tcoip.com.br>
Cc:        Ruslan Ermilov <ru@FreeBSD.org>, Bill Paul <wpaul@FreeBSD.org>, src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   Re: cvs commit: src/sys/dev/fxp if_fxp.c if_fxpreg.h if_fxpvar.h
Message-ID:  <3E5E1D66.6080801@tcoip.com.br>
In-Reply-To: <3E5E0EEC.9020203@tcoip.com.br>
References:  <200302262212.h1QMC4L8017995@repoman.freebsd.org> <3E5DFD83.4070605@tcoip.com.br> <20030227122441.GF39346@sunbay.com> <3E5E0EEC.9020203@tcoip.com.br>

next in thread | previous in thread | raw e-mail | index | archive | help
Daniel C. Sobral wrote:
> Ruslan Ermilov wrote:
> 
>> On Thu, Feb 27, 2003 at 08:58:59AM -0300, Daniel C. Sobral wrote:
>>
>>> Bill Paul wrote:
>>>
>>>> wpaul       2003/02/26 14:12:04 PST
>>>>
>>>> Modified files:
>>>>   sys/dev/fxp          if_fxp.c if_fxpreg.h if_fxpvar.h Log:
>>>> As previously threatened, add TCP/IP checksum offload support to
>>>> the fxp driver. This is enabled only for the 82550/82551 chips
>>>> (PCI revision code 12 or 13). RX and TX checksum offload are
>>>> both supported. Transmit offload is limited to TCP and UDP only
>>>> right now: there seems to be a problem with IP header checksumming
>>>> on transmit in some cases.
>>>
>>>
>>> I'm curious. Is there any way of knowing whether support has been 
>>> detected and is in use? I did the pciconf trick you mentioned, but... 
>>> <shrug>
>>>
>> ifconfig(8) will tell you:
>>
>> xl0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
>>         options=3<RXCSUM,TXCSUM>
>>         ether 00:50:da:b4:10:5b
>>         media: Ethernet autoselect (none)
>>         status: no carrier
>>
>> "ifconfig -m" will tell you the list of supported capabilities.
>>
>>
>>> Alas, when you say revision code 12 or 13... is that hex or decimal? 
>>> pciconf shows some of mine as being 0d.
>>>
>>
>> 0d == 13.  :-)
> 
> 
> Unless Bill Paul meant 13 as being 0x13 == 19. He mentions pciconf, 
> which shows just "0d", and would show just "13" for 0x13, so I'm still 
> unsure. Well, I'll have a new kernel soon on my 5.x testbox, and check 
> this out. Thanks for the ifconfig reply.

So... how does one turn it on?

fxp2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
         options=8<VLAN_MTU>
         capability list:
                 =b<RXCSUM,TXCSUM,VLAN_MTU>
         ether 00:02:b3:8f:30:41
         media: Ethernet autoselect (100baseTX <full-duplex>)
         status: active
         supported media:
                 media autoselect
                 media 100baseTX mediaopt full-duplex
                 media 100baseTX
                 media 10baseT/UTP mediaopt full-duplex
                 media 10baseT/UTP
                 media none
                 media 100baseTX mediaopt hw-loopback


-- 
Daniel C. Sobral                   (8-DCS)
Gerencia de Operacoes
Divisao de Comunicacao de Dados
Coordenacao de Seguranca
TCO
Fones: 55-61-313-7654/Cel: 55-61-9618-0904
E-mail: Daniel.Capo@tco.net.br
         Daniel.Sobral@tcoip.com.br
         dcs@tcoip.com.br

Outros:
	dcs@newsguy.com
	dcs@freebsd.org
	capo@notorious.bsdconspiracy.net

Somebody's terminal is dropping bits.
I found a pile of them over in the corner.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E5E1D66.6080801>