anarsoul has quit [Remote host closed the connection]
anarsoul|2 has quit [Ping timeout: 248 seconds]
anarsoul has joined #linux-sunxi
<NoNicknameLeft>
How do I generate an initrd image for use on some development board? For the current machine it's update-initramfs which calls mkinitramfs. So I looked at the docs and mkinitramfs says it's still based on the currently running kernel and won't work on another arch. I am able to compile running kernels for my board, I just don't get how to get the initrd image.
<KotCzarny>
adding 'howto', 'guide' or 'tutorial' is useful too
<NoNicknameLeft>
So you don't know if it applies to our question or not?
<gnarface>
i checked, it looks like it does
<gnarface>
no confirmation it'll work on arm64 but it looks worth a try too...
<NoNicknameLeft>
I am able to use google, but rather ran reading some 20 pages, I thought I'd just ask.
<NoNicknameLeft>
I thought it civil.
<KotCzarny>
if you have to rely on your distro, then partly, if you want to know how thing work, then it's 100%
<KotCzarny>
*things
<gnarface>
i skimmed it, the short version is; use cpio
<KotCzarny>
gnarface: read about difference between initrd and initramfs
<gnarface>
oh i didn't know there was one, thanks for the heads-up KotCzarny
<NoNicknameLeft>
Yeah, thanks though
<KotCzarny>
personally i'm using ramdisk root fs only for special tasks (rescue fs, safeguarding, special rootfs init needs etc)
qeed has quit [Quit: Leaving]
maz has joined #linux-sunxi
<codekipper>
anarsoul: Good work, I had a play last night with my old branch but couldn't get it working. Think something was muted in alsamixer but through the serial cable I couldn't see what.
<codekipper>
Anyway, I'll squash all the patches to something that we can apply ontop of mainline
<codekipper>
I've got another solution for wss as I've seen the requirement for it being 32bits on a few occasions
NoNicknameLeft has quit [Quit: Leaving]
kever has joined #linux-sunxi
benettig has joined #linux-sunxi
tllim has joined #linux-sunxi
sr-digitronic has joined #linux-sunxi
benettig has quit [Quit: Leaving]
benettig has joined #linux-sunxi
benettig has quit [Client Quit]
benettig has joined #linux-sunxi
benettig has quit [Client Quit]
benettig has joined #linux-sunxi
sunxi_fan has joined #linux-sunxi
maz has quit [Quit: Leaving]
maz has joined #linux-sunxi
sr-digitronic has quit [Remote host closed the connection]
sr-digitronic has joined #linux-sunxi
vagrantc has quit [Ping timeout: 240 seconds]
vagrantc has joined #linux-sunxi
msimpson has joined #linux-sunxi
yann|work has quit [Ping timeout: 264 seconds]
<nuvalo>
hello, i'm not sure if this is a good place to ask for help on loading sunxi kernels on snes mini boards, i'm sorry if this is out of topic.
<nuvalo>
I have an snes mini, connected through serial uart to my pc and i have compiled and loaded nintendo's oss kernel release
maz has quit [Ping timeout: 240 seconds]
<gnarface>
woah cool, i didn't even know that was possible
<nuvalo>
i've been able to compile and load a modified kernel and a custom initramfs kernel, and seems to work
<gnarface>
neat
<nuvalo>
"seems to work", means that it boots and execs busybox, but i'm having some annoying kernel logs related to i2c
<nuvalo>
the error comes from "drivers/i2c/busses/i2c-sunxi.c", function "twi_start", error "twi_start()403 START can't sendout!\n". Does anyone knows what does it means?
<nuvalo>
gnarface: Thanks :)
Leepty has quit [Read error: Connection reset by peer]
tllim has quit [Read error: Connection reset by peer]
Leepty has joined #linux-sunxi
kaspter has quit [Quit: kaspter]
<nuvalo>
another problem that i'm having, i don't have hdmi output. I've been following this blog (https://www.ns-koubou.com/blog/2016/11/16/nes_classic_hdmi/) and enables those flags in the kernel. I can see in the kernel log that the driver for EP952 is loaded, but i don't have a terminal on hdmi output or anything, just a "hdmi connection not detected" on my lcd. Also, trying to read/write from /dev/fb0 gives an out of memory error
maz has joined #linux-sunxi
popolon has joined #linux-sunxi
yann|work has joined #linux-sunxi
maz has quit [Ping timeout: 240 seconds]
maz has joined #linux-sunxi
kaspter has joined #linux-sunxi
sr-digitronic has quit [Remote host closed the connection]
sr-digitronic has joined #linux-sunxi
dave0x6d has joined #linux-sunxi
maz has quit [Ping timeout: 248 seconds]
xvnvx has quit [Quit: Leaving]
Andy-D_ has joined #linux-sunxi
Andy-D_ has quit [Ping timeout: 260 seconds]
indy has quit [Ping timeout: 240 seconds]
indy has joined #linux-sunxi
kever has quit [Quit: No Ping reply in 180 seconds.]
<benettig>
marble_visions: no, it says with XML "BlobNotFound"
<benettig>
same with other drivers
MoeIcenowy1 has joined #linux-sunxi
GrimKriegor has quit [Read error: Connection reset by peer]
MoeIcenowy has quit [Ping timeout: 255 seconds]
<Pe3ucTop>
Questions about CSI interface ? How driver need to determine interface type MIPI/CSI ?? Is it going from node/endpoint number or ??
GrimKriegor has joined #linux-sunxi
<Pe3ucTop>
mripard: may be you could comment on how to define port type for Camera and CPU interface?
<marble_visions>
benettig: damn. thanks though. i read your stuff from yesterday. are you getting bad alloc 0x3003 with qt and latest mainline?
skiboy has quit [Quit: Leaving]
forte has joined #linux-sunxi
maz has joined #linux-sunxi
<forte>
hi there, I want to ask if anyone has experience with using I2C with u-boot in Sunxi H3? I've enabled DM I2C driver through menuconfig and changed the device tree, but I can't probe the I2C bus and get the address of an external chip connected to my board(Orange Pi Lite)
<forte>
It works in Linux kernel though
kaspter has quit [Ping timeout: 240 seconds]
enrico_ has joined #linux-sunxi
kaspter has joined #linux-sunxi
ykchavan has joined #linux-sunxi
<Pe3ucTop>
MoeIcenowy1: may be you could give hint on correct way of CSI/MIPI type binding in device tree ?
<Pe3ucTop>
I find that in video interface there is type selection between Parallel and BT.656 based on h-sync/v-sync existance.
yann-kaelig has joined #linux-sunxi
<Pe3ucTop>
But is it correct way of defining interface ? By idea CSI interface could support both Parallel and BT. and it depends on camera abilityes and and current connection. So how to correctly define it ?
<MoeIcenowy1>
currently CSI in mainline is highly WIP
<MoeIcenowy1>
do not try it unless you know it well
dave0x6d has quit [Quit: Connection closed for inactivity]
<Pe3ucTop>
MoeIcenowy1: already tried it, got image, and going to work with better camera (prepare driver).
<Pe3ucTop>
So question still actual: Is there methodology to define/select interface type from device tree.
ykchavan has quit [Read error: Connection reset by peer]
MoeIcenowy1 is now known as MoeIcenowy
<marble_visions>
alright, so i've got chip-buildroot (qt with opengl es), chip-mali (mali and ump r6p0-01rel00), but qt wants libUMP api version 3, does anyone have a link? since the developer.arm.com one is dead
JohnDoe_71Rus has quit [Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org]
<marble_visions>
i've got an old libUMP (api ver 2) tried to lie in the #define that it's ver 3 but didn't work (i'm getting bad alloc 0x3003)
* marble_visions
is considering switching to 3.4 solely for mali
<marble_visions>
how's nand mlc support in 3.4-sunxi?
<marble_visions>
on second thought, i should first try mali r3pX, since i've got mali driver libmali ump driver and libump for that version
<aalm>
meh, i forgot to cc any maintainers on my u-boot bug report -_-
<benettig>
marble_visions: yes I'm having 0x3003 on fbdev r6p2 mali,
<MoeIcenowy>
I think chip mali blob now do not use ump
<benettig>
so now I'm trying to get X11 Mali working
<benettig>
but jernej pointed me to libreELEC where they say only wayland drivers will work,
<benettig>
but it's not clear
<benettig>
so I'm giving trials
<marble_visions>
MoeIcenowy: maybe, but in any case, qt accesses libUMP
<marble_visions>
so i need to provide it anyway
<marble_visions>
i don't see any options in the menuconfig otherwise
<MoeIcenowy>
marble_visions: maybe you used the wrong backend
Ntemis has joined #linux-sunxi
<marble_visions>
MoeIcenowy: i've selected Qt Standard (X11), and i've selected OpenGL ES v2.x support from buildroot, which gets translated to qt_configure_opts += -lopengl es2 -egl, qt_dependencies += libgles libegl
maz has quit [Ping timeout: 255 seconds]
ykchavan has joined #linux-sunxi
ninolein has quit [Ping timeout: 258 seconds]
Andy-D_ has joined #linux-sunxi
ninolein has joined #linux-sunxi
dave0x6d has joined #linux-sunxi
MoeIcenowy has quit [Remote host closed the connection]
Putti has joined #linux-sunxi
forte has quit [Ping timeout: 260 seconds]
cnxsoft has quit [Quit: cnxsoft]
reinforce has quit [Quit: Leaving.]
JohnDoe_71Rus has joined #linux-sunxi
Leepty has quit [Remote host closed the connection]
maz has joined #linux-sunxi
osc has joined #linux-sunxi
osc has quit [Client Quit]
ninolein has quit [Ping timeout: 248 seconds]
ninolein_ has joined #linux-sunxi
vagrantc has quit [Quit: leaving]
maz has quit [Ping timeout: 240 seconds]
rexxster has quit [Quit: No Ping reply in 180 seconds.]
kaspter has quit [Quit: kaspter]
kaspter has joined #linux-sunxi
rexxster has joined #linux-sunxi
fkluknav has quit [Ping timeout: 264 seconds]
<benettig>
marble_visions: dropped X11, too many complications with DRI2 and xf86-video-armsoc
<benettig>
I give a try with Wayland,
<benettig>
that "should be better" on embedded, let's hope
scream has joined #linux-sunxi
fkluknav has joined #linux-sunxi
netlynx has joined #linux-sunxi
netlynx has quit [Changing host]
netlynx has joined #linux-sunxi
leviathanch has joined #linux-sunxi
scream has quit [Remote host closed the connection]
scream has joined #linux-sunxi
maz has joined #linux-sunxi
scream has quit [Remote host closed the connection]
tllim has joined #linux-sunxi
alexxey has joined #linux-sunxi
maz has quit [Ping timeout: 240 seconds]
kaspter has quit [Ping timeout: 240 seconds]
kaspter has joined #linux-sunxi
kaspter has quit [Client Quit]
kever has quit [Quit: No Ping reply in 180 seconds.]
kever has joined #linux-sunxi
yann|work has quit [Ping timeout: 255 seconds]
msimpson has quit [Quit: Leaving]
dave0x6d has quit [Quit: Connection closed for inactivity]
skiboy has joined #linux-sunxi
alexxey has quit [Ping timeout: 240 seconds]
jbrown has joined #linux-sunxi
kaspter has joined #linux-sunxi
kaspter1 has joined #linux-sunxi
dave0x6d has joined #linux-sunxi
maz has joined #linux-sunxi
kaspter has quit [Ping timeout: 248 seconds]
kaspter1 is now known as kaspter
Guest13123 has joined #linux-sunxi
dev1990 has joined #linux-sunxi
<Guest13123>
using mainline U-boot, i can boot a mainline kernel (A33), but i can't seem to boot 3.4
fkluknav has quit [Ping timeout: 248 seconds]
benettig has quit [Remote host closed the connection]
benettig has joined #linux-sunxi
<Guest13123>
that's from SD, btw. if i try to boot it via FEL, U-boot does not find the boot.scr in ram
ykchavan has quit [Ping timeout: 240 seconds]
kaspter has quit [Ping timeout: 246 seconds]
kaspter has joined #linux-sunxi
reinforce has joined #linux-sunxi
<Guest13123>
with no output, i can't tell where it's failing
anarsoul|2 has joined #linux-sunxi
<pmpp>
Guest13123: did you use "setenv bootm_boot_mode sec" for legacy ?
sr-digitronic has quit [Remote host closed the connection]
enrico_ has quit [Quit: Bye]
aballier has quit [Quit: leaving]
benettig has quit [Read error: Connection reset by peer]
<Guest13123>
pmpp: yes, i did
<Guest13123>
however, considering that current mainline U-boot ignores a ram-based boot.scr contrary to the wiki, maybe it ignores that too for all i know. i could try to dig through commit logs to determine that, but doing so seems a bit of a useless tangent
Andy-D__ has joined #linux-sunxi
Mr__Anderson has joined #linux-sunxi
Andy-D_ has quit [Ping timeout: 260 seconds]
<pmpp>
Guest13123: could you send me your legacy kernel via https://transfer.sh ?
<Guest13123>
pmpp: i have tried building it from several sources, currently from MoeIcenowy's github
<Guest13123>
but i will now try OLD_SUNXI_KERNEL_COMPAT in U-boot menuconfig
<pmpp>
yeah but i don't have time to build, but i have fel-installer and an A33 tab
<Guest13123>
is your A33 tab 800x480, or some other res?
<pmpp>
1024x600
<Guest13123>
display would be all different then, but that's probably from the script.bin
<Guest13123>
which kernel sources have you used?
<pmpp>
none yet was just offering to test your kernel on fel boot
dave0x6d has quit [Quit: Connection closed for inactivity]
<marble_visions>
benettig: do tell if you have any success
<umit>
ok
<Guest13123>
pmpp: sorry, was in and out with errands. here is the zImage of the kernel i most recently built: https://transfer.sh/gNAH6/zImage
<pmpp>
thx i'll give a try
jstein has quit [Remote host closed the connection]
<Guest13123>
a33, not h3
<pmpp>
i route the soc from the fel info string
<pmpp>
should already have A64 and H5 but i don't know if FEL boot has been fixed yet
TEKrantz has quit [Read error: Connection reset by peer]
umit has quit [Quit: Page closed]
dave0x6d has joined #linux-sunxi
TEKrantz has joined #linux-sunxi
adj__ has quit [Remote host closed the connection]
adj__ has joined #linux-sunxi
TEKrantz has quit [Ping timeout: 248 seconds]
TEKrantz has joined #linux-sunxi
TEKrantz has quit [Read error: Connection reset by peer]
TEKrantz has joined #linux-sunxi
lerc has quit [Remote host closed the connection]
dev1990 has quit [Quit: Konversation terminated!]
lerc has joined #linux-sunxi
<Guest13123>
pmpp: btw, on the off chance you know, where is U-boot stored on the nand?
<pmpp>
no but great chances are nand[a-e]
<pmpp>
i'd try nandd first
<Guest13123>
there is a partition called "boot" and a fat fs on a partition called "bootloader"
<Guest13123>
maybe i'm blind, but i see U-boot in neither
<Guest13123>
idk where the boot rom looks for it
<pmpp>
use busybox strings on the nand? and grep
<pmpp>
mine seems in nandc
<pmpp>
in nandf too seems i have recovery
lurchi__ is now known as lurchi_
MoeIcenowy has joined #linux-sunxi
<gnarface>
Guest13123: u-boot goes in the MBR area before the first partition entry, like literally within the first few blocks of the disk
<gnarface>
Guest13123: you won't actually see it in any file or partition manager
<gnarface>
Guest13123: it's actually so close to the start of the disk that it's common for modern partitioning software to skip right over it
<gnarface>
Guest13123: you can fdisk a whole new partition scheme onto a device and miss it
<gnarface>
Guest13123: (exactly where seems to vary from device to device, and between different u-boot version numbers, and sometimes it's in two parts, sometimes it's in 3... etc
<gnarface>
)
<Guest13123>
gnarface: i dumped the MBR using FELix, and it's not there either
<gnarface>
Guest13123: i don't think it's actually PART of the MBR it's just in the empty space around it
<Guest13123>
around?
<Guest13123>
MBR starts at offset zero
<pmpp>
he means on mbr uboot is at +8K in the void
<Guest13123>
4 copies of the partition table, then zeroes up to 0x00010000, then all 0xff's until 0x01000000
<gnarface>
Guest13123: keep in mind you're not much newer at this than me. what i can tell you for sure that worked for me is that for mainline das u-boot on a pinebook, i had to put the SPL at 8k (32768 in size) and the other half at 40k (504804 in size)
<gnarface>
Guest13123: MBR i think is from 0-64B?
<pmpp>
but pinebook is emmc not nand ?
<gnarface>
Guest13123: and the partition table doesn't start until 2MB
<gnarface>
pmpp: oh, good catch
<gnarface>
Guest13123: it may be a relevant clarification that for this i was booting off the microSD slot as i couldn't get the build to work with eMMC support
<Guest13123>
on my nand, the partition table starts at 0x0, again at 0x4000, again at 0x800, and again at 0xc000
<gnarface>
pmpp: those addresses are determined by boot media and not just the hardware itself? i didn't know, thanks for the info.
<Guest13123>
*0x8000
<pmpp>
afaik a33 nand is uncharted
<pmpp>
could be anywhere :p
<gnarface>
well, it's probably within the first 2MB though, isn't it?
<Guest13123>
if anyone charted a23, i doubt it would be different