On 31.05.2015 23:34, Chanho Park wrote:
The odroid-xu3 board which is based on exynos5422 not exynos5800 is
booted from cortex-a7 core unlike exynos5800. The odroid-xu3's cpu order
is quite strange. cpu0 and cpu5-7 are cortex-a7 cores and cpu1-4 are
cortex-a15 cores. To correct this
'struct timeval' uses a 32-bit seconds representation which
will overflow in the year 2038 and beyond. This patch
replaces the use of struct timeval with struct timespec64
which uses a 64-bit seconds representation and is y2038 safe.
The patch is part of a larger effort to remove all 32-bit
'struct timeval' uses a 32-bit seconds representation which
will overflow in the year 2038 and beyond. This patch
replaces the use of struct timeval with struct timespec64
which uses a 64-bit seconds representation and is y2038 safe.
The patch is part of a larger effort to remove all 32-bit
Dear Arnd and Olof,
This is fix from April which should be applied before [0].
Apparently it was missed. I am sending it to you guys because
Kukjin seems to be busy.
Best regards,
Krzysztof
[0] http://www.spinics.net/lists/linux-samsung-soc/msg44937.html
The following changes since commit
On 05/30/2015 06:33 AM, Gustavo Padovan wrote:
2015-05-29 Joonyoung Shim jy0922.s...@samsung.com:
On 05/29/2015 06:36 AM, Gustavo Padovan wrote:
2015-05-28 Joonyoung Shim jy0922.s...@samsung.com:
On 05/28/2015 05:24 PM, Joonyoung Shim wrote:
On 05/28/2015 02:39 PM, Inki Dae wrote:
Hi
'struct timeval' uses a 32-bit seconds representation which
will overflow in the year 2038 and beyond. This patch
replaces the use of struct timeval with struct timespec64
which uses a 64-bit seconds representation and is y2038 safe.
The patch is part of a larger effort to remove all 32-bit
Hi Tina,
On Mon, Jun 01, 2015 at 08:43:08AM +0530, Tina Ruchandani wrote:
'struct timeval' uses a 32-bit seconds representation which
will overflow in the year 2038 and beyond. This patch
replaces the use of struct timeval with struct timespec64
which uses a 64-bit seconds representation and
2014-06-25 21:42 GMT+09:00 Vivek Gautam gautam.vi...@samsung.com:
Facilitate getting required 3.3V and 1.0V VDD supply for
EHCI controller on Exynos.
With the patches for regulators' nodes merged in 3.15:
c8c253f ARM: dts: Add regulator entries to smdk5420
275dcd2 ARM: dts: add max77686 pmic
2015-05-31 2:32 GMT+09:00 gabr...@unseen.is:
Hello,
I've been successfully using a self compiled linux kernel until version
3.19 together with Debian Stretch.
After upgrading the kernel to version 4.0 I see strange messages in the
logs i.e.
May 27 22:44:01 pulseaudio[1027]:
2015-05-30 22:53 GMT+09:00 Anand Moon linux.am...@gmail.com:
On 28 May 2015 at 14:49, Krzysztof Kozlowski k.kozlow...@samsung.com wrote:
On 28.05.2015 17:58, Anand Moon wrote:
Enable regulator for usbdrd3_0 and usbdrd3_1
From the schematic pin diagram USB3_0 and USB3_1
is regulated by LDO9 and
2015-05-28 17:43 GMT+09:00 Chanho Park chanho61.p...@samsung.com:
Hi,
When adding new 5422 board we can split out CPU configuration to
separate DTSI file. I already posted patches for Odroid XU3-family
common DTSI file for XU3 Lite board:
The odroid-xu3 board which is based on exynos5422 not exynos5800 is
booted from cortex-a7 core unlike exynos5800. The odroid-xu3's cpu order
is quite strange. cpu0 and cpu5-7 are cortex-a7 cores and cpu1-4 are
cortex-a15 cores. To correct this mis-odering, I added exynos5422.dtsi
and reversing cpu
12 matches
Mail list logo
