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: <1197331853.9071.12.camel@pasglop>
Date:	Tue, 11 Dec 2007 11:10:53 +1100
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Ralf Baechle <ralf@...ux-mips.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, 2007-12-10 at 23:07 +0000, Alan Cox wrote:
> > Forcing controllers into native mode tends to be something that really
> > only works on -some- controllers. I'm happy to have a hack to try to do
> > that on all of them on powermacs, because the range of controllers that
> > might not be in native mode in the first place there is pretty small,
> > and for CHRP briq, I do it for a specific known controller only.
> 
> I'm thinking of doing this solely if the platform has
> CONFIG_ATA_NO_LEGACY set. In other words we'd only try this stunt on a
> system we *know* cannot address the low PCI space ports.

Allright. I don't set CONFIG_ATA_NO_LEGACY on powerpc anyway, as I do
support legacy ATA just fine on a range of machines. 

For example, Pegasos does the a quirk the other way around which is to
put it back the VIA IDE into legacy mode as there are issues with the
way that VIA chipset is configured on those machines.

It's mostly a matter of making sure for me that the IRQ routing match
what the platform code is set to deal with or that sort of thing as
unfortunately, anything that involves legacy stuff is still pretty much
full of hacks.

Ben.


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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ