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]
Date:	Thu, 12 Feb 2015 19:59:00 +0100 (CET)
From:	Stefan Wahren <stefan.wahren@...e.com>
To:	Fabio Estevam <festevam@...il.com>
Cc:	Sascha Hauer <kernel@...gutronix.de>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Shawn Guo <shawn.guo@...aro.org>,
	Mike Turquette <mturquette@...aro.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Marek Vasut <marex@...x.de>, Zhi Li <lznuaa@...il.com>
Subject: Re: [PATCH V2 RESEND] clk: mxs: Fix invalid 32-bit access to frac
 registers

Hi Fabio,

> Fabio Estevam <festevam@...il.com> hat am 11. Februar 2015 um 22:10
> geschrieben:
>
>
> On Wed, Feb 11, 2015 at 6:31 PM, Stefan Wahren <stefan.wahren@...e.com> wrote:
>
> >> I always get 0x5e5b5513 with or without your patch.
> >
> > very strange. Do you have any idea why IO1_STABLE is permanent low?
>
> On my case it is always 1.

i expected the same behavior on my hardware.

Do you use u-boot as bootloader?

>
> > Can you confirm the behavior according to your flash issue?
>
> In my tests IO1_STABLE stays the same.

This wasn't the intension of my second question. I wanted to know about the
state of the SPI NOR flash detection process.

Does it sucessed if you apply the patch, but revert the changes in
clk_ref_set_rate() from clk-ref.c?

>
> > I think it would be the best to revert my patch. Sorry for the trouble.
>
> To be on the safe side, I agree.
>
> Could you please send a revert patch?

Sure.

>
> Thanks
>

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