From: Leif Lindholm <leif.lindholm@i3micro.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] dbau1550 patch
Date: Wed, 29 Dec 2004 11:44:48 +0100 [thread overview]
Message-ID: <1104317088.1002.19.camel@localhost> (raw)
In-Reply-To: <c166aa9f04122822171399a7a9@mail.gmail.com>
On Wed, 2004-12-29 at 00:17 -0600, Andrew Dyer wrote:
> On Tue, 07 Dec 2004 13:45:44 +0100, Leif Lindholm
> <leif.lindholm@i3micro.com> wrote:
> > Will send this to you privately, and later try to clean it up a bit and
> > fix a few bugs this caused with the db1000 board, so Wolfgang might
> > accept it into the CVS.
>
> I changed the lines setting these up in au1x00_init() to:
>
> next_tx = TX_GET_DMA_BUFFER(fifo_tx[0].addr);
> next_rx = RX_GET_DMA_BUFFER(fifo_rx[0].addr);
>
> this issue was causing me problems with rx and tx timeouts, and
> changing these values fixes my problem (at least in limited testing).
> Can someone else try out this change on au1000/1100/1500
> based systems?
This seems to clear up a similar/identical problem we had on our
hardware, but haven't had time to investigate. Good work, thanks!
I'm attaching a patch against CVS (last synced on the 10:th of December,
since the sourceforge server seems to be down as usual - but I don't
think that file has been modified) for others testing on other
boards/chips, since I only have 1550 hardware here.
/
Leif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: au1x00_eth.c.diff
Type: text/x-patch
Size: 568 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20041229/2533a9e8/attachment.bin
next prev parent reply other threads:[~2004-12-29 10:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 20:05 [U-Boot-Users] dbau1550 patch Andrew Dyer
2004-12-07 12:45 ` Leif Lindholm
2004-12-29 6:17 ` Andrew Dyer
2004-12-29 10:44 ` Leif Lindholm [this message]
2004-12-29 10:51 ` Leif Lindholm
2005-01-05 15:28 ` Thomas Lange
2005-09-24 20:06 ` Wolfgang Denk
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=1104317088.1002.19.camel@localhost \
--to=leif.lindholm@i3micro.com \
--cc=u-boot@lists.denx.de \
/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