ballerburg9005 has quit [Ping timeout: 246 seconds]
warpme_ has quit [Quit: Connection closed for inactivity]
buzzmarshall has joined #linux-amlogic
asdf28 has quit [Ping timeout: 240 seconds]
kaspter has joined #linux-amlogic
chewitt_ has joined #linux-amlogic
chewitt has joined #linux-amlogic
chewitt_ has quit [Ping timeout: 256 seconds]
<BlueMatt>
narmstrong: thanks!
buzzmarshall has quit [Quit: Leaving]
ballerburg9005 has joined #linux-amlogic
Barada has joined #linux-amlogic
sputnik_ has joined #linux-amlogic
sputnik__ has quit [Ping timeout: 264 seconds]
vagrantc has quit [Quit: leaving]
kaspter has quit [Ping timeout: 256 seconds]
kaspter has joined #linux-amlogic
_whitelogger has joined #linux-amlogic
chewitt has quit [Quit: Adios!]
asdf28 has joined #linux-amlogic
cmeerw has joined #linux-amlogic
Barada has quit [Quit: Barada]
Tony_mac32 has joined #linux-amlogic
Tonymac32 has quit [Ping timeout: 264 seconds]
cmeerw has quit [Ping timeout: 265 seconds]
Elpaulo has quit [Read error: Connection reset by peer]
Elpaulo has joined #linux-amlogic
kaspter has quit [Ping timeout: 265 seconds]
kaspter has joined #linux-amlogic
ldevulder__ is now known as ldevulder
ballerburg9005 has quit [Ping timeout: 256 seconds]
sputnik_ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
sputnik__ has joined #linux-amlogic
sputnik_ has quit [Ping timeout: 265 seconds]
sputnik__ has quit [Ping timeout: 256 seconds]
<benoitm974>
Anyone succeeded in using the RTC clock ? I get timeout when I try to read or write to it with hwclock?
kaspter has quit [Ping timeout: 265 seconds]
camus1 has joined #linux-amlogic
camus1 is now known as kaspter
warpme_ has joined #linux-amlogic
montjoie has joined #linux-amlogic
<narmstrong>
benoitm974: I don’t see what you’re speaking about
sputnik_ has joined #linux-amlogic
psydruid has quit [Quit: Bridge terminating on SIGTERM]
l-as has quit [Quit: Bridge terminating on SIGTERM]
l-as has joined #linux-amlogic
asdf28 has quit [Ping timeout: 246 seconds]
psydruid has joined #linux-amlogic
asdf28 has joined #linux-amlogic
trem has joined #linux-amlogic
sputnik__ has joined #linux-amlogic
sputnik_ has quit [Ping timeout: 240 seconds]
sputnik_ has joined #linux-amlogic
sputnik__ has quit [Ping timeout: 240 seconds]
trem has quit [Remote host closed the connection]
sputnik__ has joined #linux-amlogic
sputnik_ has quit [Ping timeout: 260 seconds]
sputnik__ has quit [Remote host closed the connection]
asdf28 has quit [Ping timeout: 265 seconds]
chewitt has joined #linux-amlogic
ldevulder_ has joined #linux-amlogic
ldevulder has quit [Ping timeout: 260 seconds]
<benoitm974>
narmstrong: The dtb define a realtime clock using module meson-vrtc (it is also in the android the dtb dump) but it when you try to set or get time it fails.
<chewitt>
in my kernel # CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
<benoitm974>
I'm not sure you want to have a code reading your "virtual" clock multiple time per second just to offer ioctl in the correct RTC_UIE right ?
<narmstrong>
well, it's the same if the physical RTC doesn't have an interrupt line connected to the SoC, there is no way to have a regular time update
cmeerw has joined #linux-amlogic
vagrantc has joined #linux-amlogic
GNUtoo has joined #linux-amlogic
<benoitm974>
quickly tested with the kernel option to 'y' same result: