warpme_ has quit [Quit: Connection closed for inactivity]
kaspter has quit [Ping timeout: 260 seconds]
kaspter has joined #linux-amlogic
buzzmarshall has quit [Remote host closed the connection]
kaspter has quit [Ping timeout: 260 seconds]
kaspter has joined #linux-amlogic
Barada has joined #linux-amlogic
chewitt has quit [Read error: Connection reset by peer]
chewitt has joined #linux-amlogic
chewitt has quit [Read error: Connection reset by peer]
chewitt has joined #linux-amlogic
warpme_ has joined #linux-amlogic
ldevulder_ has joined #linux-amlogic
ldevulder has quit [Ping timeout: 246 seconds]
Elpaulo has quit [Read error: Connection reset by peer]
Elpaulo has joined #linux-amlogic
Elpaulo has quit [Quit: Elpaulo]
sputnik__ has quit [Ping timeout: 264 seconds]
yann|work is now known as yann
buzzmarshall has joined #linux-amlogic
Barada has quit [Quit: Barada]
yann has quit [Ping timeout: 260 seconds]
yann has joined #linux-amlogic
yann has quit [Read error: No route to host]
<lvrp16>
narmstrong: is the g12 sdio problem resolved?
<narmstrong>
lvrp16: it was but at the time we pushed the fix the upstream brcmfmac driver was not working with the module, so the issue appeared later and took a (very) long time on mu side to push...
<lvrp16>
sd and sdio are fully functional without problems or performance issues?
<lvrp16>
or is it still using a workaround at the detriment of perf?
kaspter has quit [Ping timeout: 240 seconds]
kaspter has joined #linux-amlogic
yann has joined #linux-amlogic
kaspter has quit [Ping timeout: 256 seconds]
kaspter has joined #linux-amlogic
sputnik__ has joined #linux-amlogic
Elpaulo has joined #linux-amlogic
<narmstrong>
It affects performance
<narmstrong>
The amlogic first fix was to use the sdcard controller and use it for sd and sdio with an ugly routing hack, they have better performance with this but it’s very complex to implement and impossible to upstream
Elpaulo has quit [Quit: Elpaulo]
warpme_ has quit [Quit: Connection closed for inactivity]