From: Kromer <krom@gazeta•pl>
To: "Linuxppc-Embedded (E-mail)" <linuxppc-embedded@lists•linuxppc.org>
Subject: memory problem with fec on 8250
Date: Wed, 03 Dec 2003 08:48:59 +0100 [thread overview]
Message-ID: <3FCD956B.8030604@gazeta.pl> (raw)
hi there
i have some problems with using fec device on my custom 8250 board
while sending a lot of data (at least 300MB) through this device causes
lack of memory
sending same amount of data through loopback works fine
i'm using 2.4.19 kernel
any idea?
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-12-03 7:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 7:48 Kromer [this message]
2003-12-04 8:45 ` memory problem with fec on 8250 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
-- 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=3FCD956B.8030604@gazeta.pl \
--to=krom@gazeta$(echo .)pl \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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