<warpme>
apritzel: if you have working sharing emmc to PC via uboot ums: may you pls give what: uboot ver, PC kernel ver, PC OS you are using? On my current Fedora with 6.8.4 kernel I'm constantly getting in PC dmesg "device descriptor read/64, error -71" then "usb 1-3: Device not responding to setup address."
<Jookia>
good news everyone, i was preparing my t113 rgb code for submission and found out it doesn't work and none of my previous git commits work
<machinehum>
Jookia: :(
<Jookia>
you have to believe me, it worked. it was real. ;_;
<karlp>
I love those days :)
<karlp>
I'm betting you had somethign setup by uboot or something that you didn't know you were relying on :)
<Jookia>
yes, which is why i also commited my config and device tree to a temp branch ... that isn't working
<dok>
ouch
Jookia has quit [Read error: Connection reset by peer]
Jookia has joined #linux-sunxi
bauen1 has joined #linux-sunxi
<Jookia>
it works if i env set stdout to vidconsole
<Jookia>
so ... hmm
dsimic is now known as Guest1154
dsimic has joined #linux-sunxi
Guest1154 has quit [Ping timeout: 480 seconds]
bauen1_ has joined #linux-sunxi
bauen1 has quit [Ping timeout: 480 seconds]
Schimsalabim has quit [Read error: Connection reset by peer]
Schimsalabim has joined #linux-sunxi
<apritzel>
warpme: "limiting eMMC frequency to 12 MHz": thanks for the link, but that's a hack ;-) It sounds wrong, since it works fine with the full speed in Linux, and that's supposed to share the DT with U-Boot
<apritzel>
which btw is a good way to simplify your distro deployment: just use $fdtcontroladdr in U-Boot when passing a DT address to Linux, no need to load some DTB
<Jookia>
it looks like i need to set vidconsole as an stdout/etc to boot the panel?
<Jookia>
but i just want to display an image :(
<apritzel>
Jookia: I guess U-Boot's graphics subsystem only initialises the display if it sees vidconsole in stdout?