linux-kernel - Re: [PATCH] [MMC] Fix base address configuration in wbsd

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] [day] [month] [year] [list]

Message-ID: <44D6791F.8030001@drzeus.cx>
Date:	Mon, 07 Aug 2006 01:19:59 +0200
From:	Pierre Ossman <drzeus-list@...eus.cx>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	Ben Dooks <ben@...ff.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [MMC] Fix base address configuration in wbsd

Alan Cox wrote:
> Ar Sul, 2006-08-06 am 23:52 +0200, ysgrifennodd Pierre Ossman:
>   
>> Sorry, my intention wasn't to assert that it was only to be used on x86
>> but that the 16-bit assumption was safe.
>>     
>
> Your ISA bus mappings on a non x86 processor are likely to be 32bit MMIO
> -> PIO windows in memory space. 
>
>   

Since we configure the device, the PIO address must not be subject to
translation. If it is, then we must know how the translation is done.

As this is a rather crappy chip which nobody in their right mind would
use, we'll cross that bridge when/if someone decides to use it in a
system that doesn't behave like x86.

Rgds
Pierre

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