From: Paul Sokolovsky <pmiscml@gmail.com>
To: Dmitry Krivoschekov <dmitry.krivoschekov@gmail.com>
Cc: ian <spyro@f2s.com>,
kernel-discuss@handhelds.org, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.arm.linux.org.uk>
Subject: Re: [Kernel-discuss] Re: [RFC, PATCH 0/4] SoC base drivers
Date: Tue, 1 May 2007 20:12:44 +0300 [thread overview]
Message-ID: <10210279863.20070501201244@gmail.com> (raw)
In-Reply-To: <46376D14.9060803@gmail.com>
Hello Dmitry,
Tuesday, May 1, 2007, 7:38:44 PM, you wrote:
> ian wrote:
>> On Tue, 2007-05-01 at 17:53 +0400, Dmitry Krivoschekov wrote:
>>> Hi Paul,
>>
>>> I think your referring to the term "SoC (system-on-chip)" is confusing
>>> (at least for me). You rather consider companion chips than SoCs.
>>
>> A 'System' does not imply a CPU. A 'Computer System' would but the word
>> system itself doesnt even imply electronic.
>>
>>
> A "system" means something complete. Yes I agree it doesn't imply a CPU,
> but acronym SoC traditionally imply something different than you propose.
> Adding another meaning for SoC will confuse people because they will have
> to distinguish if it is a processor or just a slave IC.
I'm afraid we'd just have ontological argument unless tried to
bring in some references. But wikipedia does agree with you,
http://en.wikipedia.org/wiki/System-on-a-chip . So, well, down with
redefining SoC then. But "companion" is still too narrow and buzzwordy,
so let's explore Richard Purdie suggestion (in the other mail).
> Thanks,
> Dmitry
--
Best regards,
Paul mailto:pmiscml@gmail.com
prev parent reply other threads:[~2007-05-01 17:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 5:08 [RFC, PATCH 0/4] SoC base drivers Paul Sokolovsky
2007-05-01 8:39 ` Ben Dooks
2007-05-01 10:11 ` Paul Sokolovsky
2007-05-01 10:33 ` ian
2007-05-01 13:53 ` Dmitry Krivoschekov
2007-05-01 14:36 ` Paul Sokolovsky
2007-05-01 15:01 ` Richard Purdie
2007-05-01 17:18 ` Paul Sokolovsky
2007-05-01 18:58 ` Richard Purdie
2007-05-01 19:27 ` Russell King
2007-05-01 16:29 ` Dmitry Krivoschekov
2007-05-01 18:08 ` [Kernel-discuss] " ian
2007-05-01 19:08 ` Dmitry Krivoschekov
2007-05-01 20:09 ` Paul Sokolovsky
2007-05-01 21:17 ` Dmitry Krivoschekov
2007-05-02 13:39 ` Paul Sokolovsky
2007-05-01 15:55 ` ian
2007-05-01 16:38 ` Dmitry Krivoschekov
2007-05-01 17:12 ` Paul Sokolovsky [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=10210279863.20070501201244@gmail.com \
--to=pmiscml@gmail.com \
--cc=dmitry.krivoschekov@gmail.com \
--cc=kernel-discuss@handhelds.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=spyro@f2s.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.