| 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
| ||
|
Message-ID: <CAH5GJ0rFB4xaR7o-wVR3ze_UogeDW84dehh0rx5z+300ghB4uA@mail.gmail.com> Date: Sat, 26 May 2012 10:36:10 +0200 From: Federico Vaga <federico.vaga@...il.com> To: Wolfgang Grandegger <wg@...ndegger.com> Cc: Marc Kleine-Budde <mkl@...gutronix.de>, linux-can@...r.kernel.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, Giancarlo Asnaghi <giancarlo.asnaghi@...com>, Alan Cox <alan@...ux.intel.com> Subject: Re: [PATCH] STA2X11 CAN: CAN driver for the STA2X11 board > Thanks for your contribution. At a first glance, this driver looks > similar to the pch_can and the c_can driver. It seems that a C_CAN based > controller is used on that board as well. If that's true, it should be > handled by the C_CAN driver. To get ride of the obsolete pch_can driver, > I sent some time ago the patch "[RFC/PATCH] c_can: add driver for the > PCH CAN controller": > > http://marc.info/?t=132991563600003&r=1&w=4 > > I could serve as base of a generic c_can_pci driver. You are right, this is a C-CAN but it isn't specified on the board manual. I compared the board manual with the Bosch C-CAN manual, and it is the same. I'm working on a PCI module for this board, when it is ready we can think for a generic c_can_pci Thank you -- Federico Vaga -- 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/
Powered by blists - more mailing lists