kaji has quit [Quit: You have been kicked for being idle]
redbrain has joined #u-boot
Rondom has quit [Remote host closed the connection]
Rondom has joined #u-boot
sdfgsdfg has quit [Quit: sdfgsdfg]
sdfgsdfg has joined #u-boot
qastokes has quit [Quit: qastokes]
sdfgsdfg has quit [Quit: ZzzZ]
smartin has joined #u-boot
smartin has quit [Ping timeout: 265 seconds]
camus has joined #u-boot
sdfgsdfg has joined #u-boot
sdfgsdfg has quit [Quit: ZzzZ]
v0|d has quit [Remote host closed the connection]
vagrantc has joined #u-boot
camus has quit [Remote host closed the connection]
qastokes has joined #u-boot
qastokes has quit [Quit: qastokes]
qastokes has joined #u-boot
qastokes has quit [Quit: qastokes]
qastokes has joined #u-boot
qastokes has quit [Client Quit]
senzilla has quit []
senzilla has joined #u-boot
sdfgsdfg has joined #u-boot
smartin has joined #u-boot
qastokes has joined #u-boot
smartin has quit [Quit: smartin]
sdfgsdfg has quit [Quit: ZzzZ]
qastokes has quit [Quit: qastokes]
v0|d has joined #u-boot
qastokes has joined #u-boot
redbrain has quit [Ping timeout: 268 seconds]
macromorgan has joined #u-boot
sbach has quit [Ping timeout: 250 seconds]
milkylainen has quit [Ping timeout: 245 seconds]
sbach has joined #u-boot
<samueldr>
hi, I'm starting to get deep into uncharted territories for me; trying to get started on an Allwinner A64 MIPI DSI Host driver
<samueldr>
I'm having troubles wrapping my head around the device model for that
<samueldr>
I assume the `sunxi_de2` needs to *somehow* be involved to get the driver bound/probed, since it is for LCD/HDMI AFAIUI
<samueldr>
both of `sunxi_dw_hdmi` and `sunxi_lcd` are `UCLASS_DISPLAY`; that doesn't sound right for DSI, I assume it would be UCLASS_DSI_HOST here
<samueldr>
(given the linux driver is drivers/gpu/drm/sun4i/sun6i_mipi_dsi.c; sun6i_dsi_platform_driver)
<samueldr>
what I'm missing here is: what would be providing a `UCLASS_DISPLAY` to use?
<samueldr>
AFAIUI if I used the `UCLASS_DSI_HOST` driver in the probe sequence of the `sunxi_de2` driver, it shouldn't work as it's not a `UCLASS_DISPLAY`, and it's calling `display_*` functions on it
qastokes has quit [Quit: qastokes]
hurricos has joined #u-boot
<hurricos>
I've scoured the internet for a solution to a fairly simple problem
<hurricos>
"Where are my kernel logs?"
<samueldr>
simple problem, complex answer
<hurricos>
I have a P1020 RDB-based board which crashes silently
<samueldr>
it may be easier to reframe the problem: where do you expect your kernel logs to be?
<hurricos>
it has a WDT so it can soft-reboot
<hurricos>
After I look at System.map, I expect them to be at __log_buf
<samueldr>
(I can't help much further than that, but that's where I would start from if I knew about the platform)
<hurricos>
and yet, they are not there in their entirety, only small parts of frames of them.