public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Krivoschekov <dmitry.krivoschekov@gmail.com>
To: Paul Sokolovsky <pmiscml@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.arm.linux.org.uk,
	kernel-discuss@handhelds.org
Subject: Re: [RFC, PATCH 0/4] SoC base drivers
Date: Tue, 01 May 2007 17:53:09 +0400	[thread overview]
Message-ID: <46374645.2030900@gmail.com> (raw)
In-Reply-To: <1354376306.20070501080806@gmail.com>

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

  parent reply	other threads:[~2007-05-01 13:53 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 [this message]
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

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=46374645.2030900@gmail.com \
    --to=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=pmiscml@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox