linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: Richard Hendricks <richard.hendricks@motorola.com>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Problem with CPM I2C driver
Date: Fri, 12 May 2000 14:31:05 -0400	[thread overview]
Message-ID: <391C4DE9.67BE72B4@netx4.com> (raw)
In-Reply-To: 391C3164.E68C4EC4@motorola.com


Richard Hendricks wrote:

> If your Ethernet is on SCC2 (which it should be), you don't need the
> patch unless you are using SPI.

Right, and further just don't use the microcode patches at all......

The patches seem to cause more problems than they fix, which
isn't necessarily the patches themselves, but a combination of
using the proper patch for the proper silicon revision and proper
driver modifications.  I don't even understand all of the permutations,
I can't get anyone from Motorola to explan all of them, and I simply
have some combinations that work and others that don't.

I dropped those functions there to make sure I don't lose them,
and I doubt they will work on anything other than one spcific
combination I was testing.

The microcode patches don't "fix" anything, since nothing is
really broken.  They simply relocate devices in the parameter RAM
memory space when something like Ethernet spills into a following
memory space.



	-- Dan

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

      reply	other threads:[~2000-05-12 18:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-12  9:01 Problem with CPM I2C driver Kim Jørgensen
2000-05-12 16:29 ` Richard Hendricks
2000-05-12 18:31   ` Dan Malek [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=391C4DE9.67BE72B4@netx4.com \
    --to=dan@netx4.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=richard.hendricks@motorola.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;
as well as URLs for NNTP newsgroup(s).