All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: Rainer Kloud <rainer.kloud@siemens.at>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 8260 FCC Ethernet driver, cpm_8260.h
Date: Wed, 20 Sep 2000 12:26:32 -0400	[thread overview]
Message-ID: <39C8E538.B9F0DA84@mvista.com> (raw)
In-Reply-To: 39C8C584.D845678A@siemens.at


Rainer Kloud wrote:

> But one further question:
> After compelation of your driver I was able to send some
> data (bootp request), but I couldn't receive any.

Check to make sure you are using the same pins for clocks as
the driver has.  That is a common problem.

> So setting the desired events in the FCC mask register has
> no effect!

Well, you have to be a little careful here.  I don't have the
book handy to look up the details, but there are several places
where things are assigned 32-bit address alignments, but only
the upper 8 or 16 are valid.  In some cases, these also have
to be accessed as 16-bit operations on the 32-bit aligment.
One of the reasons is an attempt to use legacy microcode from
the 8xx, which is a 16/20/32-bit CPM architecture in a fully 32-bit
CPM of the 8260....

The code that is posted works on Rev. A parts on several platforms.
I am sure there are some mistakes, but look at it carefully....:-)

> What do you think about this?

I guess I better take a closer look.....

Thanks.


	-- Dan

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

      reply	other threads:[~2000-09-20 16:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-15  8:31 8260 FCC Ethernet driver Rainer Kloud
2000-09-15 15:43 ` Dan Malek
2000-09-15 16:12   ` Dan Malek
2000-09-20 14:11   ` 8260 FCC Ethernet driver, cpm_8260.h Rainer Kloud
2000-09-20 16:26     ` 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=39C8E538.B9F0DA84@mvista.com \
    --to=dan@mvista.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=rainer.kloud@siemens.at \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.