From: Jan Kiszka <jan.kiszka@web.de>
To: Auke Kok <auke-jan.h.kok@intel.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: e100 fails, eepro100 works
Date: Sat, 09 Sep 2006 01:37:02 +0200 [thread overview]
Message-ID: <4501FE9E.70608@web.de> (raw)
In-Reply-To: <45018F76.5080403@intel.com>
[-- Attachment #1: Type: text/plain, Size: 352 bytes --]
Auke Kok wrote:
> Can you include a full `dmesg` and `lcpci -vv -s 00:12.0` ?
>
> Also you're using 3.5.10-k2, can you try the current git tree version
> instead? I can send you the e100.c if wanted.
Yes, please, to make sure that we'll really discuss the same version.
Will then try to collect the additional information on Monday.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
prev parent reply other threads:[~2006-09-08 23:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 13:41 e100 fails, eepro100 works Jan Kiszka
2006-09-08 15:42 ` Auke Kok
2006-09-08 23:37 ` Jan Kiszka [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=4501FE9E.70608@web.de \
--to=jan.kiszka@web.de \
--cc=auke-jan.h.kok@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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).