public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Augustin Vidovic <vido@ldh.org>
To: Andrey Savochkin <saw@saw.sw.com.sg>
Cc: Ion Badulescu <ionut@cs.columbia.edu>, Alan Cox <alan@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: eepro100.c, kernel 2.4.1
Date: Tue, 20 Feb 2001 17:18:37 +0900	[thread overview]
Message-ID: <20010220171837.A26967@ldh.org> (raw)
In-Reply-To: <20010212133248.A7147@saw.sw.com.sg> <Pine.LNX.4.30.0102120048160.4687-100000@age.cs.columbia.edu> <20010220153048.A26551@ldh.org> <20010219232136.C26553@saw.sw.com.sg>
In-Reply-To: <20010219232136.C26553@saw.sw.com.sg>; from saw@saw.sw.com.sg on Mon, Feb 19, 2001 at 11:21:36PM -0800

On Mon, Feb 19, 2001 at 11:21:36PM -0800, Andrey Savochkin wrote:
> On Tue, Feb 20, 2001 at 03:30:48PM +0900, Augustin Vidovic wrote:
> > On Mon, Feb 12, 2001 at 01:00:34AM -0800, Ion Badulescu wrote:
> > > > Augustin, could you send the output of `lspci' and `eepro100-diag -ee', please?
> > > > (The latter may be taken from ftp://scyld.com/pub/diag/)
> > > 
> > > I'd be curious to see them too.
> > 
> > Ok, here is the output (the status are displayed only if the interface
> > is down, so I had to go execute this manually on the machines) :
> > 
> > 
> > eepro100-diag.c:v2.02 7/19/2000 Donald Becker (becker@scyld.com)
> >  http://www.scyld.com/diag/index.html
> > Index #1: Found a Intel i82557 (or i82558) EtherExpressPro100B adapter at 0xef00.
> [snip]
> 
> What about lspci?

Ah, yes, here it is :

00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (AGP disabled) (rev 03)
00:07.0 ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 02)
00:0c.0 Ethernet controller: Intel Corporation 82557 (rev 08)
00:0d.0 Ethernet controller: Intel Corporation 82557 (rev 08)
00:0e.0 VGA compatible controller: ATI Technologies Inc 215GP [Mach64 GP] (rev 5c)


  reply	other threads:[~2001-02-20  8:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-08  5:53 [PATCH] eepro100.c, kernel 2.4.1 Augustin Vidovic
2001-02-08  7:23 ` Ion Badulescu
2001-02-08  7:37   ` Augustin Vidovic
2001-02-08  7:42   ` Alan Cox
2001-02-08  7:55     ` Andrey Savochkin
2001-02-08  7:59     ` [PATCH] " Ion Badulescu
2001-02-08 10:41       ` Augustin Vidovic
2001-02-08 11:00         ` Ion Badulescu
2001-02-08 11:15           ` Augustin Vidovic
2001-02-08 11:26             ` Ion Badulescu
2001-02-08 11:44               ` Augustin Vidovic
2001-02-08 11:53                 ` Ion Badulescu
2001-02-08 12:08                   ` Augustin Vidovic
2001-02-12  5:32               ` Andrey Savochkin
2001-02-12  9:00                 ` Ion Badulescu
2001-02-20  6:30                   ` Augustin Vidovic
2001-02-20  7:21                     ` Andrey Savochkin
2001-02-20  8:18                       ` Augustin Vidovic [this message]
2001-02-20 23:38                         ` Andrey Savochkin

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=20010220171837.A26967@ldh.org \
    --to=vido@ldh.org \
    --cc=alan@redhat.com \
    --cc=ionut@cs.columbia.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=saw@saw.sw.com.sg \
    /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