From: Dan Malek <dan@netx4.com>
To: Graham Stoney <greyham@research.canon.com.au>
Cc: LinuxPPC Embedded Mailing List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: CLLF860T FEC problem in linux-2.4.0-test4-pre6
Date: Thu, 13 Jul 2000 12:02:22 -0400 [thread overview]
Message-ID: <396DE80E.81BFABD1@embeddededge.com> (raw)
In-Reply-To: 20000713085536.368DE289@elph.research.canon.com.au
Graham Stoney wrote:
> Has anyone got any clues on this before I dive into it tomorrow?
A while back I posted a message stating I made lots of changes to this
driver based upon patches people have sent (including some of yours).
I also stated this is quite broken and I have not yet completed all
of the changes. I am surprised it works at all.
I am now working on both the 8260 FCC (I have patches but will check
them in today), and the 8xx FEC as they are somewhat similar.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-13 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-13 8:55 CLLF860T FEC problem in linux-2.4.0-test4-pre6 Graham Stoney
2000-07-13 16:02 ` Dan Malek [this message]
2000-07-14 2:46 ` Graham Stoney
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=396DE80E.81BFABD1@embeddededge.com \
--to=dan@netx4.com \
--cc=greyham@research.canon.com.au \
--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).