Date: Thu, 12 May 2011 00:35:50 +0200 From: Damjan Marion <damjan.marion@gmail.com> To: freebsd-arm@freebsd.org Subject: Re: Few issues with Marvell code Message-ID: <2A67CDC2-37BA-4ABE-9E7E-8C151E7E9887@gmail.com> In-Reply-To: <B823839E-A0B2-4994-BDD8-6AC8747DCCEC@gmail.com> References: <B823839E-A0B2-4994-BDD8-6AC8747DCCEC@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 3, 2011, at 10:42 PM, Damjan Marion wrote:
>=20
> Hi,
>=20
> During my attempt to bring up 88F5181L I found few issues with current =
marvell code:
>=20
> 1. There is a typo in sys/arm/mv/common.c
>=20
> - { "mvrl,pcie", &decode_win_pcie_setup, NULL },
> + { "mrvl,pcie", &decode_win_pcie_setup, NULL },
>=20
>=20
> 2. Even if this is fixed, decode_win_pcie_setup will not be executed =
as in FDT file pci tree sits outside of SOC tree
>=20
>=20
> 3. CPU decode windows setup in FDT localbus tree is missing target, =
instead target is hardcoded to 1:
>=20
> cpu_win_tbl[t].target =3D 1;=20
>=20
> On other side 1st column looks like a sequence. Is this 1st column =
needed?=20
> Can we extend this definition to also have target defined?
>=20
> I.e. In case of 88F5181L I need to add following window, and it will =
be more convenient to do that in FDT file.
>=20
> cpu_win_tbl[++t].target =3D 0x04;
> cpu_win_tbl[t].attr =3D 0x79;
> cpu_win_tbl[t].base =3D 0xf0000000;
> cpu_win_tbl[t].size =3D 0x01000000;
> cpu_win_tbl[t].remap =3D -1;
>=20
I will appreciate if somebody can comment this :)
Thanks,
Damjan=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2A67CDC2-37BA-4ABE-9E7E-8C151E7E9887>