linux-kernel - Re: [PATCH v4 1/1] can: add pruss CAN driver.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <F1859F4DD03040248B42AC947304D39B@subhasishg>
Date:	Tue, 10 May 2011 15:41:49 +0530
From:	"Subhasish Ghosh" <subhasish@...tralsolutions.com>
To:	"Wolfgang Grandegger" <wg@...ndegger.com>,
	"Arnd Bergmann" <arnd@...db.de>
Cc:	<linux-arm-kernel@...ts.infradead.org>,
	"Marc Kleine-Budde" <mkl@...gutronix.de>,
	<sachi@...tralsolutions.com>,
	<davinci-linux-open-source@...ux.davincidsp.com>,
	<Netdev@...r.kernel.org>, <nsekhar@...com>,
	"open list" <linux-kernel@...r.kernel.org>,
	"CAN NETWORK DRIVERS" <socketcan-core@...ts.berlios.de>,
	<m-watkins@...com>
Subject: Re: [PATCH v4 1/1] can: add pruss CAN driver.

>> 
>> It sounds to me like the best solution would be change the firmware
>> to lift that restriction and simply allow all IDs, in case it's not
>> actually a hardware limitation (which sounds unlikely).
> 
> Yes, that would be best but they told us, that it's not possible with
> the available hardware resources. Subhasish?

Yes, In case if we allow the ALL implementation, it hogs the CPU.
In that case we do not need the PRU. The whole purpose of the PRU
is to offload the processor for any such implementations. 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/