Date: Mon, 21 Mar 2011 12:57:12 -0700 From: Juli Mallett <jmallett@FreeBSD.org> To: Andrew Duane <aduane@juniper.net> Cc: "freebsd-mips@freebsd.org" <freebsd-mips@freebsd.org> Subject: Re: phy_mem_desc_addr initialization Message-ID: <AANLkTikK0kJ5cEbTWs4riwrwQLvz-a4joGPhbbO=Danh@mail.gmail.com> In-Reply-To: <AC6674AB7BC78549BB231821ABF7A9AEA06419B0B8@EMBX01-WF.jnpr.net> References: <AC6674AB7BC78549BB231821ABF7A9AEA06419B0B8@EMBX01-WF.jnpr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 21, 2011 at 12:41, Andrew Duane <aduane@juniper.net> wrote: > I'm making good progress on my port to the first Juniper Octeon blade, bu= t I am stuck with what the real format of the memory descriptor blocks poin= ted to by phy_mem_desc_addr is. I can synthesize enough to get by, but I ev= entually fall over because all of the info is not there. > > Can anyone perhaps print me out one from their Octeon board (an EBT-3000 = would be ideal if at all possible), or point me to some actual documentatio= n on the fields? The code in sys/contrib/octeon-sdk is fairly straightforward. Really, though, probably what you should do is #ifdef octeon_memory_init for whatever config option is driving your non-standard Octeon platform. I think we talked about this previously, but it's possible there's some other use that you're running into trouble with. I'd be glad to help if you give me a pointer to the problematic usage. Thanks, Juli.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTikK0kJ5cEbTWs4riwrwQLvz-a4joGPhbbO=Danh>