linux-kernel - Re: Please revert: PCI: fix IDE legacy mode resources

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20071210134056.GC12913@linux-mips.org>
Date:	Mon, 10 Dec 2007 13:40:56 +0000
From:	Ralf Baechle <ralf@...ux-mips.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	benh@...nel.crashing.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Yoichi Yuasa <yoichi_yuasa@...peaks.co.jp>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Greg KH <gregkh@...e.de>,
	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
Subject: Re: Please revert: PCI: fix IDE legacy mode resources

On Mon, Dec 10, 2007 at 11:20:50AM +0000, Alan Cox wrote:

> > To be totally correct, we still need to also revert
> > commit fd6e732186ab522c812ab19c2c5e5befb8ec8115 which
> > is bogus.
> 
> Agreed but that would cause an revert on an obscure MIPS platform which
> is apparently now a thoughtcrime ;)
> 
> > Linus, can you still apply this to 2.6.24 ? I would also like the
> > above (fd6e...) reverted as so far, nobody have come up with a demonstration
> > that it's not bogus.
> 
> Ack the revert too.
> 
> The MIPS needs sorting out differently.

Yep.

It seems the whole MIPS resource managment is complicated enough (out of
necessity) that only a few people actually grok it.  Ioports being
actually memory mapped on MIPS only makes the confusion worse, sigh.

  Ralf
--
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/