linux-kernel - Re: [Kernel-discuss] Re: [RFC, PATCH 0/4] SoC base drivers

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: <281618366.20070501230902@gmail.com>
Date:	Tue, 1 May 2007 23:09:02 +0300
From:	Paul Sokolovsky <pmiscml@...il.com>
To:	Dmitry Krivoschekov <dmitry.krivoschekov@...il.com>
CC:	ian <spyro@....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

Hello Dmitry,

Tuesday, May 1, 2007, 10:08:23 PM, you wrote:

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

        There problem here is the same - our target chips are not
just ASICs. It just happens that the one we start with called such,
but we have different ones too. It's still important that they contain
blocks with different functionality, and drivers we propose deal with
basic, common functionality of chips. Now that it was pointed out that
there's place in the tree for such drivers, it would be not wise to
try to create another one.



> Regards,
> Dmitry


-- 
Best regards,
 Paul                            mailto:pmiscml@...il.com

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