linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: bart@ardistech.com
Cc: Alex Zeffertt <ajz@cambridgebroadband.com>,
	Embedded Linux PPC List <linuxppc-embedded@lists.linuxppc.org>,
	dmalek@jlc.net
Subject: Re: MPC823: i2c-algo-8xx read interrupt?
Date: Mon, 11 Feb 2002 11:02:17 -0500	[thread overview]
Message-ID: <3C67EB09.5010700@embeddededge.com> (raw)
In-Reply-To: 3C67E711.2108C6DD@ardistech.com


bart@ardistech.com wrote:


> You're right, but spending XX$ on a fast PPC chip and after that let it run
> busy loops to time the I2C control makes me feel bad :)

So, you think interrupt and management overhead of the software to send a
couple of bytes on a 100k serial interface is free?  The chip designers are
often upset when you don't use every feature, but you need to apply some
real systems engineering methods and analyze how all of these little things
help (or hurt) your application.


	-- Dan


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-02-11 16:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-08 15:18 MPC823: i2c-algo-8xx read interrupt? bart
2002-02-08 17:04 ` Dan Malek
     [not found]   ` <3C640C11.4080407@cambridgebroadband.com>
     [not found]     ` <3C6410F1.4000104@embeddededge.com>
2002-02-11 12:13       ` bart
     [not found]     ` <3C6776CC.634AB65D@ardistech.com>
2002-02-11 15:30       ` Dan Malek
2002-02-11 15:45         ` bart
2002-02-11 16:02           ` Dan Malek [this message]
2002-02-11 16:19             ` bart
  -- strict thread matches above, loose matches on Subject: below --
2002-02-11 15:49 Pergola, Michael

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=3C67EB09.5010700@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=ajz@cambridgebroadband.com \
    --cc=bart@ardistech.com \
    --cc=dmalek@jlc.net \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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;
as well as URLs for NNTP newsgroup(s).