| 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
| ||
|
Date: Fri, 12 Mar 2010 11:43:08 +0100 From: Stanislav Brabec <utx@...guin.cz> To: Andy Green <andy@...mcat.com> Cc: Eric Miao <eric.y.miao@...il.com>, dbaryshkov@...il.com, Cyril Hrubis <metan@....cz>, arminlitzel@....de, kernel list <linux-kernel@...r.kernel.org>, Dirk@...er-online.de, lenz@...wisc.edu, rpurdie@...ys.net, linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>, Pavel Machek <pavel@....cz>, thommycheck@...il.com, zaurus-devel@...ts.linuxtogo.org, omegamoon@...il.com Subject: Re: bit errors on spitz Andy Green wrote: > In that case is the PXA CF driver PIO? Then it can be the same load on > Vcore issue in disguise. There is a proprietary ASIC chip (Sharp Scoop) that handles CF and HDD access (and also several additional GPIOs): http://www.penguin.cz/~utx/zaurus/datasheets/ASIC_S1L50752B26B200/412752.PDF The ASIC runs in dual power mode. HVDD is powered from the 3.3V dedicated to CF resp. HDD power supply (both may be turned off by the kernel), LVDD is shared with CPU 3.3V (it is always on). It seems that there are no other chips connected to the VCC_PLL, VCC_SRAM and VCC_CORE. VCC_DRAM is the same 3.3V ans CPU ans ASIC LVDD and also the same as flash power and flash driver CPLD: http://www.penguin.cz/~utx/zaurus/datasheets/memory/ ________________________________________________________________________ Stanislav Brabec http://www.penguin.cz/~utx/zaurus -- 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