Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Jul 2013 10:51:51 -0700
From:      John Clark <jeclark2006@aim.com>
To:        Aleksander <aleek@FreeBSD.org>
Cc:        "freebsd-ppc@FreeBSD.org" <freebsd-ppc@freebsd.org>
Subject:   Re: P1020wlan REV D DTS file?
Message-ID:  <DCCC8C11-54DA-44E9-8D55-C4266C2EEF38@aim.com>
In-Reply-To: <CABkKHSaiDb_J%2B=ZHv7HMpB=Tfzp9oBYAi9%2BE4RNChVA=Tswz%2BQ@mail.gmail.com>
References:  <0E4E55FF-5FDC-40D5-844E-F93CB0969513@aim.com> <CABkKHSaiDb_J%2B=ZHv7HMpB=Tfzp9oBYAi9%2BE4RNChVA=Tswz%2BQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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 <aleek@FreeBSD.org> 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 <jeclark2006@aim.com> =
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DCCC8C11-54DA-44E9-8D55-C4266C2EEF38>