From: "bart@ardistech.com" <bart@ardistech.com>
To: Christian Schroeder <christian.schroeder@imms.de>
Cc: linuxppc-embedded@lists.linuxppc.org, reklies@mazet.de, linz@mazet.de
Subject: Re: Microcode patching
Date: Fri, 08 Nov 2002 16:17:17 +0100 [thread overview]
Message-ID: <3DCBD57D.88FC5FA6@ardistech.com> (raw)
In-Reply-To: 1036764594.3dcbc5b26bd42@imp.imms.de
Hi Christian,
Far the easiest way is to bit-bash the IIC with software and not use
the CPM for this. As pointed out earlier in the list there is not much
gained by using the CPM for IIC if your transfer sizes are small. Not
to speak of the many bugs in the algo-8xx driver.
Regards,
Bart
> I've got a question regarding the mpc8xx microcode patches in
> arch/ppc/8xx_io/micropatch.c. We do need usb host mode, i2c and
> ethernet operation at the same time. As I understood, i can't load
> the microcode patches for usb sof generation and iic/spi together,
> because they "live" at the same address. Now my question: What occurs
> if I don't load the ii2/spi patch. I do need the usb sof timing, but
> does the i2c-Interface work without the iic/spi patch ? As I read on
> the motorola webserver, the iic/spi is needed for concurrent operation
> of scc ethernet and i2c. Does i2c work correctly without the patch if
> I don't use ethernet ?
>
> Greetings
> Christian Schroeder
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-11-08 15:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-08 14:09 Microcode patching Christian Schroeder
2002-11-08 15:17 ` bart [this message]
2002-11-08 15:56 ` Joakim Tjernlund
-- strict thread matches above, loose matches on Subject: below --
2002-11-08 16:12 Rod Boyce
2002-11-11 12:29 Kári Davíðsson
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=3DCBD57D.88FC5FA6@ardistech.com \
--to=bart@ardistech.com \
--cc=christian.schroeder@imms.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=linz@mazet.de \
--cc=reklies@mazet.de \
/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).