From owner-freebsd-mips@FreeBSD.ORG Sun Apr 19 17:33:34 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 64A4C8DE for ; Sun, 19 Apr 2015 17:33:34 +0000 (UTC) Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) (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 320366D2 for ; Sun, 19 Apr 2015 17:33:34 +0000 (UTC) Received: by iecrt8 with SMTP id rt8so89560049iec.0 for ; Sun, 19 Apr 2015 10:33:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=VSEjDdWJtjrZOg9Ohffn5qbvb2ABopJU7XeiDRh0KpY=; b=Vv8/y4AWn6PNsBcgg/8lA13zbfW1X5KFONYIAnhepy+E2xju1K+cB8dZ8rQKC3zjIN utSoVyFX8IKsu0BOjAJgu6d+nt14Eld5nSjlfEonWxrmvBmGxRLGvEWKPs4ScuTH0mz5 YEZa660P/jV4IPXNDKb5vbzzBsQSGtvTtLe+RsoA/OConi73PEFq/vUM+8kg+CknUopG q92yXs0Raz187bV3on6MZGY4a0CbFlf4CmvZoHLL52suW7KUMJgQ/mLOd8vpI2a9N7ey VH39UBMCFC7RRzeQ6fXkvyw5GLaUdEsGAT+4eYFpQ9g4WVw55WdK7oLARBRXfxGSt3xm jDug== MIME-Version: 1.0 X-Received: by 10.50.97.105 with SMTP id dz9mr15886316igb.49.1429464813449; Sun, 19 Apr 2015 10:33:33 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.36.17.194 with HTTP; Sun, 19 Apr 2015 10:33:33 -0700 (PDT) Date: Sun, 19 Apr 2015 10:33:33 -0700 X-Google-Sender-Auth: Xh6OVAj_FhJULk2dgbL1dwMUaCs Message-ID: Subject: compiling freebsd/mips on gcc-4.9.2 From: Adrian Chadd To: "freebsd-mips@freebsd.org" Content-Type: text/plain; charset=UTF-8 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: Sun, 19 Apr 2015 17:33:34 -0000 Hi, I've started evaluating the external toolchain support in -HEAD so I can evaluate getting it working on at least gcc-4.9.2. (I'm hoping that I can also use this with an external clang toolchain, but that's for later.) The TL;DR is this: * with the following patch, but minus the -Wa pieces, I get a booting kernel on mips32 platforms. I haven't yet tested the mips64 platforms. * however the assembler (binutils-2.25) complains thus: '{standard input}: Warning: .gnu_attribute 4,3 requires `softfloat'' * .. so if I add -Wa as in the patch it stops complaining, right until it compiles the fp emulation code, at which point it complains about undefined instructions. Which is totally correct - they're not defined with soft-float enabled. I'm going to work with bapt/kan over the next few days to get the port update and the mips32/mips64 ports into FreeBSD so others can start using this to build/debug kernel builds. I haven't yet started on userland builds; that'll come next. Thanks! -adrian adrian@lucy-11i386:~/work/freebsd/head-embedded/src % svn diff sys/conf/ Index: sys/conf/files.mips =================================================================== --- sys/conf/files.mips (revision 281125) +++ sys/conf/files.mips (working copy) @@ -61,6 +61,9 @@ libkern/memmove.c standard libkern/cmpdi2.c optional mips | mipsel libkern/ucmpdi2.c optional mips | mipsel +# required for gcc-4.9? +libkern/ashldi3.c standard +libkern/ashrdi3.c standard # cfe support dev/cfe/cfe_api.c optional cfe Index: sys/conf/kern.mk =================================================================== --- sys/conf/kern.mk (revision 281125) +++ sys/conf/kern.mk (working copy) @@ -150,7 +150,7 @@ # For MIPS we also tell gcc to use floating point emulation # .if ${MACHINE_CPUARCH} == "mips" -CFLAGS+= -msoft-float +CFLAGS+= -msoft-float -Wa,-msoft-float INLINE_LIMIT?= 8000 .endif Index: sys/conf/kmod.mk =================================================================== --- sys/conf/kmod.mk (revision 281125) +++ sys/conf/kmod.mk (working copy) @@ -134,8 +134,17 @@ .if ${MACHINE_CPUARCH} == mips CFLAGS+= -G0 -fno-pic -mno-abicalls -mlong-calls +CFLAGS+= -msoft-float -Wa,-msoft-float .endif +.if ${MACHINE_ARCH} == mips || ${MACHINE_ARCH} == mipsel +CFLAGS+= -march=mips32 +.endif + +.if ${MACHINE_ARCH} == mips64 || ${MACHINE_ARCH} == mips64el +CFLAGS+= -march=mips64 +.endif + .if defined(DEBUG) || defined(DEBUG_FLAGS) CTFFLAGS+= -g .endif From owner-freebsd-mips@FreeBSD.ORG Mon Apr 20 01:00:57 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 66FFEAB4 for ; Mon, 20 Apr 2015 01:00:57 +0000 (UTC) Received: from mail-pd0-x230.google.com (mail-pd0-x230.google.com [IPv6:2607:f8b0:400e:c02::230]) (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 37BF68BD for ; Mon, 20 Apr 2015 01:00:57 +0000 (UTC) Received: by pdea3 with SMTP id a3so190990039pde.3 for ; Sun, 19 Apr 2015 18:00:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; bh=GlecROnuNGhiwLkl5PJDUIrdcyuP+Ntgod42EE2P5U0=; b=Es74f5eZqvisUi5PlsPlB0Fu3DGfGCSuK62z/DfWKCsajEDKn6quzgsdlQtmlXml8N cTrQBgRcMKnsyPV3S7LefxCv2ZPy/5gSzjNbbE7Z7nxEgo5Li0dypZ7R7l2Xb/0XAR0h vdlKLYzOPrWkEm+GFAKEtVDLxDKV9QGItxPSb5wIDHbg3JofikRrVFWeWFGz1tly4IKA NXgRqWVfZ/IU9KnYpf87sDTNaqWVlkXtccEN/mgTbsDi3RJX3JEND001lrrW1GKa2sxf uR4eB/yXJN4leK9GXGqdQ0jFYszTVqc0NQnTZ2wCBRsBJESFeZPlMiwA64OTWpIrQhKd AWXw== X-Received: by 10.68.224.69 with SMTP id ra5mr23414797pbc.161.1429491656762; Sun, 19 Apr 2015 18:00:56 -0700 (PDT) Received: from jarvis.local.gmail.com (c-24-130-233-249.hsd1.ca.comcast.net. [24.130.233.249]) by mx.google.com with ESMTPSA id bz11sm16306806pdb.34.2015.04.19.18.00.54 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 19 Apr 2015 18:00:55 -0700 (PDT) From: Anmol Khirbat To: Wolfgang Zenker Cc: freebsd-mips@freebsd.org Subject: Re: Edge Router Lite: ntpd/ntpdate switch to 2050 References: <20150413130309.GA82425@lyxys.ka.sub.org> Date: Sun, 19 Apr 2015 18:00:53 -0700 In-Reply-To: <20150413130309.GA82425@lyxys.ka.sub.org> (Wolfgang Zenker's message of "Mon, 13 Apr 2015 15:03:09 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (darwin) MIME-Version: 1.0 Content-Type: text/plain 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: Mon, 20 Apr 2015 01:00:57 -0000 Wolfgang Zenker writes: > Hi, > > not sure if this is platform related or a generic problem: After the > recent ntpd update my Edge Router Lite running current has the problem > that ntpd and ntpdate set the date/time to somewhere in 2050, but only > if the offset of the system clock is larger than about 0.5 seconds. > > Currently running: > FreeBSD pomona 11.0-CURRENT FreeBSD 11.0-CURRENT #0: Mon Apr 13 03:48:04 CEST 2015 wolfgang@pomona:/usr/obj/usr/src/sys/UBQTERL mips > > Problem happened with a few earlier versions after the new ntpd as well. > I think this is a problem on all big-endian systems. I tried mips, mips64 and powerpc64 using Qemu. root@:~ # uname -a FreeBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #0 9cb51c3(master): Sun Apr 19 21:37:44 UTC 2015 anmol@fbsd8:/usr/home/anmol/obj/mips.mips64/usr/home/anmol/freebsd/sys/MALTA64 mips root@:~ # date Mon Apr 20 00:17:01 UTC 2015 root@:~ # /usr/sbin/ntpdate -v time.apple.com 20 Apr 00:17:07 ntpdate[678]: ntpdate 4.2.8p1-a (1) 6 Aug 08:04:48 ntpdate[678]: step time server 17.253.16.243 offset 205.523809 sec root@:~ # date Sat Aug 6 08:04:51 UTC 2050 # <<<<<===== Looks like usr.sbin/ntp/config.h is wrong. This seems to fix ntpdate. I am not sure what a general fix for all possible architectures would look like. diff --git a/usr.sbin/ntp/config.h b/usr.sbin/ntp/config.h index b771834..a6ed749 100644 --- a/usr.sbin/ntp/config.h +++ b/usr.sbin/ntp/config.h @@ -1586,7 +1586,7 @@ typedef unsigned int uintptr_t; # endif #else # ifndef WORDS_BIGENDIAN -/* # undef WORDS_BIGENDIAN */ +# define WORDS_BIGENDIAN 1 # endif #endif Regards, Anmol From owner-freebsd-mips@FreeBSD.ORG Mon Apr 20 06:14:08 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 36225DD0 for ; Mon, 20 Apr 2015 06:14:08 +0000 (UTC) Received: from yamoy.9001888.com (yamoy.9001888.com [178.251.230.21]) by mx1.freebsd.org (Postfix) with ESMTP id 24D67B50 for ; Mon, 20 Apr 2015 06:14:07 +0000 (UTC) To: freebsd-mips@freebsd.org Subject: about our email marketing Message-ID: Date: Mon, 20 Apr 2015 07:39:01 +0200 From: "Louis" Reply-To: bonnietongy@sina.com MIME-Version: 1.0 X-Mailer-LID: 26 X-Mailer-RecptId: 20219480 X-Mailer-SID: 282 X-Mailer-Sent-By: 1 Content-Type: text/plain; format=flowed; charset="UTF-8" Content-Transfer-Encoding: 8bit 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: Mon, 20 Apr 2015 06:14:08 -0000 Hi, You are receiving this email because we wish you to use our target email marketing service. We specialize in providing target email marketing services to a number of businesses all over the world! Email marketing is one of the best marketing strategies of all time and has helped many businesses globally achieve their goals, double their profits and increase their client base. We have worked on a number of projects and campaigns, all our packages are tailor made and designed according to your requirements. We wish to be your marketing partner, we can increase your business sales 2-5 times. If you would require more information please send us an email and we would be glad to discuss the project requirements with you soon. Looking forward to your positive response. Kind Regards Louis Marketing Specialist Email: wukelili@tom.com From owner-freebsd-mips@FreeBSD.ORG Mon Apr 20 06:24:30 2015 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 34FD9851 for ; Mon, 20 Apr 2015 06:24:30 +0000 (UTC) Received: from mail-pd0-f173.google.com (mail-pd0-f173.google.com [209.85.192.173]) (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 1041BD44 for ; Mon, 20 Apr 2015 06:24:29 +0000 (UTC) Received: by pdea3 with SMTP id a3so198048797pde.3 for ; Sun, 19 Apr 2015 23:24:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:message-id:subject:mime-version :content-type:content-transfer-encoding:content-disposition; bh=Uklg1b3UJdyqe2/Ws5WqJJgiLvxoTQdISqybjjFYlI8=; b=Fh3VZ4zXsicv0hRMOeClQjxNaMHh9r9MfivSo02vi3nGq5hofzC8KHi4nsBAv6YJz3 RwC7w5Aa3UDP68SnvzUG8QP4B9skyAteer9/r3p4SP5NPtjY00hrcf3Ap9swAkeVvZqJ YfJ6/e6Pfx3lisZ8RqaIFn1enN6Vb8j1z9u4ThLyItPYhepAlRJt4oyzREQbmoD8muqY UpCqtgHiOPDi3SivJ6r0zsU0zPuym+p65E7yWblNaZR1BWWsyOJLaJcdyOTxMajxsx0i oKERlb3mZ2o4El+oOiWY2Ky9M81TTndbZFvVj7/5pdXg177W18iNbK7GLEew4hDZltbb o95Q== X-Gm-Message-State: ALoCoQne9xgz4OnBfh/LPMltO1z4BjQzsqmzl1BqyQYq+I3qVmEfPvpbHsyIhQExQJlcNCeOMp4U X-Received: by 10.68.177.226 with SMTP id ct2mr4248190pbc.105.1429511068981; Sun, 19 Apr 2015 23:24:28 -0700 (PDT) Received: from brooklyn.local ([203.86.202.251]) by mx.google.com with ESMTPSA id oq7sm17051012pac.32.2015.04.19.23.24.27 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 19 Apr 2015 23:24:28 -0700 (PDT) Date: Mon, 20 Apr 2015 18:24:25 +1200 From: Nathan Ward To: freebsd-mips@freebsd.org Message-ID: Subject: Address error trap in ng_netflow on MIPS X-Mailer: Airmail (286) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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: Mon, 20 Apr 2015 06:24:30 -0000 Hi all, I am using freebsd on MIPS (on Buffalo=C2=A0WZR-HP-AG300H hardware, which= is basically just Atheros AP96 with some more flash, RAM, and a crippled= u-boot). I am running =46reeBSD 9.1. I am using netgraph=E2=80=99s netflow module, configured to look at both = ingress and egress packets ('msg netflow: setconfig =7B iface=3D0 conf=3D= 3 =7D=E2=80=99). This does not happen if I leave the default of receive-o= nly, however that does not do what I need in my environment. This works fine, for the most part, except when the router tries to trans= mit a DHCP response, which causes the following: + Trap cause =3D 4 (address error (load or I-fetch) - kernel mode) =5B thread pid 226 tid 100066 =5D Stopped at =C2=A0 =C2=A0 =C2=A0export9=5Fadd+0x1230: =C2=A0 =C2=A0 lw =C2= =A0 =C2=A0 =C2=A0a0,0(s7) I hooked up kgdb, and the problem is at this line of code, in sys/netgrap= h/netflow/ng=5Fnetflow.c: 761 =C2=A0 =C2=A0 =C2=A0 =C2=A0 if ((ip->ip=5Fv =21=3D IPVERSION) =7C=7C Hoping for a quick hack, I replaced all the ip->ip=5Fv references with=C2= =A0(((char *)ip)=5B0=5D >> 4). Nasty, sure, but it worked OK for my purpo= ses :-) Now it=E2=80=99s dying when it calls =22ip->ip=5Fsrc=E2=80=9D in netflow.= c, same sort of error (trap 4). I am unclear exactly what this error means, but it seems to be a MIPS err= or. I don=E2=80=99t know much about CPU architectures, so, here I am. It is curious to me that ip->ip=5Fhl, which is the other 4 bits of the fi= rst octet in the ip header, works fine. Other packets (received, or transmitted - because of forwarding or respon= ding to ping/DNS requests against the local DNS cache) also work fine. Here=E2=80=99s a dump of the ip struct, which all seems just fine: (kgdb) x/10 ip 0x8420380e: 0x45000148 =C2=A00x00004000 =C2=A00x40112584 =C2=A00x0a000001= 0x8420381e: 0x0a000021 =C2=A00x00430044 =C2=A00x01345a50 =C2=A00x02010600= 0x8420382e: 0xea83f35e =C2=A00x00000000 I have tried this on amd64 (VMWare =46usion VM on modern Macbook) and don= =E2=80=99t have any problems - the DHCP reply packets are transmitted jus= t fine, hence I am posting this on this list, rather than whatever list l= ooks after netgraph. Does anyone have pointers to anywhere I might be able to start trying to = fix this=3F Upgrading to =46reeBSD 10.1 is an obvious first step, but I want to be su= re that this will fix it first, I=E2=80=99ve got a handful of changes to = various user land components, I=E2=80=99ve got it on my roadmap, and woul= d avoid bringing that forward for the moment unless it=E2=80=99s necessar= y. I found=C2=A0https://github.com/freebsd/freebsd/commit/6cc0e8d2a0b583db57= 07f811d4ebfbe1ad05e628, which changes netinet/ip.h to use =5F=5Faligned(2= ) rather than 4, which fixes what seems to be a similar issue on ARM, but= it doesn=E2=80=99t seem to help me unfortunately. -- =20 Nathan Ward From owner-freebsd-mips@FreeBSD.ORG Mon Apr 20 06:27:31 2015 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BF8CE8A9 for ; Mon, 20 Apr 2015 06:27:31 +0000 (UTC) Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001:c05::229]) (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 8AF2DD61 for ; Mon, 20 Apr 2015 06:27:31 +0000 (UTC) Received: by igbpi8 with SMTP id pi8so60308376igb.0 for ; Sun, 19 Apr 2015 23:27: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; bh=0hrRyArs2Al+jm9nIIwFfvEVhRvghB9iAfYQxjMHgVs=; b=lpoxui/Pn248Ju9qRH+4bqHSfsOi+pUGmokp72o1SIkauqdcVk+QRTdXa1OUfkf4Hz dleN0RG2GOfjCn9PM7HuBwgy7XneBJavElbudd5nPu0lRC6F3afgHDDL3PrSe6aolOVN DjJ/bsFRAlRvWnZBK9NkxAaozF0Yb7uYZnLdMJ+VOOQw0Mos0fMCeI4iU7xRsU/Ziy7G fBYViC6QfgtghGlyih/UefFnWhccQbAB9yLIlavVbHOONKhq33zJqla7b0T5gR1tg0oD XQ/YQiOfVcQgy7wrtva45vWSFHo3PfVUg5rBAlVhFrmXXIz7NGdxal+jjwkWE5IAuLY9 YsiQ== MIME-Version: 1.0 X-Received: by 10.42.20.197 with SMTP id h5mr16805354icb.22.1429511250790; Sun, 19 Apr 2015 23:27:30 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.36.17.194 with HTTP; Sun, 19 Apr 2015 23:27:30 -0700 (PDT) In-Reply-To: References: Date: Sun, 19 Apr 2015 23:27:30 -0700 X-Google-Sender-Auth: xY7QQ4AKL6VK8GtzQ95bXrdlWl8 Message-ID: Subject: Re: Address error trap in ng_netflow on MIPS From: Adrian Chadd To: Nathan Ward Cc: "freebsd-mips@freebsd.org" Content-Type: text/plain; charset=UTF-8 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: Mon, 20 Apr 2015 06:27:31 -0000 Hi! The problem is that the frame is unaligned and MIPS doesn't do unaligned accesses for you. So yes, you either replace them with a memcpy of the header into aligned memory first, or you modify everything to use macros/inlines that treat the data as a char array (1 byte aligned) and do char accesses to get to it. -adrian From owner-freebsd-mips@FreeBSD.ORG Mon Apr 20 08:36:22 2015 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1A94D9F5 for ; Mon, 20 Apr 2015 08:36:22 +0000 (UTC) Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) (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 E4A93CF1 for ; Mon, 20 Apr 2015 08:36:21 +0000 (UTC) Received: by paboj16 with SMTP id oj16so200131407pab.0 for ; Mon, 20 Apr 2015 01:36:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version:content-type :content-transfer-encoding:content-disposition; bh=qeMC40tz/xxttO7toX43tNs9S5boa8ouyZG68nroBE4=; b=EYE/jPYTb8d138aU+beD4DptZIdSluceG7CNmoH5RS6hbwlo1XybzTMmYOEG4begBP oU7VOTFaiGQYojbdvMeGpbqWJAOjg7HTIwginrz0UJwLxGSkHTq/p6CW0zc8pd+43Nd+ cHZW7ycVyF4g3sH3ahktZha5Tih4+nQpLxnWkq/IRlX9fZCAhpGmgv11tBDioeziCQye BflJv79CeXcAfYjdht9uCwFYk073adF9ib765kHy4h0J1UwbwS/PZPTwd2r08qoJlLMR q9YYb05Gn7hSt79eYvKDIoLlfFm2fOdKsPsfmmPx/j4ZzttFV9DnrfwCGToouKFpXDsy BSyg== X-Gm-Message-State: ALoCoQl9xB+hU6NeCIFGFrw2ywN4mlFMq9QZD4YbG82E8rF+qFmxz1wYnxjJcpQpU1IS/+kX3R/G X-Received: by 10.66.221.193 with SMTP id qg1mr25726409pac.134.1429518975073; Mon, 20 Apr 2015 01:36:15 -0700 (PDT) Received: from brooklyn.local ([203.86.202.251]) by mx.google.com with ESMTPSA id l8sm6221258pdj.80.2015.04.20.01.36.13 (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 20 Apr 2015 01:36:14 -0700 (PDT) Date: Mon, 20 Apr 2015 20:36:10 +1200 From: Nathan Ward To: Adrian Chadd Cc: "=?utf-8?Q?freebsd-mips=40freebsd.org?=" Message-ID: In-Reply-To: References: Subject: Re: Address error trap in ng_netflow on MIPS X-Mailer: Airmail (286) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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: Mon, 20 Apr 2015 08:36:22 -0000 On 20 April 2015 at 18:27:31, Adrian Chadd (adrian=40freebsd.org(mailto:a= drian=40freebsd.org)) wrote: > Hi=21 Hey :-) > The problem is that the frame is unaligned and MIPS doesn't do > unaligned accesses for you. > =20 > So yes, you either replace them with a memcpy of the header into > aligned memory first, or you modify everything to use macros/inlines > that treat the data as a char array (1 byte aligned) and do char > accesses to get to it. OK, I=E2=80=99ll look in to this, memory alignment isn=E2=80=99t somethin= g I know intuitively, so, reading time. Any insight in to why this only happens when trying to transmit a DHCP re= ply packet=3F This is quite odd to me, given other packets I=E2=80=99ve t= ried work fine, and a DHCP reply is unicast, so is nothing special. -- =20 Nathan Ward From owner-freebsd-mips@FreeBSD.ORG Mon Apr 20 23:23:19 2015 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E43F3A62; Mon, 20 Apr 2015 23:23:19 +0000 (UTC) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (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 7C54A394; Mon, 20 Apr 2015 23:23:19 +0000 (UTC) Received: by wicmx19 with SMTP id mx19so51186659wic.1; Mon, 20 Apr 2015 16:23:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:subject:from:to:cc:date:content-type:mime-version; bh=8Wtv2EfYduXQAGTnOBg7HA5qgDmFJruzxek+9jgJTTM=; b=jAn3rKkOvnhLYScAZClI91F29gSwVX5M/lwketaABuYZJQlvU2kfHUk1gBhCYRi9bv CpqFRwSlBnfWGDJB7mF6cNTfQ4U58CYRJYIkVimSaQmp19+jlg2gden3xTeemaCtWQs0 h1fFEM4o7uhrggKa7UuEzxgk5rUoeY4Q4x6ju8KR506VpVrSarxBKsWey4AagbOWdqOu lAHf+AHt6LwrDQ9+s/qa/WD6Dcj4KQ38glxF9x3GJGNHjuYdKB+8XO1xz1FXJ+NpRo6G IORmQUKF3AyjpgCVWZ0UAFznCPyojmyaP3TVIbjlCAcdChTSIhzj/SZ5z6sadQ38gJzu A5RA== X-Received: by 10.180.7.234 with SMTP id m10mr29184711wia.93.1429572198031; Mon, 20 Apr 2015 16:23:18 -0700 (PDT) Received: from starkiller ([2001:470:b76a:eba:6a17:29ff:fe5c:8aeb]) by mx.google.com with ESMTPSA id gy8sm553523wib.13.2015.04.20.16.23.17 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 20 Apr 2015 16:23:17 -0700 (PDT) Message-ID: <1429572177.20150.28.camel@gmail.com> Subject: Control over the RSTP functionality of the AR8327 switch engine From: Petko Bordjukov To: freebsd-mips@freebsd.org Date: Tue, 21 Apr 2015 02:22:57 +0300 Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-UmV98G5UXZzO3ABZ9135" X-Mailer: Evolution 3.16.1 Mime-Version: 1.0 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: Mon, 20 Apr 2015 23:23:20 -0000 --=-UmV98G5UXZzO3ABZ9135 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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. --=-UmV98G5UXZzO3ABZ9135 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCAAGBQJVNYpRAAoJECq9VKOh1QeKGyUP/1olzh8CN2VXgdAf5FzvZtlB P0rbl440sZ6qo/rsgpFp3kq+IWojUerFlihyBjvvxujCBGmz4h73gAL3zOIBnpsW ODA9AaKQSaCUOPZnn0zPqhclLFob6BnOhrwa9alUk/ZrO5uYOcERjJbc/BHUVfyP NZZz++9DW43lyQKvljQ2016z4F0kgvnUgbQhQ37n5b1/dn3zHTaCx0mVmhitFslh JDnvS+CCmYr6sTbH+q43VuPx0sOXFQeOjEg62N+NpYA4xwYFfFaxn6/MMnsPF/DK vJoBRm+leLb316nVodMC2Fukt+dFJXs41CtL966W9hmqfmtG2E3apJEdZjbN6PCh eL6CD6guZES4yWvT/pOonzhMJaDdstvxr0SDXOEVRnJg9//Ni9C1a3dnMr17LtZ6 gSA+2jAxSQxq5tya9apAAMijjtN0B0Mpw+U1GUsr1Qz623oGbFOXt//PoT3u60VG mnPDevbp3wWUc59A4IburbZyWpLP/Ous5KLEtflMt+cOpYMX411G0SqYz1/xyYYm +0oahSDI9gZNESipb0z8NgwSgIncqIq767VMVZuUXsQHvPtSjCkNb9YL3M5K9t6C CwRYdzmqs/bGt61ktOj5NG+Fl3f1TQvUcNVwK1bDA8bEOS9bXL1DyyMl8b935818 s34dhnxbXIp9dtbLQ8n1 =z+ha -----END PGP SIGNATURE----- --=-UmV98G5UXZzO3ABZ9135-- From owner-freebsd-mips@FreeBSD.ORG Mon Apr 20 23:27:55 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 3D6F1AFC for ; Mon, 20 Apr 2015 23:27:55 +0000 (UTC) Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) (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 08B353D3 for ; Mon, 20 Apr 2015 23:27:55 +0000 (UTC) Received: by iedfl3 with SMTP id fl3so1956073ied.1 for ; Mon, 20 Apr 2015 16:27:54 -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; bh=U1V3gzV3Eqfv6vDf5fLgXiLZKLFw76UjRawEbu0JP30=; b=UYK1jiTAhj/fVKE807GjdLQsaF8KuKx9yAO3tYdrIH/DoGq6+pacVQ2GIyAhMmv5YM t86J+0VUCI4sdS1EWRXLwCxqnykwZJFWRMPRsYevFBfYCTmxEM6cu+Wk5oto2q6rrm8i 8GMCa022LL6xkSVqk4SFJxI0Av6dleSr/6Cb9IdG2gAUwm8NaEwisXFtOUpAOP23m3Ql v7jlaJeDdNNzE1OecPMz06u8sxagfQDm428X3XpB6og28Wg3gezu+qn7EqZE2vB61/1z xIRwx0tAAcRamPRo7TskDJPO6xM9IT/P65ogyvmLr32BJvYLvUjZXyl6eT6kniQu75lX pHHQ== MIME-Version: 1.0 X-Received: by 10.107.155.13 with SMTP id d13mr24934051ioe.29.1429572474535; Mon, 20 Apr 2015 16:27:54 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.36.17.194 with HTTP; Mon, 20 Apr 2015 16:27:54 -0700 (PDT) In-Reply-To: <1429572177.20150.28.camel@gmail.com> References: <1429572177.20150.28.camel@gmail.com> Date: Mon, 20 Apr 2015 16:27:54 -0700 X-Google-Sender-Auth: sjrQhHTkacAipaVN7UdyHzq2wro Message-ID: Subject: Re: Control over the RSTP functionality of the AR8327 switch engine From: Adrian Chadd To: Petko Bordjukov Cc: "freebsd-mips@freebsd.org" Content-Type: text/plain; charset=UTF-8 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: Mon, 20 Apr 2015 23:27:55 -0000 Hi, I don't know off hand, sorry :( -adrian On 20 April 2015 at 16:22, Petko Bordjukov 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. From owner-freebsd-mips@FreeBSD.ORG Tue Apr 21 00:08:16 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 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: References: <1429572177.20150.28.camel@gmail.com> Date: Tue, 21 Apr 2015 03:08:14 +0300 Message-ID: Subject: Re: Control over the RSTP functionality of the AR8327 switch engine From: Petko Bordjukov To: Adrian Chadd Cc: "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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 wrote: > Hi, > > I don't know off hand, sorry :( > > > > -adrian > > > On 20 April 2015 at 16:22, Petko Bordjukov 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. > From owner-freebsd-mips@FreeBSD.ORG Tue Apr 21 00:23:03 2015 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0A1D1406 for ; Tue, 21 Apr 2015 00:23:03 +0000 (UTC) Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) (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 C5D59BBE for ; Tue, 21 Apr 2015 00:23:02 +0000 (UTC) Received: by iecrt8 with SMTP id rt8so2593330iec.0 for ; Mon, 20 Apr 2015 17:23:02 -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; bh=kRooIkIAbs6mje7oZKiiGD2zUAYM6KC+IMaGXT0fTtQ=; b=YYAOx02ubfEVWyVPznKALdUff3kvlbpBcxo22rm402zrmrRiVfk1Yk0LpPGL8go+PU zdxRSjrC7Xe4iFVhUBzDhg5Tff6VaXLyQ6QuAQ/wtDfgeOKbf8OZuYjp1w2Zn3bMAYVp AklZ5F/7wzu/7xRvy/j989YupSMpFtrFGuAmR8mBQpvZXMnYU1UrkLA854dsK0wjn768 eQPkq8zRCKs8M2Q3lUTEYM4XbFdzTG+sDaTDlMOUJWKBlk0RpWKSEVlJ2PRRvRFJhj5F uiM4CWLwJL5koyWvxqXt5jZoLqcJ0+ez+RQpBvlDQU4ablCUwBgiyzzQn6sn4K8KO8jg dA2w== MIME-Version: 1.0 X-Received: by 10.43.163.129 with SMTP id mo1mr425934icc.61.1429575782332; Mon, 20 Apr 2015 17:23:02 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.36.17.194 with HTTP; Mon, 20 Apr 2015 17:23:02 -0700 (PDT) In-Reply-To: References: <1429572177.20150.28.camel@gmail.com> Date: Mon, 20 Apr 2015 17:23:02 -0700 X-Google-Sender-Auth: FLC2HveumSm09pwKBbNC01_NH1w Message-ID: Subject: Re: Control over the RSTP functionality of the AR8327 switch engine From: Adrian Chadd To: Petko Bordjukov Cc: "freebsd-mips@freebsd.org" Content-Type: text/plain; charset=UTF-8 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 00:23:03 -0000 On 20 April 2015 at 17:08, Petko Bordjukov wrote: > Do you think I can get some input from Atheros on the matter? > You could try on the openwrt lists, see if anyone has already done this. I read the 8327 datasheet and yes, it mentions the port config for the port STP mode, but nothing that's "don't do STP, but do learn MACs." -adrian From owner-freebsd-mips@FreeBSD.ORG Tue Apr 21 00:31:13 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 5204C583; Tue, 21 Apr 2015 00:31:13 +0000 (UTC) Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (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 D8D54CAA; Tue, 21 Apr 2015 00:31:12 +0000 (UTC) Received: by wizk4 with SMTP id k4so119695149wiz.1; Mon, 20 Apr 2015 17:31:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:subject:from:to:cc:date:in-reply-to:references :content-type:mime-version; bh=LNlBszYpF76e0F5pMomqoiP5YOND+hvIK+SnM99dYjQ=; b=lHhe9AQ6pPf1PbAbLEdsdcHrLPjtGhyMnMyz7phBJRo2WkrLLJBcp04qGga6rfPQ3O 4/wxFhyhK/05I7wscdEv+tYJF0XFN53Qaa0q1q7JC1cMm/MetbcOJ4KHIJjNi/DP/dP2 Cqbq8Wp+BCryOGCf6mL1J5TdB5FJZ+zOgLR5BuPm/ANRQItp5LBHs1tdZO+kyzhHto/R 1l7Hnfwjs7sQ2jihs8hlKvD5YI+bfGYfgqjrziLldoYNLKGcMUfXKR7aKEsJmTWEKTDW QS3gMpA8zJLq56XETRu32C0CwTzLRFZD7SZOuJ0+rbnpE9Q8N3nXrjw/+9NAOrThLWQ6 uT0A== X-Received: by 10.194.171.199 with SMTP id aw7mr635779wjc.64.1429576271410; Mon, 20 Apr 2015 17:31:11 -0700 (PDT) Received: from starkiller ([2001:470:b76a:eba:6a17:29ff:fe5c:8aeb]) by mx.google.com with ESMTPSA id pv2sm257003wjc.33.2015.04.20.17.31.10 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 20 Apr 2015 17:31:10 -0700 (PDT) Message-ID: <1429576261.20150.31.camel@gmail.com> Subject: Re: Control over the RSTP functionality of the AR8327 switch engine From: Petko Bordjukov To: Adrian Chadd Cc: "freebsd-mips@freebsd.org" Date: Tue, 21 Apr 2015 03:31:01 +0300 In-Reply-To: References: <1429572177.20150.28.camel@gmail.com> Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-zCVO0NHCH6gTNn0lYTuF" X-Mailer: Evolution 3.16.1 Mime-Version: 1.0 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 00:31:13 -0000 --=-zCVO0NHCH6gTNn0lYTuF Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On =D0=BF=D0=BD, 2015-04-20 at 17:23 -0700, Adrian Chadd wrote: > On 20 April 2015 at 17:08, Petko Bordjukov =20 > wrote: > > Do you think I can get some input from Atheros on the matter? > >=20 >=20 > You could try on the openwrt lists, see if anyone has already done=20 > this. Thanks, I already did that: https://lists.openwrt.org/pipermail/openwrt-users/2015-April/003716.html >=20 > I read the 8327 datasheet and yes, it mentions the port config for=20 > the > port STP mode, but nothing that's "don't do STP, but do learn MACs." >=20 >=20 >=20 > -adrian --=-zCVO0NHCH6gTNn0lYTuF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCAAGBQJVNZpFAAoJECq9VKOh1QeKRSMQAIcCh8QefpZn0zDYn+wF39pV MJxvK2ZuTiQFaujhmObmxMLMTkJ6JlPlzzV8rBjMT+NdTgMcp5oDEKzJxb3Mm/kq Y2oKfBERQb2TQGg3chQ3zi+vYWLVQ7ksSlHYYuPWyfUeGjLh4cMd2VfMzKuUiOlD GWg/hMvW/aadXaGoQunncHdjKHUzzIxPtn/mAbp0I4j1EoUXOYzBXtyaJ0VP5WWQ zja/r50bCh5J5w6FkA1bOmsTzFkLFtaLvzrsOowEy/NAwTDD7emZGFlHnsrpaKJ4 uloML10zpDpJr2xntvgGn7mVxeyzLNYL2b8Sv7d4UohFdhvrFtU2o1tD+j75C34q h01DLcmtQoGzeXzWzln7YNEatRaaRXZ6jyhN/CIWZ1vxtwWkcTGJTqvo84ZmdnHK yZfHRSLX+qlgD806blUOTXEdVdr2jiTjfZDC47VIefcrGIA5WI/lDRfjapqCr7Dh uaPrZAxmBIkcetQa52i19v8FGrogfNz0jX/KBCBe1md4rzrAAxjkKgqmgqiw8gUt xrjl+vcJdIOjzIpvxkAozc+YaVORWwbOJEnMQoTrhuJa2n7Sv0gywSGO7G8frXs2 IkbzUN//YQy/MEyhCX6g3GWqYl31qhrvQqyYqs4SsTiYIX5wPx/dT0TU8JcQngLZ RkqgRxctPoAej3/QHPhs =32KO -----END PGP SIGNATURE----- --=-zCVO0NHCH6gTNn0lYTuF-- From owner-freebsd-mips@FreeBSD.ORG Tue Apr 21 00:35:14 2015 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 83CD35F0 for ; Tue, 21 Apr 2015 00:35:14 +0000 (UTC) Received: from mail-ig0-x230.google.com (mail-ig0-x230.google.com [IPv6:2607:f8b0:4001:c05::230]) (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 4CC2CCBB for ; Tue, 21 Apr 2015 00:35:14 +0000 (UTC) Received: by igbhj9 with SMTP id hj9so3123786igb.1 for ; Mon, 20 Apr 2015 17:35:13 -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; bh=TPfBa2XVa28KIx/35laNkamx9NzoUkcDXvo7nxdK0aQ=; b=wMMWxjBLjz8p6CXvRTcTE1tJnhwslcI4llT3MtExKhOw6ZlqIx25B4qBuqfN5xD/ko JSZlOcXEkKcK1ozGxNIIWbu6dIHC2JIhc+gGiek/MJZYTFWNhydBk6X8swy3k3UETEYc i2ynyh7anCQcBR67X6+L0v9VQI6A/6U1Jknn88PD0dhECFsitbzzydRU4YaCCDg0ssNq TwDxc6vStAw3QBI9bDNfPkbJNUJNDIGn4u7imsHiq9QrwcHf7wzeHyh1287/88t8Zyvn DCzqSg5IZ7lk1F/wLsG3L6iId0vNXjmNBHfo098ZI79L5ujC1k7xfergdHM2r40r9tMT yIfQ== MIME-Version: 1.0 X-Received: by 10.107.136.25 with SMTP id k25mr24680460iod.88.1429576513665; Mon, 20 Apr 2015 17:35:13 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.36.17.194 with HTTP; Mon, 20 Apr 2015 17:35:13 -0700 (PDT) In-Reply-To: <1429576261.20150.31.camel@gmail.com> References: <1429572177.20150.28.camel@gmail.com> <1429576261.20150.31.camel@gmail.com> Date: Mon, 20 Apr 2015 17:35:13 -0700 X-Google-Sender-Auth: gdFCYztNoxChoTQ8dg3De0mZg80 Message-ID: Subject: Re: Control over the RSTP functionality of the AR8327 switch engine From: Adrian Chadd To: Petko Bordjukov Cc: "freebsd-mips@freebsd.org" Content-Type: text/plain; charset=UTF-8 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 00:35:14 -0000 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. -adrian From owner-freebsd-mips@FreeBSD.ORG Tue Apr 21 00:48:04 2015 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 53E3F698; Tue, 21 Apr 2015 00:48:04 +0000 (UTC) Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) (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 EBEA1DAC; Tue, 21 Apr 2015 00:48:03 +0000 (UTC) Received: by wiax7 with SMTP id x7so95596313wia.0; Mon, 20 Apr 2015 17:48:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:subject:from:to:cc:date:in-reply-to:references :content-type:mime-version; bh=VtVU2Fzo0nhdmdjiYBxj9xCyLTdk9rHcYz3gP679gro=; b=x+Ue4hyjf+IIP/biItYUjHbR0btihyeD0qJOycmLYY0ayLNTZ2u/bnGDNByNaM4xf3 +XnxBpk7KKoCDfNuAjm0FsAX6sUk60ZbJDBrMX4Of7PKDr4p+3wKoZbxejb5PECEaZAE S7jLsWvPPvQb34ydNgWhxkOmZBFKD5Leygt0YSTUJMgZE0EyNzavNJZcOX6f+fKD4bHn 0e0RGuvh4ToCvG0SxHPB/Te5Kk97UgfPIWZJ6BxSPXrGwApNuvY43enQQbVHdaFVwXXC jIV87nvyCPooOvWkGWhqGKo8vNfoUpa0zsiypqXvjfPufXcGAaJajfE+JJ5prtasTk9V VH4Q== X-Received: by 10.180.215.101 with SMTP id oh5mr888204wic.6.1429577282506; Mon, 20 Apr 2015 17:48:02 -0700 (PDT) Received: from starkiller ([2001:470:b76a:eba:6a17:29ff:fe5c:8aeb]) by mx.google.com with ESMTPSA id di7sm716562wib.23.2015.04.20.17.48.01 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 20 Apr 2015 17:48:02 -0700 (PDT) Message-ID: <1429577274.20150.35.camel@gmail.com> Subject: Re: Control over the RSTP functionality of the AR8327 switch engine From: Petko Bordjukov To: Adrian Chadd Cc: "freebsd-mips@freebsd.org" Date: Tue, 21 Apr 2015 03:47:54 +0300 In-Reply-To: References: <1429572177.20150.28.camel@gmail.com> <1429576261.20150.31.camel@gmail.com> Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-of2VRd0qkKbE/rYOjt/D" X-Mailer: Evolution 3.16.1 Mime-Version: 1.0 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 00:48:04 -0000 --=-of2VRd0qkKbE/rYOjt/D Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On =D0=BF=D0=BD, 2015-04-20 at 17:35 -0700, Adrian Chadd wrote: > Oh. >=20 > 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. >=20 > 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. Thanks, Adrian, I will update the other thread as well. >=20 >=20 >=20 > -adrian --=-of2VRd0qkKbE/rYOjt/D Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCAAGBQJVNZ46AAoJECq9VKOh1QeKjOYP/RJojYomzSc7yK8cdpvmG0l6 C15tId2wxGUkXia+09OfNnwltH1BoN5YadnespVf8UCwsp0wG4esEP8oGnE4+vVg bgahHQ5/XwHRjf9bA63x9Mqeo4PKqOs0BEXHKoYUn30JX/6QS+DdmpYsNbylvTcL qVa2lJDQ2J6bkAhaUpsh6coFvz/PGaSWm9AEy9/dcrYeoww/mN422WJccxx6LfQ3 X3tWHLxx3wFF94pjqI7PqIgnZ3qKbzMO+SwrHN5GSDAl4afbpWRf0ajCqKSa5mFc PT5wcIwxeqloDCSDXrXkCPsPmXkLknwRwsMupBcDS3FFPrkdlFDq+RuxhCQmtAzZ cwn8Z21t4tE+w3imaoVx9mDlpikP3yekFQc6xMdUGRuOoWwKoeTsJAT8n8w7iwoh wPoyjQBpcX+96jKzS3ctIFF+rdWQwlDr0XzlECCEE4ii72vGvNzn58TAfdj+qB3R 04XoA1TcSGgbpQ/ND5WQlGD9uBIV0WyGOHbsx/FRBEljsR0Asl8kXP4I1FGOpFq0 vWAFgW4aSF4oUQJxvECg00YfO6jGr33NQ2JOII+WB0tlqz1bSW11YebZ8nxjo+jQ QgVzS9tfkMS++y2tu7C63U9fxyrNuAf4LAoJLAYwPemSgF+alFUUqCUuP7pNJPwJ taspP7RfvxNGaUaJYIyu =nXpX -----END PGP SIGNATURE----- --=-of2VRd0qkKbE/rYOjt/D-- From owner-freebsd-mips@FreeBSD.ORG Tue Apr 21 00:58:51 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 3C682A36 for ; Tue, 21 Apr 2015 00:58:51 +0000 (UTC) Received: from mail-pd0-f176.google.com (mail-pd0-f176.google.com [209.85.192.176]) (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 10FC3E98 for ; Tue, 21 Apr 2015 00:58:50 +0000 (UTC) Received: by pdbqa5 with SMTP id qa5so224453077pdb.1 for ; Mon, 20 Apr 2015 17:58:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Z5Lqv2ltpPzeKzUxFyvVwmTB6F1i6irWCQDtNQoA9l8=; b=KUAUjTPXGOf65UaEUfWjfv1lZ2P9bKT35hWYVRYHL9/ziWjCBYde3+TGS4jc2BNalB di/MAw9vvh0iafagIE5JU/HIBCTGWr9OOmGx64w29UKWorSVoOW7TXX5oslbJm9vcUjQ J/y5SQnK4+AW9lwG7dMQy0mdQ4BHAJ9Nkw1ZObd/SjI8J+i6aSyg+e2N3GCfpYeGJSLd KNBqafUvTLxU+P5VkykH/+TyO72DF3biRQ20U10nuFtUTtpxK4hncH5PXL/wRqesAP7y mRhSnGBvVBGV/uzrA2dXtf/IT75En7BZWiX8wHrUgNfjiMCkRi8ft5oLV7vtQPgsx1eM Iouw== X-Gm-Message-State: ALoCoQla+HblhhASkEhmPU9vb1I7nsfgRwD1sDiHfLZ4Pna6d4+FGwGj9RN8/+TuC9Hs9VZ7Xn2l MIME-Version: 1.0 X-Received: by 10.70.108.137 with SMTP id hk9mr16040505pdb.105.1429577924423; Mon, 20 Apr 2015 17:58:44 -0700 (PDT) Sender: andy@fud.org.nz Received: by 10.70.76.229 with HTTP; Mon, 20 Apr 2015 17:58:44 -0700 (PDT) In-Reply-To: <1429577274.20150.35.camel@gmail.com> References: <1429572177.20150.28.camel@gmail.com> <1429576261.20150.31.camel@gmail.com> <1429577274.20150.35.camel@gmail.com> Date: Tue, 21 Apr 2015 12:58:44 +1200 X-Google-Sender-Auth: rbacTPkJ21-3Tp4EisV-fEZQWj4 Message-ID: Subject: Re: Control over the RSTP functionality of the AR8327 switch engine From: Andrew Thompson To: Petko Bordjukov Cc: Adrian Chadd , "freebsd-mips@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Apr 2015 00:58:51 -0000 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 does 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. cheers, Andrew 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 From owner-freebsd-mips@FreeBSD.ORG Tue Apr 21 22:45:07 2015 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4E08AE64; Tue, 21 Apr 2015 22:45:07 +0000 (UTC) Received: from saturn.lyxys.ka.sub.org (saturn.lyxys.ka.sub.org [217.29.35.151]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B2E50177C; Tue, 21 Apr 2015 22:45:06 +0000 (UTC) Received: from juno.lyxys.ka.sub.org (juno.lyx [IPv6:fd2a:89ca:7d54:0:240:caff:fe92:4f47]) by saturn.lyxys.ka.sub.org (8.14.9/8.14.9) with ESMTP id t3LMig7Z050655 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 22 Apr 2015 00:44:42 +0200 (CEST) (envelope-from wolfgang@lyxys.ka.sub.org) Received: from juno.lyxys.ka.sub.org (localhost [127.0.0.1]) by juno.lyxys.ka.sub.org (8.14.9/8.14.9) with ESMTP id t3LMnxDs013985 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 22 Apr 2015 00:49:59 +0200 (CEST) (envelope-from wolfgang@lyxys.ka.sub.org) Received: (from wolfgang@localhost) by juno.lyxys.ka.sub.org (8.14.9/8.14.9/Submit) id t3LMnwAt013984; Wed, 22 Apr 2015 00:49:58 +0200 (CEST) (envelope-from wolfgang@lyxys.ka.sub.org) X-Authentication-Warning: juno.lyx: wolfgang set sender to wolfgang@lyxys.ka.sub.org using -f Date: Wed, 22 Apr 2015 00:49:58 +0200 From: Wolfgang Zenker To: freebsd-mips@freebsd.org Cc: glebius@FreeBSD.org Subject: Re: Edge Router Lite: ntpd/ntpdate switch to 2050 Message-ID: <20150421224958.GA13041@lyxys.ka.sub.org> References: <20150413130309.GA82425@lyxys.ka.sub.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: private site User-Agent: Mutt/1.5.23 (2014-03-12) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (saturn.lyxys.ka.sub.org [IPv6:fd2a:89ca:7d54:1:200:24ff:feca:b4cc]); Wed, 22 Apr 2015 00:44:43 +0200 (CEST) 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 22:45:07 -0000 [Cc Gleb because he committed the current ntp/config.h] * Anmol Khirbat [150420 03:00]: > Wolfgang Zenker writes: >> not sure if this is platform related or a generic problem: After the >> recent ntpd update my Edge Router Lite running current has the problem >> that ntpd and ntpdate set the date/time to somewhere in 2050, but only >> if the offset of the system clock is larger than about 0.5 seconds. >> Currently running: >> FreeBSD pomona 11.0-CURRENT FreeBSD 11.0-CURRENT #0: Mon Apr 13 03:48:04 CEST 2015 wolfgang@pomona:/usr/obj/usr/src/sys/UBQTERL mips >> Problem happened with a few earlier versions after the new ntpd as well. > I think this is a problem on all big-endian systems. I tried mips, > mips64 and powerpc64 using Qemu. > [..] > Looks like usr.sbin/ntp/config.h is wrong. This seems to fix ntpdate. > I am not sure what a general fix for all possible architectures would look like. > diff --git a/usr.sbin/ntp/config.h b/usr.sbin/ntp/config.h > index b771834..a6ed749 100644 > --- a/usr.sbin/ntp/config.h > +++ b/usr.sbin/ntp/config.h > @@ -1586,7 +1586,7 @@ typedef unsigned int uintptr_t; > # endif > #else > # ifndef WORDS_BIGENDIAN > -/* # undef WORDS_BIGENDIAN */ > +# define WORDS_BIGENDIAN 1 > # endif > #endif I agree, running the configure script in /usr/src/contrib/ntp on a big-endian system produces a config.h that has the "# define WORDS_BIGENDIAN 1" line. Probably everyone expected the ntp sources to use the proper macros to convert between "network" and "host" byte order, in that case the ntp sources would not need to know about the endian-ness. But apparently that is not the case, so our pre-defined /usr/src/usr.sbin/ntp/config.h needs to have a mechanism to set WORDS_BIGENDIAN depending on the platform. Wolfgang From owner-freebsd-mips@FreeBSD.ORG Thu Apr 23 05:06:57 2015 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 710181E5 for ; Thu, 23 Apr 2015 05:06:57 +0000 (UTC) Received: from aur.1dianliulan.com (aur.1dianliulan.com [23.92.219.77]) by mx1.freebsd.org (Postfix) with ESMTP id 0286B171A for ; Thu, 23 Apr 2015 05:06:57 +0000 (UTC) To: freebsd-mips@freebsd.org Subject: business leads Message-ID: <9c07246c4184eb3e7ac1327c840aeedc@cakegroup.com> Date: Thu, 23 Apr 2015 06:54:38 +0200 From: "John" Reply-To: healerc@tom.com MIME-Version: 1.0 X-Mailer-LID: 5 X-Mailer-RecptId: 6480522 X-Mailer-SID: 282 X-Mailer-Sent-By: 1 Content-Type: text/plain; format=flowed; charset="UTF-8" Content-Transfer-Encoding: 8bit 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: Thu, 23 Apr 2015 05:06:57 -0000 Hey, You are receiving this email because we wish you to use our email marketing service. We wish to be your email marketing partner, we can grow your business 2-5 times than now. If you would require more information please send us an email and we would be glad to discuss the project requirements with you soon. Looking forward to your positive response. Kind Regards John Email: pottleyo@aliyun.com ------------------------------------------------- This e-mail message and its attachments (if any) are intended solely for the use of the addressee(s) hereof. In addition, this message and the attachments (if any) may contain information that is confidential, privileged and exempt from disclosure under applicable law. If you are not the intended recipient of this message, you are prohibited from reading, disclosing, reproducing, distributing, disseminating or otherwise using this transmission. Delivery of this message to any person other than the intended recipient is not intended to waive any right or privilege. If you have received this message in error, please promptly notify the sender and immediately delete this message from your system. If you don't wish our future news letter, pls send address to ttickmay@aliyun.com for removal. From owner-freebsd-mips@FreeBSD.ORG Fri Apr 24 05:49:32 2015 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 94E6F991 for ; Fri, 24 Apr 2015 05:49:32 +0000 (UTC) Received: from potato.366627.com (potato.366627.com [104.217.3.40]) by mx1.freebsd.org (Postfix) with ESMTP id 4F8C91707 for ; Fri, 24 Apr 2015 05:49:32 +0000 (UTC) To: freebsd-mips@freebsd.org Subject: leads for your business Message-ID: <4126191a8fa63b4b47097ceaa6af1732@getcake.com> Date: Thu, 23 Apr 2015 18:23:41 +0200 From: "John" Reply-To: broling@aliyun.com MIME-Version: 1.0 X-Mailer-LID: 26 X-Mailer-RecptId: 20219480 X-Mailer-SID: 322 X-Mailer-Sent-By: 1 Content-Type: text/plain; format=flowed; charset="UTF-8" Content-Transfer-Encoding: 8bit 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: Fri, 24 Apr 2015 05:49:32 -0000 Hey, We can help you to generate business from our email marketing. I can help you accomplish that if you're not already. I specialize in the following: Email Marketing Leads Generating. Just reply back and I can go over options for you. Thanks, John Email: pottleyo@aliyun.com ------------------------------------------------- This e-mail message and its attachments (if any) are intended solely for the use of the addressee(s) hereof. In addition, this message and the attachments (if any) may contain information that is confidential, privileged and exempt from disclosure under applicable law. If you are not the intended recipient of this message, you are prohibited from reading, disclosing, reproducing, distributing, disseminating or otherwise using this transmission. Delivery of this message to any person other than the intended recipient is not intended to waive any right or privilege. If you have received this message in error, please promptly notify the sender and immediately delete this message from your system. If you don't wish our future news letter, pls send address to ttickmay@aliyun.com for removal.