<montjoie>
pgreco: with 2019.01 and no DM_MMC it still fail
<pgreco>
ok, not related to my problem, thanks
<montjoie>
argh, 2018.01 fail also
<fALSO>
yo
shfil has joined #linux-sunxi
dddddd has joined #linux-sunxi
fkluknav has quit [Remote host closed the connection]
fkluknav has joined #linux-sunxi
random_yanek has quit [Ping timeout: 250 seconds]
<montjoie>
pff nearly none of uboot 2017.x compile
random_yanek has joined #linux-sunxi
victhor has quit [Ping timeout: 258 seconds]
<KotCzarny>
use older gcc?
tnovotny has joined #linux-sunxi
cch has quit [Quit: cch]
megi has joined #linux-sunxi
Rafael1980 has joined #linux-sunxi
<montjoie>
the failure wasnt related to C code, binman exiting with error
\\Mr_C\\ has quit [Quit: (Read error: Connection reset by beer)]
yann has quit [Ping timeout: 264 seconds]
\\Mr_C\\ has joined #linux-sunxi
reinforce has joined #linux-sunxi
lurchi_ is now known as lurchi__
f0xx has quit [Ping timeout: 255 seconds]
hitech95 has joined #linux-sunxi
<hitech95>
wens, WTF m8. I have just seen that you merged the BT on a lot of boards... wondering why my old patch / attempt wasn't wokring its the mostly the same of yours. Have you made some changes on the RTC module? https://gist.github.com/hitech95/94b46bdb4cbd8d15b3d3966a8bc21105#file-wifi-bt-bpi-m2m-patch Anyway Good Job, i've spent days on that and at the end i giveup on Allwinner stuff :(
<hitech95>
I could try to give my board another GO now that it's working... But i still have to make the ASoc Driver Work as I need it.
yann has joined #linux-sunxi
tnovotny has quit [Ping timeout: 268 seconds]
MoeIcenowy has quit [Quit: ZNC 1.6.5+deb1+deb9u1 - http://znc.in]
MoeIcenowy has joined #linux-sunxi
gamelaster has quit [Ping timeout: 245 seconds]
tnovotny has joined #linux-sunxi
airwind has quit [Ping timeout: 245 seconds]
gamelaster has joined #linux-sunxi
tnovotny has quit [Quit: Leaving]
f0xx has joined #linux-sunxi
f0xx has quit [Read error: Connection reset by peer]
nuuuciano has joined #linux-sunxi
gamelaster has quit [Ping timeout: 244 seconds]
DonkeyHotei has quit [Read error: Connection reset by peer]
DonkeyHotei has joined #linux-sunxi
reinforce has quit [Quit: Leaving.]
<tuxd3v>
ARM Trusted FirmWare v2.1
<tuxd3v>
Has support for allwinner H6
<tuxd3v>
but they stated it was tested with linaro cross toolchain 6.2 I think
<tuxd3v>
I am using Linaro 8.2
<tuxd3v>
Should this be a problem?
<paulk-leonov>
montjoie, h8 as in a83t?
<montjoie>
paulk-leonov: yes h8 homlet was the proto board sent by allwinner
<montjoie>
so collector
<montjoie>
the board came with an "allwinner teeshirt" which I wear when I want to troll my amlogic maintainers coworkers
<KotCzarny>
lol
<mru>
t-shirt trolling is fun
<paulk-leonov>
hehe
<mru>
I once wore an opensuse t-shirt to the linaro connect conference
<mru>
switched to an intel t-shirt the second day
<KotCzarny>
and symbian on the third?
<mru>
no, vlc t-shirt in the gstreamer mini-conf
<tuxd3v>
hehe
<montjoie>
I want to print an "allwinner crypto perfowhat ?" teeshort
<KotCzarny>
'i worked on hwcrypto deccelerators and all i got was this lousy t-shirt'
<wens>
hitech95: rtc was patched, yes
<montjoie>
wens: which uboot do you use on your h8 homlet ?
<wens>
montjoie: been a while since I used it
<montjoie>
all 2017 and 2018 fail to find mmc, I try 2016
<wens>
paulk-leonov: bpi-m3 has ov8865 CSI camera sensor module
<wens>
paulk-leonov: not supported in mainline. not sure about BSP
<paulk-leonov>
wens, is that MIPI CSI-2 or parallel csi?
<wens>
paulk-leonov: CSI-2
<wens>
paulk-leonov: the camera module has 2 sensors, one ov5640, one ov8865
<paulk-leonov>
oh nice
<paulk-leonov>
thanks wens!
<wens>
ov5640 wired to parallel csi ( I have a series somewhere )
<wens>
ov8865 wired to mipi csi-2
<wens>
they share i2c and reset signal, while having separate power rails and shutdown signal lol
<paulk-leonov>
what could go wrong :p
<wens>
I'm on vacation, but I'll try to send out the parallel bits sometime next week
<paulk-leonov>
oh nice
<paulk-leonov>
my plan is to try and work on csi-2 bringup
<wens>
you just have to be careful with the asserting reset :/
JohnDoe_71Rus has joined #linux-sunxi
aalm has quit [Ping timeout: 246 seconds]
msimpson has quit [Read error: Connection reset by peer]
shfil has quit [Quit: Connection closed for inactivity]
Nyuutwo has joined #linux-sunxi
gamelaster has joined #linux-sunxi
aalm has joined #linux-sunxi
<tuxd3v>
Hello Guys,
<tuxd3v>
For the first time I am getting some warnings after clonning u-boot and arm trusted firmware v2.1
tllim has quit [Read error: Connection reset by peer]
* karlp
boggles
<mru>
not the first time I've seen such things
<karlp>
adding bom cost, just to confuse developers? sounds pretty dumb.
<mru>
a directv box I worked on once upon a time had something similar
pmpp has quit [Disconnected by services]
pmpp_ has joined #linux-sunxi
aash_ has joined #linux-sunxi
<aash_>
Question to chroot experts - I am trying to chroot into an arm environment with qemu-arm-static and binfmt enabled on my host - this all goes well, but all my normal binries are missing (find, su) etc
<aash_>
Does one have to manually copy this over as well?
thefloweringash has quit [Ping timeout: 264 seconds]
thefloweringash has joined #linux-sunxi
<angelo_ts>
where can i find H3 bootstrap pin and boot mode selectipon ?
<KotCzarny>
in h3 datasheet?
<angelo_ts>
I thought the 4.2 Boot System may explainn something, but there is nothing there
<KotCzarny>
you ask about fel button?
<KotCzarny>
or something else?
<angelo_ts>
i mean, how it selects the boot media, as mmc or spi nor etc
<KotCzarny>
i think it might be selected by efuses
<KotCzarny>
but i may be wrong here
tllim has joined #linux-sunxi
tllim has quit [Ping timeout: 245 seconds]
<angelo_ts>
There is nothing about the boot process on the manual of H3
<angelo_ts>
also, i would like to know if i am fallen into FEL nut not clear how
t3st3r has quit [Ping timeout: 256 seconds]
t3st3r has joined #linux-sunxi
<beeble>
aash_: if you do a chroot then the directory will be your new root and it does not know anything from the outside (as long as it's not bind mounted into the chroot)
<aash_>
beeble: I found my issue - multistrap 2.2.0 didn't have the su binary, but multistrap 2.2.9 does..
<aash_>
i.e for the same multistrap configuration
vagrantc has joined #linux-sunxi
tllim has joined #linux-sunxi
Rafael1980 has quit [Quit: Konversation terminated!]
Rafael1980 has joined #linux-sunxi
tllim has quit [Remote host closed the connection]
tllim has joined #linux-sunxi
kaspter has quit [Read error: Connection reset by peer]
kaspter has joined #linux-sunxi
t3st3r has quit [Ping timeout: 256 seconds]
tllim has quit [Remote host closed the connection]
tllim has joined #linux-sunxi
t3st3r has joined #linux-sunxi
t3st3r has quit [Ping timeout: 256 seconds]
tllim has quit [Ping timeout: 245 seconds]
t3st3r has joined #linux-sunxi
<megi>
angelo_ts: look at the H6 manual, perhaps it's similar in H3
<megi>
there's an extensive boot selection docs and flow charts
<megi>
details like register locations will probably be different
<megi>
even H5 manual has more info on booting
<tuxd3v>
<aash_>, did you installed the package 'binfmt-support' and 'qemu-user-static' ?