From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: linuxppc-dev@lists.ozlabs.org
Cc: Igal Liberman <igal.liberman@freescale.com>
Subject: Status of DPAA integration for NXP QoriQ?
Date: Mon, 9 May 2016 10:29:24 +0200 [thread overview]
Message-ID: <57304A64.1020607@embedded-brains.de> (raw)
Hello,
the "fman" Ethernet driver was integrated in mainline Linux Dezember=20
2015 ("drivers/net/ethernet/freescale/fman"). It seems that the other=20
parts, e.g. BMan, QMan ("drivers/soc/fsl/qbman") and basic DPAA Ethernet=20
support ("drivers/net/ethernet/freescale/dpaa") are still missing. Are=20
there any plans to integrate them? I didn't notice any activity on the=20
mailing list in the last couple of months in this respect.
--=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=
.
next reply other threads:[~2016-05-09 8:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 8:29 Sebastian Huber [this message]
2016-06-04 0:07 ` Status of DPAA integration for NXP QoriQ? Scott Wood
2016-06-06 11:47 ` Sebastian Huber
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=57304A64.1020607@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=igal.liberman@freescale.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 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).