From: "bart@ardistech•com" <bart@ardistech•com>
To: Dan Malek <dan@embeddededge•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 17:19:17 +0100 [thread overview]
Message-ID: <3C67EF05.8B20B8A5@ardistech.com> (raw)
In-Reply-To: 3C67EB09.5010700@embeddededge.com
Dan Malek wrote:
>
>
> 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.
>
Most important reason for me to do the i2c with the RISC is the scalebility:
if the application needs to do a lot more i2c io as expected it won't affect
the overal performance.
Bart
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-11 16:19 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
2002-02-11 16:19 ` bart [this message]
-- 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=3C67EF05.8B20B8A5@ardistech.com \
--to=bart@ardistech$(echo .)com \
--cc=ajz@cambridgebroadband$(echo .)com \
--cc=dan@embeddededge$(echo .)com \
--cc=dmalek@jlc$(echo .)net \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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