From owner-freebsd-mips@FreeBSD.ORG Wed May 2 19:26:57 2007 Return-Path: X-Original-To: freebsd-mips@FreeBSD.org Delivered-To: freebsd-mips@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 38CF716A403 for ; Wed, 2 May 2007 19:26:57 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 143A413C48A for ; Wed, 2 May 2007 19:26:57 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 593F821DC7A for ; Wed, 2 May 2007 15:26:55 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Wed, 02 May 2007 15:26:57 -0400 X-Sasl-enc: XcHVK/G3xa0gqRfD06DbJf1KW1W12wCAhZkgsBV23KT1 1178134016 Received: from [192.168.124.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 734F31D37B for ; Wed, 2 May 2007 15:26:56 -0400 (EDT) Message-ID: <4638E5FE.3060901@incunabulum.net> Date: Wed, 02 May 2007 20:26:54 +0100 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: freebsd-mips@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Broadcom 4710a0 X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 May 2007 19:26:57 -0000 Hi, I've been investigating what, if anything, needs to be done with the FreeBSD/mips system compiler to support the earlier Broadcom 4710A0 chips found in the Linksys WRT54G and Asus WL-HDD2.5 systems. It looks as though the patches Broadcom integrated into their gcc fork only prevent the generation of branch-likely instructions. In our import of GCC 3.4.6, the -mno-branch-likely option now exists, therefore I believe no patch is required. For system bringup it looks like some TLB and cache workarounds are necessary (based on reading Linux). A patch against Linux appears here: http://www.freewrt.org/trac/browser/trunk/freewrt/target/linux/brcm-2.6/patches/003-bcm4710_cache_fixes.patch?rev=1&format=txt Regards, BMS