From: Dragan Stancevic <visitor@valinux.com>
To: "Udo A. Steinberg" <sorisor@Hell.WH8.TU-Dresden.De>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: New discoveries in the EEPro100 init saga
Date: Thu, 28 Dec 2000 13:33:10 -0800 [thread overview]
Message-ID: <20001228133310.B31635@valinux.com> (raw)
In-Reply-To: <3A446A49.C1E7AAFB@Hell.WH8.TU-Dresden.De>
In-Reply-To: <3A446A49.C1E7AAFB@Hell.WH8.TU-Dresden.De>; from Udo A. Steinberg on Sat, Dec 23, 2000 at 10:03:05AM +0100
On Sat, Dec 23, 2000, Udo A. Steinberg <sorisor@Hell.WH8.TU-Dresden.De> wrote:
;
; Hi all,
;
; After enabling the option "EEPRO100_PM" and upgrading to test13-pre4
; my problems with the eepro100 driver mysteriously ceased to exist.
; I no longer see any "Card reports no RX buffers" or "Card reports no
; resources" messages.
;
; Since I don't think -pre4 changed anything from -pre3 that would
; affect the eepro100 driver, my bet is that enabling the experimental
; power management feature somehow works around the issue.
;
; Can others who've had similar problems check if that works for them
; as well? If it does, it should be somewhat simple to work out what
; the problem actually is, because the PM code is just a couple dozen
; lines.
Udo,
the driver has an issue that is affected by fiddling with different
parameters, it's a timing issue of somesort, changing a bit of code
seems to fix it on one system but it breaks it on others, I am comparing
the driver line by line to the specs to see where the misbehavioure
could be comming from.
--
I knew I was alone, I was scared, it was getting dark and
it was a hardware problem.
-Dragan
-
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/
prev parent reply other threads:[~2000-12-28 20:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-23 9:03 Udo A. Steinberg
2000-12-28 21:33 ` Dragan Stancevic [this message]
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=20001228133310.B31635@valinux.com \
--to=visitor@valinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sorisor@Hell.WH8.TU-Dresden.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
all inboxes | Powered by JetHome®