[PATCH v2 09/13] can: pruss CAN driver.

[Subhasish Ghosh]

Hello,

The problem with the "all" implementation is that it hogs the ARM/DSP 
heavily and that's the reason why we specifically avoided this in our 
firmware design.
Hence, implementing this condition spoils the whole purpose of the PRU!!

--------------------------------------------------
From: "Marc Kleine-Budde" <mkl at pengutronix.de>
Sent: Monday, February 14, 2011 3:05 PM
To: "Subhasish Ghosh" <subhasish at mistralsolutions.com>
Cc: "Wolfgang Grandegger" <wg at grandegger.com>; "Kurt Van Dijck" 
<kurt.van.dijck at eia.be>; <davinci-linux-open-source at linux.davincidsp.com>; 
<linux-arm-kernel at lists.infradead.org>; <m-watkins at ti.com>; 
<nsekhar at ti.com>; <sachi at mistralsolutions.com>; "open list:CAN NETWORK 
DRIVERS" <socketcan-core at lists.berlios.de>; "open list:CAN NETWORK DRIVERS" 
<netdev at vger.kernel.org>; "open list" <linux-kernel at vger.kernel.org>
Subject: Re: [PATCH v2 09/13] can: pruss CAN driver.

Hello,

On 02/14/2011 09:45 AM, Subhasish Ghosh wrote:
> That is correct, we receive only pre-programmed CAN ids and "all" or
> "range" implementation is not there in the PRU firmware.

I'd really like to see that you add a "all" implementation to the
firmware. Or even better use the standard id/mask approach.

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   |