From owner-freebsd-mips@FreeBSD.ORG Sun Sep 29 14:43:39 2013 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3A57C8EA for ; Sun, 29 Sep 2013 14:43:39 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-ee0-f48.google.com (mail-ee0-f48.google.com [74.125.83.48]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C34A129ED for ; Sun, 29 Sep 2013 14:43:38 +0000 (UTC) Received: by mail-ee0-f48.google.com with SMTP id l10so2138332eei.35 for ; Sun, 29 Sep 2013 07:43:30 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=syyp7hjJSvIdj7+2lmuQtxfOQyd1eQSJkNt9WCwBJk8=; b=drbFZaxhvHXhLQa2L8ebqeWanMIVdeK2YkkVt/8Drg5Sh3fehgjN/3LGdbEt3A/Cvj 2LcqRZRPJrnJDzcOUJ/S4NRFVG0eWOaUcG8LMf3WvdyLuv7Y8IzN4syZyw880o02CL6/ fmQZvjCZlw6bmFhnjEq7Fgt/zwAVOLizDanBLPjjFEBeNVDEj6DWmm38zN3f3QL/wfTZ H6o+cwikj32XnJJm02neqv7RvLz+Qg8rDa+pxByrnZBG4zmJH5v0qJZVBTa3HOT9h1Je oO+zXMyQckIq4XSH45HjP6nn7IlBijXTEprgLljYWhNjI/o1otI/sQKlzwF22bCHfDEL 4Eiw== X-Gm-Message-State: ALoCoQk3lY0DLo8aIJP86sgRRgvKmK14h/GLCHx3pkp4QB4bR9o/AO1frrBAPwH2TOEK7jObfsmo X-Received: by 10.15.64.1 with SMTP id n1mr29380040eex.15.1380465810696; Sun, 29 Sep 2013 07:43:30 -0700 (PDT) Received: from ?IPv6:2a02:dd0:3:100:129a:ddff:feb5:90b2? ([2a02:dd0:3:100:129a:ddff:feb5:90b2]) by mx.google.com with ESMTPSA id a6sm40081002eei.10.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 29 Sep 2013 07:43:30 -0700 (PDT) Sender: Warner Losh Subject: Re: [rfc] mips74k/ar9344 support Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: Date: Sun, 29 Sep 2013 16:43:28 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <945A50E4-685D-4CC7-88B5-89278744E389@bsdimp.com> References: To: Adrian Chadd X-Mailer: Apple Mail (2.1085) Cc: "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: Sun, 29 Sep 2013 14:43:39 -0000 I'd be tempted to use 'sll zero, 3' instead of '.word 0xc0' and define a = macro for it. Why 'sll zero,3' instead of ehb? It allows us to use it on = older MIPS platforms as well... (because it will assemble in other = modes, not for binutils issues)... Speaking of which, I'd also change the last 'nop' on the HAZARD_DELAY = and ITLBNOPFIX to be 'sll zero, 3' as well. This will be an appropriate = nop on older kit, as well as 'fail safe' when someone starts to cope = with newer compilers. Ditto COP0_SYNC. On Sep 29, 2013, at 4:37 PM, Adrian Chadd wrote: > grr, wrong list. >=20 > also, try this: >=20 > = http://people.freebsd.org/~adrian/mips/20130929-mips74k-2.diff >=20 >=20 >=20 > -adrian >=20 > ---------- Forwarded message ---------- > From: Adrian Chadd > Date: 29 September 2013 04:38 > Subject: [rfc] mips74k/ar9344 support > To: "freebsd-wireless@freebsd.org" >=20 >=20 > Hi! >=20 > Here's an initial hacked up patch to get the AR9344 to mountroot> . >=20 > (Which isn't true - it panics due to missing PHY setup on if_arge; = I'll fix > that up soon.) >=20 > http://people.freebsd.org/~adrian/mips/20130929-mips74k-1.diff >=20 > The specific changes: >=20 > * add CPU_MIPS24KC and CPU_MIPS74KC > * mips32r2 CPUs require an EHB as a hazard for things, rather than = NOPs > * mips74k cores have a different CCA (cache coherency attributes) than = the > default - I lifted this from the netbsd mips support. >=20 > now, the ar71xx CPUs are all currently marked as CPU_MIPS4KC. I'll = follow > this up with a commit to change that. There may be things we can = optimise > in the CPU_MIPS24KC case. >=20 > Warner and I have started talking about how to properly fix all of the > hazard handling. We'll discuss that later. >=20 > I'd like to commit this to -HEAD so people wishing to hack on mips74k > platforms can do stuff. Does anyone have any issues with the above? >=20 > Thanks, >=20 >=20 >=20 > -adrian > _______________________________________________ > freebsd-mips@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mips > To unsubscribe, send any mail to = "freebsd-mips-unsubscribe@freebsd.org"