From owner-cvs-src@FreeBSD.ORG Tue Apr 24 23:40:50 2007 Return-Path: X-Original-To: cvs-src@freebsd.org Delivered-To: cvs-src@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9C8A816A402; Tue, 24 Apr 2007 23:40:50 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.freebsd.org (Postfix) with ESMTP id C852113C487; Tue, 24 Apr 2007 23:40:47 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.4) with ESMTP id l3ONegZq006528; Wed, 25 Apr 2007 03:40:42 +0400 (MSD) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.4/Submit) id l3ONWYtf006018; Wed, 25 Apr 2007 03:32:34 +0400 (MSD) (envelope-from yar) Date: Wed, 25 Apr 2007 03:32:33 +0400 From: Yar Tikhiy To: Peter Jeremy Message-ID: <20070424233233.GE31094@comp.chem.msu.su> References: <200704241051.l3OApoV0055362@repoman.freebsd.org> <20070424221721.GI1736@turion.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070424221721.GI1736@turion.vk2pj.dyndns.org> User-Agent: Mutt/1.5.9i Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/share/man/man4 vlan.4 X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Apr 2007 23:40:50 -0000 On Wed, Apr 25, 2007 at 08:17:22AM +1000, Peter Jeremy wrote: > On 2007-Apr-24 10:51:49 +0000, Yar Tikhiy 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