linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: Scott Wood <oss@buserror.net>, linuxppc-dev@lists.ozlabs.org
Cc: Igal Liberman <igal.liberman@freescale.com>
Subject: Re: Status of DPAA integration for NXP QoriQ?
Date: Mon, 6 Jun 2016 13:47:15 +0200	[thread overview]
Message-ID: <575562C3.1060804@embedded-brains.de> (raw)
In-Reply-To: <1464998843.22191.44.camel@buserror.net>

On 04/06/16 02:07, Scott Wood wrote:
> On Mon, 2016-05-09 at 10:29 +0200, Sebastian Huber wrote:
>> Hello,
>>
>> the "fman" Ethernet driver was integrated in mainline Linux Dezember
>> 2015 ("drivers/net/ethernet/freescale/fman"). It seems that the other
>> parts, e.g. BMan, QMan ("drivers/soc/fsl/qbman") and basic DPAA Ethern=
et
>> support ("drivers/net/ethernet/freescale/dpaa") are still missing. Are
>> there any plans to integrate them? I didn't notice any activity on the
>> mailing list in the last couple of months in this respect.
> Yes, we are still planning to integrate the other components.

Good to hear, do you plan to add support for receive checksum offload as=20
well?

https://freescale.jiveon.com/thread/388076

--=20
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.huber@embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine gesch=C3=A4ftliche Mitteilung im Sinne des EHUG=
.

      reply	other threads:[~2016-06-06 11:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-09  8:29 Status of DPAA integration for NXP QoriQ? Sebastian Huber
2016-06-04  0:07 ` Scott Wood
2016-06-06 11:47   ` Sebastian Huber [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=575562C3.1060804@embedded-brains.de \
    --to=sebastian.huber@embedded-brains.de \
    --cc=igal.liberman@freescale.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=oss@buserror.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).