From owner-freebsd-mips@FreeBSD.ORG Thu May 23 17:43:44 2013 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BE2A9780 for ; Thu, 23 May 2013 17:43:44 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-oa0-f43.google.com (mail-oa0-f43.google.com [209.85.219.43]) by mx1.freebsd.org (Postfix) with ESMTP id 82A5030D for ; Thu, 23 May 2013 17:43:44 +0000 (UTC) Received: by mail-oa0-f43.google.com with SMTP id o6so4838747oag.16 for ; Thu, 23 May 2013 10:43:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=AkEFWyBWxKCIFVXpzo83vOsj4uLe7KASflwiHIDGeGQ=; b=dBdydaD8oUPeTD4AR6T+UZAFYTzhW5sgOM41lxwQsVI+d8PrjkSgF7//s7+ZxSuOpv pmmj1MuQrOtPQDG3kc2t+ssp2IBDBviBxMUV7/WkLjArLcjCczEvdx5k5kCI+ImRZSuH EfKOJ8l6WP5Hfs2bsKDkKbUKboSk4ckV7CCbIhClDbNc3zoiuF8h9Qi3eNubpVVY6zbb cqROdFSWAqzilUvnkI89xG2mFnfjT0SXhWwwbiWR9Pba+m4N9wrKukKPkBnmdkQToduq qhCfeK9zLH1BWYrq3cS8cW6oB0rExrG41lxl8rt9y2ATsgcfQ6btCJ8VVIgeHsESpeiZ gFUw== X-Received: by 10.182.87.134 with SMTP id ay6mr9292642obb.13.1369331023602; Thu, 23 May 2013 10:43:43 -0700 (PDT) Received: from fusionlt2834a.int.fusionio.com ([209.117.142.2]) by mx.google.com with ESMTPSA id jw8sm13172706obb.14.2013.05.23.10.43.41 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 23 May 2013 10:43:41 -0700 (PDT) Sender: Warner Losh Subject: Re: Ubiquiti EdgeRouter Lite works multi-user with -CURRENT. Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <20130523134206.69ea6994@zeta.dino.sk> Date: Thu, 23 May 2013 11:43:39 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <07C411D8-C5D3-4CD4-896B-844F6514C3DF@bsdimp.com> References: <20130516111059.38543d57@wind.dino.sk> <20130516131642.adfae355aa3bf7767e9b56e5@ddteam.net> <20130516124248.33ae4e05@wind.dino.sk> <51952112.9010607@rewt.org.uk> <20130517192206.5db0533f@zeta.dino.sk> <51966CB6.2040701@rewt.org.uk> <20130520110659.1d1d2165@zeta.dino.sk> <20130520164001.5f7d99b8@zeta.dino.sk> <20130520172508.087daf7b@zeta.dino.sk> <20130523070225.4d9a3a59@zeta.dino.sk> <519DA801.2090205@rewt.org.uk> <20130523075537.37e4bcba@zeta.dino.sk> <20130523134206.69ea6994@zeta.dino.sk> To: Milan Obuch X-Mailer: Apple Mail (2.1085) X-Gm-Message-State: ALoCoQnpkl2KUfJUThCXDDdm2ghXK1N18MQXE+3fBI2sOktHGZH5UNLoLz8cGquHQ3RzsLUv5ANc Cc: Aleksandr Rybalko , freebsd-mips@freebsd.org X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 17:43:44 -0000 On May 23, 2013, at 5:42 AM, Milan Obuch wrote: > On Wed, 22 May 2013 22:59:36 -0700, Juli Mallett = > wrote: >=20 >> On Wed, May 22, 2013 at 10:55 PM, Milan Obuch >> wrote: >>> Yes, you are right - now I checked with octe0 connected to 100 >>> megabit switch and it initializes correctly when booting. When I >>> plug gigabit card now instead, it does not work - no communication >>> on interface. Even if I do ifconfig octe down/ifconfig octe up, it >>> does not transmit/receive packets. So I think problem is phy link >>> speed change on live system. Reboot in this case is a big hackish >>> 'workaround' for now - good for tests, not yet fully for real work >>> (but if you know there will be no link speed change it is OK). >>=20 >> The link state management is crappy, I concede. I kept it as it was >> in the Linux code because I wanted to be able to merge driver updates >> from Cavium, but that's not viable given how much they've changed the >> driver anyway. How long did you wait? It could take between 5 >> seconds and a minute for link state to change at runtime in my >> experience. I looked into making this faster at one point and even >> had a patch, but don't know where it is or why I didn't commit it. >>=20 >> If either of you wants to take a crack at fixing it I can explain = what >> to instrument in the driver and what's likely to be the problem. Let >> me know if that might be useful. (Apologies of the latency is high = on >> my responding.) >>=20 >> Thanks, >> Juli. >=20 > If you have any patches to test, some how-to what to look for and try > to change etc... I could try to work a bit on it. It seems there is = not > much freely available resources for Cavium CPUs (I found cnusers.org = is > of interest, it seems) so some leading will be good to have :) cnusers is Cavium's release vehicle for GPL'd code... There's lots of = code available for the Cavium processor, but the docs are kinda hard to = get a hold of... Warner=