From owner-freebsd-ppc@FreeBSD.ORG Tue Jul 30 17:57:48 2013 Return-Path: Delivered-To: freebsd-ppc@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 4EC9BC96 for ; Tue, 30 Jul 2013 17:57:48 +0000 (UTC) (envelope-from jeclark2006@aim.com) Received: from omr-m10.mx.aol.com (omr-m10.mx.aol.com [64.12.143.86]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 023432240 for ; Tue, 30 Jul 2013 17:57:47 +0000 (UTC) Received: from mtaout-db03.r1000.mx.aol.com (mtaout-db03.r1000.mx.aol.com [172.29.51.195]) by omr-m10.mx.aol.com (Outbound Mail Relay) with ESMTP id 879F0700EC714; Tue, 30 Jul 2013 13:51:53 -0400 (EDT) Received: from [10.0.0.233] (wsip-68-105-252-106.sd.sd.cox.net [68.105.252.106]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mtaout-db03.r1000.mx.aol.com (MUA/Third Party Client Interface) with ESMTPSA id BBA98E0000A7; Tue, 30 Jul 2013 13:51:52 -0400 (EDT) Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: P1020wlan REV D DTS file? From: John Clark In-Reply-To: Date: Tue, 30 Jul 2013 10:51:51 -0700 Message-Id: References: <0E4E55FF-5FDC-40D5-844E-F93CB0969513@aim.com> To: Aleksander X-Mailer: Apple Mail (2.1508) x-aol-global-disposition: G DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20121107; t=1375206713; bh=GqibiAJnTV/kI3Rhbd9SE15cRKc2x1VosOeC6RlE16M=; h=From:To:Subject:Message-Id:Date:Mime-Version:Content-Type; b=CH5O81J54sYfA3g5CLpjJMG3+6JBvunnEGeARmOuXWJ493tz32WeWZQDNj6/Pkids FQXVYHs49vO/HuE59HGdkfkANmNb5HloezucFRfW8/Em/4Z33cehkqAH+vWFJpR7/M 8XEhKrHAbDqqhtZrxOSGXhNrMjSZiHzyq5xAFYUE= X-AOL-SCOLL-SCORE: 0:2:429859104:93952408 X-AOL-SCOLL-URL_COUNT: 0 x-aol-sid: 3039ac1d33c351f7fd385b1d X-AOL-IP: 68.105.252.106 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-ppc@FreeBSD.org" X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jul 2013 17:57:48 -0000 Thanks for the patch. Since my board is the WLAN board, there are some = differences, but you fixes confirm that I'm somewhat on the right track. With my patched up WLAN DTS file, I get to the point of probing the TSEC = devices. My board has etsec2 'network' devices, and 'simplistically' = replacing etsec2 with 'gianfar' doesn't seem to work. By replacing the 'etsec2' compatible descriptor, the probe process goes = on to attempt find out how much memory to allocate for accessing the = device, but I think there's a 'reg' declaration that is missing. The question I have is, are you using the network interface 'tsec' or = have you modified the DTS in that regard? The 'tsec' driver I have does = not seem to detect the etsec2 type network device. Thanks, John Clark. On Jul 30, 2013, at 2:41 AM, Aleksander wrote: > That reminds me, I need to send the patch, because I had the same = problem. > In the meantime, here is the patch for p1020rdb.dts. This works for = me. >=20 > diff --git a/sys/boot/fdt/dts/p1020rdb.dts = b/sys/boot/fdt/dts/p1020rdb.dts > index ec5118c..c95ab27 100644 > --- a/sys/boot/fdt/dts/p1020rdb.dts > +++ b/sys/boot/fdt/dts/p1020rdb.dts > @@ -59,17 +59,20 @@ > device_type =3D "cpu"; > reg =3D <0x0>; > next-level-cache =3D <&L2>; > + bus-frequency =3D <400000000>; // = Filled out by uboot. > }; > =20 > PowerPC,P1020@1 { > device_type =3D "cpu"; > reg =3D <0x1>; > next-level-cache =3D <&L2>; > + bus-frequency =3D <400000000>; // = Filled out by uboot. > }; > }; > =20 > memory { > device_type =3D "memory"; > + reg =3D < 0x0 0x0 0x0 0x20000000 >; > }; > =20 > localbus@ffe05000 { > @@ -193,7 +196,7 @@ > #address-cells =3D <1>; > #size-cells =3D <1>; > device_type =3D "soc"; > - compatible =3D "fsl,p1020-immr", "simple-bus"; > + compatible =3D "simple-bus"; > ranges =3D <0x0 0x0 0xffe00000 0x100000>; > bus-frequency =3D <0>; // Filled out by = uboot. > =20 > @@ -624,4 +627,9 @@ > 0x0 0x100000>; > }; > }; > + > + chosen { > + stdin =3D "serial0"; > + stdout=3D "serial0"; > + }; > }; >=20 > regards > aleek >=20 >=20 > On Mon, Jul 29, 2013 at 9:53 PM, John Clark = wrote: > I've been working intermittently on a p1020wlan board and getting = FreeBSD up and running on it. >=20 > I have a working Linux setup, but wanted to look at FreeBSD. >=20 > The process has been fraught with problems. >=20 > 1) U-Boot. The board has u-boot and despite the 'suggestive' tool = titled 'ubldr', this does not seem to work, unless the u-boot has been = 'enabled' with the U-boot API. > Did that but other than some number of diagnostics, the ubldr fails = to present a command interface or seemingly try to 'bootp' via the = network interface. >=20 > 2) Using a DTS file that 'works' with Linux, there are a number of = 'holes' in the DTS structure which the boot firmware seems to be = expected to 'fill in the blanks'. > I've plugged many holes, an rearranged elements in the 'tree' that = seem to allow for the kernel to be loaded, and get to the point of = attempting to initialize the network drivers to > perform a 'bootp' NFS style root mount. >=20 > I did get some assistance in April from someone working on a similar = board, but those 'hints' have not yielded a bootable setup. >=20 > It would appear that this board, and perhaps most of the P1020 (and = other recent Freescale boards) do not have many people, if any, working = on getting FreeBSD up on them. >=20 > The questions are=85 >=20 > 1) is there anyone with a working P1020Wlan setup? > 2) Anyone with working P1020xxx boards, and using the 'as found in = sys/boot/fdt/dts' DTS files? >=20 >=20 > Any help would be appreciated, >=20 > John Clark. >=20 > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" >=20 >=20 >=20 > --=20 > regards > aleek