Date: Sat, 9 Feb 2008 12:39:35 +0100
From: Sam Ravnborg <sam@ravnborg.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Christoph Hellwig <hch@infradead.org>,
       linux-arm-kernel@lists.arm.linux.org.uk, linux-kernel@vger.kernel.org,
       Greg KH <greg@kroah.com>
Subject: Re: [PATCH] arch/arm/Kconfig: Make UIO available on ARM architecture
Message-ID: <20080209113935.GB5776@uranus.ravnborg.org>
References: <20080207133805.13f092ff@dilbert.local> <20080207125824.GB7111@infradead.org> <20080207130117.GA18750@uranus.ravnborg.org> <200802071609.36960.openembedded@haerwu.biz> <20080207160557.GB28435@flint.arm.linux.org.uk> <20080207202329.GA21949@uranus.ravnborg.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20080207202329.GA21949@uranus.ravnborg.org>
User-Agent: Mutt/1.4.2.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2578
Lines: 56

On Thu, Feb 07, 2008 at 09:23:29PM +0100, Sam Ravnborg wrote:
> On Thu, Feb 07, 2008 at 04:05:58PM +0000, Russell King - ARM Linux wrote:
> > On Thu, Feb 07, 2008 at 04:09:34PM +0100, Marcin Juszkiewicz wrote:
> > > Dnia Thursday, 7 of February 2008, Sam Ravnborg napisał:
> > > > On Thu, Feb 07, 2008 at 07:58:24AM -0500, Christoph Hellwig wrote:
> > > 
> > > > > Any chance to make arm finally use drivers/Kconfig?  It's a bit silly
> > > > > that arm still is crapping around while even s390 uses it.
> > > 
> > > > rmk said that it should be easy to check the amount of work needed to
> > > > do so. But I have not had time to look into it yet - hopefully someone
> > > > in ARM land could fix it.
> > > 
> > > I looked at it and 'arch/arm/Kconfig' does not source few entries: 
> > 
> > diff -u arch/arm/Kconfig drivers/Kconfig shows the situation.  This is
> > why I insist that new entries to arch/arm/Kconfig should be in the same
> > order as drivers/Kconfig.
> > 
> > > Including of 'drivers/mtd' depends on "ALIGNMENT_TRAP || !CPU_CP15_MMU".
> > 
> > It's this which is the main issue.
> > 
> > > Including of 'drivers/ide' depends on "PCMCIA || ARCH_CLPS7500 || 
> > > ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_L7200 || 
> > > ARCH_LH7A40X || ARCH_PXA || ARCH_RPC || ARCH_S3C2410 || ARCH_SA1100 || 
> > > ARCH_SHARK || FOOTBRIDGE || ARCH_IXP23XX" but 'drivers/ata' (which can be 
> > > used instead on PCMCIA enabled platforms) does not depend on such set.
> > 
> > IDE people insisted that we _will_ have that silly conditional for IDE.
> > I personally do not want it and would be happy to see it go - but I
> > don't have the authority to do that.  Take this one up with Bart.
> 
> Both situations are trivially fixable by introducing
> HAVE_IDE and HAVE_MTD.
> See attached patch.
> 
> My quick scan told me that only S390 and UM did not
> support IDE neither MTD.
> ARM is the only one where IDE and MTD support is conditional
> and the rest you select them unconditionally.

Quick status on this.
I have submitted a corrected patch containing only the
HAVE_IDE stuff via kbuild.git and considering the
comment from David the mtd bits are trivial done.
So I expect someone that better can check the arm stuff
to do the final conversion bits to introduce drivers/Kconfig
when kbuild.git hits mainline.

	Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/