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]
Date:	Tue, 5 Mar 2013 21:59:36 +0000
From:	Arnd Bergmann <arnd@...db.de>
To:	Ley Foon Tan <lftan@...era.com>
Cc:	"Greg Kroah-Hartman" <gregkh@...uxfoundation.org>,
	Rob Landley <rob@...dley.net>, linux-kernel@...r.kernel.org,
	linux-doc@...r.kernel.org
Subject: Re: [PATCH 1/1] drivers/misc: Add Altera System ID driver

On Tuesday 05 March 2013, Ley Foon Tan wrote:
> The sysid give the unique system ID and system generation timestamp of
> the system.
> 
> CASE 1:
> SOCFPGA SoC + Sysid component in FPGA
> 
> CASE 2
> Nios II soft core CPU + Sysid  (All in FPGA and no SoC is involved)
> 
> From example use cases above, Case 2 doesn't involve SoC component. 
> To support both cases, do you think drivers/base/soc.c is still
> suitable?

Yes, I think so. I would consider the second case still a SoC, because
you have a single chip that contains the CPU and peripherals. From
the OS point of view, it does not matter that they are in an FPGA.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ