From owner-freebsd-ppc@FreeBSD.ORG Wed Oct 3 20:14:18 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5176C1065674 for ; Wed, 3 Oct 2012 20:14:18 +0000 (UTC) (envelope-from aleksey.v.fedorov@gmail.com) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 00C4D8FC0A for ; Wed, 3 Oct 2012 20:14:17 +0000 (UTC) Received: by qcsl39 with SMTP id l39so7692434qcs.13 for ; Wed, 03 Oct 2012 13:14:17 -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:content-transfer-encoding; bh=aCIdqO+L2PQRbCPhjfZkDGDXFm6QNe2BcQDlpFgVph8=; b=nXvxNHRrP9YDa7vgPJ4Vhk456niF1CjI0+CJ0qEtZ3NN1JhcxIjLHrcjNqsYYIwtfo GdkPe3dhocqXDCK6LtjeCkbcr2TMgzHAz6FlIBipmnbZsVvc9ZyuqQ5BwRYred3mndw0 x2GjxA7vkYA1weJefHgqXG8/Qhzq59gBsB/eoBc/NlqDFSMRk4K00hBkOrs2pr0bvEve xRVl1eGnsnEIHMhufjmbAmZg7BlvyVVjVSmDF7GMP1KOwugO3KzhpGWozY1i5KvgKVWn z52ncutLEzq/QruCumJmcnrUjMY2YQKuYDjCxhOZtAnLSvbhAvVG3v2cYKMPdC0uY/9b o7NQ== MIME-Version: 1.0 Received: by 10.224.179.7 with SMTP id bo7mr9085394qab.96.1349295257254; Wed, 03 Oct 2012 13:14:17 -0700 (PDT) Received: by 10.49.27.105 with HTTP; Wed, 3 Oct 2012 13:14:16 -0700 (PDT) In-Reply-To: <764EEFAD-1730-466E-85C5-791A3A72BAD4@semihalf.com> References: <39077F2D-B518-4EE4-ACE0-E8EB804E245B@semihalf.com> <764EEFAD-1730-466E-85C5-791A3A72BAD4@semihalf.com> Date: Thu, 4 Oct 2012 00:14:16 +0400 Message-ID: From: Aleksey Fedorov To: Rafal Jaworowski Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-ppc@freebsd.org Subject: Re: FreeBSD on e500mc 36bit physical addressing X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Oct 2012 20:14:18 -0000 Hi! 2012/9/27 Rafal Jaworowski : > We are supposed to be compatible with ePAPR spec of the device tree (so i= s Linux), so no special handling is needed. > > Regarding the error it might be caused by the recent import of changes fo= r ARM which affected FDT infrastructure code (http://svn.freebsd.org/change= set/base/239268). We had a side conversation with Marcel regarding DSI pani= c during localbus node processing, which seems similar to what you're seein= g. Can you try some older code base (prior to r239268) to see if it shows t= he same/related problem? > > Rafal > This changes in fdt_common.c help me to deal with "interrupt-parent": - if (OF_getprop(node, "interrupt-parent", &iph, sizeof(iph)) <=3D 0)= { + if (OF_searchprop(node, "interrupt-parent", &iph, sizeof(iph)) <=3D= 0) { Next waypoint is to bring up SMP APs. Now I have: Adding CPU 0, pir=3D0, awake=3D1 Waking up CPU 1 (dev=3D1) SMP: CPU 0 didn't wake up (trace code 0). Waking up CPU 2 (dev=3D2) SMP: CPU 0 didn't wake up (trace code 0). Waking up CPU 3 (dev=3D3) SMP: CPU 0 didn't wake up (trace code 0). Waking up CPU 4 (dev=3D4) SMP: CPU 0 didn't wake up (trace code 0). Waking up CPU 5 (dev=3D5) SMP: CPU 0 didn't wake up (trace code 0). Waking up CPU 6 (dev=3D6) SMP: CPU 0 didn't wake up (trace code 0). Waking up CPU 7 (dev=3D7) SMP: CPU 0 didn't wake up (trace code 0). SMP: 8 CPUs found; 8 CPUs usable; 1 CPUs woken What is the right way to bring up cores in FreeBSD? Using ePAPR spinlocks or custom reset?