Re: MPC5200B and the CAN interface

2008-11-08 Thread Robert Schwebel
On Sat, Nov 08, 2008 at 05:32:35AM -0700, Gary Thomas wrote:
> I'm pretty sure this is just the SocketCAN interface.
> 
> You still need a hardware driver (and one which is SocketCAN compatible).
> I don't see such a driver for the MSCAN (the hardware on the MPC5200) in
> the stock 2.6.27 tree.

The drivers for MPC5200B's mscan are still in the SocketCAN repository,
right. The team is working on getting the patches ready for mainline.

rsc
-- 
 Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
   Handelsregister:  Amtsgericht Hildesheim, HRA 2686
 Hannoversche Str. 2, 31134 Hildesheim, Germany
   Phone: +49-5121-206917-0 |  Fax: +49-5121-206917-9

___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


Re: MPC5200B and the CAN interface

2008-11-08 Thread Gary Thomas
Nick wrote:
> Hi Everyone,
> 
> I am looking for information on how to use the CAN driver for the MPC5200b.  
> I have built the kernel (2.6.27) with the MPC5200b can bus drivers and I see 
> them being initialized on start up.
> 
> [   37.122041] can: controller area network core (rev 20071116 abi 8)
> [   37.128687] NET: Registered protocol family 29
> [   37.133379] can: raw protocol (rev 20071116)
> [   37.137807] can: broadcast manager protocol (rev 20080415)

I'm pretty sure this is just the SocketCAN interface.

You still need a hardware driver (and one which is SocketCAN compatible).
I don't see such a driver for the MSCAN (the hardware on the MPC5200) in
the stock 2.6.27 tree.

-- 

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


MPC5200B and the CAN interface

2008-11-07 Thread Nick
Hi Everyone,

I am looking for information on how to use the CAN driver for the MPC5200b.  I 
have built the kernel (2.6.27) with the MPC5200b can bus drivers and I see them 
being initialized on start up.

[   37.122041] can: controller area network core (rev 20071116 abi 8)
[   37.128687] NET: Registered protocol family 29
[   37.133379] can: raw protocol (rev 20071116)
[   37.137807] can: broadcast manager protocol (rev 20080415)

Do I have to define a UDEV rule?  Has anyone already written a rule to make the 
can driver visible in /dev?

Any pointers or snippets of code would be greatly appreciated.

Nick
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev