<Armbian-Discord>
<adeepv> for which board are you looking?
<Armbian-Discord>
<SG_94> X96 X4 Amlogic S905X4
<Armbian-Discord>
<trohn_javolta> Hi all, yesterday I ran into a weird problem with my android tv box. After a freeze and restart it seems it refuses to boot from micro sd card 😄
<Armbian-Discord>
<trohn_javolta> The box is a tanix tx5 pro, S905x2, 4gb 32gb
<Armbian-Discord>
<trohn_javolta> Can anyone tell my why and how I could make it boot again from sd? I already tried toothpick method but that only got my into android recovery.
chewitt has joined #armbian-amlogic
<Armbian-Discord>
<trohn_javolta> for fun I also tried to hook up the sd card to usb port via usb card reader and the box booted from usb... but not for long..tells me it can't find usb device but the card reader is a really crappy one so i think it is the card readers fault.
<Armbian-Discord>
<trohn_javolta> also on the sd card I found an aml sth. zip which I tried to flash in android via the updater app. but in the android recovery I got an error, flash failed.
<Armbian-Discord>
<IdoLi> Hey. I'm getting this error:
<Armbian-Discord>
<IdoLi> also, I think that I downloaded the wrong OS. is there one for s905x3?
<Armbian-Discord>
<ManoftheSea> TV box goes to forum
<Armbian-Discord>
<trohn_javolta> thats unfortunate, was hoping for a chat with sb knowledgeable
<Armbian-Discord>
<c0rnelius> problem is knowledge of the SoC doesn't always translate exactly the same to a have tvbox.
<Armbian-Discord>
<c0rnelius> especially when it comes to the boot process.
<Armbian-Discord>
<narmstrong> dealing with the vendor u-boot is the problem, otherwise the fully upstream boot chain is simple and documented
<Armbian-Discord>
<c0rnelius> yeah... i just bricked this one. 🙂
<Armbian-Discord>
<ManoftheSea> That's why you go to the forum
<Armbian-Discord>
<trohn_javolta> I understand, was just hoping for a quick help. chat is way faster than posting in a forum
<Armbian-Discord>
<ManoftheSea> and far more ephemeral, ensuring the problem is asked again and again
<Armbian-Discord>
<Aoyfe> Hey all, don't have an Armbian specific problem but hoping to gain some knowledge to fix my own stuff. I'm currently working on getting support for the ODroid HC4 into Talos (https://www.talos.dev/). Right now I'm trying to determine what I even need in order to do that. Talos boots from u-boot and comes bundled with upstream kernel 5.15. I'm very new at this so forgive the ignorance and feel free to point me to
<Armbian-Discord>
a better location to ask questions.
<Armbian-Discord>
<Aoyfe> What's the "secret sauce" to get petitboot to see the Talos disk as bootable? Or should I stuff upstream u-boot into SPI? Or, if I understand correctly, can I chainload the u-boot in Talos from u-boot that shipped with the HC4
<Armbian-Discord>
<c0rnelius> I don't own one, but if sticking with petitboot just flash the vendor uboot bin and use either a vfat or ext2 boot partition. from there you can use boot.cmd / boot.scr and boot.ini file(s).
<Armbian-Discord>
<Aoyfe> Pretend like I recognize all of the words and understand none of what you said. 🙂
<Armbian-Discord>
<Aoyfe> I'm sorry, I'm very new at this.
<Armbian-Discord>
<c0rnelius> thats a problem 🙂
<Armbian-Discord>
<Aoyfe> I don't have a preference of sticking with petitboot or not, to be honest. I'd prefer to stick with upstream u-boot as opposed to using vendor u-boot, I think?
<Armbian-Discord>
<c0rnelius> that requires extra effort 'as far as I know?' like erasing the SPI.
<Armbian-Discord>
<c0rnelius> I would think its easier just to keep pboot.
<Armbian-Discord>
<Aoyfe> So if I keep pboot, I have to use vendor's u-boot as well?
<Armbian-Discord>
<c0rnelius> I believe so, yes. Someone else may know better? In my experience pboot doesn't not play well with mainline u-boot.
<Armbian-Discord>
<Aoyfe> And I should be able to place u-boot.bin from the vendor onto a vfat partition at the beginning of e.g. a UFD and it'll "just work"?
<Armbian-Discord>
<ManoftheSea> I got talos on an ebin, from the EFI booting.
<Armbian-Discord>
<c0rnelius> on the odroid n2's there is a switch to bypass pboot. on the odroid m1 there is a command you can use to also bypass it... I don't believe the same is the case on the HC4
<Armbian-Discord>
<ManoftheSea> You should be able to accomplish the same... Does petitboot attempt to find the EFI app on the ESP?
<Armbian-Discord>
<Aoyfe> @c0rnelius There's a button on the bottom of the board, looks like?
<Armbian-Discord>
<Aoyfe> Momentary switch
<Armbian-Discord>
<c0rnelius> you can't use GPT on aml devices. in my testing.
<Armbian-Discord>
<ManoftheSea> Another thing you might try is booting talos from netboot.
<Armbian-Discord>
<c0rnelius> yeah, but you would need to use the button everytime to boot the board with mainline u-boot.
<Armbian-Discord>
<c0rnelius> unless you erase SPI
<Armbian-Discord>
<ManoftheSea> Ah right, the conflict between the GPT's entries and the boot code. Fixable, just need to set the GPT offset.
<Armbian-Discord>
<ManoftheSea> But if u-boot is in SPI, you don't need u-boot on SD
<Armbian-Discord>
<c0rnelius> how would you offset GPT?
<Armbian-Discord>
<ManoftheSea> Yeah, talos even has instructions to run an initial cluster in docker to make the netboot available to run the "real" cluster. Petitboot can netboot. That's probably your fast path.
<Armbian-Discord>
<Aoyfe> @ManoftheSea For reasons I won't get into, I'm not netbooting Talos. 🙂
<Armbian-Discord>
<Aoyfe> Talos needs to run from a persistent disk. There's no way to do what e.g. ESXi does and just always boot from the networkk
<Armbian-Discord>
<c0rnelius> I looked into that "i think cuz you mentioned it?"... its my understanding you can't offset GPT>
<Armbian-Discord>
<Aoyfe> Netboot is a quick path for install, but I'm at the part where I'm trying to make the installer work with the HC4.
<Armbian-Discord>
<ManoftheSea> Ah, I confused amlogic (needs sector 2) and allwinner (needs sector 16) again. No, you can't GPT with u-boot on uSD. But... we aren't doing uboot on uSD.
<Armbian-Discord>
<c0rnelius> pretty sure I ran into a post from a GPT dev who said this can not be done.
<Armbian-Discord>
<ManoftheSea> Sure, it installs persistent info to disk. But you can still netboot the image and it finds the configuration on persistent disk.
<Armbian-Discord>
<ManoftheSea> Can't offset GPT header. Can offset the entries table. Amlogic interferes with the former.
<Armbian-Discord>
<Aoyfe> So I have to use MBR partitions in order to boot the ODroid HC4?
<Armbian-Discord>
<ManoftheSea> A previous discussion.
<Armbian-Discord>
<ManoftheSea> No. Only if you have u-boot on uSD. If you have uboot on SPI (far superior install, IMO), you don't have to care about amlogic, allwinner, etc.
<Armbian-Discord>
<Aoyfe> Ok, so how in order to stick u-boot in SPI, do I need to use vendor, mainline, mainline with patches?
<Armbian-Discord>
<ManoftheSea> Well, that's where I asked if petitboot (which is already running from SPI, right?) can boot uefi image
<Armbian-Discord>
<ManoftheSea> it should.
<Armbian-Discord>
<ManoftheSea> I don't remember if Talos puts the kernel/initrd in UEFI app, or if those are chainloaded from UEFI bootloader.
<Armbian-Discord>
<ManoftheSea> but basically, you want petitboot to launch the kernel/initrd.
<Armbian-Discord>
<Aoyfe> I believe it they're chainloaded.
<Armbian-Discord>
<ManoftheSea> you already have a bootloader
<Armbian-Discord>
<ManoftheSea> If you search this discord for talos, you'll find where I mentioned it a few other times. For a little while, I was launching the kernel/initrd from extlinux.conf and NOT from UEFI
<Armbian-Discord>
<Aoyfe> Grub is the EFI app, then Grub loads the kernel.
<Armbian-Discord>
<ManoftheSea> Petitboot on itself: Petitboot uses udev to discover block devices and network interfaces and parses a set of known locations for bootloader configurations. Petitboot supports a number of configuration formats including GRUB, SYSLINUX, and Yaboot. Booting is performed via the kexec mechanism.
<Armbian-Discord>
<ManoftheSea> So... it ought to detect the grub configuration that Talos sets up.
<Armbian-Discord>
<rpardini> for HC4: get a recent Armbian image, boot from SD by holding button below the board.
<Armbian-Discord>
<rpardini> Install u-boot to SPI with armbian-install, that will wipe Petitboot.
<Armbian-Discord>
<rpardini> Then you can boot EFI or whatever you want from SD or even SATA.
<Armbian-Discord>
<ManoftheSea> Oh, though... you'll need to drop your DTB in manually
<Armbian-Discord>
<Aoyfe> Yeah, that's fine. There's a DTB in mainline linux now for the HC4.
<Armbian-Discord>
<ManoftheSea> Is it complete? The helios64 has a dtb in mainline, but it's definitely not the same as the one armbian patches in
<Armbian-Discord>
<ManoftheSea> (that's a rockchip RK3399)
<Armbian-Discord>
<rpardini> it is, mainline support for the HC4 is stellar, thanks to Neil.
<Armbian-Discord>
<ManoftheSea> great!
<Armbian-Discord>
<Aoyfe> @rpardini How does armbian package u-boot for the HC4? Trying to get that into Talos' build process so that I can streamline the installation
<Armbian-Discord>
<rpardini> Yep.
<Armbian-Discord>
<Aoyfe> ....I don't think that's a yes or no question. 😛
<Armbian-Discord>
<ManoftheSea> I think it was to "great"
<Armbian-Discord>
<ManoftheSea> But armbian doesn't flash spi automatically
<Armbian-Discord>
<rpardini> the u-boot package for HC4 has 2 bins
<Armbian-Discord>
<rpardini> one for SD and one for SPI
<Armbian-Discord>
<Aoyfe> @ManoftheSea That one installs u-boot to the sdcard.
<Armbian-Discord>
<ManoftheSea> I know, so does armbian.
<Armbian-Discord>
<Aoyfe> Yeah, I was trying to follow upstreams' docs, but quickly got confused.
<Armbian-Discord>
<rpardini> it's worth noting the SD version of u-boot for the HC4 does not support SATA; it is really a C4 (not HC4) build.
<Armbian-Discord>
<ManoftheSea> oh wow, yeah, I'm reading through this too, and my conclusion continues to be "throw amlogic in the garbage"
<Armbian-Discord>
<rpardini> the SPI version supports SATA no problem.
<Armbian-Discord>
<c0rnelius> be easier just to stick with vendor u-boot on that board. plus no compiling really needed.
<Armbian-Discord>
<rpardini> "vendor uboot" comes with Petitboot and it's brain-deadness
<Armbian-Discord>
<rpardini> also, boots a legacy 4.x kernel, and then kexec's. good luck with that.
<Armbian-Discord>
<c0rnelius> yeah... but using mainline just complicates things. i have no horse in the race as I don't have the unit. but for the masses vendor u-boot seems the easiest road to take.
<Armbian-Discord>
<c0rnelius> BS... you can use upstream kernel on that.
<Armbian-Discord>
<rpardini> fact they don't release the source for their Petitboot says all.
<Armbian-Discord>
<ManoftheSea> If petitboot can read grub or extlinux configuration, I don't see a reason to overwrite petitboot just to have a cattle system to run Talos.
<Armbian-Discord>
<c0rnelius> sure and I agree. but he is talking about getting the board booted not reinventing the wheel.
<Armbian-Discord>
<rpardini> well, I am just contributing what I knew, since he considered wiping Petitboot, and that's what I do on my HC4 army.
<Armbian-Discord>
<narmstrong> Wut ? Do you mean upstream uboot or vendor uboot ? Upstream uboot definitely support sata on both sd and spi
<Armbian-Discord>
<ManoftheSea> booting talos from SATA? I don't think that's the plan.
<Armbian-Discord>
<rpardini> Armbian's, Neil, sorry. The SD u-boot shipped on Armbian for the HC4 is still the C4, for... lack of time reasons 😉
<Armbian-Discord>
<rpardini> The SPI version is using the correct defconfig, while the SD is still using c4's defconfig. Will fix this one day.
<Armbian-Discord>
<ManoftheSea> Why doesn't petitboot find and run the grub config that Talos puts down?
<Armbian-Discord>
<rpardini> well -- go decompile it and find out
<Armbian-Discord>
<rpardini> I won't 😉
<Armbian-Discord>
<ManoftheSea> I don't ask you to. But I think that question is the fastest route to @Aoyfe 's solution
<Armbian-Discord>
<rpardini> well I offered one solution, sans-petitboot, someone with Petitboot experience can offer another 🫡
<Armbian-Discord>
<ManoftheSea> I suppose that is a limitation, yes.
<Armbian-Discord>
<ManoftheSea> And I agree, for my own pets, I would also wipe petitboot
<Armbian-Discord>
<Aoyfe> Ok, so I should be able to build upstream u-boot and flash it to SPI and then from there do regular EFI boot things?
<Armbian-Discord>
<narmstrong> Yes
<Armbian-Discord>
<rpardini> yes.
<Armbian-Discord>
<Aoyfe> And then other than that I need the DTB in the boot partition, correct?
<Armbian-Discord>
<narmstrong> Ah ok :-p it doesn’t really matter since the spi version is usually the one used for EFI
<Armbian-Discord>
<narmstrong> Nop it will use the dtb from uboot
<Armbian-Discord>
<narmstrong> The « u-boot.bin » you get when building uboot is the « BL33 u-boot.bin », to be distinguished with the « u-boot.bin » you get after build.sh you use to boot the device
<Armbian-Discord>
<ManoftheSea> You're going to, by default, overwrite the platform firmware?
<Armbian-Discord>
<ManoftheSea> You are going to surprise people.
<Armbian-Discord>
<rpardini> where did you get this idea?
<Armbian-Discord>
<ManoftheSea> This right here.
<Armbian-Discord>
<narmstrong> @ManoftheSea for Odroid-HC4 ?
<Armbian-Discord>
<rpardini> well ok some dissonance in here, relax.
<Armbian-Discord>
<c0rnelius> 🙂
<Armbian-Discord>
<ManoftheSea> If you build and flash u-boot to SPI, then the install of Talos will change the boot process of the board such that other installations will be broken.
<Armbian-Discord>
<Aoyfe> @narmstrong Right, so build-fip.sh outputs u-boot.bin that includes all the various bootloader stages and I can dd that to SPI?
<Armbian-Discord>
<narmstrong> Yes exact
<Armbian-Discord>
<Aoyfe> I was so close . 😄
<Armbian-Discord>
<ManoftheSea> If you instead use the existing petitboot to run Talos linux, then people can try it without consequence.
<Armbian-Discord>
<ManoftheSea> also, don't dd to spi, there's a different tool for the memory device
<Armbian-Discord>
<rpardini> dd works perfectly well against an mtdblock device.
<Armbian-Discord>
<ManoftheSea> oh, maybe my info is old.
<Armbian-Discord>
<ManoftheSea> okay
<Armbian-Discord>
<ManoftheSea> is it because "mtdblock" is handling the erasure process?
<Armbian-Discord>
<rpardini> btw, cat xx.bin > /dev/mtdblockX; sync also works. it's all in the kernel.
<Armbian-Discord>
<rpardini> mtdblock exposes the mtd as a block device.
<Armbian-Discord>
<rpardini> for sequential write of u-boot it's perfectly fine.
<Armbian-Discord>
<rpardini> either way I think we have mtdutils in all userlands now, so you can use the legacy commands as well. but that's not what armbian-install does (it uses dd).
<Armbian-Discord>
<ManoftheSea> I concede
<Armbian-Discord>
<ManoftheSea> But maintain that overwriting petitboot is going to surprise people who will complain that "Talos broke my system"
<Armbian-Discord>
<rpardini> lol then they can go to the Talos Discord and complain there 😉
<Armbian-Discord>
<Aoyfe> @ManoftheSea Sure, but it'll be called out in the documentation because it's something that won't be automated. We can supply the built u-boot, they'll need to apply it
<Armbian-Discord>
<ManoftheSea> so you need to be able to boot from petitboot anyway
<Armbian-Discord>
<rpardini> untrue. you can skip petitboot by holding the button.
<Armbian-Discord>
<rpardini> this process of "boot Armbian once with toothpick/button, flash u-boot to eMMC or SPI, then use for EFI" is being used for Amlogic boards by quite a few folks. never seen it "documented" though.
<Armbian-Discord>
<rpardini> I've similar also for the N2+, but that requires an overlay/alt-dtb to get access to the MTD.
<Armbian-Discord>
<rpardini> so HC4 SPI -> SATA is very doable, and N2+ SPI -> USB3 also.
<Armbian-Discord>
<ManoftheSea> Why is it wrong to boot from petitboot?
<Armbian-Discord>
<ManoftheSea> Particularly for something like Talos, which exists only to be a thin layer that enables a k8s cluster?
<Armbian-Discord>
<rpardini> leaves
<Armbian-Discord>
<Aoyfe> I don't think it's wrong to boot from pboot, just that it requires board-specific layouts, etc. Using mainline u-boot gives a much nicer experience.
<Armbian-Discord>
<ManoftheSea> If it boots from petitboot, aoyfe doesn't have to build u-boot, doesn't have to flash spi, doesn't have to break the factory state of the board, and still gets a Talos system
<Armbian-Discord>
<Aoyfe> Like, for example, not being able to use GPT disks.
<Armbian-Discord>
<ManoftheSea> I don't see the difference in board-specificity between u-boot and petitboot
<Armbian-Discord>
<ManoftheSea> that's in regards to mainline u-boot from uSD, no?
<Armbian-Discord>
<ManoftheSea> you can't use GPT and mainline u-boot for amlogic from uSD
<Armbian-Discord>
<rpardini> phew. you can't have u-boot and GPT on the same media for Amlogic.
<Armbian-Discord>
<rpardini> if u-boot is in SPI, you can have whatever you want on SD/SATA/whatever.
<Armbian-Discord>
<rpardini> Petitboot's u-boot is probably vendor, 2015.x, and can't EFI and shit.
<chewitt>
petitboot is petitboot, not a derivative of u-boot
<Armbian-Discord>
<rpardini> Petitboot's u-boot boots a vendor 4.x kernel, also in SPI, which does braindead things, then kexec's into the target kernel.
<Armbian-Discord>
<rpardini> If that is not reason enough to remove Petitboot, I dunno what is. Ahn, maybe cos we don't have the source for it, either.
<Armbian-Discord>
<rpardini> chewitt: Christian, long time no see. Hello!
<Armbian-Discord>
<ManoftheSea> that it can't bootload is a good reason to kill it.
<chewitt>
rpardini: You all buggered off into sub-channels .. and I've been work-busy
<Armbian-Discord>
<rpardini> that said, I've complained endlessly to HardKernel; for the ODROID-M1 (rk3568) they did go out of their way to make it easier to avoid Petitboot. It's still.... not good enough but shows willingness to accomodate mainline better.
<Armbian-Discord>
<ManoftheSea> I'm still unhappy that it seems like platform firmware is distro-specific.
<Armbian-Discord>
<ManoftheSea> Oh, that's good to hear.
<chewitt>
am trying to score points by cleaning-up and upstreaming as much stuff as I can from my tree
<Armbian-Discord>
<rpardini> chewitt: excellent. as you know I constantly borrow from your tree. we've diverged a bit recently due to AXG vs SM1 vs meson-gx-mmc clock phase. I've to update the venc/vdec patches after you're done too...
<chewitt>
I dropped the 270º patch from 6.1/62
<chewitt>
and I reverted the SDIO interrupt support which seems to cause issues
<chewitt>
the vdec patches are an attempt to put code in public view in the hope someone takes an interest in fixing the many issues
<chewitt>
I've dropped HEVC from g12a+ as it wedges the board with 10-bit code
<Armbian-Discord>
<rpardini> yep, so did we -- but @adeepv needs them for his AXG JetHub boards. He did a patch to read phase, if existing, from DT, so only his boards get 270. Then, later, the BananaPi M5 turned out to also need 270! (lol)...
<chewitt>
HEVC 8-bit works, but since you can't tell 8-bit vs 10-bit easily it's better to force software decode on all than wedge the board
<Armbian-Discord>
<rpardini> Yep, I've confirmation from @c0rnelius that the Radxa Zero, at least, needs reverting of the SDIO IRQ stuff. Have you found any other boards that break with it?
<Armbian-Discord>
<c0rnelius> @chewitt this is off topic. I've noticed when using 6.1.y on RK3328 the HDMI doesn't work. Have you seen this?
<chewitt>
I also disabled MPEG1/2 as that got broken along the way .. although I won't push that upstream
<chewitt>
(too much dirty laundry)
<chewitt>
RK things have a large SEP field around them so no clue about that, sorry..
<Armbian-Discord>
<c0rnelius> alright, thanx.
<chewitt>
try one of the 10.95.0 (LE11) test images from our test server
<Armbian-Discord>
<rpardini> Yep -- I wanna get Armbian working with basic ffmpeg venc/vdec, I guess I need to include the vdec/venc firmware bin's as well... and unclear if ffmpeg itself needs patching?
<Armbian-Discord>
<c0rnelius> k
<chewitt>
if it works there you're missing patches perhaps
<chewitt>
there is/will-be an effort to clear house a bit on the RK side soon
<chewitt>
rpardini: you need kernel patches + firmware + ffmpeg patches
<Armbian-Discord>
<c0rnelius> indeed... i pulled ur patches and built a new kernel, but never actually did the install as something came up. I was mostly just curious if you have seen the issue or it was just me.
<chewitt>
a serious attempt to upstream the ffmpeg bits has started
<chewitt>
one of the ffmpeg maintainers who we've abused for helping the upstream process before (who has an interest in pi matters) is working with the Pi developer who's been hoarding changes
<chewitt>
RPi Foundation have committed to doing the work, i.e. funding their developer to get it done
<chewitt>
firmware is in linux-firmware or you can pick the LE meson-firmware repo which has only the firmware we need
<chewitt>
the kernel patches I've sent today will probably endure some bikeshedding but work as-submitted
<Armbian-Discord>
<rpardini> very nice! thanks for the updates, it's nice to know a little about behind the scenes.
<chewitt>
I made the case early on in the Pi dev cycle that changes working on more than RPi hardware will be easier to upstream (and are prob. more robust)
<chewitt>
we found a few differences .. which is inevitable with stateful decoders
<chewitt>
but the code handles 3-4 different v4l2_m2m SoC types now
<chewitt>
and also v4l2_requests to handle the stateless side of things; which is much better shape due to the lack of firmware blobs
<chewitt>
RPi4 using both v4l2_m2m for H264 and v4l2_requests for HEVC
<Armbian-Discord>
<rpardini> I've LE's master/main from October build running here on RPi4b, very few artifacts, some vdec hangs very rarely, otherwise works great.
<chewitt>
there are some firmware fixes that should get confirmed before we ship LE11 .. in a couple of weeks
<chewitt>
things that help with users seeing blank screens on boot
<chewitt>
some timing juju has been tinkered with
<chewitt>
also some graphical glitches seen during certain operations like scrolling in large Kodi GUI lists
<Armbian-Discord>
<rpardini> oh weeks, it it that close? (/me fires off builds of LE)
<Armbian-Discord>
<c0rnelius> I'm a dick. I use CE.
<chewitt>
10.95.0 (LE11 b1) should be out within days
<chewitt>
we prob. move quickly to an rc1, then release
<chewitt>
it's quite well baked by now
<Armbian-Discord>
<rpardini> it is. great work 👍
<Armbian-Discord>
<Aoyfe> Sorry, got work busy. Thank you all for your help
<Armbian-Discord>
<rpardini> chewitt: nice to know LE 11 is gonna be released. when it is, I'll try to send @Tonymac32 's patches for the Tinkerboard2, maybe Heitbaum will run with them for 12.
<Armbian-Discord>
<c0rnelius> @rpardini Hey i'm not discounting all the great efforts LE does. Just... on my AML devices. CE I feel works better. Must be all that vendor garbage.
<Armbian-Discord>
<c0rnelius> When i wanna watch a movie, I want to play. simple.
<chewitt>
CE works better for anything media related
<chewitt>
although on older hardware LE is now working quite nicely
<Armbian-Discord>
<rpardini> Yep I don't... judge.... well I do 😉 mainline all the things... or no-movie-for-rpardini.
<Armbian-Discord>
<rpardini> "no soup for you!"
<chewitt>
the current 'vdec' driver is authored against GXL/GXM and most of that is applicable to GXBB too
<Armbian-Discord>
<c0rnelius> ha
<chewitt>
the newer hardware needs the 'hevc' driver (not to be confused with HEVC codec)
<chewitt>
this does more on software and skips the esparser stage which helps with memory management
<chewitt>
but architecturally really needs a different driver
<chewitt>
the current code tries to do everything in one, but that's not really the right direction
<chewitt>
right now the 'hevc' driver isn't really working right, so g12a/b and sm1 aren't well supported
<Armbian-Discord>
<rpardini> switches to testing an S912 from the S922
<Armbian-Discord>
<rpardini> hmm, nice to know, I thought they were the same bits for all meson64
<Armbian-Discord>
<c0rnelius> @chewitt done any magic concerning the N2L and mainline u-boot?
<chewitt>
there's 2.5 generations
<chewitt>
gxbb, then gxl/gxm, then g12a/b + sm1
<chewitt>
gxbb/gxl/gxm are similar enough except gxbb not having vp9, and gxbb/gxl being 8-bit only (gxl converts 10-bit to 8-bit for output), then gxm has 10-bit output
<Armbian-Discord>
<Tonymac32> the regulator driver was contributed to me by Asus. the fan53555 driver is SO FREAKING BAD that I didn't even attempt to merge them into one
<Armbian-Discord>
<Tonymac32> like "I'm ashamed for the devs" bad
<Armbian-Discord>
<c0rnelius> @narmstrong ur awesome. thanx.
<Armbian-Discord>
<rpardini> buys an N2L
<Armbian-Discord>
<rpardini> yeah, thanks guys for all your work, it's awesome.
<Armbian-Discord>
<narmstrong> It’s a cool little boardy 🙂
<Armbian-Discord>
<Tenkawa> looks over at his
<Armbian-Discord>
<c0rnelius> i only wish it had ath
<Armbian-Discord>
<narmstrong> Yep it’s the only bad point
<Armbian-Discord>
<c0rnelius> indeed
<Armbian-Discord>
<Tenkawa> Not practical for me since my router is 180 ft away
<Armbian-Discord>
<Tonymac32> oooooooof I didn't notice that
<Armbian-Discord>
<c0rnelius> @Tenkawa still. I like options.
<Armbian-Discord>
<rpardini> well if the USB3 works decently... unlike the N2...
<Armbian-Discord>
<Tonymac32> should be no hub
<Armbian-Discord>
<Tenkawa> the USB3 flies
<Armbian-Discord>
<c0rnelius> the n2's usb3 is pretty spot on. the n2+ is not so much.
<Armbian-Discord>
<Tenkawa> I was amazed at even how well a thumbdrive ran
<Armbian-Discord>
<rpardini> oh, sorry, yeah, N2+ I meant.
<Armbian-Discord>
<Tonymac32> lol my N2 USB was toast
<Armbian-Discord>
<c0rnelius> not sure what thats about. poor design?
<Armbian-Discord>
<rpardini> Powering issues, a hog instead of proper hub, etc
<Armbian-Discord>
<Tonymac32> there are 3 revs of N2 before the USB3 was fixed
<Armbian-Discord>
<Tenkawa> I fried a
<Armbian-Discord>
<Tonymac32> but I don't have a fixed one to comment on the fix
<Armbian-Discord>
<Tenkawa> N2+
<Armbian-Discord>
<Tenkawa> but my N2 is solid
<Armbian-Discord>
<rpardini> mine N2+'s USB3 is fried.
<Armbian-Discord>
<Tenkawa> same
<Armbian-Discord>
<Tenkawa> rest works fine
<Armbian-Discord>
<Tonymac32> that's a Genesys logic hub on those, eh?
<Armbian-Discord>
<rpardini> ehh... I think so... haven't touched it, well, since it fried. heh...
<Armbian-Discord>
<Tenkawa> checking
<Armbian-Discord>
<Tenkawa> Bus 002 Device 002: ID 05e3:0620 Genesys Logic, Inc. USB3.1 Hub
<Armbian-Discord>
<Tenkawa> yes
<Armbian-Discord>
<Tonymac32> ah
<Armbian-Discord>
<Tonymac32> bummer on the no ETH thing on the N2L
<Armbian-Discord>
<Tonymac32> I wanted a 64-bit replacement for the MC1
<Armbian-Discord>
<Tenkawa> do you need more processing or io?
<Armbian-Discord>
<Tonymac32> MC1 is a compute board only
<Armbian-Discord>
<Tenkawa> if you don't need much network speed you could use the usb2 port for an eth dongle
<Armbian-Discord>
<Tonymac32> such a mess
<Armbian-Discord>
<Tenkawa> and save the usb3
<Armbian-Discord>
<Tonymac32> this is more like La Frite, just with a big SoC
<Armbian-Discord>
<Tonymac32> of course even that has ETH
<Armbian-Discord>
<c0rnelius> @Tenkawa has one. Says its nice.
<Armbian-Discord>
<Tonymac32> I'm sure it is, it just doesn't fit what I had in mind
<Armbian-Discord>
<Tonymac32> seems an interesting choice is all
<Armbian-Discord>
<c0rnelius> Currently we using the vendor uboot to get it going. I wanna try mainline of couse.
<Armbian-Discord>
<c0rnelius> Yes... Seems to be very specific. Meant to be embedded.
<Armbian-Discord>
<Tenkawa> The thing that surprised me is that its barely bigger than a Radxa zero.
<Armbian-Discord>
<Aoyfe> Sorry, back again.
<Armbian-Discord>
<Tonymac32> it should be an "A" size
<Armbian-Discord>
<Tonymac32> roughly
<Armbian-Discord>
<c0rnelius> Its the size of a XU4 right?
<Armbian-Discord>
<Tenkawa> Let me look
<Armbian-Discord>
<Aoyfe> I built u-boot and I flashed an sdcard with HardKernel's Ubuntu install. I don't see /dev/mtdblock0, but I do see /dev/spidev0.0. Is that the SPI or am I missing something
<Armbian-Discord>
<Tonymac32> that's a device so you can userspace some SPI devices
<Armbian-Discord>
<Tonymac32> you'd need to adjust the dtb to have the spi flash device
<Armbian-Discord>
<Aoyfe> Looks like what HK ships doesn't have it, then.
<Armbian-Discord>
<Aoyfe> Can I overwrite SPI from within pboot (which is booted from SPI)?
<Armbian-Discord>
<Tonymac32> unknown
<Armbian-Discord>
<Tenkawa> a bit smaller... xu4: 83 x 58 x 20 n2l: 69mm x 56mm x 22
<Armbian-Discord>
<Tenkawa> so mixed differences
<Armbian-Discord>
<Tenkawa> that 83 vs 69 is noticeable
<Armbian-Discord>
<c0rnelius> sweet... even with its lacking an eth i'm still very interested.
<Armbian-Discord>
<Tenkawa> I see why they are marketing these for industrial use
<Armbian-Discord>
<c0rnelius> i feel onboard wifi should have been the road taken.
<Armbian-Discord>
<c0rnelius> exactly
<Armbian-Discord>
<Tonymac32> ok pi A is 65x56
<Armbian-Discord>
<Tonymac32> so that's what I figured
<Armbian-Discord>
<Tonymac32> normal HAT bolt pattern
<Armbian-Discord>
<IdoLi> Hey, where is the lateset image file for Amlogic S905X3?
<Armbian-Discord>
<Tonymac32> we don't support that directly, maybe TV box?
<Armbian-Discord>
<IdoLi> yeah it's for a tv box
<Armbian-Discord>
<Tonymac32> or is it in a board I've forgotten? 🙂
<Armbian-Discord>
<IdoLi> ^^
<Armbian-Discord>
<Tonymac32> forums under TV boxes should have some info
<Armbian-Discord>
<IdoLi> okay
<Armbian-Discord>
<IdoLi> but I didn't find it any where
<Armbian-Discord>
<IdoLi> ill look again
<Armbian-Discord>
<IdoLi> thanks
<Armbian-Discord>
<Tonymac32> I don't handle those unfortunately
<Armbian-Discord>
<rpardini> tobetter's 5.x or 6.x trees have no mention of either old chip nor "new chip" -- they don't want you touching "their SPI NOR"
<Armbian-Discord>
<rpardini> goes touching HK's SPI NOR chip all over
<Armbian-Discord>
<narmstrong> Let’s touch it even harder
<Armbian-Discord>
<rpardini> yep, I'm patching (and a small detour to bump to 6.2-rc5)
<Armbian-Discord>
<rpardini> xt25f128b we had, I had... borrowed... either from chewitt's or Neil's tree...
<Armbian-Discord>
<rpardini> hopefully didn't mess up add for XT25Q64 in similar vein.
<Armbian-Discord>
<Aoyfe> So what's the difference between mtd and spidev?
<Armbian-Discord>
<rpardini> spidev are for generic spi stuff you connect to the gpio pins
<Armbian-Discord>
<rpardini> mtd is memory technology device, of which SPI NOR are one type of
<Armbian-Discord>
<Aoyfe> But your thought is that maybe since there's no SPI stuff exposed on the pins in the HC4 that might be connected to the board's SPI NOR?
<Armbian-Discord>
<rpardini> no, where did you get that idea.