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 02:37:20 -0700 [thread overview]
Message-ID: <20030723023720.1a98b541.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0307231031240.26107-100000@hek.netunix.com>
On Wed, 23 Jul 2003 10:35:56 +0100 (BST)
"C.Newport" <crn@netunix.com> wrote:
> In that case none, but your original message implied that this did
> not exist and would not be supported.
>
> Maybe I misunderstood what you meant.
>
> OTOH, (if !SBUS) might screw up ?.
Look, SBUS does _NOT_ use the generic device abstraction.
Therefore all SBUS drivers call into the sbus_* DMA operations
directly.
Everything just works, as it always has, and it's not going to break
any time soon.
What I'm saying is that I'm not going to move the SBUS layer
over to use generic devices.
next prev parent reply other threads:[~2003-07-23 9:24 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
2003-07-23 9:35 ` C.Newport
2003-07-23 9:37 ` David S. Miller [this message]
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=20030723023720.1a98b541.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