Andreas Fc3a4rber wrote: > Just to be clear, this is not just about adding a wlan interface. > Since you're the one with the board, I pointed you to look at > JeOS-nanopineo as template to create a JeOS-nanopineoair image - don't > expect the image for another board to just work for you. LEDs are one > of the most common things to differ between boards, compared to serial > ports.
I've been trying to do this more or less from scratch - I figure that'll give me a better overall understanding of what's involved. I'll try to sum up where I am at the moment, I would much appreciate someone correcting my mistakes/misunderstandings. I started out here: https://en.opensuse.org/openSUSE:OpenSUSE_on_your_ARM_board, "Bootstrapping a kernel using openSUSE chroot". I figured from there it couldn't be too difficult getting u-boot installed, and ROOT+BOOT partitions updated and maybe have a somewhat working system. I'm still waiting for the ttl serial interfaces to arrive :-) u-boot - this is installed in a known place in the beginning of the SD card, and the board BIOS knows where to look for it. Is that correct? u-boot - does not seem to be platform specific? I've looked at u-boot in OBS, all the variations link to u-boot, where the spec file has a few platform-specific customizations. It seems to me that nanopi-neo ought to work with nanopi-neo-air too? dtb file - this is a hardware description needed because embedded platforms typically don't offer the interfaces for the OS to discover the hardware itself. The dtb file is part of the kernel tree. I've found a kernel patch for adding a dtb for the nanopi-neo-air. It applied cleanly to 4.10.1. When booting, how is the correct dtb file loaded? thanks Per -- Per Jessen, Zürich (4.4°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
