From owner-freebsd-mips@FreeBSD.ORG Tue Apr 21 01:34:31 2015 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 23245DED; Tue, 21 Apr 2015 01:34:31 +0000 (UTC) Received: from mail-ig0-x22b.google.com (mail-ig0-x22b.google.com [IPv6:2607:f8b0:4001:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DD2CF2E3; Tue, 21 Apr 2015 01:34:30 +0000 (UTC) Received: by igbhj9 with SMTP id hj9so3983723igb.1; Mon, 20 Apr 2015 18:34:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=Np4k9ccKk/j2einY/cGdaFRLDGI3d2z7e1o0LDzsiiw=; b=sQVrIlq5Pd1NaVaIwEcIrQ/fkSSytLPZUMZzQlMftbfLMm0Lo0pYOll8PMMRYOOjRp hQwGbGeG/Nnz1sS5W9h4z5BpHI7pJlBClnzMZpr0RUnoiPmXOvdSqi0i+jXqkKwEeI9f Oc5QRZ2VcNrItJz5sO1/yEBmozmrcUof80VTOZGG/21kSXuz6mrAt0C9bLe60vxNbbmw 7MAErqfoVOja89eoSc3y4u0snvMnb1gEwuIGXRJp+xt9q0r5Fl6hPfi407LQIKJzLYg0 wCfyjM6ncItuxAAJKlg3H/Xk8DaaRwxL87w9gKzxvkoXFzi87+MXHWNgXscrO/ECEQRz y5zA== MIME-Version: 1.0 X-Received: by 10.107.155.13 with SMTP id d13mr25427525ioe.29.1429580070321; Mon, 20 Apr 2015 18:34:30 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.36.17.194 with HTTP; Mon, 20 Apr 2015 18:34:30 -0700 (PDT) In-Reply-To: References: <1429572177.20150.28.camel@gmail.com> <1429576261.20150.31.camel@gmail.com> <1429577274.20150.35.camel@gmail.com> Date: Mon, 20 Apr 2015 18:34:30 -0700 X-Google-Sender-Auth: bOuVZF2LU3iS-U5tRmYDj_JYFP4 Message-ID: Subject: Re: Control over the RSTP functionality of the AR8327 switch engine From: Adrian Chadd To: Andrew Thompson Cc: Petko Bordjukov , "freebsd-mips@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Apr 2015 01:34:31 -0000 On 20 April 2015 at 17:58, Andrew Thompson wrote: > On 21 April 2015 at 12:47, Petko Bordjukov wrote: >> >> On =D0=BF=D0=BD, 2015-04-20 at 17:35 -0700, Adrian Chadd wrote: >> > Oh. >> > >> > So, I think the point here is that you can control the port STP mode >> > (blocked, learning, active, etc) - you then glue that into the >> > existing bridge code in software that's speaking STP. >> > >> > I don't know if the AR8327 speaks STP/RSTP itself. I know it manages >> > its own learning. >> >> I came to that conclusion as well. It looks like AR8327 only gives you >> the tools to control the mode of the port and you have to implement >> RSTP yourself. Which brings us back to square one in the other thread. > > > We already have a standalone RSTP implemetation in net/bridgestp.c, it do= es > not depend on the bridge code. If you look in bridgestp.h there are only = a > couple of functions you need to call. You could hook in to > bstp_set_port_state() to set the chip register to the correct > discard/learn/forward state and somehow pass up the PDUs to bstp_input(). > Not sure if its worth it but the hard part is done. Hi, Right. So it wouldn't be that difficult to do; someone just has to go ahead and do it. :-) Petko - having per-port STP awareness on etherswitch would be nice. If anyone here is interested in helping Petko out then please let him know. I'm way too busy doing other things. -adrian