15:09 <SheriF> I am trying to debug u-boot, where does the u-boot.map is located after the crash?

17:46 <sjg1> SheriF: It is generated by building U-Boot. It is not available within U-Boot when running it

18:09 <sjg1> Tartarus: Hi, I'd like to apply the ACPI-refactoring patches from this series: https://patchwork.ozlabs.org/project/uboot/list/?series=274675&state=*

18:10 <sjg1> Tartarus: then perhaps try another version. I have not seen any reviews from the ARM side though

18:10 <sjg1> Tartarus: What do you think?

18:13 <mps> whom to report bug for peach pi chromebook (exynos-5800) about spi

18:14 <mps> I got this on boot `cros_ec_command: Returned status 1`

18:14 <mps> and on any keypress I got this `Card did not respond to voltage select! : -110`

18:14 <mps> though it boots kernel fine

18:16 <mps> or it is not related to SPI but something else

18:25 <sjg1> mps: https://source.denx.de/groups/u-boot/-/issues

18:26 <sjg1> mps: If you add a link here I'll make some comments

18:28 <mps> sjg1: I have to register there to create issue?

18:29 <sjg1> mps: Yes I already registered, but yes, you do. I don't have that device in my lab at present but I could add it. Feel free to send an email to the mailing list also in the meantime

18:30 <mps> sjg1: ok, I will send mail

18:32 <mps> looking source I think it is mmc issue and not spi

18:39 <SheriF> sigmaris:ccccccnjgtkdbgituvijhvijvnvheutjjifevjuftjge

18:39 <SheriF> ccccccnjgtkdurguiiffnlunscdfgufkkolnfkveruvnhd

18:39 <SheriF> sorry, about this garbage :D darn yubikey :)

18:40 <SheriF> sjg1: thanks! I will check the package, I am building off fedora 2022.01 package and if the distro + ubotu on emmc, cpu resets, if the uboot on emmc and distor in sdcard on rk3399,it boots, so I am just trying to figure out what is wrong

18:56 <sjg1> SheriF: Is this using chainloading or bare metal?

19:09 <SheriF> I am not sure to be honest, I am so new to this :) so I have the uboot on the image and then that uboot loads efi and the efi will load shimaa64 / bootaa64 to grub and goes kernel from there, not sure if that consider chaining? I am using pine64 rockpro64 and I guess it is only "maskrom" that boots uboots and then all goes from there, fedora35 works btw with the uboot I built from fedora rpms

20:02 <mps> sjg1: after looked more at peach pi problem I talked about above I think I should try first to reset its flash and test again to see will it happen again, so will not report bug yet, maybe it is not problem with u-boot

20:50 <sjg1> SheriF: neither am I. Here are the instructions, if you are not reflashing the SPI then it must be chain-loading

20:50 <sjg1> SheriF: https://u-boot.readthedocs.io/en/latest/chromium/chainload.html