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, 6 Nov 2014 10:53:19 -0600
From:	Nishanth Menon <nm@...com>
To:	Tony Lindgren <tony@...mide.com>
CC:	Tom Rini <trini@...com>, <balbi@...com>,
	<devicetree@...r.kernel.org>, <beagleboard@...glegroups.com>,
	<linux-kernel@...r.kernel.org>, <gerald@...nddesignsgroup.com>,
	<fcooper@...com>, <linux-omap@...r.kernel.org>,
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] ARM: dts: Add am57xx-beagle-x15

On 11/06/2014 10:48 AM, Tony Lindgren wrote:
> * Nishanth Menon <nm@...com> [141106 08:44]:
>> On 11/06/2014 10:37 AM, Tom Rini wrote:
>>
>>>>> device_type = "memory"; +		reg = <0x80000000 0x40000000>; /* 1GB
>>>>> to start. Target 2GB */
>>>>
>>>> 1GiB ? Why would you put this here btw ? u-boot fills this one up.
>>>
>>> Yes, it should either be the full and correct value or 0x0 (like a
>>> number of PowerPC platforms do) so it's clear something else gives us
>>> the right value here.
>>
>> Honest mistake, my bad.. I thought I cleaned up the patch! Sigh!!! i
>> will repost with proper 2GB. it is better that way in case being used
>> with "other bootloaders" which are not exactly too good like u-boot.
> 
> Can you also describe why all the always-on regulators are needed?
yep - will do that similar to
https://patchwork.kernel.org/patch/5125431/ - same rationale unless
there is any specific voltage rail that you are explicitly interested
in that needs additional explanation. Is there additional rails of
interest?



-- 
Regards,
Nishanth Menon
--
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