Date: Wed, 25 Apr 2007 03:32:33 +0400 From: Yar Tikhiy <yar@comp.chem.msu.su> To: Peter Jeremy <peterjeremy@optushome.com.au> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/share/man/man4 vlan.4 Message-ID: <20070424233233.GE31094@comp.chem.msu.su> In-Reply-To: <20070424221721.GI1736@turion.vk2pj.dyndns.org> References: <200704241051.l3OApoV0055362@repoman.freebsd.org> <20070424221721.GI1736@turion.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 25, 2007 at 08:17:22AM +1000, Peter Jeremy wrote: > On 2007-Apr-24 10:51:49 +0000, Yar Tikhiy <yar@freebsd.org> wrote: > >yar 2007-04-24 10:51:49 UTC > > > > FreeBSD src repository > > > > Modified files: > > share/man/man4 vlan.4 > > Log: > > tl(4) in fact has no signs of long frame support. > > Have you verified that tl(4) _doesn't_ support vlan frames? When > vlan(4) was first being put together, I looked at the ThunderLAN > datasheet, looked at the code and I think I may have tested it. > AFAIR, ThunderLAN chips don't have any frame size limits and rely on > the framesize information in the shared buffers - so there's nothing > the driver needs to do other than have the correct MTU. > > I will check this later this week if I get the chance. If tl(4) can receive long frames in default mode, it should set the respective hardware capability bit. -- Yar
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070424233233.GE31094>