<KotCzarny>
there is also uart dongle and 128x64 oled display
kaspter has quit [Quit: kaspter]
JohnDoe9 has joined #linux-sunxi
<miasma>
do you think the wiki should have a page describing the use of device tree overlays with sunxi boards?
<KotCzarny>
might be just a paragraph on mainline kernel page
JohnDoe_71Rus has quit [Ping timeout: 276 seconds]
<miasma>
i mean a howto style page showing how to enable stuff like dallas temp sensor
<KotCzarny>
it's a wiki, make it and see what happens
<miasma>
it's not really sunxi related, but people often complain that nano/opi boards lack this kind of 'support'
<KotCzarny>
otoh while you are at it, you can make DT page
<miasma>
also, it's a great way to study how it works. i've mostly used userspace drivers, not the industrial sensor drivers builtin kernel
<KotCzarny>
and dt overlays being a subpage
<miasma>
right
<miasma>
i just realized the wiki doesn't describe this at all when searching for info about the overlays
<miasma>
first I thought these overlays can only be applied at boot time, but apparently the overlay system is dynamic and also can be configured after booting?
mpmc is now known as {mpmc}
cnxsoft has quit [Quit: cnxsoft]
dave0x6d has joined #linux-sunxi
reinforce has joined #linux-sunxi
Langoor has quit [Ping timeout: 248 seconds]
Langoor has joined #linux-sunxi
<icenowy[m]>
and I think sunxi github should have a repo for overlays
Ntemis has joined #linux-sunxi
<KotCzarny>
ho hum, since they are dynamic and can be loaded runtime, why not make everything an overlay?
embed-3d__ has quit [Ping timeout: 276 seconds]
hardfalcon has joined #linux-sunxi
hardfalcon1 has quit [Ping timeout: 260 seconds]
embed-3d has joined #linux-sunxi
longsleep has quit [Ping timeout: 240 seconds]
longsleep has joined #linux-sunxi
Gerwin_J has quit [Quit: Gerwin_J]
Gerwin_J has joined #linux-sunxi
Gerwin_J has quit [Client Quit]
Gerwin_J has joined #linux-sunxi
Gerwin_J has quit [Client Quit]
Gerwin_J has joined #linux-sunxi
Gerwin_J has quit [Client Quit]
nuuuciano has joined #linux-sunxi
freemangordon has joined #linux-sunxi
longsleep has quit [Ping timeout: 255 seconds]
longsleep has joined #linux-sunxi
vagrantc has joined #linux-sunxi
vagrantc has quit [Client Quit]
codekipper has joined #linux-sunxi
codekipper has quit [Client Quit]
<willmore>
miasma, sounds more distro related, a la armbian. Is there any armbian page on the wiki?
<KotCzarny>
willmore: not necessarily, say you wanted to create your own image that would accomodate your boards
<KotCzarny>
but you would like to have one image instead of 1-per-board
<willmore>
That's still a distro level question.
<willmore>
In this case you're the distro maker. :)
<KotCzarny>
hehe
<willmore>
And you are.
<KotCzarny>
distro is something unknown people use
<KotCzarny>
baking something for yourself you still could benefit from knowing how to
<miasma>
willmore: how exactly is it distro related? the tech is common to all linux distros. it's a kernel structure
<miasma>
the same howto works for all distros
chlorine has joined #linux-sunxi
Langoor has quit [Ping timeout: 248 seconds]
chlorine has quit [Ping timeout: 240 seconds]
Langoor has joined #linux-sunxi
hardfalcon1 has joined #linux-sunxi
hardfalcon has quit [Ping timeout: 268 seconds]
<willmore>
miasma, I don't mean to say it's specific to 'a distro', just that it's something that gets though of on the distro level.
<willmore>
For example armbian has pages on how to use overlays. Maybe just link to their wiki?
<miasma>
willmore: the armbian instructions are armbian specific
DonkeyHotei has quit [Ping timeout: 268 seconds]
loblik has quit [Ping timeout: 246 seconds]
<willmore>
Can you use them as an inspiration or template for something more generic? That seems like it would make sense on the linux-sunxi wiki, IMHO.
foxx_ has joined #linux-sunxi
_whitelogger has joined #linux-sunxi
obbardc has joined #linux-sunxi
<obbardc>
hey guys, is there an H5 I2S/SoC WIP branch around?
<obbardc>
or any info on H5 I2S etc
<Wizzup>
How would one get earlyprintk on sunxi platforms? In my case the LIME2 A20 boards. I'm trying to debug a kernel issue that shows up with specific options enabled, and doesn't show in QEMU's virt target.
<Wizzup>
I'm hoping to get early Linux output, since I basically don't get anything after 'Loading kernel ...' in u-boot, but only with specific options enabled.
<Wizzup>
The wiki didn't get help me get any further
<icenowy[m]>
WIzzup;
<icenowy[m]>
maybe you can try earlycon when using uart
<Wizzup>
hm, how would I know the address of uart?
<icenowy[m]>
for A20 uart0 the base addr is 0x01c28000
<Wizzup>
Aha, thank you. Where did you find that if I may ask?
<icenowy[m]>
so add earlycon=uart,mmio32,0x01c28000 to the cmdline
<icenowy[m]>
in fact... I found it when apritzel debug A64 ;-)
<Wizzup>
so I can remove anything related to earlyprintk, and just use that earlycon line, right?
<icenowy[m]>
yes
<Wizzup>
thank you. I will try it once this kernel finishes compiling.
<afaerber>
Hi, 4.15-rc2 dtb fails to boot on my Cubietruck, but same kernel works with 4.14 dtb - is there some known issue with the new clk drivers maybe?
* Wizzup
now hopes that the lime2 uart0 is indeed the uart that is exposed
<Wizzup>
Another questions that some of you might know - I'm trying to emulate a cubieboard since it's a supported board in qemu, but I fail to get any output (say on serial) with it. This works with -M virt: qemu-system-arm -M virt -kernel /usr/src/linux-4.14.4/arch/arm/boot/zImage -append 'console=ttyAMA0,115200 verbose debug' -nographic -serial stdio -monitor none
<Wizzup>
Any clue if something special is required for the cubieboard board - the board file seems pretty empty in the qemu git
<afaerber>
Wizzup, what's your command line for cubieboard? you need a different uart
<Wizzup>
I tried ttyS0,115200 to no avail
<icenowy[m]>
I think the A10 emulation of qemu is just not mature at all
<lurchi__>
afaerber: shouldn't overlays be named *.dtso?
<afaerber>
lurchi__, it doesn't matter, important is .dtbo
<Wizzup>
afaerber: but it doesn't seem to be ttyS0 either - that's why I figured I'd dig into the qemu machine file
<icenowy[m]>
I remember on ARMv8 I cannot run qemu-system-arm
<icenowy[m]>
I need to run qemu-system-aarch64 with some parameters to disable AArch64 mode
<Wizzup>
yes, same here
<Wizzup>
like specify the right cpu and then it works
<Wizzup>
I am also pleasantly surprised because now qemu-system-arm actually accepts -enable-kvm as a flag, before it didn't and I had to test with kvmtool
<icenowy[m]>
oh it has been there for along time!
<Wizzup>
interesting :)
nuuuciano has quit [Quit: Leaving]
nuuuciano has joined #linux-sunxi
<obbardc>
Anyone know anything on H5 I2S audio support?