linux-kernel - Re: [PATCH] arch/arm/Kconfig: Make UIO available on ARM architecture

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200802071609.36960.openembedded@haerwu.biz>
Date:	Thu, 7 Feb 2008 16:09:34 +0100
From:	Marcin Juszkiewicz <openembedded@...rwu.biz>
To:	linux-arm-kernel@...ts.arm.linux.org.uk
Cc:	Sam Ravnborg <sam@...nborg.org>,
	Christoph Hellwig <hch@...radead.org>,
	Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arch/arm/Kconfig: Make UIO available on ARM architecture

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: 

- of - does not appear on ARM if enabled
- macintosh - does not appear on ARM if enabled
- telephony - drivers for ISA/PCI/PCMCIA so can probably be used on some
              ARM platforms
- infiniband - like above(?)
- edac - does not appear on ARM if enabled
- auxdisplay - basically it is for one LCD controller connected to x86
               parallel port - safe to have it sourced on ARM
- uio

Including of 'drivers/mtd' depends on "ALIGNMENT_TRAP || !CPU_CP15_MMU".

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.

Does it look like 'drivers/mtd' require extra check 'if ARM then check for 
ALIGNMENT_TRAP || !CPU_CP15_MMU' and probably extra check 
in 'drivers/ide'?

I hope this info will help (test in 2.6.24-git 
488b5ec871191359b9b79262a3d48456dae7ea5f).

-- 
JID: hrw-jabber.org
OpenEmbedded developer/consultant

        "To be or not to be that is the question.":
         every programmer knows the answer $2b or (not $2b) is $ff.


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