From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0207.outbound.protection.outlook.com [207.46.163.207]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id DECD71A00D8 for ; Tue, 10 Jun 2014 23:26:30 +1000 (EST) Message-ID: <53970599.2050508@Freescale.com> Date: Tue, 10 Jun 2014 08:18:17 -0500 From: Emil Medve MIME-Version: 1.0 To: Tony Subject: Re: in dts file References: <5395CC7C.4040608@Freescale.com> In-Reply-To: Content-Type: text/plain; charset="UTF-8" Cc: linuxppc-dev@lists.ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hello Tony, On 06/09/2014 10:28 AM, Tony wrote: > Thank Emil. > > Where can i find the details about a 'diff' of qman revisions ? Let me look if someody bothered to write an AN about this > The code > i ported doesnt support latest qman revision (REV3). Ported from what (I suspect) SDK release? v1.5 should already have support for the latest xMan revision(s) > Can i still work on > qman REV1.1 for all the latest targets ? (read t-series) I'm inclined to say yes (of course the new features will not be available), but I need to have a look at the code to see with what limitations Cheers, > Regards > > > On Mon, Jun 9, 2014 at 8:32 PM, Emil Medve > wrote: > > Hello Tony, > > > On 06/09/2014 06:43 AM, Tony wrote: > > How's the fsl,qman-channel-id value different for different targets ? > > Channel ids are assigned in hardware > > > Is there any document on how this value is achieved ? > > They are described in the RM of each SoC and in the DPAA RM > > > Or can it be any value ??? > > Nope. It must be the right value or frames will end up in the wrong > portal or worse > > > Cheers, > > > > > _______________________________________________ > Linuxppc-dev mailing list > Linuxppc-dev@lists.ozlabs.org > https://lists.ozlabs.org/listinfo/linuxppc-dev