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  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]
Date:	Mon, 10 Mar 2014 16:26:53 +0100
From:	Michal Simek <michal.simek@...inx.com>
To:	Arnd Bergmann <arnd@...db.de>
CC:	<linux-arm-kernel@...ts.infradead.org>,
	Marc Kleine-Budde <mkl@...gutronix.de>, <monstr@...str.eu>,
	<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	<netdev@...r.kernel.org>, <michal.simek@...inx.com>,
	<linux-can@...r.kernel.org>, <robh+dt@...nel.org>,
	Kedareswara rao Appana <appana.durga.rao@...inx.com>,
	<grant.likely@...aro.org>,
	Kedareswara rao Appana <appanad@...inx.com>,
	<wg@...ndegger.com>, Fengguang Wu <fengguang.wu@...el.com>
Subject: Re: [PATCH v5] can: xilinx CAN controller support.

On 03/10/2014 04:15 PM, Arnd Bergmann wrote:
> On Monday 10 March 2014 16:10:31 Marc Kleine-Budde wrote:
>>>>> +config CAN_XILINXCAN
>>>>> +   tristate "Xilinx CAN"
>>>>> +   depends on ARCH_ZYNQ || MICROBLAZE
>>>>
>>>> Is Zynq multiarch already?
>>>
>>> let me just answer this. Zynq is device with hardcoded dual arm cortex-a9 + some IPs
>>> and programmable logic.
>>> It means if you add Microblaze to PL or another CPU then you get multi architecture setup.
>>
>> Sorry for the confusion, I'm not talking about
>> more-than-one-architecture-in-a-FPGA, but the feature of the ARM-Linux
>> Kernel to run on different ARM architecture. For example, it's possible
>> to start the same kernel on a freescale imx6 and a the new marvel ebu
>> platform. If the Zynq Kernel supports this feature, too, we should not
>> limit to ARCH_ZYNQ, but use ARM instead.
> 
> Zynq has been multiplatform capable from the start. Ideally we'd let
> users build the driver for any architecture and specify the exact
> dependencies, it doesn't even have to be limited to ARM.
> 
> You probably want something like
> 
> 	config CAN_XILINX
> 	tristate "Xilinx CAN"
> 	depends on ARCH_ZYNQ || MICROBLAZE || COMPILE_TEST
> 	depends on COMMON_CLK && HAS_MMIO  # whatever you need for other architectures

Fengguang: Are you use COMPILE_TEST in zero day testing system?

Thanks,
Michal


--
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