public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: David Miller <davem@davemloft.net>
Cc: alan@lxorguk.ukuu.org.uk, mroos@linux.ee, linux-kernel@vger.kernel.org
Subject: Re: libata & no PCI: dma_[un]map_single undefined
Date: Mon, 4 Jun 2007 17:56:34 -0700	[thread overview]
Message-ID: <20070605005634.GG15426@holomorphy.com> (raw)
In-Reply-To: <20070604.142243.98381397.davem@davemloft.net>

From: Alan Cox <alan@lxorguk.ukuu.org.uk>
Date: Mon, 4 Jun 2007 14:30:05 +0100
>> There are PCMCIA controllers and PCI/PCMCIA/Cardbus adapters for the
>> Sparc platform I thought ?

On Mon, Jun 04, 2007 at 02:22:43PM -0700, David Miller wrote:
> The 32-bit sparc port has some but those PCMCIA controllers aren't
> going to be supported in the foreseeable future, you have to abstract
> out all the inb/outb etc. operations to go through the pcmcia
> controller driver for one thing.
> Secondarily, sparc32 lacks an active maintainer and it's
> been like this for several years, the only things getting
> worked on therefore are basica functionality and the most
> important bug fixes.

I don't foresee my ever dealing with those PCMCIA controllers. If by
some miracle I manage to get any work done on basic functionality I'll
consider that having won.


-- wli

  reply	other threads:[~2007-06-05  0:55 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-03 20:23 libata & no PCI: dma_[un]map_single undefined Meelis Roos
2007-06-04  0:40 ` David Miller
2007-06-04  7:47   ` Christoph Hellwig
2007-06-04 17:19     ` Jeff Garzik
2007-06-05 11:22       ` Alan Cox
2007-06-05 13:56         ` Jeff Garzik
2007-06-05 14:17           ` Russell King
2007-06-05 14:25             ` Jeff Garzik
2007-06-05 14:35             ` Jeff Garzik
2007-06-05 14:51               ` Russell King
2007-06-05 14:56                 ` Jeff Garzik
2007-06-05 14:59                   ` Russell King
2007-06-05 15:11                     ` Jeff Garzik
2007-06-05 15:18                       ` Russell King
2007-06-05 15:21                         ` Russell King
2007-06-05 19:27                           ` David Miller
2007-06-05 21:25                             ` Russell King
2007-06-05 21:38                               ` Russell King
2007-06-05 21:48                                 ` Jeff Garzik
2007-06-05 22:03                                   ` Russell King
2007-06-05 22:16                                     ` Jeff Garzik
2007-06-06  0:25                                       ` Valdis.Kletnieks
2007-06-05 15:41                         ` Jeff Garzik
2007-06-05 15:45                           ` Russell King
2007-06-05 19:27                         ` David Miller
2007-06-05 19:24                       ` David Miller
2007-06-05 21:10                         ` Chuck Ebbert
2007-06-05 19:23                     ` David Miller
2007-06-05 21:20                       ` Russell King
2007-06-05 15:50             ` Alan Cox
2007-06-05 15:52               ` Russell King
2007-06-04  7:54   ` Geert Uytterhoeven
2007-06-04 13:30   ` Alan Cox
2007-06-04 21:22     ` David Miller
2007-06-05  0:56       ` William Lee Irwin III [this message]
2007-06-05 11:12         ` Alan Cox

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=20070605005634.GG15426@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    /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