-
Posts
498 -
Joined
-
Last visited
Reputation Activity
-
wildcat_paris reacted to Igor in [Device specific] Olimex A13-SOM
@Zador
I made a "master" default now.
@Booli
Documenatation is not properly updated yet so I can't point you there
start here:
https://github.com/igorpecovnik/lib/blob/master/configuration.sh
We have a kernel family that is not present (sun5i) so you need to check the exception part in the bottom and you need sun5i kernel config for legacy kernel. The rest is just like other board.
Then there is this file (which is about to be reworked)
https://github.com/igorpecovnik/lib/blob/master/boards.sh
regarding some special board definitions and boot scripts.
IRC, IgorPec@Freenode
-
wildcat_paris reacted to zador.blood.stained in [Framework] Build script improvement suggestions #1
I agree that this directory structure is not exactly user-friendly, but right now I'm thinking like this because kernel patches don't grow on trees, if user can make, change or find a patch that he wants to apply, you can expect him to know how to figure out this directory layout. Or at least to read and understand documentation about it.
Also, Armbian supports many different SBCs now and probably will support even more later, and since some boards have unique kernel or u-boot sources, some have 2 possible kernel versions, some have 1, in the end you can't make directory structure simple enough without introducing tons of workarounds and extra configuration bits in build scripts.
-
wildcat_paris reacted to zador.blood.stained in [Framework] Build script improvement suggestions #1
It doesn't duplicate files, it creates only empty directories.
In my mind it is one of the reasons too.
-
wildcat_paris reacted to zador.blood.stained in Mainline A10/A20 audio driver
It should work on kernel 4.4 with this patch (which is planned for 4.5).
-
wildcat_paris reacted to Igor in [Framework] Build script improvement suggestions #1
It could be possible to add it to 3.4 too I guess. But let's leave this for "once".
I left behind boot script mod because this area is a mess. I'll be happy to see one general boot script for all boards but it's not possible without u-boot fixing: cubox, udoo, neo, guitar, odroid, ... they are all (very) different.
Let's focus on bug fixing into two major tasks: to build images with default settings and to build a kernel for all builds in a batch.
I promise update "this year"
-
wildcat_paris reacted to Igor in [Framework] Build script improvement suggestions #1
Configs fixed
https://github.com/igorpecovnik/lib/commit/65bb88cb3394ca914e0dcf39dd8692a84e505b67
What about sunxi legacy?
I am going to fix firstrun / resize2fs next ...
-
wildcat_paris reacted to zador.blood.stained in [Framework] Build script improvement suggestions #1
I almost finished adding support for building images with F2FS root filesystem (and it's relatively easy to add support for other filesystems, though I don't see the reason to do it for now), but there is small obstacle in the way - partition resizing in firstrun and resize2fs scripts.
Igor, can you change these scripts so it's possible to disable resizing operation (while executing everything else, plus if no resizing is needed, you need to start resize2fs script right away at first boot instead of reboot)?
Logic for disable resizing can look like this:
local root_partition=$(findmnt --target / -o SOURCE -n) local rootfstype=$(blkid -s TYPE -o value $root_partition) if [[ $rootfstype != ext4 ]]; then ... Edit: or it can be just a file, i.e. /etc/.no_rootfs_resize
Plus next time you will be checking kernel configs, some of them don't have f2fs enabled or it's enabled as a module, which won't work for rootfs.
linux-cubox-default.config(5506): # CONFIG_F2FS_FS is not set linux-guitar-default.config(3334): # CONFIG_F2FS_FS is not set linux-odroid-default.config(3873): CONFIG_F2FS_FS=m linux-odroid-next.config(3481): CONFIG_F2FS_FS=m linux-s500-default.config(3334): # CONFIG_F2FS_FS is not set linux-udoo-default.config(3482): # CONFIG_F2FS_FS is not set linux-udoo-neo.config(3707): # CONFIG_F2FS_FS is not set linux-udoo-next.config(4171): # CONFIG_F2FS_FS is not set -
wildcat_paris reacted to Igor in [odroid xu4+cloudshell] first tests with "hardkernel" images
I guess there was something wrong with my previous build. This is working fine with me so we have first official Armbian build:
http://www.armbian.com/odroid-xu4/
Thank you for assistance.
-
wildcat_paris reacted to Igor in (BananaPi) OTG not working in latest published testing image (Armbian_5.00_Bananapi_Debian_jessie_4.4.0-rc5.zip)
--- a/arch/arm/boot/dts/sun7i-a20-bananapi.dts +++ b/arch/arm/boot/dts/sun7i-a20-bananapi.dts @@ -269,7 +269,7 @@ }; &usb_otg { - dr_mode = "otg"; + dr_mode = "host"; status = "okay"; }; That image was deliberately compiled with OTG in host mode
You need to alter Bananapi DTB ... Simply use the one from BananaPRO and it should work since OTG mode is default.
-
wildcat_paris got a reaction from tkaiser in armbian for odroid (e.g. xu4)
I got my USB/UART for odroid XU4 from Hardkernel/South Korea, for testing.
-
wildcat_paris reacted to zador.blood.stained in [Framework] Build script improvement suggestions #1
I think tar should support "absolute" paths in patterns, --exclude='/dev/*' and so on should be safer in case it finds directory named "dev", "proc" or "run" somewhere in the future. I'll test it later.
-
wildcat_paris reacted to Igor in [Framework] Build script improvement suggestions #1
OK. Removing "sys" from tar seems to be o.k. no more problems found ...
Since now we won't have the "make scripts" I'll put "make" into headers package post install script ...that its' done auto if "make" exists.
-
wildcat_paris reacted to zador.blood.stained in [Framework] Build script improvement suggestions #1
Okay, I'm not crazy. Same image, reflashed
debsums libc6-dev
debsums: missing file /usr/include/arm-linux-gnueabihf/sys/acct.h (from libc6-dev:armhf package) debsums: missing file /usr/include/arm-linux-gnueabihf/sys/auxv.h (from libc6-dev:armhf package) ... debsums: missing file /usr/include/arm-linux-gnueabihf/sys/xattr.h (from libc6-dev:armhf package) # debsums libc6-dev 2>&1 | grep missing | wc -l 81 Edit: directory /usr/include/arm-linux-gnueabihf/sys/ is empty. All other files/directories are OK.
Edit 2:
tar cp --directory=$DEST/cache/sdcard/ --exclude='dev/*' --exclude='proc/*' --exclude='run/*' --exclude='tmp/*' \ --exclude='mnt/*' --exclude='sys/*' . | pv -p -b -r -s $(du -sb $DEST/cache/sdcard/ | cut -f1) -N "$RELEASE.tgz" | pigz > $DEST/cache/rootfs/$RELEASE.tgz --exclude='sys/*' Can this be a problem?
Edit 3: Oh no, it found another "sys" directory
.. debsums: missing file /usr/lib/arm-linux-gnueabihf/perl/5.20.2/sys/ioctl.ph (from perl package) debsums: missing file /usr/lib/arm-linux-gnueabihf/perl/5.20.2/sys/sysmacros.ph (from perl package) debsums: missing file /usr/lib/arm-linux-gnueabihf/perl/5.20.2/sys/ucontext.ph (from perl package) debsums: missing file /usr/lib/arm-linux-gnueabihf/perl/5.20.2/sys/select.ph (from perl package) debsums: missing file /usr/lib/arm-linux-gnueabihf/perl/5.20.2/sys/types.ph (from perl package) debsums: missing file /usr/lib/arm-linux-gnueabihf/perl/5.20.2/sys/cdefs.ph (from perl package) ... -
wildcat_paris reacted to zador.blood.stained in [Framework] Build script improvement suggestions #1
Okay, this is starting to get crazy.
Fresh cubietruck jessie with next kernel, "make scripts" fails due to sys/types.h error. libc6-dev is installed.
apt-get install --reinstall libc6-dev
"make scripts" succeeded
I checked, it doesn't have any pre- or postinstall scripts, but something is broken when it is installed in chroot.
-
wildcat_paris reacted to Igor in [Framework] Build script improvement suggestions #1
Ah, there is a problem on target:
root@cubietruck:/usr/src/linux-headers-4.3.3-sunxi# make headers_check CHK include/generated/uapi/linux/version.h HOSTCC scripts/basic/fixdep scripts/basic/fixdep.c:106:23: fatal error: sys/types.h: No such file or directory #include <sys/types.h> ^ compilation terminated. scripts/Makefile.host:91: recipe for target 'scripts/basic/fixdep' failed make[1]: *** [scripts/basic/fixdep] Error 1 Makefile:439: recipe for target 'scripts_basic' failed make: *** [scripts_basic] Error 2 -
wildcat_paris reacted to zador.blood.stained in [Framework] Build script improvement suggestions #1
Yes, it's compiler related, it compiles past this point in Trusty (great, another legacy compatibility problem, goodbye cross-gcc 4.9, welcome cross-gcc 4.8. Or I need to disable stack protector options somehow).
So what build options give errors for you? Udoo has non-default sources for both default and next kernels, which one to test?
-
wildcat_paris reacted to Igor in [Framework] Build script improvement suggestions #1
Works fine for me with or w/o cache. This must be compiler related.
-
wildcat_paris reacted to zador.blood.stained in [Framework] Build script improvement suggestions #1
Did you remove packages from your build host or reinstalled OS? What libc6-dev* packages do you have installed now?
-
wildcat_paris reacted to tkaiser in Support of Raspberry Pi
The only feature that's interesting on the Raspberry Pi is that one can use the VPU correctly now (after a few years). We use RPi B+ as IP camera (even when the CPU core is clocked with just 200 MHz the VPU is able to provide a 1080p@30 fps h.264 encoded video stream) or for digital signage, often combined. In the meantime also lightweight distros exist like http://dietpi.com
For everything else the RPi is always the worst choice due to its one single USB 2.0 connection to the outside.
Supporting the RPi would mean Armbian either focuses on a completely new use case (desktop stuff -- VPU) or on a completely new user base (clueless people).
-
wildcat_paris reacted to Toast in Support of Raspberry Pi
on OSMC we are running on 4.3.0-10 on RPI 1 & 2 pretty much on the bleeding edge considering its raspberry pi
-
wildcat_paris reacted to zador.blood.stained in [Framework] Build script improvement suggestions #1
Oops... my bad, I'll fix it ASAP. Guess saturday evenings can be hard too
-
wildcat_paris reacted to Toast in Regarding the SUSE Imagewriter tool
Hi @Igor
you should consider changing imagetool when you ship your image files since the Suse image tool is quite broken on Windows platforms 8 or higher since its often just gives a blank non function interface that crashes upon pressing buttons.
Perhaps Rufus would be a better alternative
-
wildcat_paris reacted to Igor in [Framework] Build script improvement suggestions #1
OK, lets put this in.
@wildcat_paris
My fresh compiled Trusty with 4.3.3 works normally on Cubietruck. I'll check R1 in the morning.
-
wildcat_paris reacted to tkaiser in Armbian mainline and sun4i_csi csi-cam on BananaPi R1?
I think working on CSI is still "work in progress" in mainline kernel. And regarding the OV5460 it's not worth the efforts. This is a "5MP" camera and I've never seen anyone being able to get more than 640x480 pixels with questionable quality out.
I tried to get an idea why and stumbled across a freescale forum (IIRC) where one engineer said that it's hard to write a driver for this module without loading/using BLOBs with tables for conversion (or something like that) on the camera first. In short words: If you don't sign an NDA with Omnivision you won't be able to write a driver for this module that doesn't suck.
We still use the RPi (B+) for this purpose. And the difference are just the drivers (for both the VPU -- HW accelerated h.264/1080p@30fps -- and OV5647 -- image quality)
Today I stumbled across these links: http://www.arducam.com/camera-modules/raspberrypi-camera/ and http://www.arducam.com/camera-modules/5mp-ov5640/
No idea how to deal with currently (maybe they've drivers that work better, but this still won't help with mainline kernel)
-
wildcat_paris reacted to pschasch in Armbian mainline and sun4i_csi csi-cam on BananaPi R1?
Hi tkaiser
1)IMAGE see:
[ the black shadow on the left is from my too small hole in self-made R1-case :-) ]
http://www.directupload.net/file/d/4204/pndxoapx_png.htm
<a href="http://www.directupload.net"target="_blank"><img src="http://fs5.directupload.net/images/151216/pndxoapx.png" title="Kostenlos Bilder und Fotos hochladen"></a>
2)
How can I test max resolution?
I didn't config anything, see my first post for what I (only) did.
3)
What do you want to say with your link-answer:
http://linux-sunxi.org/Mainlining_Effort#Major_drivers
"CSI (camera sensor interface) driver (WiP: Yassin Jaffer (ddc))"
Nothing is happening?
Nothing will ever happen?
I hoped anyone here or Igor has modified the code from : https://github.com/LeMaker/linux-sunxi/blob/lemaker-3.4/drivers/media/video/sun4i_csi/device/ov5640.cto/for 4.x-kernel or can do this with minimal effort...
regards