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

Hi Paul,

Paul Sokolovsky wrote:
> In contemporary systems, lots of functionality oftentimes handled by various
> kinds of SoCs (system-on-chip), representing a number of deversified
> controllers packaged in one chip. 

I think your referring to the term "SoC (system-on-chip)" is confusing
(at least for me). You rather consider companion chips than SoCs.

Yes, any chip integrating a number of controllers could be considered
as a system-on-chip but if the chip doesn't make sense without
some master chip (processor) I'd consider the chip as a companion
(to the processor) chip.

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/