linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wojciech Kromer <krom@dgt.com.pl>
To: linuxppc-embedded@ozlabs.org
Subject: 8250 FCC in half-duplex mode transmit timed out
Date: Wed, 19 Jan 2005 14:11:52 +0100	[thread overview]
Message-ID: <41EE5C98.4000607@dgt.com.pl> (raw)

hello again,
after few month of silence, i found this group here :)
thx for getting it back to live

i have new problem with 8250 FCC in ethernet mode,
it works fine in FDX, but after some time of heavy transmit all BD-s 
become busy

the only way to continue is to reset FCC, but ituation repeats after 
10-30 seconds

any sollution?

i've tried out CPM11,CPM112 and CPM119 microcode pathes from freescale,
no success with this stuff

by the way: does anyone know how to apply muiltiple patches at same time?

             reply	other threads:[~2005-01-19 13:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-19 13:11 Wojciech Kromer [this message]
2005-01-31  7:24 ` 8250 FCC in half-duplex mode transmit timed out Wojciech Kromer

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=41EE5C98.4000607@dgt.com.pl \
    --to=krom@dgt.com.pl \
    --cc=linuxppc-embedded@ozlabs.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).