From: Manfred Spraul <manfred@colorfullife.com>
To: Urban Widmark <urban@teststation.com>
Cc: Jonathan Morton <chromi@cyberspace.org>,
linux-kernel@vger.kernel.org, ksa1 <ksa1@gmx.de>
Subject: Re: d-link dfe-530 tx (bug-report)
Date: Sun, 04 Feb 2001 13:35:26 +0100 [thread overview]
Message-ID: <3A7D4C8E.EC487631@colorfullife.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0102041127500.24217-100000@cola.teststation.com>
Urban Widmark wrote:
>
> The "transmit timed out" message is simply saying that we told the card to
> send something but it hasn't generated an interrupt or anything allowing
> the driver to know the packet was actually sent.
>
check via_rhine_tx_timeout():
the function is basically empty.
>
> Oh, that's known already. They haven't released any info on the older
> "VT3043" chip either, afaik. And the vt86c100a.pdf document is just a
> preliminary version.
>
Where can I find that file?
I'll try to implement tx_timeout()
--
Manfred
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-04 12:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-04 10:23 d-link dfe-530 tx (bug-report) Jonathan Morton
2001-02-04 11:40 ` hjb
2001-02-04 12:14 ` Urban Widmark
2001-02-04 12:35 ` Manfred Spraul [this message]
2001-02-04 12:40 ` Urban Widmark
2001-02-04 15:39 ` Manfred
[not found] ` <Pine.LNX.4.30.0102042130100.26061-300000@cola.teststation.com>
2001-02-05 0:07 ` Thomas Stewart
2001-02-05 8:38 ` Manfred Spraul
2001-02-05 9:26 ` Urban Widmark
2001-02-05 10:41 ` Thomas Stewart
2001-02-05 10:58 ` Manfred Spraul
2001-02-05 19:41 ` Thomas Stewart
-- strict thread matches above, loose matches on Subject: below --
2001-02-05 14:51 ksa1
2001-02-06 21:15 ` Jonathan Morton
2001-02-04 9:26 ksa1
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=3A7D4C8E.EC487631@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=chromi@cyberspace.org \
--cc=ksa1@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=urban@teststation.com \
/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