<apritzel>
renze: the .dts file says: "Minimal dts file for the iNet 3F for u-boot only". There is no SD card node in there. Look at other .dts files and add some "&mmc0 { status = "okay"; .... }
apritzel has quit [Ping timeout: 480 seconds]
Luke-Jr has quit [Ping timeout: 480 seconds]
Mangy_Dog has quit [Ping timeout: 480 seconds]
Luke-Jr has joined #linux-sunxi
vagrantc has quit [Quit: leaving]
cnxsoft has joined #linux-sunxi
Mangy_Dog has joined #linux-sunxi
cnxsoft has quit [Remote host closed the connection]
megi1 has quit [Ping timeout: 480 seconds]
megi1 has joined #linux-sunxi
c23456 has joined #linux-sunxi
c23456 has quit [Ping timeout: 480 seconds]
apritzel has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
tnovotny has joined #linux-sunxi
joaoSchim__ is now known as JoaoSchim
uwu has joined #linux-sunxi
<renze>
apritzel: thanks, I will try that this evening
apritzel has joined #linux-sunxi
uwu has quit []
TuxBlackEdo has quit []
lunixoid has joined #linux-sunxi
<JoaoSchim>
Anyone have a good reference/overview of DRM/KSM in relation to sunxi/allwinner ? Need to get the basic concepts straight.
<JoaoSchim>
i mean DRM/KMS
<JoaoSchim>
i did find a presentation by Jagan Teki (Demystifying Linux MIPI-DSI Subsystem) but i guess i need some more familiarity with the terms used.
<buZz>
demystifying sounds like a good route to familiarity ;)
<buZz>
a lot of it isnt even allwinner specific
megi1 has quit [Ping timeout: 480 seconds]
<JoaoSchim>
well it talks about panels and bridges and connectors and encoders and what not... i need to get these concepts mentally mapped to the sunxi code in the kernel. if you know what i mean :)
<buZz>
not really :P do you want to run a lcd panel from the MIPI-DSI interface then?
<JoaoSchim>
never really dug into the display area of linux really.
<clever>
JoaoSchim: this is some DRM code i had written for the rpi, it allocates a framebuffer, and renders it on a specific video port
<JoaoSchim>
clever: thanks. is userland application ?
<clever>
JoaoSchim: yep
<JoaoSchim>
i don't even have kernel side working yet :)
<JoaoSchim>
buZz: no HDMI on my board. only special purpose LCD/RGB display via ICN6211
<JoaoSchim>
trying to get the DSI driver for A33 to work with A83T. but the terms confuse me :D
<buZz>
MIPI-DSI to DPI bridge?
<buZz>
sounds like you're using some cheapass tablet :P
<JoaoSchim>
No... even worse.
<JoaoSchim>
my own pcb design :P
<buZz>
you have your orders wrong ;)
<JoaoSchim>
hahahahah
<JoaoSchim>
Step 1 is getting DSI working on its own for this Soc.
<clever>
ive heard that dsi is always a pain to get working
<JoaoSchim>
i can see that the (dummy) panel gets attached to dsi. but it keeps waiting for half a minute for vblanking. not sure where that is supposed to come from.
<JoaoSchim>
therefor i am in desperate search for more fundamental knowledge on the structures and relations in drm
megi1 has joined #linux-sunxi
Danct12 has joined #linux-sunxi
<MoeIcenowy>
JoaoSchim: bad news: A83T DSI should be quite different from A33 one
<MoeIcenowy>
because A83T is 28nm and A33 is 40nm
<MoeIcenowy>
JoaoSchim: the DSI panel's vblank should be from DSI controller, I think
<MoeIcenowy>
it means the panel ACKed your data
<JoaoSchim>
MoeIcenowy: hmm that's no good.
<JoaoSchim>
So without any resources from Allwinnertech on using dsi on 28nm this isn't gonna fly..
<JoaoSchim>
since no other mipi-dsi drivers are there.. :(
diego71 has quit [Ping timeout: 480 seconds]
<buZz>
what does the amount of nanometers have to do with it?
<buZz>
ah, different DSI IP from ARM?
diego71 has joined #linux-sunxi
<JoaoSchim>
buZz: good question. looking at tcon driver the compatibility list is endless; 40nm as well as 28nm soc's.
<JoaoSchim>
so why does it matter for mipi_dsi ? @MoeIcenowy can you tell ?
<JoaoSchim>
no, only binds to dsi port and encodes for it. but just wondering why for tcon compat between 28nm / 40nm is not an issue and for dsi it is..
<buZz>
because its not the same IP ?
JohnDoe_71Rus has joined #linux-sunxi
jernej_ is now known as jernej
sunshavi has quit [Read error: Connection reset by peer]
sunshavi has joined #linux-sunxi
<jernej>
JoaoSchim: When nm change, usually also PHYs change
<jernej>
for example, A83t has same HDMI controller than other SoCs of that era, but it has different PHY
<jernej>
if I'm not mistaken, DSI is also split in controller and PHY part
<jernej>
JoaoSchim: usual approach in developing mainline driver is to take BSP driver as documentation and write your own using approach, that is acceptable for upstream
Net147 has quit [Ping timeout: 480 seconds]
<JoaoSchim>
jernej: indeed there is a d-phy that accompanies dsi.
<JoaoSchim>
jernej: i am willing to go in the deep. but i have no clue where to find BSP driver.
<buZz>
in the non-foss kernel, i assume?
<jernej>
well, then, you have a long way before you :)
<MoeIcenowy>
controller register map looks different too
<JoaoSchim>
For my understanding: this is the kernel sources for banana pi-3 by sinivoip. this is not mainline kernel but very specific for the Bpi-M3 hw, right ?
<jernej>
no
c23456 has joined #linux-sunxi
<jernej>
why it would be board specific?
<MoeIcenowy>
JoaoSchim: it's not specific to BPi-M3, it's specific to A83T
<MoeIcenowy>
it's based on kernel provided for A83T to Sinovoip
<JoaoSchim>
cause it would not make sense for sinivoip to be compatible..
<JoaoSchim>
right
<MoeIcenowy>
BPi M3 is just A83T board
<jernej>
sinovoip doesn't do any kernel development, they just take sources provided by AW
<jernej>
well, at least not much
<MoeIcenowy>
jernej: well they do some small modifications
<MoeIcenowy>
but too small to affect the code we mentioned here
<jernej>
yeah, I corrected myself
<JoaoSchim>
i do that all the time :)
<MoeIcenowy>
a DSI driver should be possible based on the source code in BSP
<MoeIcenowy>
but it couldn't be an easy work
<JoaoSchim>
if it were it would be there already
<MoeIcenowy>
BTW this DSI controller is called de_dsi_28 in newer AW SDKs
<jernej>
nope, you need to learn KMS basics and gain some DSI understanding
<MoeIcenowy>
and Allwinner A63 seems to share the same DSI controller
<MoeIcenowy>
(well, no one in the community cares about A63 yet, I only found this by reading Makefile in AW Linux 4.9 SDK
<gamiee>
A63? Is any SBC with it?
<MoeIcenowy>
gamiee: I think 0
<MoeIcenowy>
it's a chip that is too tablet-specific
<jernej>
I think somebody here has a tablet with A63. smauel maybe?
<jernej>
*smaeul
<gamiee>
Ahh, but also tablet is hard to source with it I guess
<gamiee>
BTW I'm surprised that there isn't any on-going work on V5/V536
<gamiee>
(only some work on V831)
<JoaoSchim>
okay lots of fun for me tomorrow , thanks for the link jernej
<JoaoSchim>
it's not the destination but the road you travel. :)
<jernej>
take it as several months long project
<MoeIcenowy>
gamiee: well V831 work is done by me, but then both Sipeed and I lost interest because Allwinner is just too mean on V831/V833 NPU
<jernej>
It took me few months for initial HDMI driver in U-Boot - DRM/KMS driver is more complicated
<gamiee>
Too mean => not providing info about NPU?
<MoeIcenowy>
jernej: but I think DRM/KMS driver is componented enough
<MoeIcenowy>
gamiee: not only this, but even try to hide info about the NPU
<MoeIcenowy>
(some RE work shows that the V831/V833 NPU is customized NVDLA
<jernej>
MoeIcenowy: It shouldn't be that hard nowadays, but you still need to understand what each part does and how it fits together
<JoaoSchim>
jernej: i guess starting with structure / interfaces first, then move on to specific implementation.
<gamiee>
MoeIcenowy: that's absolutely illogical for me why they doing it, but recently Allwinner surprises me with their decisions, so... It's shame
<JoaoSchim>
Learn a lot from whats already there
<apritzel>
I have an A63 tablet, but it's not exactly accessible as a development platform, not does it have high priority
<MoeIcenowy>
gamiee: well, a scary story -- Allwinner bought the customized NVDLA as some IP core
<apritzel>
but at least I could use the UART via the SD slot, and could do some FEL booting, plus there is a manual
tnovotny has quit [Quit: Leaving]
<apritzel>
as jernej said, the A63 isn't exactly a tempting chip for a devboard (no Ethernet, no HDMI, and the rest is just "meh")
<MoeIcenowy>
well no one cares about A63
<MoeIcenowy>
apritzel: is there DSI on your A63 manual?
<gamiee>
MoeIcenowy: oh :/
<MoeIcenowy>
oh the manual is on linux-sunxi.rog
<MoeIcenowy>
org *
<apritzel>
MoeIcenowy: DSI is mentioned, but no details
<MoeIcenowy>
as expected.
<apritzel>
but the SoC has eDP, and that is actually documented
<MoeIcenowy>
oh? (considering eDP is just DP)
<apritzel>
yeah, don't know how much platform/AW specifics there is in there
<apritzel>
the display is probably the only good thing in this tablet ;-)
<MoeIcenowy>
ah A63 CPUS processor is no longer AR100, it's Cortex-M
<apritzel>
yes, that's one oddity, but I haven't see another AW-SoC with a Cortex-M yet