public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul Rolland" <rol@as2917.net>
To: "'Andrey Nekrasov'" <andy@spylog.ru>, <linux-kernel@vger.kernel.org>
Subject: Re: eepro100: wait_for_cmd_done timeout
Date: Fri, 28 Feb 2003 07:50:27 +0100	[thread overview]
Message-ID: <023a01c2def5$ae59a6e0$3f00a8c0@witbe> (raw)
In-Reply-To: <20030227203013.GA25009@an.spylog.com>

Hello,

> Hello Paul Rolland,
> 
> > Feb 27 13:50:01 rms-01 Feb 27 13:50:01:30726 kernel: eepro100: 
> > wait_for_cmd_done  timeout!
> > 
> > eth0: OEM i82557/i82558 10/100 Ethernet, 00:06:5B:39:69:2B, IRQ 16.
> >   Board assembly 02d484-000, Physical connectors present: RJ45
> >   Primary interface chip i82555 PHY #1.
> >   General self-test: passed.
> >   Serial sub-system self-test: passed.
> >   Internal registers self-test: passed.
> >   ROM checksum self-test: passed (0x04f4518b).
> > Anyone knows why ?
> 
>  try update bios on motherboard.
>  i am use INTEL STL2 and after update bios to last version 
> network card work ok

Thanks for the suggestion...
I got another one, telling me to have a look at the e100 driver,
and this raises a question I have for quite a long time : why does
the Kernel have two different supports for the same hardware ?
Is this a migration plan, a long run "please switch from eepro100
to e100" ?
Is there a better working one ?

I don't say that, once a driver exists, no one should ever think
of doing another one, but there are little indication as to which
one people should select...

Quite puzzling ;-)

Regards,
Paul


  reply	other threads:[~2003-02-28  6:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-27 16:56 eepro100: wait_for_cmd_done timeout Paul Rolland
2003-02-27 20:30 ` Andrey Nekrasov
2003-02-28  6:50   ` Paul Rolland [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-28 11:42 Chris Bacott
2003-03-28 17:59 ` Jeff Garzik
2001-06-20 23:31 Dionysius Wilson Almeida
2001-06-20 23:51 ` Andrey Savochkin
2001-06-21  0:02   ` Dionysius Wilson Almeida
2001-06-21 13:46     ` Rafael Martinez
2001-06-22  1:36     ` Dionysius Wilson Almeida
2001-06-22 13:31       ` Andrey Savochkin
2001-06-22 20:06         ` Dionysius Wilson Almeida
2001-06-21 14:19 ` Masaru Kawashima
2001-06-21 14:37   ` John Madden
2001-06-22  1:27     ` Masaru Kawashima
2001-06-21 16:28   ` Masaru Kawashima

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='023a01c2def5$ae59a6e0$3f00a8c0@witbe' \
    --to=rol@as2917.net \
    --cc=andy@spylog.ru \
    --cc=linux-kernel@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