linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Hans Feldt <Hans.Feldt@uab.ericsson.se>
To: linuxppc-embedded@lists.linuxppc.org
Subject: 8260 CPM commands, need better resource ctrl?
Date: Tue, 22 Oct 2002 18:10:43 +0200	[thread overview]
Message-ID: <3DB57883.4040109@uab.ericsson.se> (raw)


CPM commands are executed from different drivers, e.g. fcc_enet.c and
in different execution contexts.

Isn't there a need for a central place to handle CPM commands?

For example:

m8260_cpm_cmd(...)
	disable ints
	bounded wait until FLG is clear
	if not clear => ???
	write to CPCR
	enable ints

I have problems when testing the ATM driver and at the same time having
limited Ethernet traffic (debug printouts).  I get a "transmit timed
out" and descriptor ring dump from the eth driver. Disabling irqs in the
atm driver around CPCR handling seems to fix that problem.

Comments?

Thanks,
Hans


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

             reply	other threads:[~2002-10-22 16:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-22 16:10 Hans Feldt [this message]
2002-10-22 17:40 ` 8260 CPM commands, need better resource ctrl? Dan Malek
2002-10-23 13:06   ` Pete McCormick

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=3DB57883.4040109@uab.ericsson.se \
    --to=hans.feldt@uab.ericsson.se \
    --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).