All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emil Medve <Emilian.Medve@Freescale.com>
To: Tony <blacklites@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: <fsl,qman-channel-id> in dts file
Date: Tue, 10 Jun 2014 08:18:17 -0500	[thread overview]
Message-ID: <53970599.2050508@Freescale.com> (raw)
In-Reply-To: <CAE1uq6uSEd+NZW+Q+9V8QqxcEDaiQQmcQTJ1GCrgQGL7N98t_g@mail.gmail.com>

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 <Emilian.Medve@freescale.com
> <mailto:Emilian.Medve@freescale.com>> 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

      reply	other threads:[~2014-06-10 13:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09 11:43 <fsl,qman-channel-id> in dts file Tony
2014-06-09 15:02 ` Emil Medve
2014-06-09 15:28   ` Tony
2014-06-10 13:18     ` Emil Medve [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53970599.2050508@Freescale.com \
    --to=emilian.medve@freescale.com \
    --cc=blacklites@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.