public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Otto Solares <solca@guug.org>
To: "David S. Miller" <davem@redhat.com>
Cc: 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:55:38 -0600	[thread overview]
Message-ID: <20030723085538.GH30174@guug.org> (raw)
In-Reply-To: <20030723002737.376d93ca.davem@redhat.com>

On Wed, Jul 23, 2003 at 12:27:37AM -0700, David S. Miller wrote:
> On Wed, 23 Jul 2003 01:20:56 -0600
> Otto Solares <solca@guug.org> wrote:
> 
> > everything else includes the generic one (pci dependant).
> > With this model what happens if a box had more than one
> > bus type (if technically possible)?
> 
> If the architecture wants to support such situations,
> then the implementation needs to vector off to different
> operations based upon the actual bus type.
> 
> Even though technically devices having SBUS and PCI variants could do
> this, none do currently, and also I do not use the generic device
> model in the SBUS layer, therefore I'm not going to add such multi-bus
> support to what Sparc uses for dma-mapping.h

ok, i understand now.  Theorically could be nice the new API,
i better stick with the current per-bus-drivers.

> If someone is bored and willing to do all of the generic device and
> ->dma_ops work for Sparc and SBUS, feel free to send me some patches.
> Otherwise, it won't get done :-)

:) fine with me.

-solca


      parent reply	other threads:[~2003-07-23  8:45 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
2003-07-23  8:55                       ` Otto Solares [this message]

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=20030723085538.GH30174@guug.org \
    --to=solca@guug.org \
    --cc=davem@redhat.com \
    --cc=debian-sparc@lists.debian.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.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