linux-kernel - Re: ioports 0x100-0x3af and iomem 0xd000-0xdffff, 0xa0000000-0xa0ffffff -- safe to use on x86 for pcmcia?

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: <20091124231653.30084.qmail@stuge.se>
Date:	Wed, 25 Nov 2009 00:16:52 +0100
From:	Peter Stuge <peter@...ge.se>
To:	x86@...nel.org, Komuro <komurojun-mbn@...ty.com>,
	linux-pcmcia@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: ioports 0x100-0x3af and iomem 0xd000-0xdffff,
	0xa0000000-0xa0ffffff -- safe to use on x86 for pcmcia?

Dominik Brodowski wrote:
> 	include port 0x100-0x3af
> 	include memory 0xc0000-0xfffff
> 	include memory 0xa0000000-0xa0ffffff
..
> Do you think it would be safe to enable these areas by (kernel)
> default on x86?

c0000-fffff is option ROM and BIOS land. Maybe every BIOS out there
is being a good boy/girl and actually adds entries to e820 or similar
but I would kindof like to stay away from the region anyway.

0xa0000000 is 2.5GB, so it's doomed on systems with >=2.5GB RAM. :(


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