All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Dunkel <harri@synopsys.COM>
To: Tim Walberg <twalberg@mindspring.com>
Cc: Andrew Morton <akpm@zip.com.au>, linux-kernel@vger.kernel.org
Subject: Re: 3c59x:command 0x3002 did not complete! Status=0xffff
Date: Mon, 29 Oct 2001 22:22:01 +0100	[thread overview]
Message-ID: <3BDDC879.7F1D2D2C@Synopsys.COM> (raw)
In-Reply-To: <3BDD9FF4.D54DC0C9@Synopsys.COM> <3BDDA4C0.F4391EC@zip.com.au> <3BDDB312.589D2E04@Synopsys.COM> <3BDDB4E0.C90BFACB@zip.com.au> <3BDDBD60.3540EFCA@Synopsys.COM> <20011029145307.A8312@mindspring.com>

Tim Walberg wrote:
> 
> Is the NIC sharing interrupts or I/O ports with
> the SCSI HBAs?
> 

Nope:

  Bus  0, device  10, function  0:
    SCSI storage controller: Adaptec 7899A (rev 1).
      IRQ 15.
      Master Capable.  Latency=32.  Min Gnt=40.Max Lat=25.
      I/O at 0xa000 [0xa0ff].
      Non-prefetchable 64 bit memory at 0xd5000000 [0xd5000fff].
  Bus  0, device  10, function  1:
    SCSI storage controller: Adaptec 7899A (#2) (rev 1).
      IRQ 9.
      Master Capable.  Latency=32.  Min Gnt=40.Max Lat=25.
      I/O at 0x9800 [0x98ff].
      Non-prefetchable 64 bit memory at 0xd4800000 [0xd4800fff].
  Bus  0, device  11, function  0:
    Ethernet controller: 3Com Corporation 3c900 Combo [Boomerang] (rev 0).
      IRQ 10.
      Master Capable.  Latency=32.  Min Gnt=3.Max Lat=8.
      I/O at 0x9400 [0x943f].


The SCSI controller is an Adaptec 39160, so it allocates 2 IRQs, 2 I/Os,
etc.


Regards

Harri

  reply	other threads:[~2001-10-29 21:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-29 18:29 3c59x:command 0x3002 did not complete! Status=0xffff Harald Dunkel
2001-10-29 18:49 ` Andrew Morton
2001-10-29 19:16   ` Harald Dunkel
2001-10-29 19:50   ` Harald Dunkel
2001-10-29 19:58     ` Andrew Morton
2001-10-29 20:34       ` Harald Dunkel
2001-10-29 20:53         ` Tim Walberg
2001-10-29 21:22           ` Harald Dunkel [this message]
2001-10-29 21:21       ` Wolfgang Rohdewald

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=3BDDC879.7F1D2D2C@Synopsys.COM \
    --to=harri@synopsys.com \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=twalberg@mindspring.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.