linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Dooks <ben@fluff.org>
To: Erik Mouw <erik@harddisk-recovery.com>
Cc: Matthew Wilcox <matthew@wil.cx>,
	Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
	linux-ide@vger.kernel.org
Subject: Re: [PATCH] Some IDE chipsets are architecture-specific
Date: Mon, 7 Mar 2005 15:51:52 +0000	[thread overview]
Message-ID: <20050307155152.GA7789@home.fluff.org> (raw)
In-Reply-To: <20050307154755.GA31844@harddisk-recovery.com>

On Mon, Mar 07, 2005 at 04:47:55PM +0100, Erik Mouw wrote:
> On Mon, Mar 07, 2005 at 03:28:03PM +0000, Matthew Wilcox wrote:
> > Mark some chipset support as being for specific architectures.
> > I may have got some wrong, so please double-check.
> > 
> > Signed-off-by: Matthew Wilcox <matthew@wil.cx>
> > 
> > Index: ./drivers/ide/Kconfig
> > ===================================================================
> > RCS file: /var/cvs/linux-2.6/drivers/ide/Kconfig,v
> > retrieving revision 1.25.2.1
> > diff -u -p -r1.25.2.1 Kconfig
> > --- ./drivers/ide/Kconfig	2 Mar 2005 11:19:06 -0000	1.25.2.1
> > +++ ./drivers/ide/Kconfig	7 Mar 2005 04:49:26 -0000
> > @@ -457,6 +457,7 @@ config BLK_DEV_AEC62XX
> >  
> >  config BLK_DEV_ALI15X3
> >  	tristate "ALI M15x3 chipset support"
> > +	depends on X86
> >  	help
> >  	  This driver ensures (U)DMA support for ALI 1533, 1543 and 1543C
> >  	  onboard chipsets.  It also tests for Simplex mode and enables
> 
> AFAIK the ALI 1533 and 1543 are generic PCI southbridges that can be
> used on any PCI bus, so I wouldn't limit them to X86 only.

The Simtec (ex Chalice) CATS uses an ALI 1543, and that is an ARM

-- 
Ben (ben@fluff.org, http://www.fluff.org/)

  'a smiley only costs 4 bytes'

  reply	other threads:[~2005-03-07 15:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-07 15:28 [PATCH] Some IDE chipsets are architecture-specific Matthew Wilcox
2005-03-07 15:47 ` Erik Mouw
2005-03-07 15:51   ` Ben Dooks [this message]
2005-03-07 16:58 ` 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=20050307155152.GA7789@home.fluff.org \
    --to=ben@fluff.org \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=erik@harddisk-recovery.com \
    --cc=linux-ide@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).