00:58
apritzel has quit [Ping timeout: 246 seconds]
01:00
mmu_man has quit [Ping timeout: 250 seconds]
01:33
Peng_Fan has joined #u-boot
01:50
yollom_ has quit [Server closed connection]
01:50
yollom has joined #u-boot
01:58
rvalue has quit [Ping timeout: 246 seconds]
02:04
jclsn has quit [Ping timeout: 264 seconds]
02:06
jclsn has joined #u-boot
02:10
rvalue has joined #u-boot
02:10
qqq has quit [Remote host closed the connection]
03:02
jclsn has quit [Ping timeout: 246 seconds]
03:04
jclsn has joined #u-boot
03:06
teejay has joined #u-boot
04:00
wooosaiiii has joined #u-boot
04:23
wooosaiiii has quit [Quit: wooosaiiii]
04:23
wooosaiiii1 has joined #u-boot
04:26
wooosaiiii1 is now known as wooosaiiii
04:35
LinuxHackerman has quit [Server closed connection]
04:38
LinuxHackerman has joined #u-boot
05:08
kabel has quit [Server closed connection]
05:09
kabel has joined #u-boot
05:32
monstr has joined #u-boot
05:34
monstr_ has joined #u-boot
05:34
monstr has quit [Remote host closed the connection]
05:42
Wouter0100670440 has joined #u-boot
05:54
wooosaiiii has quit [Quit: wooosaiiii]
05:55
wooosaiiii has joined #u-boot
06:01
rvalue has quit [Ping timeout: 240 seconds]
06:11
rvalue has joined #u-boot
06:24
goliath has joined #u-boot
06:32
sng has joined #u-boot
06:33
apritzel has joined #u-boot
06:35
justache has quit [Server closed connection]
06:36
justache has joined #u-boot
06:41
srk has quit [Remote host closed the connection]
06:42
srk has joined #u-boot
06:48
ldevulder_ has quit [Quit: Leaving]
06:51
sszy has joined #u-boot
06:55
apritzel has quit [Ping timeout: 240 seconds]
07:03
ldevulder has joined #u-boot
07:05
sng has quit [Remote host closed the connection]
07:07
sng has joined #u-boot
07:23
ldevulder_ has joined #u-boot
07:25
foxtrot has quit [Server closed connection]
07:26
foxtrot has joined #u-boot
07:28
ldevulder has quit [Ping timeout: 245 seconds]
08:01
sng has quit [Remote host closed the connection]
08:09
ldevulder_ is now known as ldevulder
08:11
ikarso has joined #u-boot
08:33
jpanisbl has joined #u-boot
08:34
sng has joined #u-boot
08:35
naoki has quit [Quit: naoki]
08:41
jpanisbl has quit [Ping timeout: 264 seconds]
08:42
jpanisbl has joined #u-boot
08:44
sng has quit [Remote host closed the connection]
08:46
sng has joined #u-boot
08:51
camus has quit [Remote host closed the connection]
08:57
apalos- has joined #u-boot
09:10
\dev\ice has quit [Changing host]
09:10
\dev\ice has joined #u-boot
09:14
Peng_Fan has quit [Quit: Connection closed for inactivity]
09:17
mmu_man has joined #u-boot
09:19
jpanisbl has quit [Ping timeout: 264 seconds]
09:19
jpanisbl has joined #u-boot
09:30
apalos- has joined #u-boot
09:31
apalos- has quit [Client Quit]
09:32
redbutton has quit [Server closed connection]
09:33
redbutton has joined #u-boot
09:33
apalos- has joined #u-boot
10:05
apritzel has joined #u-boot
10:09
jpanisbl has quit [Quit: Konversation terminated!]
10:16
apalos- has joined #u-boot
10:17
apalos- has quit [Client Quit]
10:19
brujah has joined #u-boot
10:37
apalos- has joined #u-boot
11:17
PhoenixMage has joined #u-boot
11:17
<
PhoenixMage >
Is it possible to dump what modules are in a grub image?
11:23
rvalue has quit [Ping timeout: 240 seconds]
11:33
rvalue has joined #u-boot
12:11
sng has quit [Remote host closed the connection]
12:12
rainbyte has joined #u-boot
12:17
jpanisbl has joined #u-boot
12:17
rainbyte_ has joined #u-boot
12:20
rainbyte__ has joined #u-boot
12:21
jpanisbl has quit [Client Quit]
12:22
cbmuser has quit [Server closed connection]
12:22
cbmuser has joined #u-boot
12:23
jpanisbl has joined #u-boot
12:27
rainbyte has quit [Remote host closed the connection]
12:27
rainbyte__ is now known as rainbyte
12:34
sng has joined #u-boot
12:36
sng has quit [Remote host closed the connection]
12:37
sng has joined #u-boot
12:45
<
jclsn >
One question about line-names. When set as gpio-line-names in the device tree, should they be printed after the gpio value when calling gpio status?
12:45
<
jclsn >
I am asking because I just set a hog, where I also set the line name. Now they line name is printed as LINE_NAME.gpio-hog after the value
12:46
<
marex >
jclsn: check the code ?
12:46
<
jclsn >
Since we already set all line names before though, I would expect that the line name should be set already. It seems to me like it is not working correctly for all the other pins
12:47
<
jclsn >
marex: Yeah you are right
12:47
<
marex >
afaict if you request the GPIO, the line name will be in the list
12:50
<
marex >
jclsn: why are you looking at u-boot 2022.04 , that's horribly outdated version
12:50
<
jclsn >
marex: We are stuck on that version
12:51
<
jclsn >
The bootloader is part of the hardware. Long story. It is a complex project :)
12:51
<
marex >
jclsn: then please ask your vendor for support
12:52
<
jclsn >
It is not about the vendor
12:52
<
jclsn >
We are the vendor
12:52
<
jclsn >
We are using mainline u-boot but cannot update for specific reasons
12:54
<
marex >
jclsn: then you need to either support yourself, or update and work on latest codebase
12:55
<
jclsn >
So I should only ask questions about the latest version?
12:55
<
marex >
if you are debugging something, always try the latest version, chance is, the bug is already fixed
12:56
mmu_man has quit [Ping timeout: 240 seconds]
12:56
<
jclsn >
I would if I could ^^
12:56
<
marex >
not my problem really
12:57
<
marex >
you can try and start uboot from uboot, load ... dcache off ; icache off ; go 0xaddress
12:57
<
jclsn >
interesting
13:00
<
jclsn >
Thanks for the advice. It is really something to consider to circumevent this painful regulation
13:06
mmu_man has joined #u-boot
13:13
sng has quit [Read error: Connection reset by peer]
13:23
apalos- has quit [Read error: Connection reset by peer]
13:23
<
rainbyte >
hello, I have been doing some bisecting and found a group of commits which cause black scren on Asus C201
13:40
apalos- has joined #u-boot
13:42
jpanisbl has quit [Ping timeout: 240 seconds]
13:59
jpanisbl has joined #u-boot
14:04
ikarso has quit [Quit: Connection closed for inactivity]
14:04
mmu_man has quit [Ping timeout: 240 seconds]
14:08
<
alpernebbi >
rainbyte: are you talking about libreboot or just u-boot
14:10
jpanisbl has quit [Quit: Konversation terminated!]
14:10
<
alpernebbi >
I'm told c201 works on u-boot master if you enable DM_RESET, HAS_ROM, ROCKCHIP_SPI_IMAGE and use u-boot.rom
14:14
<
alpernebbi >
I assume you reached the commits that add rk3399 support to rockchip edp driver which make it necessary to use DM_RESET
14:17
apalos- has joined #u-boot
14:19
<
alpernebbi >
do tell if it's something else, but if you were testing u-boot as part of libreboot it might be better to talk on #libreboot (with me)
14:19
<
rainbyte >
I tried with pure u-boot, given that I couldn't make libreboot work
14:20
<
rainbyte >
the affecting commits are 9749d2ea29 and cd529f7ad6
14:21
<
alpernebbi >
yes those are what I meant
14:22
<
rainbyte >
I tried with the default config and didn't work, so I reverted those commits and worked
14:22
<
alpernebbi >
try enabling DM_RESET in your config, and adding "select"s for HAS_ROM and ROCKCHIP_SPI_IMAGE in /arch/arm/mach-rockchip/rk3288/Kconfig for veyron boards
14:24
<
rainbyte >
ok, I will try that suggestion... will those options be included in the default config in the future? (or at least in the docs?)
14:25
<
alpernebbi >
assuming I find the time to send a patch, yes
14:26
<
rainbyte >
I could try to help writing a patch, is there some guidelines I should take into account?
14:27
<
alpernebbi >
I'll do it, don't worry about it
14:27
<
rainbyte >
ok, thanks
14:27
<
rainbyte >
the machine it is working fine now, but I will test those options
14:28
<
alpernebbi >
please test and report back, reverting those is not really an option because it makes gru-kevin and others work
14:28
<
rainbyte >
by the way, I'm having trouble with other Veyron machine, but this one is a Veyron Jerry
14:29
<
alpernebbi >
I'm also told those aren't enough to make it work on jerry
14:29
apalos- has joined #u-boot
14:29
apalos- has quit [Client Quit]
14:30
<
rainbyte >
u-boot is booting since commit 70e351bd, it was black screen before that commit in this machine
14:30
<
rainbyte >
I have access to u-boot console, but if I try to boot Linux from there it given green garbage and then it stops booting
14:30
apalos- has joined #u-boot
14:31
monstr_ has quit [Remote host closed the connection]
14:31
<
rainbyte >
similar kernel config is working fine with vendor bootloader
14:32
goliath has quit [Quit: SIGSEGV]
14:32
<
rainbyte >
(I didn't even need to revert the commits, it seems DM_RESET is there by default for Jerry)
14:32
<
alpernebbi >
I've been seeing that green garbage on gru-kevin, it used to boot with older kernels but likewise can't boot with newer kernels
14:33
<
alpernebbi >
don't know why, but I'll get back to working on u-boot real soon, can investigate it on a veyron mighty I have
14:33
<
alpernebbi >
in the meantime, try booting through EFI
14:34
<
rainbyte >
is there some way I could provide useful info? I tried UART but it is not showing meaningful errors
14:34
<
rainbyte >
I tried to start edk2 shell with EFI, and there is also garbage on the screen :(
14:35
<
alpernebbi >
I'm not sure what to look for honestly, will need a lot of code-flash-think cycles
14:36
<
rainbyte >
I see, it needs more investigation
14:36
<
rainbyte >
I extracted dtbs from vendor system, not sure if it could help
14:37
apalos- has joined #u-boot
14:37
mmu_man has joined #u-boot
14:38
<
rainbyte >
it is a machine locally branded as BGH G1160, I couldn't find too much info, but I suspect it is similar to Hisense C11
14:39
<
alpernebbi >
they are both "jerry", so yes
14:40
<
rainbyte >
could it be possible that panel is different from other Jerry's?
14:42
mmu_man has quit [Ping timeout: 240 seconds]
14:43
<
Forty-Bot >
marex: maybe he burned U-Boot into ROM and only has a console :)
14:44
<
alpernebbi >
rainbyte: as long as it works on mainline linux we can use that dtb and make it work I think
14:47
<
rainbyte >
I'm using default chromebook_jerry_defconfig, is there some option I could try?
14:48
<
rainbyte >
or if u-boot is already showing something on screen it means problem is on Linux kernel dtb / driver?
14:49
<
alpernebbi >
could be on either side, idk
14:50
<
alpernebbi >
what I meant is can you boot linux from stock firmware and have the panel work
14:51
<
rainbyte >
I tried many combinations, but if I remember well I could boot kernel 4.19 with stock firmware and postmarketos kernel config
14:52
<
rainbyte >
I will try again also with newest version and report here
14:52
<
rainbyte >
a few minutes ago I flashed back the stock firmware
14:53
sng has joined #u-boot
14:54
<
alpernebbi >
if you're going to use postmarketos do a fresh install
14:55
<
alpernebbi >
might be worth mentioning there if it works on your jerry
14:57
rainbyte__ has joined #u-boot
14:57
rainbyte___ has joined #u-boot
14:59
rainbyte_ has quit [Ping timeout: 240 seconds]
14:59
rainbyte has quit [Ping timeout: 246 seconds]
14:59
rainbyte___ is now known as rainbyte
15:00
<
rainbyte__ >
alpernebbi, I only copied kernel config from pmOS, the userland was ArchLinuxARM
15:00
<
rainbyte__ >
but I could try full pmOS, there is no important data on the device
15:02
mmu_man has joined #u-boot
15:03
rainbyte has quit [Quit: rainbyte]
15:03
rainbyte has joined #u-boot
15:04
<
alpernebbi >
it may still have the green garbage with u-boot, but it's tested to work with depthcharge
15:04
rainbyte_ has joined #u-boot
15:05
Leopold has quit [Ping timeout: 246 seconds]
15:05
<
alpernebbi >
brb, food
15:07
rainbyte__ has quit [Ping timeout: 252 seconds]
15:14
Leopold has joined #u-boot
15:19
mmu_man has quit [Ping timeout: 246 seconds]
15:38
sng has quit [Remote host closed the connection]
15:58
apritzel has quit [Ping timeout: 240 seconds]
15:59
mmu_man has joined #u-boot
16:02
Wouter0100670440 has joined #u-boot
16:02
apalos| has joined #u-boot
16:14
mmu_man has quit [Ping timeout: 240 seconds]
16:15
apritzel has joined #u-boot
16:19
vagrantc has joined #u-boot
16:28
mmu_man has joined #u-boot
16:48
goliath has joined #u-boot
16:50
apalos- has joined #u-boot
16:52
apalos- has quit [Client Quit]
16:53
apalos- has joined #u-boot
17:08
goliath has quit [Ping timeout: 260 seconds]
17:21
goliath has joined #u-boot
17:46
rainbyte has quit [Quit: rainbyte]
17:50
rainbyte_ has quit [Ping timeout: 245 seconds]
17:50
mmu_man has quit [Ping timeout: 260 seconds]
18:02
rainbyte_ has joined #u-boot
18:09
qqq has joined #u-boot
18:18
sng has joined #u-boot
18:19
sng has quit [Remote host closed the connection]
18:20
sng has joined #u-boot
18:21
rainbyte_ has quit [Ping timeout: 246 seconds]
18:38
mmu_man has joined #u-boot
18:44
goliath has quit [Quit: SIGSEGV]
18:45
sbach has quit [Remote host closed the connection]
18:45
sbach has joined #u-boot
18:49
WoC has quit [Remote host closed the connection]
18:49
WoC has joined #u-boot
18:53
rainbyte_ has joined #u-boot
19:22
samueldr is now known as samueldr[m]
19:23
samueldr has joined #u-boot
19:29
samueldr[m] has left #u-boot [#u-boot]
19:34
___nick___ has joined #u-boot
19:34
Hypfer has quit [Read error: Connection reset by peer]
19:34
Hypfer has joined #u-boot
19:53
___nick___ has joined #u-boot
19:54
___nick___ has quit [Client Quit]
19:57
___nick___ has joined #u-boot
19:57
Wouter0100670440 has joined #u-boot
20:04
___nick___ has quit [Ping timeout: 260 seconds]
20:20
apritzel has quit [Ping timeout: 246 seconds]
20:54
sng has quit [Read error: Connection reset by peer]
21:10
redbrain has quit [Read error: Connection reset by peer]
21:16
redbrain has joined #u-boot
21:38
marc1 has quit [Server closed connection]
21:39
marc1 has joined #u-boot
21:43
brujah has quit [Quit: Leaving]
21:47
apritzel has joined #u-boot
21:52
mckoan_ has joined #u-boot
21:55
mckoan|away has quit [Ping timeout: 260 seconds]
22:45
m5zs7k has quit [Ping timeout: 246 seconds]
22:45
m5zs7k has joined #u-boot
23:21
apritzel has quit [Ping timeout: 264 seconds]
23:41
naoki has joined #u-boot