linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Robin Holt <holt@sgi.com>
To: Robin Holt <holt@sgi.com>, Marc Kleine-Budde <mkl@pengutronix.de>,
	Wolfgang Grandegger <wg@grandegger.com>,
	U Bhaskar-B22300 <B22300@freescale.com>
Cc: socketcan-core@lists.berlios.de, netdev@vger.kernel.org,
	PPC list <linuxppc-dev@lists.ozlabs.org>,
	Robin Holt <holt@sgi.com>
Subject: [PATCH v10 0/5] [flexcan/powerpc] Add support for powerpc flexcan (freescale p1010)
Date: Tue,  9 Aug 2011 22:05:59 -0500	[thread overview]
Message-ID: <1312945564-6626-1-git-send-email-holt@sgi.com> (raw)


With all the patches applied, my p1010rdb works for communicating between
its two can ports and also can communicate with an external PSOC.  I have
done no testing beyond compile testing on an arm system as I have no
access to an arm based system.

For the first three patches in the series, I believe they are all ready
for forwarding to David S. Miller for the netdev tree.  I think patch
4 is ready for submission to the PPC85xx maintainer.  Patch 5 changed
from the previous post by adding a second compatible string for the
fsl,p1010_flexcan.

Thanks,
Robin Holt

             reply	other threads:[~2011-08-10  3:06 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10  3:05 Robin Holt [this message]
2011-08-10  3:06 ` [PATCH v10 1/5] [flexcan] Remove #include <mach/clock.h> Robin Holt
2011-08-10  3:06 ` [PATCH v10 2/5] [flexcan] Abstract off read/write for big/little endian Robin Holt
2011-08-10  3:06 ` [PATCH v10 3/5] [flexcan] Add of_match to platform_device definition Robin Holt
2011-08-10 14:33   ` Robin Holt
2011-08-10  3:06 ` [PATCH v10 4/5] [powerpc] Add flexcan device support for p1010rdb Robin Holt
2011-08-10  9:56   ` Marc Kleine-Budde
2011-08-10 10:15     ` Robin Holt
2011-08-10  3:06 ` [PATCH v10 5/5] [powerpc] Fix up fsl-flexcan device tree binding Robin Holt
2011-08-10  8:15   ` Robert Schwebel
2011-08-10 10:09   ` Robin Holt
2011-08-10 13:47   ` Wolfgang Grandegger
2011-08-10 14:15     ` Robin Holt
2011-08-10 14:36       ` U Bhaskar-B22300
2011-08-10 16:00         ` Robin Holt
2011-08-10 16:53           ` Kumar Gala
2011-08-10 17:16             ` Robin Holt
2011-08-10 17:17               ` Kumar Gala
2011-08-10 17:20                 ` Robin Holt
2011-08-10 17:26                   ` Kumar Gala
2011-08-10 18:23           ` Wolfgang Grandegger
2011-08-10 18:27             ` Scott Wood
2011-08-10 18:35               ` Robin Holt
2011-08-10 18:39                 ` Scott Wood
2011-08-10 14:41       ` Wolfgang Grandegger
2011-08-10 14:46         ` Kumar Gala
2011-08-10 14:45       ` Kumar Gala
2011-08-10 15:35         ` Robin Holt
2011-08-10 10:01 ` [PATCH v10 0/5] [flexcan/powerpc] Add support for powerpc flexcan (freescale p1010) Marc Kleine-Budde
2011-08-10 10:11   ` Robin Holt
2011-08-10 10:24     ` Marc Kleine-Budde
2011-08-10 11:09 ` Marc Kleine-Budde

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=1312945564-6626-1-git-send-email-holt@sgi.com \
    --to=holt@sgi.com \
    --cc=B22300@freescale.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=socketcan-core@lists.berlios.de \
    --cc=wg@grandegger.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).