From: "David S. Miller" <davem@redhat.com>
To: "C.Newport" <crn@netunix.com>
Cc: solca@guug.org, hch@infradead.org, zaitcev@redhat.com,
linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org,
debian-sparc@lists.debian.org
Subject: Re: sparc scsi esp depends on pci & hangs on boot
Date: Wed, 23 Jul 2003 01:28:24 -0700 [thread overview]
Message-ID: <20030723012824.5d8dec9b.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0307230926170.26107-100000@hek.netunix.com>
On Wed, 23 Jul 2003 09:33:40 +0100 (BST)
"C.Newport" <crn@netunix.com> wrote:
> Ouch - As I mentioned a few days ago, the Ex000 range can have a
> mixture of SBUS and PCI.
So what?
> This configuration is becoming increasingly
> common as these machines are upgraded to attach to SAN stuff and
> other FCAL variants for which there is no SBUS card.
Nothing I have said prevents these systems from fully
working.
Because I won't move SBUS over to generic struct device,
none of the SBUS device drivers will change either, therefore
everything works as it does today.
What's the problem?
next prev parent reply other threads:[~2003-07-23 8:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-22 2:51 sparc scsi esp depends on pci & hangs on boot Otto Solares
2003-07-22 12:09 ` Pete Zaitcev
2003-07-22 18:26 ` Otto Solares
2003-07-23 0:54 ` David S. Miller
2003-07-23 2:32 ` Otto Solares
2003-07-23 6:07 ` Christoph Hellwig
2003-07-23 6:24 ` David S. Miller
2003-07-23 6:28 ` Christoph Hellwig
2003-07-23 6:29 ` David S. Miller
2003-07-23 6:40 ` Christoph Hellwig
2003-07-23 6:57 ` David S. Miller
2003-07-23 7:02 ` Christoph Hellwig
2003-07-23 7:20 ` David S. Miller
2003-07-23 8:45 ` Otto Solares
2003-07-23 14:42 ` Geert Uytterhoeven
2003-07-23 6:43 ` Otto Solares
2003-07-23 7:04 ` Christoph Hellwig
2003-07-23 7:20 ` Otto Solares
2003-07-23 7:27 ` David S. Miller
2003-07-23 8:33 ` C.Newport
2003-07-23 8:28 ` David S. Miller [this message]
2003-07-23 9:35 ` C.Newport
2003-07-23 9:37 ` David S. Miller
2003-07-23 8:55 ` Otto Solares
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=20030723012824.5d8dec9b.davem@redhat.com \
--to=davem@redhat.com \
--cc=crn@netunix.com \
--cc=debian-sparc@lists.debian.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=solca@guug.org \
--cc=sparclinux@vger.kernel.org \
--cc=zaitcev@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox