Date: Mon, 29 May 2017 06:36:57 +0900 (JST) From: Mori Hiroki <yamori813@yahoo.co.jp> To: "freebsd-mips@freebsd.org" <freebsd-mips@freebsd.org> Subject: Hang up boot time on some BCM module Message-ID: <5350.13140.qm@web101702.mail.ssk.yahoo.co.jp>
next in thread | raw e-mail | index | archive | help
Hi.=0A=0AI make old BCM support patch. This can boot my all BCM module.=0AB= ut I have still hung up problem.=0A=0ABCM5351 is fine. But BCM4712,BCM5352,= BCM5354 is hung up.=0A=0Ahttps://gist.github.com/yamori813/04a4749d0342ae3b= bc6026b8e03cef26=0A=0A=0AI can't break at hung up.=0A=0AFirst I found this = problem is end of 2015 on ray's BCM code.=0A=0AI seem hardware and software= interrupt conflict on some module.=0A=0AI seem last output is uart tx filo= length at hung up.=0A=0AI think arm's cns11xx have same problem.=0A=0AIf y= ou have advice, please let me know.=0A=0AThanks=0A=0AHiroki Mori From owner-freebsd-mips@freebsd.org Mon May 29 09:16:18 2017 Return-Path: <owner-freebsd-mips@freebsd.org> Delivered-To: freebsd-mips@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1E602CF656C for <freebsd-mips@mailman.ysv.freebsd.org>; Mon, 29 May 2017 09:16:18 +0000 (UTC) (envelope-from mizhka@gmail.com) Received: from mail-ua0-x231.google.com (mail-ua0-x231.google.com [IPv6:2607:f8b0:400c:c08::231]) (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 BD15E7221C for <freebsd-mips@freebsd.org>; Mon, 29 May 2017 09:16:17 +0000 (UTC) (envelope-from mizhka@gmail.com) Received: by mail-ua0-x231.google.com with SMTP id y4so32780432uay.2 for <freebsd-mips@freebsd.org>; Mon, 29 May 2017 02:16:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=IzjTU6qb7hPgKvXnc57YvQxZ4GGwhrNayrmXD3bQ710=; b=kRdEf0IdMdPftn7JLK8DaXa+exCaBxsaeKSPPgvpS8pPROIB2fnqybf8jC9tAD1i5K VVz0cucxIiflGUXa38ybD3lfmHc4uLF0u9Clhq/DprN+TvjhCwlcInmKR6TybnK1S8uU 1kxmy73XUrKa20RXOkE5797jUZyOqW3ZMbhowWkLVzTb8qAIoQu7XWRaLkn/QdWfnL7i Fe1Jy8M1zr47s/nSR4jNrdtwMTBfUlV0v8rH6rdbQbgFEjsNnBzGahWATOjxwLBjE4n0 /+Oe35eHztOQgBG0CUPJIelM0n3NDWmwewoSiangwtPFtknsXsGdYwHlU/LQJ+VLcPTc ZVdw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=IzjTU6qb7hPgKvXnc57YvQxZ4GGwhrNayrmXD3bQ710=; b=sXSbsHIcjtDs1mh8peWu6A8JYBjHBfV5S8XkOzdN1LNPQ8C7C3S2FId8colho67cmK mes2rdxyT1DTZtmkuohJXyExl52r2kfBds7jVnyk+yr0kZg27q/bp9K7QAkSQpx/EjcY aLtq4uUTETcCdJf387aIQRaCEoEao+jIEI0z/daqGL8rjfpq+ti5hiKuSTDJ2aZ5oZL8 OhCjxLu2T0L/8n2xuUAiMhEXq/mOaQF/GsOiky38suNcwFwhtbi/IfpwmuV7DL1FY7BI dPi97QOrCqLpBpj26KzTVurkuuxTFnvBosmmR4MuMJDBD67X9YX/ae9I5eljJoeQL489 JNsQ== X-Gm-Message-State: AODbwcBvlCDpFawyAHWvFDVMudAEf4LRaekRWFHseuYm0jnx0/0XhOSx 0x9Jc8PGHQNWzuqhI0NVjLaO96aIRg== X-Received: by 10.176.95.97 with SMTP id z33mr5970680uah.121.1496049376781; Mon, 29 May 2017 02:16:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.166.22 with HTTP; Mon, 29 May 2017 02:16:16 -0700 (PDT) In-Reply-To: <5350.13140.qm@web101702.mail.ssk.yahoo.co.jp> References: <5350.13140.qm@web101702.mail.ssk.yahoo.co.jp> From: Michael Zhilin <mizhka@gmail.com> Date: Mon, 29 May 2017 12:16:16 +0300 Message-ID: <CAF19XBK9sGi_xLUaTmQRx8g0KVCULZfu7E8ObrOcaNg0uMpwAA@mail.gmail.com> Subject: Re: Hang up boot time on some BCM module To: Mori Hiroki <yamori813@yahoo.co.jp> Cc: "freebsd-mips@freebsd.org" <freebsd-mips@freebsd.org> Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to MIPS <freebsd-mips.freebsd.org> List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-mips>, <mailto:freebsd-mips-request@freebsd.org?subject=subscribe> X-List-Received-Date: Mon, 29 May 2017 09:16:18 -0000 Hi Hiroki-san, Actually all SoC under question are BMIPS33. It has a lot of custom Broadcom registers, I saw usage of some in bcm bootloader bytes (using r2 to disassemble). BMIPS33 requires some extra love to boot FreeBSD. I had no change to hack it, but I really what to do it ;) Thanks! On Mon, May 29, 2017 at 12:36 AM, Mori Hiroki <yamori813@yahoo.co.jp> wrote: > Hi. > > I make old BCM support patch. This can boot my all BCM module. > But I have still hung up problem. > > BCM5351 is fine. But BCM4712,BCM5352,BCM5354 is hung up. > > https://gist.github.com/yamori813/04a4749d0342ae3bbc6026b8e03cef26 > > > I can't break at hung up. > > First I found this problem is end of 2015 on ray's BCM code. > > I seem hardware and software interrupt conflict on some module. > > I seem last output is uart tx filo length at hung up. > > I think arm's cns11xx have same problem. > > If you have advice, please let me know. > > Thanks > > Hiroki Mori > _______________________________________________ > freebsd-mips@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-mips > To unsubscribe, send any mail to "freebsd-mips-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5350.13140.qm>