urja has quit [Read error: Connection reset by peer]
urja has joined #u-boot
KREYREN has joined #u-boot
<KREYREN>
is it possible to put uboot on SnapDragon Mobile 845 device? (Xiaomi-Ursa or Xiaomi Mi8 Pro Explorer Edition) while it still supporting both Android And Linux?
sszy has joined #u-boot
enok has joined #u-boot
naoki has quit [Quit: naoki]
enok has quit [Read error: Connection reset by peer]
enok71 has joined #u-boot
KREYREN has quit [Ping timeout: 264 seconds]
enok71 has quit [Ping timeout: 244 seconds]
KREYREN has joined #u-boot
mmu_man has joined #u-boot
clamor has quit [Ping timeout: 248 seconds]
clamor has joined #u-boot
<f_>
KREYREN: there's been work on that area
<f_>
Ah "still supporting both Android And Linux?" not sure about Android though
<KREYREN>
f_, Do you have more info on that? I would like to get u-boot on that device and on Quest 3S
sally has quit [Ping timeout: 272 seconds]
enok has joined #u-boot
<KREYREN>
f_, android afaik works on u-booted SBCs what would it change there?
<f_>
IIRC I was just told downstream android requires stuff u-boot doesn't provide
<sjg1>
jdautheribes: It seems that when it comes to read the FDT blob from disk, it doesn't have the filename. I suppose that state.Prepare() , which sets up the available dtbs, does not see 'spl/u-boot-spl.dtb' available and so there is no DTB for SPL ?
<sjg1>
jdautheribes: It would be better for Entry_blob_dtb.ObtainContents() to raise an exception if self._pathname() is None
<clamor>
sjg1: ping me when you get to bloblist. Thanks!
KREYREN has quit [Remote host closed the connection]
KREYREN has joined #u-boot
mripard has quit [Quit: WeeChat 4.5.1]
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
Stat_headcrabbed has quit [Remote host closed the connection]
vagrantc has joined #u-boot
Stat_headcrabbed has joined #u-boot
KREYREN has quit [Ping timeout: 264 seconds]
eballetbo has quit [Quit: Connection closed for inactivity]
<paulbarker>
Tartarus: Do you have any thoughts on adding a CONFIG_WERROR option to U-Boot, similar to the one in the Linux kernel?
<paulbarker>
It's useful to be able to use the same method to catch warnings when jumping between U-Boot and Linux, and it can be disabled by default.
<paulbarker>
I can send the patch, but thought it's worth a quick check if it's wanted first
<Tartarus>
In a call atm
<paulbarker>
Tartarus: No rush :)
<marex>
export KCFLAGS=-Werror ; make ...
<marex>
yes , Werror is useful
<paulbarker>
marex: I know it can be enabled with KCFLAGS. I still like to have the config option to match Linux
<marex>
paulbarker: I am all for it
clamor has quit [Ping timeout: 265 seconds]
Stat_headcrabbed has quit [Remote host closed the connection]
monstr has quit [Remote host closed the connection]
jdautheribes has quit [Ping timeout: 260 seconds]
monstr has joined #u-boot
monstr has quit [Remote host closed the connection]
<Tartarus>
paulbarker: So, yes, we've been using Werror in CI for forever, so I don't see a problem with making that the default behavior more easily. I hope a cherry-pick applies cleanly enough, but please do, thanks.
<paulbarker>
Tartarus: It's not quite a cherry-pick from Linux to U-Boot, but it's a simple patch
<paulbarker>
I'll send it later today
<Tartarus>
Sounds good
<marex>
qschulz: I assume it isnt possible to use HDMI as GPIOs on RK3568 ?
clamor has joined #u-boot
<marex>
vagrantc: is upstream/2025.01 what I want to rebase the debian uboot stuff on ?
<marex>
vagrantc: or is that debian/latest ?
<vagrantc>
marex: debian/latest includes the packaging changes
<vagrantc>
marex: which includes all of upstream/2025.01 ...
<marex>
vagrantc: ah yes, I see it now
<marex>
vagrantc: and if I want to test the package build, just do some dpkg-buildpackage -us -uc -nc -j`nproc` ?
<vagrantc>
looks like upstream/2025.01 == v2025.01
<marex>
or do I need to do native build ?
<vagrantc>
i used to have to remove some files and make a +dfsg version, but now upstream removed all the files i was removing, so yay. :)
<marex>
woohoo, always good to make it easier for packagers
<vagrantc>
marex: hmmm... i use sbuild to do cross builds as it helps get it right more easily ... or native builds withh dpkg-buildpackage
<vagrantc>
in theory you could do cross builds with dpkg-buildpackage too, but i do not remember all the details :)
<vagrantc>
marex: you're maybe the third person in the last week to ask about the status in debian ... really ought to slog through the copyright review and get this uploadable...
<vagrantc>
but obviously, i am not sure there is anyone in the world who has fun doing that. :)
<marex>
vagrantc: I don't want to push you obv
<marex>
vagrantc: I have an email from you in my mailbox from like 2023 which says , test dh_imx6 in debian ... so, I got to it, heh
<vagrantc>
i want to push me, at least ... it has been nagging at me
<marex>
vagrantc: and I figured it is time to fix the rest too
<vagrantc>
i also owe upstream a couple patches too, so it goes both ways :)
<vagrantc>
more than a couple, probably...
<marex>
vagrantc: u-boot too ?
<vagrantc>
a few niggling typos and some obviously not right SPDX headers ... probably posted to the list about them about a year or so ago but never got around to the patches
<vagrantc>
in u-boot, yeah
<marex>
ah
<vagrantc>
hah. 2023-11-21 sounds like
<vagrantc>
regarding the weird licensing discrepancies
<marex>
vagrantc: the email from you is from 2022-12-29 , ugh ... time sure flies
<vagrantc>
marex: you... win? :)
<marex>
vagrantc: well ... at least it is not forgotten :)
<vagrantc>
submissions are still via email, not merge requests or something?
<marex>
vagrantc: email, although Tartarus is experimenting with some gitlab stuff
<Tartarus>
Gitlab is more about enabling CI for more people than trying a pull request approach more broadly, atm
clamor has quit [Read error: Connection reset by peer]
<Tartarus>
marex: Looking at some output from a tool Simon pointed out, what's the state of RZN1 stuff? There's a single instance of ARCH_RZN1 in drivers/pinctrl/Makefile
<marex>
Tartarus: I think that was something Linaro upstreamed, not much activity there, why ?
<Tartarus>
Because there's unused code around that symbol. Not a huge deal or anything
<marex>
Tartarus: oh ?
<marex>
Tartarus: which code ?
<Tartarus>
drivers/pinctrl/Makefile :)
<marex>
Tartarus: eh ? drivers/pinctrl/renesas surely is used ?
<Tartarus>
ARCH_RZN1 does not exist as a symbol
<marex>
oh, ARCH_RZN1 symbol ... huh ... send email to Ralph ?
f_[x] has quit [Ping timeout: 260 seconds]
<Tartarus>
Meh, it's just one line, I'll let it go if you aren't worried
<Tartarus>
but I see a bunch of dead USB code that was missed with removing rx51