From: Joakim Tjernlund <joakim.tjernlund@transmode.se>
To: "ppc@mindchasers.com" <ppc@mindchasers.com>
Cc: "igal.liberman@freescale.com" <igal.liberman@freescale.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"Emilian.Medve@Freescale.com" <Emilian.Medve@Freescale.com>
Subject: Re: [RFC 00/10] Freescale DPAA B/QMan drivers
Date: Fri, 20 Feb 2015 14:57:19 +0000 [thread overview]
Message-ID: <1424444239.23987.39.camel@transmode.se> (raw)
In-Reply-To: <54E747F9.4000001@mindchasers.com>
On Fri, 2015-02-20 at 09:43 -0500, Bob Cochran wrote:
> On 02/05/2015 10:52 AM, Emil Medve wrote:
> > Hello Bob,
> >=20
> >=20
> > On 02/05/2015 09:48 AM, Bob Cochran wrote:
> > > On 02/04/2015 09:48 AM, Emil Medve wrote:
> > > >=20
> > > > Hello,
> > > >=20
> > > >=20
> > > > This is the first attempt to publish the Freescale DPAA B/QMan driv=
ers. They are
> > > > not to be applied yet. At this stage, this is more or less the dri=
vers from the
> > > > Freescale PowerPC SDK roughly squashed and split in a sequence of c=
omponent
> > > > patches. They still needs some work and cleanup before we expect to=
have them
> > > > applied, but we appreciate early feedback
> > >=20
> > >=20
> > > Hi Emil,
> > >=20
> > > I had thought to try to apply these patches and build it, but I won't=
get very far using it without=20
> > > FMAN (on my t1040). I searched through the mail archives and didn't=
find FMAN patches other than for=20
> > > the device tree. I also don't see it in the mainline tree.
> > >=20
> > > If FMAN patches have already been submitted, please point me to it.
> > >=20
> > > If not, then please let me know when we will see code to support FMAN=
.
> >=20
> > Let me inquire with the FMan guy here. I'll get back to you on this, ho=
wever, don't hold your breath.=20
> > There might be some weeks before the FMan driver will hit the e-mail li=
sts
>=20
>=20
> Hi Emil,
>=20
> Were you able to obtain information on when we'll see the FMAN driver pat=
ches submitted? I would like to=20
> be able to work with FSL DPAA on mainline.
>=20
> Thanks,
>=20
> Bob
Me too! I am happy just to get a normal ethernet interface though.
Jocke
prev parent reply other threads:[~2015-02-20 15:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 14:48 [RFC 00/10] Freescale DPAA B/QMan drivers Emil Medve
2015-02-04 14:48 ` [RFC 01/10] fsl_bman: Add drivers for the Freescale DPAA BMan Emil Medve
2015-02-04 14:48 ` [RFC 02/10] fsl_qman: Add drivers for the Freescale DPAA QMan Emil Medve
2015-02-04 14:48 ` [RFC 03/10] powerpc/mpc85xx: Add platform support for the Freescale DPAA BMan Emil Medve
2015-02-04 14:48 ` [RFC 04/10] powerpc/mpc85xx: Add platform support for the Freescale DPAA QMan Emil Medve
2015-02-04 14:48 ` [RFC 05/10] fsl_bman: Add self-tester Emil Medve
2015-02-04 14:48 ` [RFC 06/10] fsl_qman: " Emil Medve
2015-02-04 14:48 ` [RFC 07/10] fsl_bman: Add debugfs support Emil Medve
2015-02-04 14:48 ` [RFC 08/10] fsl_qman: " Emil Medve
2015-02-04 14:48 ` [RFC 09/10] fsl_bman: Add HOTPLUG_CPU support Emil Medve
2015-02-04 14:48 ` [RFC 10/10] fsl_qman: " Emil Medve
2015-02-04 18:40 ` [RFC 00/10] Freescale DPAA B/QMan drivers Greg KH
2015-02-04 22:16 ` Emil Medve
2015-02-05 2:29 ` Greg KH
2015-02-05 8:41 ` Dan Carpenter
2015-02-05 14:55 ` Emil Medve
2015-02-05 15:48 ` Bob Cochran
2015-02-05 15:52 ` Emil Medve
2015-02-20 14:43 ` Bob Cochran
2015-02-20 14:57 ` Joakim Tjernlund [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=1424444239.23987.39.camel@transmode.se \
--to=joakim.tjernlund@transmode.se \
--cc=Emilian.Medve@Freescale.com \
--cc=igal.liberman@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ppc@mindchasers.com \
/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).