Hi Marc

Thanks for the advice, much appreciated!!!

Since I'm having a prototype made, I'll pass on the recommendation and see
if I can switch one of the MCP 2515's for SJA1000 and test both solutions.

I'm using Telit's GE863-PRO which only has a 200Mhz cpu so ideally I need to
conserve as many cpu cycles as possible.

Cheers
Bruce



On Fri, Apr 1, 2011 at 12:31 PM, Marc Kleine-Budde <[email protected]>wrote:

> On 03/30/2011 08:05 PM, bruce bushby wrote:
> > I'm hoping the list could offer some quick advice. I'm having a board
> > designed and have decided to use 2x MCP2515 but first wanted to hear how
> the
> > list felt about:
> >
> > 1. Support for the device in the 2.6.38 Linux kernel
> > 2. Opinions regarding having both devices on the same SPI interface?
> >
> > Any comments good or bad would be appreciated!!
>
> My advice:
> Avoid using a SPI can controller if you can. I've seen ~30% system load
> on a mx35 (~500 MHz ARM11, which has probably not the best
> SPI-controller), while the internal CAN controller of the mx35 produces
> just a load of 1-3%.
>
> There are a couple of arm controllers with two CAN cores on chip, e.g.
> MX25, MX35, MX28, which are already supported by the mainline kernel.
> There are probably other vendors that have such controllers.
>
> The other alternative would be to attach two SJA1000 to one or two chip
> selects of your CPU. If you have a PCI bus you can attach them via a PLX
> bridge.
>
> Last but not least Andre coded and I improved an optimized driver for
> the mcp2515. But I have had no time to mainline the driver, yet.
>
> cheers, Marc
>
> --
> Pengutronix e.K.                  | Marc Kleine-Budde           |
> Industrial Linux Solutions        | Phone: +49-231-2826-924     |
> Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
> Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |
>
>
_______________________________________________
Socketcan-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/socketcan-users

Reply via email to