netdev - Re: [PATCH net-next-2.6 v2 1/1] can: c_can: Added support for Bosch C

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: <070E08D3134344CBB04FC2F201E778B7@hacdom.okisemi.com>
Date:	Thu, 16 Dec 2010 21:09:52 +0900
From:	"Tomoya MORINAGA" <tomoya-linux@....okisemi.com>
To:	"Bhupesh Sharma" <bhupesh.sharma@...com>,
	"Wolfgang Grandegger" <wg@...ndegger.com>
Cc:	<Socketcan-core@...ts.berlios.de>, <netdev@...r.kernel.org>
Subject: Re: [PATCH net-next-2.6 v2 1/1] can: c_can: Added support for Bosch C_CAN	controller

On Thursday, December 16, 2010 6:11 PM, Wolfgang Grandegger wrote:

> Ah, oh, I just realized that the register layout is almost identical to
> the recently accepted *pch_can* driver. Tomoya, does pch_can use a c_can
> core? Well, then it makes really sense to have a generic c_can driver
> for the SPEAR, PCH, etc. Board specific details are handled via platform
> definition. This driver already provides that functionality, IFAICS.

Hi Wolfgang,

It seems pch_can similar to c_can.
However, sorry, I don't know if pch_can core is the same as c_can since LSI 
is provided by Intel.
If necessary, please contact to Intel.

Thanks,
---
Tomoya MORINAGA
OKI SEMICONDUCTOR CO., LTD.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html