linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Wojciech Kromer <krom@dgt-lab.com.pl>
Cc: "Linuxppc-Embedded (E-mail)" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: memory problem with fec on 8250
Date: Thu, 04 Dec 2003 09:03:35 -0500	[thread overview]
Message-ID: <3FCF3EB7.5080404@embeddededge.com> (raw)
In-Reply-To: 3FCF19C3.9070205@dgt-lab.com.pl


Wojciech Kromer wrote:

> _anyone_ knows why there is such difference between allocs and frees in
> fcc_enet.c

What kernel and driver is this?

The latest one I checked into linuxppc_2_4_devel a long time ago
had the benefit of being tested at the UNH Interoperability Laboratory.
This included performance testing and error recovery.  For this driver
to be failing, it must have been modified from that version and we
need to determine what was done to get it corrected.

Thanks.


	-- Dan


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

  reply	other threads:[~2003-12-04 14:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-03  7:48 memory problem with fec on 8250 Kromer
2003-12-04  8:45 ` Wojciech Kromer
2003-12-04  9:15   ` Eugene Surovegin
2003-12-04  9:45     ` Wojciech Kromer
2003-12-04 10:19       ` Eugene Surovegin
     [not found]         ` <3FCF0E68.4010303@dgt-lab.com.pl>
     [not found]           ` <20031204105532.GA2065@gate.ebshome.net>
2003-12-04 11:25             ` Wojciech Kromer
2003-12-04 14:03               ` Dan Malek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-04 15:55 Samo Pogacnik
2004-01-05  8:15 ` Wojciech Kromer
2004-01-05 22:52   ` Samo Pogacnik
2004-01-06  7:47     ` cd Wojciech Kromer
2004-01-06 22:03       ` memory problem with fec on 8250 Samo Pogacnik

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=3FCF3EB7.5080404@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=krom@dgt-lab.com.pl \
    --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).