From owner-freebsd-mips@FreeBSD.ORG  Tue Apr 21 00:08:16 2015
Return-Path: <owner-freebsd-mips@FreeBSD.ORG>
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 A57E212F;
 Tue, 21 Apr 2015 00:08:16 +0000 (UTC)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com
 [IPv6:2a00:1450:400c:c00::22d])
 (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 3EE329F4;
 Tue, 21 Apr 2015 00:08:16 +0000 (UTC)
Received: by wgso17 with SMTP id o17so196517739wgs.1;
 Mon, 20 Apr 2015 17:08:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=skyzAkLqVQ4Xtypiue59ACX3/xCspP8Hiu8oRscv3vo=;
 b=N0udoTL/+6mcDYsFqhFJls55bIQ6X3td1mJvuzigRYQQ4UgnE3SEgiyUTa21rIcq9E
 MlkOlvLaZnPWYDNs1JDvoY+rEjmnHCBTntF4vQ1kMYsS5IAp0WF4WY7lJI2SPxKi9PXH
 ySADU6L6+DBmRQu43TU5Bs5etwvoJ7qqjuR6Lq7d4J331cnF5iWEUEk06gNYSFoIDA3r
 AyV/cc4mOfuIl1iF1MqN7AL2gZ0F1Rkja79Y9VEEX4j3x/OhVQiPKU26+1Oo8e7qhhWU
 LXFrGvtkPboS+1NGnoOl6L3XVR2Zf02cl5WzdJHWUtEFbETegzjUcO77KT16Nnas3Qsc
 KfLQ==
MIME-Version: 1.0
X-Received: by 10.180.100.101 with SMTP id ex5mr618655wib.13.1429574894523;
 Mon, 20 Apr 2015 17:08:14 -0700 (PDT)
Received: by 10.28.17.20 with HTTP; Mon, 20 Apr 2015 17:08:14 -0700 (PDT)
In-Reply-To: <CAJ-VmokzcNSLzBSy2v2KQU1oVENM9nautcAwviaRDMO7ZdmztQ@mail.gmail.com>
References: <1429572177.20150.28.camel@gmail.com>
 <CAJ-VmokzcNSLzBSy2v2KQU1oVENM9nautcAwviaRDMO7ZdmztQ@mail.gmail.com>
Date: Tue, 21 Apr 2015 03:08:14 +0300
Message-ID: <CAAgmp6ucYsXVh=1nL=yoCCObpA-4OXmFVT4bAjGqp_U+pj2eTQ@mail.gmail.com>
Subject: Re: Control over the RSTP functionality of the AR8327 switch engine
From: Petko Bordjukov <bordjukov@gmail.com>
To: Adrian Chadd <adrian@freebsd.org>
Cc: "freebsd-mips@freebsd.org" <freebsd-mips@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.20
X-BeenThere: freebsd-mips@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Porting FreeBSD to MIPS <freebsd-mips.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-mips>,
 <mailto:freebsd-mips-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-mips/>
List-Post: <mailto:freebsd-mips@freebsd.org>
List-Help: <mailto:freebsd-mips-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mips>,
 <mailto:freebsd-mips-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2015 00:08:16 -0000

Do you think I can get some input from Atheros on the matter?

On Tue, Apr 21, 2015 at 2:27 AM, Adrian Chadd <adrian@freebsd.org> wrote:

> Hi,
>
> I don't know off hand, sorry :(
>
>
>
> -adrian
>
>
> On 20 April 2015 at 16:22, Petko Bordjukov <bordjukov@gmail.com> wrote:
> > Hello,
> >
> > I recently noticed that the data sheet of AR8327 states that it has
> > embedded spanning tree support.
> >
> >> Spanning Tree can be enabled globally or on a per-port basis by
> >> configuring the Port Status register.
> >
> > Do you think it would be feasible to expose control over this
> > functionality? I couldn't quite figure out which register needs to be
> > changed in order to enable it.
>