flyback has quit [Remote host closed the connection]
flyback has joined #u-boot
jwillikers has joined #u-boot
jwillikers has quit [Remote host closed the connection]
macromorgan has quit [Killed (calcium.libera.chat (Nickname regained by services))]
macromorgan has joined #u-boot
agust has joined #u-boot
fdanis_away is now known as fdanis
guillaume_g has joined #u-boot
sbach has quit [Read error: Connection reset by peer]
sszy has joined #u-boot
mckoan|away is now known as mckoan
sbach has joined #u-boot
gsz has joined #u-boot
alpernebbi has joined #u-boot
monstr has joined #u-boot
mranostaj has quit [Remote host closed the connection]
mranostaj has joined #u-boot
redbrain has joined #u-boot
frieder has joined #u-boot
cebrax has joined #u-boot
<cebrax>
hello
<cebrax>
Is this channel active?
<cebrax>
I am pretty new to embedded linux
<cebrax>
Does anybody know *whether* u-boot-fslc v2020 support LCD IF drivers for iMX6ULL or not?
frieder has quit [Remote host closed the connection]
matthias_bgg has joined #u-boot
jwillikers has joined #u-boot
mmu_man has joined #u-boot
<marex>
cebrax: for downstream forks, ask the fork vendor (NXP in this case)
<marex>
cebrax: however, if you plan to display splash screen in u-boot, you will get flicker when linux boots and reinits the display, better boot fast enough and let linux init the display
<cebrax>
yeah, asked them and they have forwarded me to a dts example and that's all..
<cebrax>
Actually I am trying to learn and trying to do this for educational purposes, so I don't mind the flicker at all
<cebrax>
I have linux controlling the display correctly but cannot say the same for u-boot
<cebrax>
So, I've seen this video, it's in Chinese but even without sound you can understand it:
<cebrax>
I don't understand u-boot-fslc, why break something if it's working?
<cebrax>
Sorry if I am being too dumb, it's my first time in embedded linux world
<marex>
cebrax: upstreaming takes extra time and isn't as willing to accept random half-cooked patches as fork is
<cebrax>
So, for the sake of learning, I guess it is better for me to patch u-boot-fslc v2020 using v2021? By patching, I mean copy, paste edit the current code source on my machine
<marex>
which machine is that ?
<cebrax>
I am feeling I should not mess with bureaucracy of proper patching, yocto-recipe making etc?
<marex>
if you want to deal with u-boot, set up cross toolchain and build it by hand, ignore OE and all the other buildsystem crap for now
<cebrax>
I am building it using YOCTO on a ubuntu VM
<marex>
ubuntu has cross toolchains in it, so just install those
<marex>
the you can build u-boot from scratch by hand
<cebrax>
OK, how do I burn it to my SD card so that I can make it bootable?
<cebrax>
YOCTO creates .wic images for me, which includes uboot and rootfs
<cebrax>
I only burn it to SD by using "dd"
<marex>
cebrax: dd u-boot.imx or whatever you get to the right offset of the SD card
<marex>
cebrax: make sure to do the test for frequencies a bit around the 400 MHz range too
<cebrax>
Hmm, OK, I will try to do that too
<cebrax>
Thank you very much
<marex>
seems like a good idea with new custom hardware, otherwise it might start to fail in various weird thermal conditions
<cebrax>
Hmm, got it! :]
<marex>
cebrax: well, and then once you have it going, try the mxsfb driver, it worked on mx28, but the mx6ull lcdif might be slightly different (they all are, nxp keeps mutating them between different soc series)
<marex>
cebrax: if you have it running in linux, dump the mxsfb registers via /sys/kernel/debug/regmap/ or with devmem and compare the result with what u-boot programs into those ... there is like 10 relevant registers, so it should be easy to follow the bits
<cebrax>
How do I understand if uboot-fslc even tries to initialize lcdif?
<marex>
no idea about u-boot-fslc , they have some hundreds of thousands of lines changed from mainline u-boot
<marex>
cebrax: but if you git grep VIDEO_MXS in mainline, there seem to be a few example boards, e.g.