Ntemis has quit [Remote host closed the connection]
dave0x6d has joined #linux-sunxi
florianH has quit [Quit: Connection closed for inactivity]
lurchi__ is now known as lurchi_
afaerber has quit [Quit: Leaving]
lkcl has quit [Ping timeout: 258 seconds]
Hao has joined #linux-sunxi
chomwitt has quit [Ping timeout: 240 seconds]
lurchi_ has quit [Quit: Konversation terminated!]
lurchi_ has joined #linux-sunxi
Hao has quit [Remote host closed the connection]
cnxsoft has joined #linux-sunxi
ninolein has joined #linux-sunxi
ninolein_ has quit [Ping timeout: 258 seconds]
sgteem_ has joined #linux-sunxi
Hao has joined #linux-sunxi
sgteem has quit [Ping timeout: 240 seconds]
Andy-D_ has quit [Ping timeout: 240 seconds]
<willmore>
KotCzarny, not bad connector placement. Power, HDMI, ethernet (if any), and some USB out the back and uSD card and USB( if any left) out the front.
apritzel has quit [Ping timeout: 246 seconds]
egbert has quit [Disconnected by services]
egbert has joined #linux-sunxi
terra854 has joined #linux-sunxi
lurchi_ is now known as lurchi__
lurchi__ is now known as lurchi_
lurchi_ is now known as lurchi__
pg12 has quit [Ping timeout: 260 seconds]
pg12 has joined #linux-sunxi
wzyy2 has joined #linux-sunxi
dave0x6d has quit [Quit: Connection closed for inactivity]
victhor has quit [Ping timeout: 268 seconds]
JohnDoe_71Rus has joined #linux-sunxi
leviathancn has joined #linux-sunxi
lurchi_ has joined #linux-sunxi
lurchi__ has quit [Ping timeout: 240 seconds]
cnxsoft has quit [Read error: Connection reset by peer]
<ssvb>
lkcl: you still seem to be able to edit the wiki, so I don't quite understand why you can't or unwilling to provide a bit more details about your NAND problems
<ssvb>
lkcl: wiki is an excellent collaboration tool for sharing information, you could improve it a lot by providing the information about the exact NAND IC model(s) that you were having problems with
<ssvb>
lkcl: just a generalized claim that "it aint work" looks like a FUD
Guest54298 has quit [Quit: ChatZilla 0.9.93 [Firefox 51.0.1/20170125094131]]
<ssvb>
lkcl: and BTW, nobody is forcing you to use the mailing list, because the wiki is a much better place for sharing this kind of information
<KotCzarny>
(or irc?, which is also permanently remembered, searchable)
<ssvb>
KotCzarny: nope, irc logs are a pain to search
<ssvb>
wiki is a lot more structured than irc or mailing list archives
<KotCzarny>
but still, better than no info, and remember most people here trace the backlog daily
<ssvb>
yeah, irc is good to discuss something in real time
<ssvb>
but it would be best if lkcl could just add a table to the wiki with the list if NAND chips which do not work for him on A20
<ssvb>
we also can't rule out the possibility that lkcl just did not flash these chips correctly, so step by step instructions about how to reproduce the failure would be welcome too
<KotCzarny>
offtopic, is there a way to find out details of the socket in linux? in /proc/pid/fd/number there is 'socket:[149311]'
<beeble>
KotCzarny: lsof?
<KotCzarny>
ss doesnt even list it
<KotCzarny>
beeble: thanks! found it
<KotCzarny>
now, how can i nudge it to check if it's still valid? it's in ESTABLISHED state but libav is stuck (my ip changed in the meantime)
apritzel has joined #linux-sunxi
Andy-D_ has joined #linux-sunxi
scream has joined #linux-sunxi
Net147 has quit [Read error: Connection reset by peer]
Mr__Anderson has quit [Remote host closed the connection]
mzki_ has quit [Quit: leaving]
Andy-D_ has quit [Ping timeout: 246 seconds]
IgorPec has joined #linux-sunxi
JohnDoe_71Rus has quit [Ping timeout: 260 seconds]
marvs has quit [Read error: Connection reset by peer]
_whitelogger has joined #linux-sunxi
netlynx has joined #linux-sunxi
foxx has joined #linux-sunxi
foxx has quit [Ping timeout: 258 seconds]
vagrantc has joined #linux-sunxi
jernej has joined #linux-sunxi
<MoeIcenowy>
jernej: someone posted some document of DW HDMI from DesignWare here
<MoeIcenowy>
I downloaded, checked and found no confidential mark
<jernej>
MoeIcenowy: It still says confidential on second page
<MoeIcenowy>
？
<jernej>
under "copyright notice and proprietry information"
<MoeIcenowy>
P.S. I tried to manually override the different registers on broken U-Boot
<MoeIcenowy>
it didn't work.
<jernej>
but anyway, the only new thing which is not described in a imx6 manual, it would be i2s audio transport, but that is already implemented in kernel driver
<MoeIcenowy>
is there any magic bits that is needed to update the configuration?
<KotCzarny>
doesnt allwinner docs say confidential too on quite a few of them?
<jernej>
MoeIcenowy: then it might be timing issue. Can you enable debug output in DE2 and sunxi driver? It slowed execution just enough to work when I worked on it, before I add wait on clock stabilization.
<jernej>
eh, hdmi driver
scream has quit [Remote host closed the connection]
<jernej>
KotCzarny: true, but because IANAL, I don't know what is considered safe to use
reinforce has joined #linux-sunxi
chomwitt has joined #linux-sunxi
<jernej>
MoeIcenowy: did you set driver to 32 bpp? Maybe that will help
<MoeIcenowy>
both 16 bpp and 32 bpp do not work
<MoeIcenowy>
jernej: I seem to get only 3 lines of debug info
Ntemis has quit [Remote host closed the connection]
LargePrime has joined #linux-sunxi
lurchi__ is now known as lurchi_
apritzel has joined #linux-sunxi
<apritzel>
MoeIcenowy: I have 0xb591 in my code, but that's just some number, AFAIK there is no explanation
<MoeIcenowy>
P.S. is there any method to do MDIO in userspace?
<MoeIcenowy>
I'm curious about the initial value ;-)
<beeble>
linux does not have userspace mdio interface. there are drivers floating around exposing it to uesrland. or you could write it yourself. if you are interested in initial values maybe uboot is good enough for you?
<beeble>
there is a mdio command available
<MoeIcenowy>
wow thx
<MoeIcenowy>
apritzel: the default value seems to be 0x8575
<MoeIcenowy>
too many bits are different
<MoeIcenowy>
no help.
<apritzel>
MoeIcenowy: It's a kind of magic ...
<MoeIcenowy>
yes...
victhor has joined #linux-sunxi
<MoeIcenowy>
I hope the driver maintainer can accept the magic numbers
<MoeIcenowy>
as they really work, although we cannot tell why
<apritzel>
MoeIcenowy: does it have a negative effect on the working PHYs?
<MoeIcenowy>
maybe some performance issues
<MoeIcenowy>
but as I don't really use the ethernet function in production, I cannot judge it
<MoeIcenowy>
(and even my kernel images are sent to one of my friends as I do not have broken PHYs
f0xx has joined #linux-sunxi
<MoeIcenowy>
apritzel: P.S. will you push 32-bit SPL patchset to mainline u-boot?
<BenG83>
as far as I understood what Tl said the Realtek engineer did was disable internal delay tuning for RX
<BenG83>
this has nothing to do with the normal delay tuning though
<KotCzarny>
ssvb, my idea was to create simple-pill-for-pasting-to-articles-about-how-things-are-in-allwinner-land
<ssvb>
also we can't really expect to have unbiased information about other SoCs at the linux-sunxi wiki :-)
<MoeIcenowy>
KotCzarny: for the states, I think we should have some more
<MoeIcenowy>
e.g. "officially closed, reverse enginerring WIP"
<MoeIcenowy>
and this status can be divided into "RE result mature" and "RE result not mature"
<KotCzarny>
moeicenowy: that could be added as notes/references imo, not to overload the table with info
<MoeIcenowy>
but this situation sometimes belong to no existed option
<MoeIcenowy>
for example, the status of A64 DRAM -- we have some supports, but not as good as the official one (e.g. lack of LPDDR3 support in at least denx's repo)
<KotCzarny>
in cases where open source driver is wip/not working well, i guess it would be 'closed source or blobbed only', and a note that work is being done, or just update it once it hits mainline
<KotCzarny>
ssvb, our bias cant be worse than any random/phoronix article
<apritzel>
MoeIcenowy: yes, I was thinking the same
<MoeIcenowy>
apritzel: this answer is about 32-bit spl?
<apritzel>
for the DRAM controller we have something that works (for H3/H5/A64/R40), but I wouldn't say that we have full understanding
<apritzel>
MoeIcenowy: no: about that Wiki page
<MoeIcenowy>
I agree
<KotCzarny>
does it work well?
<apritzel>
KotCzarny: define: "well"
<MoeIcenowy>
P.S. when I went to AW they mentioned they will largely change the DRAM controller when adding LPDDR4 support
<KotCzarny>
no issues, breakages, hangs, does what its supposed to do (ie. initialize hardware)
<MoeIcenowy>
I'm very worried...
<apritzel>
KotCzarny: I am pretty sure the code is wrong in places, also we leave performance and reliability on the table
maik_ has joined #linux-sunxi
<MoeIcenowy>
I think the status is "it works; but it can surely work much better"
<KotCzarny>
regarding performance and reliability, it is worse than aw blob?
<apritzel>
KotCzarny: who knows?
<apritzel>
did somebody did elaborate testing?
<KotCzarny>
benchmarks? stability-testers?
<BenG83>
not for A64 I think? I looked at what was done for A10/A20 on the wiki
<apritzel>
BenG83: indeed
<maik_>
Hi, i like to use the analog audio output of the nanopiNEO. Should this work with buildroot + linux-4.11-rc3 out of the box?
<MoeIcenowy>
maik_: seems no...
<MoeIcenowy>
I remember the audio pins are only available with expand pins...
<MoeIcenowy>
that will mean you may need some device tree change
<KotCzarny>
moeicenowy: have you seen nanopi air audio board?
<MoeIcenowy>
KotCzarny: nope
<maik_>
But this was planed for the 4.11 "Audio codec device tree changes"
<MoeIcenowy>
maik_: yes, but our maintainer do not like to add functions directly to the device tree, when it's not available without expansion boards
<apritzel>
MoeIcenowy: re: 32-bit SPL: I have other stuff higher in my priority list
<apritzel>
MoeIcenowy: I think we need to find a way to use the same defconfig for both bitnesses
<maik_>
But the analog pins are available without any extension board!
<MoeIcenowy>
maik_: the standard connector is not available
<MoeIcenowy>
you can refer to arch/arm/boot/dts/sun8i-h3-orangepi-pc.dts for chapter &codec
<KotCzarny>
it's for nanopi air
<MoeIcenowy>
and try to adapt this part to arch/arm/boot/dts/sun8i-h3-nanopi.dtsi
<maik_>
No, i am talking about the nanopi NEO. Its hase a analog LINEOUT. These pins are working with the default image. But i like to use buildroot + mainline kernel.
<MoeIcenowy>
maik_: nanopi m1 and nanopi neo both uses sun8i-h3-nanopi.dtsi
<MoeIcenowy>
so you can enable it there
<MoeIcenowy>
and I mention the opi pc device tree for a reference
<MoeIcenowy>
mripard: may we enable unmuxed pins that is available via expansion connectors by default?
<MoeIcenowy>
I think this problem at least exists on Nano Pi NEO and Orange Pi Zero
jernej has joined #linux-sunxi
<MoeIcenowy>
or if we cannot, at least our community should maintain a repository for all official expansion boards' device tree overlays
LargePrime has quit [Ping timeout: 240 seconds]
<apritzel>
MoeIcenowy: actually we should have such a DT repo in any case
LargePrime has joined #linux-sunxi
<apritzel>
because having DTs for each and every *board* in the kernel isn't strictly necessary
<maik_>
So i have to add this block "&codec {allwinner,audio-routing ="Line Out", "LINEOUT", ... };" in arch/arm/boot/dts/sun8i-h3-nanopi.dtsi. This will enable the analog pins?
cloud-e has quit [Ping timeout: 264 seconds]
<apritzel>
shall we create another repo in github/linux-sunxi?
<MoeIcenowy>
maik_: I think so.
pg12 has quit [Ping timeout: 260 seconds]
pg12 has joined #linux-sunxi
f0xx has quit [Ping timeout: 240 seconds]
netlynx has quit [Quit: Ex-Chat]
<maik_>
When I add "&codec {allwinner,audio-routing ="Line Out", "LINEOUT", ... };", then the sound card disapears in /proc/asound/cards? http://pastebin.com/GWxBcHwm
apritzel has quit [Ping timeout: 240 seconds]
<MoeIcenowy>
maik_: have you enabled sun4i-codec and sun8i-analog-codec drivers?
<ssvb>
lkcl: if you think that you can provide some constructive input, such as the real-world examples of problematic NAND ICs, then it would surely improve the page and help other people to avoid problems
<ssvb>
lkcl: feel free to ping me on IRC if you want to discuss something
<KotCzarny>
its legacy kernel, abandoned and smelly
<KotCzarny>
Latest commit d47d367 on Feb 20, 2015
<yann-kaelig>
KotCzarny, HI, I know that, but actually there is nothing correct for MALI GPU 400 on mainline
<KotCzarny>
wasnt there a patch for mainline?
vinimac has joined #linux-sunxi
lurchi_ has joined #linux-sunxi
<yann-kaelig>
a patch for what ? I need 3D acceleration for gpu mali400.
<KotCzarny>
or even a;lready integrated
<KotCzarny>
btw. mali is only 3d, you know? it wont accel 2d or videos
<KotCzarny>
also in mainline without any patch: # CONFIG_DRM_MALI_DISPLAY is not set
<KotCzarny>
though i dont know what it does
parazyd has quit [Quit: nuked]
<yann-kaelig>
KotCzarny, drm_mali if I remember correctly is for mali450 and other one, but not the 400
<KotCzarny>
but what do you need mali for?
parazyd has joined #linux-sunxi
parazyd has joined #linux-sunxi
lurchi_ is now known as lurchi__
<yann-kaelig>
I need Mali for two software. Kodi and Mixxx (DJ turntable) without Mali kodi doesn't start and on mixxx turnable control is impossible due to the lag
<KotCzarny>
as for kernel, you are right, it's for dp500,550,650
<yann-kaelig>
yes, thx you right dp...
<KotCzarny>
ssvb: ^ another reason to have mali supported
<vinimac>
hi. how can I define interrupt function in dts code? function="irq"?
terra854 has quit [Quit: Connection closed for inactivity]
lurchi__ has quit [Ping timeout: 264 seconds]
<ssvb>
KotCzarny: yeah, Kodi can't function properly without Mali, it's a known thing
<yann-kaelig>
KotCzarny, I ask on lima channel if a crowdfunding could help to finish the development, and replied that it is simply impossible. So we can't use the full power of this good multimedia board. It's like a lamborghini with a 2CV ^^
<KotCzarny>
kodi is known, i meant the other program
<ssvb>
yann-kaelig: you still can use the proprietary driver
<ssvb>
I mean the mali blob
<yann-kaelig>
ssvb, hi. but not on the mainline kernel ?
<KotCzarny>
um, allwinner is more like dacia
<ssvb>
yann-kaelig: why not?
<KotCzarny>
definitely far from any power-stuff ;)
<ssvb>
yann-kaelig: you can hook the Mali driver anywhere
lkcl has quit [Ping timeout: 260 seconds]
<yann-kaelig>
ssvb, the userspace binary blob is not only compiled for a specific kernel version ?
<ssvb>
yann-kaelig: it is
<ssvb>
but the kernel driver is open source
<ssvb>
and you can adapt it
<yann-kaelig>
ssvb, ok, but what can I with kernel driver without the userspace side ?
<ssvb>
in fact everyone and their dog is doing that
<yann-kaelig>
do*
<ssvb>
you get the userland blob
<ssvb>
check what kind of version it is
<ssvb>
then go to the arm website and download a tarball with the matching kernel driver version (it is open source)
<ssvb>
then do a bit of patching to integrate it with the display driver, and also ensure that it is properly configured and clocked
<ssvb>
numerous people have done this in their private kernel trees
<ssvb>
there is also a recent effort to contribute some parts of Mali support code to the mainline kernel
<ssvb>
basically, the devicetree bindings and maybe some other minor things
<ssvb>
this should reduce the amount of patching required in people's private forks
<ssvb>
yann-kaelig: what kind of hardware do you have? and what are you trying to do with it?
IgorPec has quit [Ping timeout: 240 seconds]
<yann-kaelig>
I have a cubieboard2 and cubietruck (A20) I would like to use them for my musical purpose, and touchscreen control and Mixxx is one of them and also with kodi
wzyy2 has quit [Read error: Connection reset by peer]
reinforce has quit [Quit: Leaving.]
wzyy2_ has quit [Ping timeout: 240 seconds]
jbrown has quit [Ping timeout: 240 seconds]
maik_ has quit [Ping timeout: 260 seconds]
maik_ has joined #linux-sunxi
<rreignier>
For another use-case of Mali, I wanted to create a Qt 5.8 qtquickcontrols2 app on a H3 device and it failed because required OpenGL ES support. So I had to use the old kernel.
lurchi__ has joined #linux-sunxi
<rreignier>
And somehow related, do someone aware of something like fbcp on Raspberry that allow to copy the HDMI framebuffer to the one provided by fbtft (SPI display) in order to take the benefit of hardware accelerated graphics on a small screen? (for an H3 device).
jernej has quit [Ping timeout: 256 seconds]
jbrown has joined #linux-sunxi
ericxdu has quit [Remote host closed the connection]
chomwitt has joined #linux-sunxi
lurchi__ has quit [Ping timeout: 240 seconds]
<ssvb>
rreignier: you can have 3D accelerated Qt5 on H3 with a legacy kernel
<ssvb>
mainline kernel is also possible, but just needs some work
<Net147>
rreignier: Qt 5.8 has software rendering support built-in for Qt Quick now. You won't have tear-free graphics though.
<rreignier>
ssvb: Yes, I managed to get it on legacy. It just would have prefered a mainline one. I have followed what mripard did for the CHIP so yes, it would be possible to get a driver for mali in mainline but I do not have the knowledge and time right now :(
<ssvb>
rreignier: exactly, as I said, a bit of patching is needed to adapt Mali drivers and hook them with the display driver
<ssvb>
one of the problems is that the mainline kernel is a moving target
<ssvb>
the mali blobs are a moving target too
<rreignier>
Net147: Actually, I did not try the software rendering because I was not sure about the performance. Actually, it is a GUI for a robot so the CPU has a lot of tasks to do in the background...
<ssvb>
if you want to be always up to date, then it is going to constantly drain your time and efforts
maik_ has quit [Ping timeout: 260 seconds]
<rreignier>
ssvd: Thanks for the link, I did not see it before.
<ssvb>
it's a very old link, I don't know if it still works
<rreignier>
ssvb: and yes, it seems that maintaining a mali driver would be quite time consuming.
ericxdu has joined #linux-sunxi
<rreignier>
Does anyone knows if mrpiard's sunxi-mali repo could be apply to other CPU than the R8 of the CHIP?
<ssvb>
first of all, you need a display driver
<rreignier>
Ah yes, I see
<rreignier>
I am not very confortable with all the elements of the Linux graphics stack applied to Allwinner
<ssvb>
because mali is just rendering everything to memory buffers, it does not implement hdmi or lcd support
<ssvb>
a display driver is something that can be completely open source, and some work is ongoing in this direction
<ssvb>
both in U-Boot (for simplefb and/or efifb) and in the linux kernel (drm/kms)
<rreignier>
Ok, nice.
<rreignier>
And does the new tiny-drm thing is something that we can call a "display driver"?