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: <46379027.7050202@gmail.com>
Date:	Tue, 01 May 2007 23:08:23 +0400
From:	Dmitry Krivoschekov <dmitry.krivoschekov@...il.com>
To:	ian <spyro@....com>
CC:	Paul Sokolovsky <pmiscml@...il.com>, kernel-discuss@...dhelds.org,
	linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.arm.linux.org.uk
Subject: Re: [Kernel-discuss] Re: [RFC, PATCH 0/4] SoC base drivers

ian wrote:
> On Tue, 2007-05-01 at 20:29 +0400, Dmitry Krivoschekov wrote:
>> If you used ASIC acronym it would be more appropriate and not so
>> ambiguous. 
>
> Actually, thats not bad. I'd be ok with that is SoC isnt used.
>
I'm ok with that too, i.e. very rough definition is:
SoC (system-on-chip) is  a platform level chip which incorporates processor
devices (CPU, cache, coprocessors, memory controller etc.), system devices
(timers, interrupt controllers etc.) and peripheral devices
(UARTs, LCD controllers, USB controllers etc),
while ASIC (Application-specific integrated circuit) is also a platform
level
chip which incorporates peripheral and system devices but does not include
processor devices.  ASICs are designed to expand processor functionality,
it could supplement a normal processor (non-SoC) and also could supplement
a SoC processor.


ASIC-related code (I mean core) forms additional platform layer, so I
suggest
adding ASIC helpers to generic platform code i.e. drivers/platform.c, but
ASIC drivers to drivers/asic/ directory.



Regards,
Dmitry
-
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