iyzsong has quit [Read error: Connection reset by peer]
<damex>
i think this might be the most active channel to get support around sunxi or sbcs in general
<KotCzarny>
are there any other channels about sunxi?
<damex>
about sbcs - gentoo ones are pretty active
<KotCzarny>
asking about sunxi specifically, just curious if there are any
<damex>
i see there people with sunxi boards
<damex>
we;
<mru>
I guess most people messing with these kinds of things would haev a sunxi board or two by now
<damex>
well, my pain now is testing builds on real sbcs - is there better way to do so without poe switch and microusb/barrel plug poe splitter?
<damex>
i wany
<damex>
i want to pick few dozens of them for video capture ;)
<damex>
so keeping things up to date might be a huge pita
<DuClare>
Not sure I understand what exactly the challenge is.. power delivery?
<mru>
lots of ways of doing that
<damex>
something like - trigger build, build uboot/rootfs/kernel and trigger power on sbc
<damex>
then sbc boots from what you just build
<mru>
I'm sure someone sells a board with a bunch of usb controlled relays
<DuClare>
And if you don't mind booting all boards at once.. there are radio controlled relays
<DuClare>
I mean for standard power plugs
<KotCzarny>
netboot
<KotCzarny>
or fel-boot
<KotCzarny>
netboot + some controllable hardware power switch is best tho
<damex>
i think about pxe boot. not sure how to deal with testing uboot updates.
<KotCzarny>
you dont have to mess with uboot
<KotCzarny>
its stable enough so just focus on kernel/rootfs
<damex>
so with poe - boards will have poe splitter (problematic). probably would be a good idea to make custom rackmount case to hold boards + splitters in place (no zipties)
<damex>
i have been thinking - maybe gpio ? it will still be needed for debug
macc24 has quit [Quit: WeeChat 2.8]
macc24 has joined #linux-sunxi
sunshavi has quit [Ping timeout: 240 seconds]
yann has joined #linux-sunxi
putti_ has joined #linux-sunxi
Putti has quit [Ping timeout: 260 seconds]
cnxsoft has quit [Quit: cnxsoft]
aloo_shu has joined #linux-sunxi
macc24 has quit [Quit: WeeChat 2.8]
putti_ has quit [Changing host]
putti_ has joined #linux-sunxi
putti_ is now known as Putti
grw has joined #linux-sunxi
macc24 has joined #linux-sunxi
ats_ has quit [Quit: leaving]
atsampson has joined #linux-sunxi
sunshavi has joined #linux-sunxi
gaston1980 has joined #linux-sunxi
dddddd has joined #linux-sunxi
macc24 has quit [Quit: WeeChat 2.8]
<montjoie>
damex: for testing builds on real sbcs, you should use LAVA
<montjoie>
damex: you could read kernelci documentation
<damex>
montjoie: thanks, will read that. i didn't knew there were already something for that purpose :)
<montjoie>
for each board you need serial and a PDU
macc24 has joined #linux-sunxi
<montjoie>
the hard part is reliable PDU
andy25225 has quit [Ping timeout: 260 seconds]
<montjoie>
related to the budget you can invest in it
<Zerogoki>
I updated u-boot to 2020.01 version and screen started working but my tablet simply turns off after this line of log "[ 1.435061] sun5i-pinctrl 1c20800.pinctrl: 1c20800.pinctrl supply vcc-pd not found, using dummy regulator"
<mru>
the whole tablet or just the display?
<Zerogoki>
The whole tablet
<mru>
what tablet is it?
<Zerogoki>
I already had this problem in past and solved it by downgrading to uboot 2015.10
<mru>
and what devicetree are you using? is it known good?
<Zerogoki>
I use sun5i-a13-q8-tablet.dtb
<gediz0x539>
any chance that tablet is powered with a supply something other than axp?
<gediz0x539>
because I have a board like that
<gediz0x539>
and I use olinuxino-micro dts to bringup my board. olinuxino micro a13 does not have an axp.
<Zerogoki>
I tried this dts and it works now!
<Zerogoki>
It's powered by battery and usb charger
<gediz0x539>
what about regulator? there may be an IC marked AXP209
<Zerogoki>
Do you have wifi working?
<gediz0x539>
nope
<Zerogoki>
Where is regulator located?
<gediz0x539>
probably close to the usb connector, I guess
<Zerogoki>
Yeah, I see it
<Zerogoki>
It's not close to usb connector btw
<gediz0x539>
oh okay
<Zerogoki>
AXP209 DC110CB 61L1
<gediz0x539>
its strange how would it work with a device tree which does not include power supply configuration
<gediz0x539>
you better try to use it with tablet's own device tree. I really have no idea but ignoring power supply settings still does not sound like something reasonable.
<gediz0x539>
maybe diff them and patch the difference
RichardG867 has quit [Read error: Connection reset by peer]
<gediz0x539>
Zerogoki: I've compiled 5.7 kernel and it boots. uname -a -> Linux gediz 5.6.0 #1 SMP Sun May 10 22:21:34 +03 2020 armv7l GNU/Linux
<gediz0x539>
sorry, 5.6
<Zerogoki>
It already boots for too after changing device tree
<gediz0x539>
cool then
matterway has quit [Quit: Leaving]
matterway has joined #linux-sunxi
noblock has joined #linux-sunxi
noblock has quit [Client Quit]
noblock has joined #linux-sunxi
noblock has quit [Client Quit]
noblock has joined #linux-sunxi
matterway has quit [Client Quit]
matterway has joined #linux-sunxi
<matterway>
I'm experimenting with a Tanix TX6 (H6 + linux 5.6); The hdparm -t /dev/mmc is very slow: <2MB/s; Did you have trouble with the mmc speed?
noblock has quit [Client Quit]
aloo_shu has quit [Ping timeout: 256 seconds]
<gediz0x539>
not the same soc but this is what I get on 5.6 with a cheap sd card: /dev/mmcblk0: Timing buffered disk reads: 67 MB in 3.02 seconds = 22716 kB/s
<matterway>
I've no trouble with my Orange Pi PC2 (H5) using the same kernel: ~20MB/s
<Zerogoki>
Please help, I have problem with wifi on Allwinner A13 Forfun Q88DB tablet (RTL8188EUS adapter). I'm running 5.6 kernel and adapter doesn't even get listed in lsusb output. How can I fix it?
lkcl has joined #linux-sunxi
<Zerogoki>
USB keyboard doesn't get listed too. Looks like it's general problem with usb
<Zerogoki>
UPD: it works not. Device tree was causing problen
matthias_bgg has quit [Ping timeout: 256 seconds]
lurchi__ is now known as lurchi_
lkcl has quit [Remote host closed the connection]
<Zerogoki>
My WiFi FINALLY works!
jstein has quit [Quit: quit]
<sunshavi>
Zerogoki: nice to know. Yesterday I had a similar problem booting opipc using uSD for booting from usb. I am going to debug and see which dtb is being picked
<Zerogoki>
Do you know how to make usb keayboard work? I think I simply miss something in kernel configuration.
<sunshavi>
during u-boot process it is not recognized. Just after kernel start it works
<Zerogoki>
It doesn't work for me in kernel
<sunshavi>
lsusb?
<Zerogoki>
Bus 001 Device 002: ID 0bda:0179 Realtek Semiconductor Corp. RTL8188ETV Wireless LAN 802.11n Network AdapterBus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubBus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
lurchi_ is now known as lurchi__
<Zerogoki>
I doesn't get listed in usb devices
<sunshavi>
you are right. It is the only device not listed. Does it recognizes pendrives?
<Zerogoki>
It doesnt (connected using usb otg cable)
<sunshavi>
have You changed the mode for otg on the dts?
<Zerogoki>
How can I change it?
<sunshavi>
search on dts for "dr_mode = otg" and change it to "dr_mode = host"
ldevulder has joined #linux-sunxi
ldevulder_ has quit [Ping timeout: 272 seconds]
<Zerogoki>
My dts doesn't contain this so I just copypasted it from another dts with dr_mode and changed to "host". Still doesn't work
<Zerogoki>
I have FEX file from original android system. Maybe it can help?
<Zerogoki>
I'm an idiot
<Zerogoki>
USB was unavailable because I started tablet with charged inserted
<Zerogoki>
charger*
<Zerogoki>
u-boot marked port as already used and it was unavailable for linux even when I disconnected charger and connected keyboard
\\Mr_C\\ has joined #linux-sunxi
gaston1980 has quit [Ping timeout: 246 seconds]
Zerogoki has quit [Ping timeout: 245 seconds]
reinforce has quit [Quit: Leaving.]
<aloo_shu>
he, I had been following this
<aloo_shu>
at least learned what the reason was
<aloo_shu>
so, not too idiotic from my perspective ;)