linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Bjorn Helgaas <bjorn.helgaas@hp.com>,
	B.Zolnierkiewicz@elka.pw.edu.pl, linux-kernel@vger.kernel.org,
	linux-ide@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: [PATCH] IDE: don't offer IDE_GENERIC on ia64
Date: Tue, 16 Aug 2005 15:49:20 +0200	[thread overview]
Message-ID: <58cb370e05081606497e4d9907@mail.gmail.com> (raw)
In-Reply-To: <20050816134029.GA5113@parcelfarce.linux.theplanet.co.uk>

On 8/16/05, Matthew Wilcox <matthew@wil.cx> wrote:
> On Tue, Aug 16, 2005 at 01:55:58PM +0100, Alan Cox wrote:
> > On Maw, 2005-08-16 at 11:38 +0200, Bartlomiej Zolnierkiewicz wrote:
> > > * removing IDE_ARCH_OBSOLETE_INIT define has some implications,
> > >   * non-functional ide-cs driver (but there is no PCMCIA on IA64?)
> >
> > IA64 systems can support PCI->Cardbus/PCMCIA cards so they do actually
> > need this support. They could also do with cardbus IDE support but that
> > means a whole pile of patches still although the refcounting stuff means
> > its a lot closer to doable now
> 
> Then IDE_ARCH_OBSOLETE_INIT needs to be added back for all other
> architectures that support PCI too ...

Rather ide-cs needs to be fixed to use ide_std_init_ports() instead of
ide_init_hwif_ports() (please see my reply to Alan).

Bartlomiej

  reply	other threads:[~2005-08-16 13:49 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-11 20:24 [PATCH] IDE: don't offer IDE_GENERIC on ia64 Bjorn Helgaas
2005-08-11 20:34 ` Christoph Hellwig
2005-08-11 20:37   ` Bjorn Helgaas
2005-08-12 19:41   ` Jan Engelhardt
2005-08-16 10:02   ` Bartlomiej Zolnierkiewicz
2005-08-16 14:05     ` Alan Cox
2005-08-11 20:36 ` Jeff Garzik
2005-08-11 20:45   ` Bjorn Helgaas
2005-08-11 20:56     ` Jeff Garzik
2005-08-11 21:42       ` Bjorn Helgaas
2005-08-11 21:48         ` Jeff Garzik
2005-08-11 21:56           ` Jeff Garzik
2005-08-11 23:07             ` Bjorn Helgaas
2005-08-11 23:49               ` Jeff Garzik
2005-08-12  8:35               ` Alan Cox
2005-08-12 10:33               ` Maciej W. Rozycki
2005-08-11 23:01         ` Jack Steiner
2005-08-11 23:08 ` Jack Steiner
2005-08-12  8:40 ` Alan Cox
2005-08-15 21:07   ` Bjorn Helgaas
2005-08-16  9:38     ` Bartlomiej Zolnierkiewicz
2005-08-16  9:54       ` Bartlomiej Zolnierkiewicz
2005-08-16 12:55       ` Alan Cox
2005-08-16 12:59         ` Bartlomiej Zolnierkiewicz
2005-08-16 13:40         ` Matthew Wilcox
2005-08-16 13:49           ` Bartlomiej Zolnierkiewicz [this message]
2005-08-16 19:16       ` Bjorn Helgaas
2005-08-16 20:16         ` Bartlomiej Zolnierkiewicz
2005-08-16 20:25         ` Alan Cox
2005-08-16 20:42           ` Bartlomiej Zolnierkiewicz
2005-08-16 21:48             ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2005-08-11 21:58 Luck, Tony
2005-08-11 22:03 ` Jeff Garzik

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=58cb370e05081606497e4d9907@mail.gmail.com \
    --to=bzolnier@gmail.com \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bjorn.helgaas@hp.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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;
as well as URLs for NNTP newsgroup(s).