ikarso has quit [Quit: Connection closed for inactivity]
slobodan has quit [Ping timeout: 256 seconds]
qschulz has quit [Remote host closed the connection]
qschulz has joined #u-boot
macromorgan has quit [Read error: Connection reset by peer]
macromorgan has joined #u-boot
apritzel has quit [Ping timeout: 245 seconds]
goliath has quit [Quit: SIGSEGV]
thopiekar has quit [Ping timeout: 256 seconds]
thopiekar has joined #u-boot
jclsn has quit [Ping timeout: 256 seconds]
jclsn has joined #u-boot
<tlwoerner>
given a specific board (rock-pi-e)
<tlwoerner>
earlier revisions had the rtl8211e phy, newer ones have the rtl8211f phy
<tlwoerner>
currently the device tree for the rock-pi-e only has a stanza for the rtl8211e
<tlwoerner>
but if i added a second stanza for the rtl8211f and set both to: 'status = "disabled"'
<tlwoerner>
is there a way to set one of them to 'status = "okay"' in the e/f probe function before passing off to linux?
<tlwoerner>
(or is there a better way to go about this?)
dhruvag2000 has joined #u-boot
Leopold has quit [Ping timeout: 245 seconds]
Leopold has joined #u-boot
mmu_man has quit [Ping timeout: 264 seconds]
Leopold has quit [Remote host closed the connection]
Leopold has joined #u-boot
<jan_V2>
it sounds like you'd need 2 different files for each board
<jan_V2>
that's what most manufacturers do, when they have differences like that
<jan_V2>
usually they'd have a board-name-common.dtsi, and and then board-ref-a.dts and board-ref-b.dts
<jan_V2>
the files with the revision, only contain the differences
Clamor has joined #u-boot
ikarso has joined #u-boot
Clamor has quit [Read error: Connection reset by peer]
Clamor has joined #u-boot
sakman has joined #u-boot
GNUtoo has quit [Ping timeout: 240 seconds]
GNUtoo has joined #u-boot
jaganteki has joined #u-boot
norton has joined #u-boot
prabhakarlad has joined #u-boot
monstr has joined #u-boot
slobodan has joined #u-boot
apritzel has joined #u-boot
Mis012 has quit [Remote host closed the connection]
Mis012 has joined #u-boot
Hammdist has quit [Quit: Client closed]
apritzel has quit [Ping timeout: 276 seconds]
mmu_man has joined #u-boot
dsimic has quit [Ping timeout: 240 seconds]
dsimic has joined #u-boot
rvalue has quit [Ping timeout: 276 seconds]
rvalue has joined #u-boot
goliath has joined #u-boot
Clamor has quit [Ping timeout: 260 seconds]
Clamor has joined #u-boot
apritzel has joined #u-boot
jaganteki has quit [Ping timeout: 250 seconds]
apritzel has quit [Ping timeout: 260 seconds]
jaganteki has joined #u-boot
Clamor has quit [Ping timeout: 260 seconds]
Clamor has joined #u-boot
Hammdist has joined #u-boot
ad__ has quit [Changing host]
ad__ has joined #u-boot
<marex>
tlwoerner: look at what the board/dhelectronics/dh_imx8mp did with patching DTs and does now with DTOs
<marex>
tlwoerner: and then ... fdt set $fdtcontroladdr -> figure out which DTO was applied by U-Boot to its control DT, and apply matching to Linux DT in some boot script
prabhakarlad has quit [Quit: Client closed]
Hammdist has quit [Quit: Client closed]
Hammdist has joined #u-boot
Hammdist has left #u-boot [#u-boot]
jaganteki has quit [Quit: Client closed]
jaganteki has joined #u-boot
jaganteki has quit [Ping timeout: 250 seconds]
apritzel has joined #u-boot
prabhakar has quit [Quit: Connection closed]
prabhakar has joined #u-boot
prabhakarlad has joined #u-boot
goliath has quit [Quit: SIGSEGV]
prabhakarlad has quit [Quit: Client closed]
prabhakar has quit [Quit: Connection closed]
prabhakarlad has joined #u-boot
prabhakar has joined #u-boot
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
vagrantc has joined #u-boot
prabhakarlad has quit [Quit: Client closed]
rvalue has quit [Ping timeout: 246 seconds]
rvalue has joined #u-boot
<Clamor>
sjg1: you prefer v2 not v4?
<Clamor>
Or how should I react to your review?
apritzel has quit [Ping timeout: 260 seconds]
<sjg1>
Clamor: Which review?
<Clamor>
sjg1: fastboot console commits. membuf commit to be exact