sakman has quit [Remote host closed the connection]
sakman has joined #u-boot
sakman has quit [Read error: Connection reset by peer]
indy has quit [Ping timeout: 260 seconds]
indy has joined #u-boot
behanw has quit [Quit: Connection closed for inactivity]
camus has joined #u-boot
jackmitchell has joined #u-boot
redbrain has joined #u-boot
camus has quit [Ping timeout: 260 seconds]
camus has joined #u-boot
mmu_man has joined #u-boot
camus has quit [Ping timeout: 260 seconds]
jackmitchell has quit [Ping timeout: 260 seconds]
camus has joined #u-boot
camus has quit [Quit: camus]
akaWolf has quit [Ping timeout: 260 seconds]
<ac_slater>
Forty-Bot: awesome, thanks so much. That halps
<ac_slater>
helps *
akaWolf has joined #u-boot
<ac_slater>
I still can't tell if those hardcoded address are Xilinx(board) specific of Linux specific.
<ac_slater>
Forty-Bot: I looked at my kernel Image's header, and I see that magic 0x800000 "text_offset" that matches what Xilinx u-boot hardcodes as 4kernel_addr
<ac_slater>
$kernel_addr *
<Forty-Bot>
they are specific to a particular ram layout
<Forty-Bot>
though I think the kernel address is for <5.8 kernels only; for newer kernels the load address is 0
<mwalle>
Tartarus: thanks, btw. I'd like to add myself as a reviewer to the ls1028a devicetree include. So I get changes without constantly watching the ML
<mwalle>
Tartarus: should i add an entry to MAINTAINERS or should i just add that file to my board MAINTAINERS file
<Tartarus>
mwalle: Go whack whatever MAINTAINERS files list the dts* that you care about
<Tartarus>
And in the event that none currently do, probably should whack a more top-level entry that already exists, I hope
<mwalle>
Tartarus: I didn't find anything layerscape specific
<Tartarus>
mwalle: Sigh, yes, a high level MAINTAINERS is missing :(
<mwalle>
Tartarus: also, if i add a new entry, it wouldn't have a maintainer. at least if i wouldn't add someone from nxp
<mwalle>
so the simplest solution would be to just add the file to board/kontron/sl28/MAINTAINERS, being an include file shared among other boards that would be a grey area ;)
<Tartarus>
Yeah
<Tartarus>
And I need to poke NXP folks, sigh.
<mwalle>
Tartarus: is that "yeah" a go ahead and add it?
redbrain has quit [Ping timeout: 268 seconds]
<mwalle>
mhh should board/path/to/MAINTAINERS work at all? Either it doesn't or I'm missing some flags to scripts/get_maintainer.pl
<Tartarus>
It's supposed to work, and get_maintainers.pl is supposed to support it as well, esp given our project .get_maintainer.conf file
<Tartarus>
And yes, add an entry to the board one for now
<mwalle>
Tartarus: mhh, I don't see a get_maintainer.conf in the u-boot top level
<Tartarus>
... I thought we had one, but no
<Tartarus>
just checkpatch
<mwalle>
if i could just decipher that perl code *g
<mwalle>
Tartarus: mh. for me, scripts/get_maintainer.pl works only with the following options: --find-maintainer-files --maintainer-path=.
<Tartarus>
mwalle: how about in a .get_maintainers.conf file in the project?
<mwalle>
Tartarus: that works, should I post a patch
smartin has joined #u-boot
espeer has joined #u-boot
<espeer>
Hello. Anyone had any luck booting a nanopi-r2s board from SPI flash?
mthall has joined #u-boot
smartin has quit [Quit: smartin]
<simeonm>
^ further to espeer's question: or more generally, booting an RK3328 system (e.g. Rock64 or some chromebooks) from SPI flash