linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Restructuring of ibm_ocp_enet driver
Date: Wed, 21 Aug 2002 17:19:11 +1000	[thread overview]
Message-ID: <20020821071911.GL18818@zax> (raw)
In-Reply-To: <5.1.0.14.2.20020820231900.03a9e008@pop.prodigy.net>


On Tue, Aug 20, 2002 at 11:26:03PM -0700, Eugene Surovegin wrote:
>
> David,
>
> At 09:36 PM 8/20/2002, you wrote:
> >The patch below make some first steps to restructuring the
> >ibm_ocp_enet driver .
>
> Wouldn't it be nice BEFORE another ibm_ocp_enet restructuring to fix bugs
> introduced in the previous one?

Well, I'm thinking about this in 2.5.  There's no way the current OCP
setup stuff will go in.

> Current version has broken rx ring buffer management and the typo in
> requesting IRQ for RXDE event.

I noticed the RXDE problem while doing this work.  What's the problem
with Rx buffer management?

> I send bug report and a fix (maybe not the most elegant one) to Armin two
> weeks ago. Nothing happened :(

--
David Gibson			| For every complex problem there is a
david@gibson.dropbear.id.au	| solution which is simple, neat and
				| wrong.
http://www.ozlabs.org/people/dgibson

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

  reply	other threads:[~2002-08-21  7:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-21  4:36 Restructuring of ibm_ocp_enet driver David Gibson
2002-08-21  6:26 ` Eugene Surovegin
2002-08-21  7:19   ` David Gibson [this message]
2002-08-22  5:58   ` akuster
2002-08-21 17:20 ` akuster
2002-08-22  2:12   ` David Gibson

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=20020821071911.GL18818@zax \
    --to=david@gibson.dropbear.id.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).