narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - Publicly Logged on https://irclog.whitequark.org/linux-amlogic
vagrantc has quit [Quit: leaving]
sputnik__ has joined #linux-amlogic
sputnik__ has quit [Ping timeout: 240 seconds]
nickotheus has joined #linux-amlogic
TheAssassin has joined #linux-amlogic
TheAssassin has quit [Ping timeout: 240 seconds]
TheAssassin has joined #linux-amlogic
TheAssassin has quit [Ping timeout: 240 seconds]
TheAssassin has joined #linux-amlogic
TheAssassin has quit [Ping timeout: 240 seconds]
TheAssassin has joined #linux-amlogic
TheAssassin has quit [Ping timeout: 240 seconds]
TheAssassin has joined #linux-amlogic
sputnik__ has joined #linux-amlogic
TheAssassin has quit [Ping timeout: 240 seconds]
nickotheus has quit [Quit: Leaving]
TheAssassin has joined #linux-amlogic
TheAssassin has quit [Remote host closed the connection]
TheAssassin has joined #linux-amlogic
TheAssassin has quit [Ping timeout: 240 seconds]
TheAssassin has joined #linux-amlogic
buzzmarshall has quit [Remote host closed the connection]
_whitelogger has joined #linux-amlogic
TheAssassin has quit [Ping timeout: 240 seconds]
TheAssassin has joined #linux-amlogic
<lvrp16> this is out of scope but amlogic's sdk...*shakes fists*, so many errors.
<lvrp16> amazed that it can be certified for hailstorm and google with this many bugs
<lvrp16> narmstrong: upstream android is a warzone, downstream android is a minefield
TheAssassin has quit [Remote host closed the connection]
TheAssassin has joined #linux-amlogic
_whitelogger has joined #linux-amlogic
TheAssassin has quit [Ping timeout: 240 seconds]
<chewitt> I wonder how many board/device manufacturers are hoarding fixes for bugs in their offline repos due to no upstream target to send them to
<chewitt> I'm aware of a few who do try to fix stuff
TheAssassin has joined #linux-amlogic
TheAssassin has quit [Ping timeout: 240 seconds]
TheAssassin has joined #linux-amlogic
_whitelogger has joined #linux-amlogic
TheAssassin has quit [Ping timeout: 240 seconds]
damex has quit [Quit: damex]
damex has joined #linux-amlogic
TheAssassin has joined #linux-amlogic
TheAssassin has quit [Ping timeout: 240 seconds]
TheAssassin has joined #linux-amlogic
cmeerw has joined #linux-amlogic
TheAssassin has quit [Ping timeout: 240 seconds]
TheAssassin has joined #linux-amlogic
TheAssassin has quit [Ping timeout: 240 seconds]
TheAssassin has joined #linux-amlogic
TheAssassin has quit [Ping timeout: 240 seconds]
armoon has joined #linux-amlogic
<armoon> Hello chewitt
<armoon> some time Ethernet on odroid N2 dose not work
<armoon> some time Ethernet on odroid N2 dose not work, see the error below
<armoon> [ 5.423012] meson8b-dwmac ff3f0000.ethernet eth0: no phy at addr -1
<narmstrong> lvrp16: upstream Android never really changed, google doesn’t really try to be a true open source project, and AOSP is kept as a buildable, non-optimized, minimum featured version of their internal android frameworks, which is quite lame
<armoon> do you have a fix for this issue.
<narmstrong> lvrp16: it’s a shame since chromium and chrome does a nice work as a true open source upstream first project...
<narmstrong> *chromeos
<narmstrong> lvrp16: BTW chromeos should theoretically work with Lima & panfrost now
<chewitt> @armoon I've not seen any problems with Ethernet on N2
<narmstrong> armoon: I think we need much more details on your issue
<chewitt> I was experimenting with rgmii-id on some devices and a user reported broken Ethernet connected to a GB switch
<chewitt> I haven't seen the same issue, but most of the time I have devices connected to a WiFi bridge that presents 100-BaseT Ethernet
<chewitt> I dropped the patches from my recent changes
<chewitt> so not sure if GB vs 100-Base is relevant, and I'm not really capable of diagnosing anything in code
<armoon> on reboot suddenly Ethernet PHY dose not get initialized correctly, throwing with the above error
<chewitt> I haven't see it, sorry
<chewitt> s/see/seen
<armoon> @narmstrong by the way the VRTC rtc wakeup works perfectly with suspend / resume wakeup
<chewitt> ^ on N2
<chewitt> as a general comment, even if box/board devices don't have a power cell connected I see marginally faster reboot times with rtc enabled
<chewitt> if the device remains powered the rtc content is preserved
<chewitt> and if the device is cold cycled the error from having rtc enabled and no cell connected is harmless
<armoon> @chewitt suspend/resume it worked on 5.7.x kernel but it's broken in 5.8-rc kernel
<chewitt> I didn't really do much with 5.8 yet .. work has been busy
<chewitt> only basic testing with the stuff I sent upstream today
<armoon> with using VRTC but the timeline is 1970
<armoon> Thanks you very much. Yes I will test you patches on my device
TheAssassin has joined #linux-amlogic
armoon has quit [Remote host closed the connection]
TheAssassin has quit [Ping timeout: 240 seconds]
ccaione has joined #linux-amlogic
TheAssassin has joined #linux-amlogic
TheAssassin has quit [Ping timeout: 240 seconds]
TheAssassin has joined #linux-amlogic
<lvrp16> narmstrong: good to know. Maybe I will give Chrome OS a try when I am done.
sputnik__ has quit [Ping timeout: 258 seconds]
armoon has joined #linux-amlogic
drieschel has joined #linux-amlogic
<armoon> narmstrong I have tested this https://patchwork.kernel.org/patch/11660165/ patch on C4 but it's fails to recognize the usb device. This Odroid C4 hangs when booting up here is the boot log https://pastebin.com/s5bcuJS https://patchwork.kernel.org/patch/11660165/
<armoon> Hope you could reproduce this at your end.
drieschel has quit [Quit: drieschel]
<armoon> here is the link to boot logs https://pastebin.com/s5bcuJSF
<armoon> On Odroid N2 this patch works.
sputnik__ has joined #linux-amlogic
TheAssassin has quit [Ping timeout: 240 seconds]
TheAssassin has joined #linux-amlogic
sputnik_ has joined #linux-amlogic
sputnik__ has quit [Ping timeout: 260 seconds]
TheAssassin has quit [Ping timeout: 240 seconds]
PurpleCow4u has joined #linux-amlogic
TheAssassin has joined #linux-amlogic
sputnik_ has quit [Ping timeout: 240 seconds]
TheAssassin has quit [Ping timeout: 240 seconds]
TheAssassin has joined #linux-amlogic
drieschel has joined #linux-amlogic
drieschel has quit [Client Quit]
drieschel has joined #linux-amlogic
drieschel has quit [Client Quit]
buzzmarshall has joined #linux-amlogic
armoon has left #linux-amlogic [#linux-amlogic]
TheAssassin has quit [Ping timeout: 240 seconds]
TheAssassin has joined #linux-amlogic
sputnik_ has joined #linux-amlogic
TheAssassin has quit [Ping timeout: 240 seconds]
TheAssassin has joined #linux-amlogic
drieschel has joined #linux-amlogic
PurpleCow4u has quit [Quit: geht mal an die frische Luft...]
vagrantc has joined #linux-amlogic
drieschel has quit [Quit: drieschel]
TheAssassin has quit [Ping timeout: 240 seconds]
TheAssassin has joined #linux-amlogic
drieschel has joined #linux-amlogic
drieschel has quit [Quit: drieschel]
drieschel has joined #linux-amlogic
cmeerw has quit [Ping timeout: 256 seconds]
drieschel has quit [Client Quit]
vagrantc has quit [Remote host closed the connection]
vagrantc has joined #linux-amlogic
drieschel has joined #linux-amlogic
drieschel has quit [Quit: drieschel]
ldevulder_ has joined #linux-amlogic
ldevulder has quit [Ping timeout: 240 seconds]
TheAssassin has quit [Remote host closed the connection]
TheAssassin has joined #linux-amlogic