fkluknav has quit [Remote host closed the connection]
fkluknav has joined #linux-sunxi
<wens>
it simply means there are too many variables to say whether it is properly working or not
<wens>
for instance, if the system drops 59 out of 60 frames every two seconds, how do you know if all the frames are good or not
<wens>
if the sensor is working properly, then the frames on the wire would be correct, but you have no way of telling
<wens>
if you have a system that directly displays the captured frames in an efficient way, i.e. passing dma_buf directly from csi/v4l to drm/kms, then that would work
<wens>
I don't have such a system around
<wens>
all my boards are headless. I can only use ffmpeg and compress the captured frames, which isn't fast enough for full blown 30 fps at any resolution
<jaganteki>
I understand this, i just looking whether H3 has tested this resolution on your changes.
<wens>
the series doesn't introduce any changes to the driver, beyond separating the compatible strings
<wens>
the A31 has more capabilites than the H3, that while aren't supported yet by the driver, necessitates splitting the compatibles
<wens>
this is a preemptive measure
<jaganteki>
correct, i have an impression of testing 5MP since the sensor support it. ok thanks.
<wens>
so what exactly are you asking anyway?
<jaganteki>
A64 do work all resolutions, via ffmpeg upto 1080p with 300MHz clock
<wens>
ok. that's good.
<jaganteki>
but I do find similar framedrop on 5MP
<wens>
framedrop likely means your userspace application isn't requesting new frames (passing in new buffers) fast enough
<wens>
at least that is what I make of the code
<jaganteki>
so we need proper display interface to test this, is it
<wens>
probably
<jaganteki>
ok, thanks for the info. I can resend the series.
<wens>
your commit logs are lacking details, or confusing with conflicting details
<wens>
you need to work on that
yangxuan has joined #linux-sunxi
<jaganteki>
sure.
kaspter has quit [Remote host closed the connection]
kaspter has joined #linux-sunxi
tnovotny has quit [Quit: Leaving]
megi has joined #linux-sunxi
kaspter has quit [Remote host closed the connection]
kaspter has joined #linux-sunxi
clemens3 has joined #linux-sunxi
pmpp has joined #linux-sunxi
chomwitt has joined #linux-sunxi
dizzuhen has joined #linux-sunxi
dizzuhen has quit [Client Quit]
<karlp>
what's the "ideal" process for adding new boards? add the dts to linux, send that linux-sunxi, _copy_ the file to u-boot? or just put in a minimal dts in uboot? or do you just put in a minimal dts in u-boot?
kaspter1 has joined #linux-sunxi
<wens>
linux first, then u-boot
kaspter has quit [Ping timeout: 250 seconds]
kaspter1 is now known as kaspter
willmore has quit [Ping timeout: 245 seconds]
willmore has joined #linux-sunxi
<karlp>
and you just copy the file as is right?
<karlp>
is there any procedure for continually updating the uboot files? or is it just "leave them if it's enough to run boot basics"
<wens>
sometimes someone will do a wholesale sync-up
<wens>
that normally coincides with new features being enabled in U-boot
<wens>
so it rarely happens
\\Mr_C\\ has quit [Quit: (Read error: Connection reset by beer)]
yangxuan has quit [Remote host closed the connection]
yangxuan has joined #linux-sunxi
yangxuan has quit [Remote host closed the connection]
yangxuan has joined #linux-sunxi
\\Mr_C\\ has joined #linux-sunxi
Andy-D has joined #linux-sunxi
yangxuan has quit [Ping timeout: 268 seconds]
\\Mr_C\\ has quit [Quit: (Read error: Connection reset by beer)]
msimpson has quit [Ping timeout: 240 seconds]
fkluknav has quit [Remote host closed the connection]
fkluknav has joined #linux-sunxi
msimpson has joined #linux-sunxi
<karlp>
so, wrt uboot, the only thing I'd be doing is copying an existing file and changing the dtb name, is that "just how it's done" ? it seems like just endless copypasta, hence 1328 defconfig files i uboot,
yangxuan has joined #linux-sunxi
\\Mr_C\\ has joined #linux-sunxi
yangxuan has quit [Remote host closed the connection]
qeed has joined #linux-sunxi
dddddd has quit [Quit: Hasta otra..]
dddddd has joined #linux-sunxi
msimpson has quit [Ping timeout: 268 seconds]
JohnDoe_71Rus has joined #linux-sunxi
reinforce has quit [Quit: Leaving.]
selfbg has quit [Remote host closed the connection]
lurchi_ is now known as lurchi__
Gerwin_J has quit [Ping timeout: 264 seconds]
<karlp>
is "someone other than me" alreayd taking care of these CONFIG_DM_MMC and CONFIG_DM_USB issues for sunxi defconfigs?
<fALSO>
i just reported about it here
<fALSO>
a few days ago
<fALSO>
but i was SHUNNED and told to fix it myself ;-P
<fALSO>
karlp, DO IT
<fALSO>
if i knew i would
<karlp>
I don't even know what it means yet, other than what its doc/driver-model/MIGRATION.txt
<karlp>
nanopi-k2 uses DM_MMC, so might be just change the define inthe defconfig
<karlp>
will try it next build
<fALSO>
i juyst saw those messages while building the latest uboot
<fALSO>
and saw something about the support being removed if it wasnt fixed
nuuuciano has joined #linux-sunxi
Putti has joined #linux-sunxi
itdnhr has quit [Ping timeout: 252 seconds]
itdnhr has joined #linux-sunxi
msimpson has joined #linux-sunxi
formruga has quit [Read error: Connection reset by peer]
alexxey has quit [Ping timeout: 250 seconds]
tllim has joined #linux-sunxi
qeed has quit [Quit: Leaving]
formruga has joined #linux-sunxi
noblock has joined #linux-sunxi
noblock has quit [Client Quit]
reinforce has joined #linux-sunxi
megi has quit [Ping timeout: 272 seconds]
tllim has quit [Read error: Connection reset by peer]
merbzt has quit [Ping timeout: 268 seconds]
<karlp>
well, if this one worked. home worked fine, at work a rebuild is just giving DRAM: 0 MiB. that's unhelpful :)
msimpson has quit [Quit: Leaving]
<karlp>
hrm, 2018.11 works.
fl_0 has quit [Ping timeout: 252 seconds]
merbzt has joined #linux-sunxi
fl_0 has joined #linux-sunxi
* karlp
pulls out the bisecting clippers
leviathanch has quit [Remote host closed the connection]
<karlp>
what's neat is that I get 1000kB/sec FEL on this computer, only about 760k at home :)
tllim has joined #linux-sunxi
m4ssi has quit [Remote host closed the connection]
<karlp>
pretttttty sure it's going to be a8011eb
IgorPec has quit [Ping timeout: 246 seconds]
megi has joined #linux-sunxi
clemens3 has quit [Ping timeout: 250 seconds]
clemens3 has joined #linux-sunxi
NeuroScr has joined #linux-sunxi
Nyuutwo has quit [Read error: No route to host]
Nyuutwo has joined #linux-sunxi
return0e has quit [Ping timeout: 244 seconds]
<karlp>
fALSO: well, the sunxi-mmc file is full of explicit "#if !CONFIG_IS_ENABLED(DM_MMC)" so it's not going to be just "turn it on"
<karlp>
need to know what an example driver model file would be to compare against.
Mr__Anderson has joined #linux-sunxi
return0e has joined #linux-sunxi
<plaes>
oh no.. :P
<plaes>
that one came from me
<karlp>
a8011eb? commit _looks_ ok :) it's all logically sound, turn on dram after power!
* karlp
shrugs
<karlp>
I've posted to uboot-dev, but i'm not subscribed, so it's in moderation.