archive-org.com » ORG » M » MERPROJECT.ORG

Total: 820

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Tools - Mer Wiki
    it is called from QtCreator to perform qmake make phases of a project Note that any other build steps in the spec file will also be run mb2 can be invoked via shell using mb2 build command similar to deprecated mb build Example mb2 t SB2 TARGET NAME build mb2 t SB2 TARGET NAME make where SB2 TARGET NAME is sysroots for example nemo armv7hl SailfishOS armvhl etc For more info mb2 help spectacle Spectacle creates spec files from yaml files This makes is a lot easier to package your code https github com mer tools spectacle cd mer tools mkdir spectacle git clone https github com mer tools spectacle more info about spectacle here qemu specific snapshot qemu is needed for building non native ARM MIPS packages that need to execute ARM binaries qemu is found in the Mer Tools project currently on the MeeGo community OBS 19 Nov2011 Using 0 14 1 The OBS and IMG systems use qemu usermode static You need to install qemu usermode static package when you do osc build for non intel architecture and have chroot failed to run command some command Exec format error or Warning could not register binfmt handlers As the package is statically linked you may install OpenSUSE rpm on Fedora and it should work fine Tools for Image Building kickstarter https meego gitorious org sage meego developer tools sages kickstarter cd mer tools mkdir kickstarter cd kickstarter git clone git gitorious org sage meego developer tools sages kickstarter git kickstarter mic2 image creator http meego gitorious org meego developer tools image creator cd mer tools mkdir image creator cd image creator git clone git gitorious org meego developer tools image creator git image creator Development Tools for on Device usage Device Memory Profiling via sp smaps First you have to add the Mer Extras repository to your device zypper configuration available repositories are Mer Extras armv6l Mer Extras armv7hl Mer Extras armv7l and Mer Extras i568 root device zypper addrepo http repo pub meego com Project KDE Mer Extras repository Mer Extras Now feel free to install the sp smaps toolset root device zypper refresh root device zypper in sp smaps Usage Create a memory profiling snapshot root device sp smaps snapshot my memory sp smaps snapshot cap Create a HTML report from the smaps capture root device sp smaps analyze my memory sp smaps snapshot cap Feel free to compress and copy the generates files for further analysis to a host system root device tar cvf my memory sp smaps snapshot tar my memory sp smaps snapshot cap my memory sp smaps snapshot html my memory sp smaps snapshot dir root device bzip2 my memory sp smaps snapshot tar root device scp my memory sp smaps snapshot tar bz2 your user your host Development of tools In OBS the Mer tools are in two projects SDK and device side tools in Mer Tools Host Linux distribution side tools in Project MINT SDK and device side tools are

    Original URL path: https://wiki.merproject.org/wiki/index.php?title=Tools&printable=yes (2016-02-01)
    Open archived version from archive


  • Adaptation Guide - Mer Wiki
    packaging template available at https github com lbt mer kernel adaptation Patches When compiling kernel for ARM with Mer 0 20110105 1 or newer NOTE Kernels newer than 3 4 seem to have fix for this error already thus this patchs isn t needed You will need to apply this patch to your kernel with this new Mer and toolchain release if your kernels break on boot they likely will It will enable mno unaligned access in your kernel compilation flags linux 3 1 Makefile 2011 10 24 18 10 05 000000000 1100 b Makefile 2011 12 24 16 06 38 848284875 1100 640 6 640 8 KBUILD CFLAGS DCC HAVE ASM GOTO endif KBUILD CFLAGS mno unaligned access Add user supplied CPPFLAGS AFLAGS and CFLAGS as the last assignments But warn user when we do so warn assign When compiling arm kernels 2 6 36 This patch needs adding to stop systemd journal taking 100 cpu and also other features https github com nemomobile kernel adaptation n950 n9 commit 3154069946ec127ef1c25c2bcd9d0414c2e0387b Patches for proper cgroups support on older kernels https github com nemomobile kernel adaptation n950 n9 commit f6432438f979a6fd83dda5fcfcedee09ec48e261 https github com nemomobile kernel adaptation n950 n9 commit 8ccba06cd34324a8be5c8510136846f4ef0c5af1 https

    Original URL path: https://wiki.merproject.org/wiki/Adaptation_Guide (2016-02-01)
    Open archived version from archive

  • Nemo/Porting - Mer Wiki
    information to MW via properties The mw monitors consumes these properties as required Properties http maemo gitorious org maemo af contextkit blobs master spec core context Interesting properties that should be provided by a hardware adaptation daemon Screen TopEdge device orientation Screen IsCovered Screen Blanked TODO is this screen is turned off Position Stable Position Shaky Position IsFlat Battery ChargePercentage Battery ChargeBars Battery OnBattery Battery LowBattery Battery IsCharging Battery TimeUntilLow Battery TimeUntilFull Environment IsDark Environment IsBright Other properties we probably need to cover Location based position stuff geoclue Implementation plan On the hardware side Nokia devices first as they re an easy target and most things already work A good idea would be to look into mce dsme and turning them into our Nokia adaptation daemons ExoPC is probably a good target next upower for charger info orientation info is available somewhere in Qt Mobility afaik but currently nonfunctional Problem is likely in sensorfw Accelerometer data may be trickier at least in Lenovo S10 3t that doesn t work Brightness sensor is present and somehow already controls screen brightness and never turns it up On the middleware side Remove duplicated qmsystem APIs Neuter qmsystem Mobility into talking to our properties only Longer term look at exposing more Mobility APIs for things like battery information introduce stabilize in qmsystem then propose upstream TODO Things yet to cover Connman portability modem drivers properties etc Bluetooth info does it belong to our hardware abstraction Screen lock how does that factor into things mce tells sysuid soon lipstick to turn lock on but should it no but where does it belong How does sensorfw fit into this If it supports plugins then it can potentially already cover a lot for us Seems sensorfw indeed works on the idea of plugins plus a configuration to

    Original URL path: https://wiki.merproject.org/wiki/Nemo/Porting (2016-02-01)
    Open archived version from archive

  • Adaptations - Mer Wiki
    RaspberryPi Nokia N8x0 N8x0 armv7 Allwinner A20 eoma68 Barnes Noble Nook Color Nook Colour Google Nexus 7 Community Workspace Tegra3 Nexus7 Nokia N900 Nemo Nemo Installing Nokia N900 Nokia N9 N950 Adaptation N9 N950 TI PandaBoard Community Workspace Omap4 Pandaboard Jolla sbj Adaptations Sbj libhybris libhybris gpu libhybris device porters MIPS x86 This section covers x86 based adaptations HP Touchpad Jolla Tablet Virtual Machine Build an image Trying it out

    Original URL path: https://wiki.merproject.org/wiki/Adaptations (2016-02-01)
    Open archived version from archive

  • Adaptation/N8x0 - Mer Wiki
    Adaptation is in COBS home cxl000 n810 testing 2 6 38 8 kernel utility programs and configuration COBS home cxl000 n810 next 3 3 8 kernel The current kernels have both be used to boot a N810 to X using fbdev driver watchdog keepalive X Configuration to enable access to all keyboard keys with touchscreen calibrated WiFi calibration data is extracted and stored to the firmware directory With the WiFi firmware from Maemo the p54spi WiFi driver has been loaded hw ether address taken from etc sysconfig wlan mac at first boot manual set and connection to WPA2 enabled Access Point established using connman test Battery Management calibration data is extracted to firmware directory X omapfb driver works RTC patches enables reading sane time values Offset read from calibration area Time now set from clock at boot using a prototype service N810 WiMax requires disabling of rng and aes drivers at this time Adaptation ToDo Find how to extract MAC addresses N800 touchscreen calibration hardware clock further functionality Sound Bluetooth USB Host OTG USB gadgets Network lock key keyboard slide other keys camera battery management keyboard backlight indicator LED UI integration N800 FM radio GPS To Build Current Kickstart file n810 armv6l razor01 ks Use mic2 to create a raw image mic image creator pkgmgr yum prefix n810 tmpdir tmp fstype vfat format raw cache your cache arch armv6l record pkgs name config n810 armv6l razor01 ks outdir your outdir overlay size mb 64 logfile your logfile dd to external card mount root partition p1 copy bluetooth and WiFi firmware to firmware directory mount boot partition p3 copy the zImage from boot partition Images available http images formeego org n810 n810 armv6l razor01 ks Based on Mer release 2011 11 11 Provides basic Razor QtDesktop with calibration touchscreen and working

    Original URL path: https://wiki.merproject.org/wiki/Adaptation/N8x0 (2016-02-01)
    Open archived version from archive

  • N9 Kernel update project - Mer Wiki
    Mer SDK chroot sb2 make n9 mer defconfig sb2 make j4 zImage sb2 make j4 modules sb2 make modules install INSTALL MOD PATH mods Deploying to device kind of flashing Pre requisite have MOSLO set up on your N9 like this We use helper scripts that prepare the modules etc prepare modules sh Then use copy script NOTE do this outside Mer SDK chroot Plug N9 to USB and let it boot so the filesystem gets mounted Then flash the kernel it s just a simple cp actually sudo copy kernel sh path to mounted N9 filesystem Packaging OBS used https build pub meego com OBS API https api pub meego com Packaging development project https build pub meego com project show project home 3Akjokinie 3AN9update Includes kernel and any possible userspace packages needed for new 3 5 y based kernel updating kernel package osc co kernel pack do changes in your local mer n9 linux git master branch tag the kernel git tag nemo n9 3 5 3 YYYYMMDD X e g git tag nemo n9 3 5 3 20121018 1 create a tarball from the package replace YYYYMMDD X with date and a running number X for that date starting from 1 git archive format tar prefix kernel 3 5 3 YYYYMMDD X nemo n9 3 5 3 YYYYMMDD X bzip2 kernel 3 5 3 YYYYMMDD X tar bz2 remove the old tarball in your local OBS checkout of kernel adaptation n950 rm tar bz2 move the tarball to your OBS checkout of kernel adaptation n950 mv path to kernel 3 5 3 YYYYMMDD X tar bz2 update changelog gedit kernel adaptation n950 changes manually add changelog entry update changes and commit osc addremove osc ci m latest changes from git TO DO list for kernel update Port needed device drivers from 2 6 32 kernel to latest kernel Some hint may come from missing kernel config options found in initial kernel config migration from 2 6 32 to 3 5 3 Currently work is being done here https github com filippz kernel adaptation n950 n9 Updated June 2014 Work item Person fixing it Other comments USB networking phdeswer 2 different patches have been sent to linux omap can also be solved by using CONFIG SOC OMAP3430 as it only influences USB and is in no way specific to 3430 This option will be removed though at some point in time Display drivers jnikula DONE PowerVR 3D drivers missing jnikula DONE Audio driver parts missing filippz Commits to upstream repo pending 1 2 CPU frequency tables missing N9 running only at 600MHz currently Tieto DONE CMT cellular modem drivers Tieto filippz Reintroducing old Harmattan H SSI framework Part 1 1 2 3 4 5 6 7 8 9 10 11 Part 2 12 13 14 15 16 17 18 19 20 21 22 23 Kernel report ssi protocol ssi protocol WAKELINES TEST FAILED more info is fixed since 24 Touch driver board configuration jnikula DONE Driver merged thanks

    Original URL path: https://wiki.merproject.org/wiki/N9_Kernel_update_project (2016-02-01)
    Open archived version from archive

  • Community Workspace/RaspberryPi - Mer Wiki
    sb2 init A armv6l M armv6l d L sysroot C sysroot c usr bin qemu arm dynamic m sdk build n N t mer rpi opt cross bin armv6l meego linux gnueabi gcc There will be errors from sb2 init concerning ld and host gcc but it should be safe to ignore them Step four is to fix a quirk about var run in the target being a symlink sb2 doesn t like this rm var run mkdir var run Step five is to rebuild and refresh the packaging system so we can install devel packages sb2 m sdk install R rpm rebuilddb sb2 t mer rpi m sdk install R zypper ref Building RPi Examples As an example of how to use sb2 to build we shall build the RPi examples TBD sane way to get them First off we know beforehand that we will need the rpi graphics and freetype devel packages installed to compile the examples Usually the exact dependencies are either in the README or INSTALL of the project or sadly often found out by building and failing We also need make and gcc in the target to compile To install we will use sb2 in sdk install mode and also request to fake that we are root user as we did in setup too This will enable us to write to the rootfs normally it is considered read only and trick the tools to think we have super powers sb2 m sdk install R zypper install gcc make gfx rpi devel gfx rpi libEGL devel gfx rpi libGLESv2 devel gfx rpi libOMXIL devel freetype devel NOTE sometimes it s necessary to be on the top directory of the target to successfully run commands in the sdk install mode If a command fails mysteriously try that first Next we create a symbolic link from usr where the libs should be to mer pi opt vc where the libs are in RPi official images This way we avoid changing the include paths in the project which would be a valid fix as well ln s usr opt vc Then we simply go to the hello pi directory and invoke the build script which just goes through the example directories calling make in them through sb2 sb2 rebuild sh If everything is set up right you should in a moment have cross compiled binaries to copy to your device NOTE couple of examples hello audio hello video need lpthread to be added to their LDFLAGS to link succesfully due to the ilclient helper lib requiring it The same principle works for most other projects as well just install the dependencies and run the build commands through sb2 TBD how to install non packaged dependencies Maintainers For questions suggestions and contributions you can ping the following persons in mer Freenode cristi kulve vgrade zuh For maintainers Qt5 Platform Plugin I ve spent sometime this weekend setting up a package to hopefully build a Qt Platform Plugin which will mean

    Original URL path: https://wiki.merproject.org/wiki/Community_Workspace/RaspberryPi (2016-02-01)
    Open archived version from archive

  • Adaptation/Nook Color - Mer Wiki
    use usbnet to access an SSH shell on the device and work with it remotely Adaptation TODO Lots to say the very least Figure out how to get all of this mess up on COBS and have it to a complete build Xorg is registering the accelerometer as an input device thus doing weird things Xorg is not registering the touch panel No PowerVR drivers in current builds Adaptation Notes The Nook Color can be triggered to boot from the SD card slot by holding the volume key while the unit either reboots or is powered on from the off state It will then load the x loader on the SD card then u boot then the kernel Sources and support files Kernel https github com dalingrin nook kernel This kernel is a modified variant of the stock kernel from Barnes and Noble Noisy build and some hacks for things like Bluetooth and USB Host support Kernel Patches and configs https gitorious org mer nook compat mer nook kernel apply against the above kernel Patches based on several N9 N950 kernel patches to extend support for Mer back to 2 6 32 Attempting to consolidate files on gitorious if at all possible Kickstart files https gitorious org mer nook compat mer nook kickstart Various and sundry kickstart files U Boot sources https github com verygreen u boot encore x loader Before attempting a build please check out ALL of the above repositories For building in the platform SDK ensure you have the Mer SB2 armv7l pattern installed and a suitable minimal mer armv7l target Note that the nook x loader source assumes that there is a u boot dir at a peer level ln s u boot encore u boot Creating a bootable image Build x loader cd nook x loader make omap3621 evt1a config make jN In the platform SDK CROSS COMPILE sb2 t mer armv7l min make The x loader is effectively unchanged Build u boot cd u boot encore make omap3621 evt1a config make jN In the platform SDK CROSS COMPILE sb2 t mer armv7l min make This version of u boot is the same as the one found when booting CyanogenMod 7 Holding the N button at boot with it installed will display a menu with the ability to choose the boot target As a result neither x loader nor u boot need to be present in the boot partition if CM7 is installed but u boot still needs to be built for the tools needed to prepare the uImage Ensure the tools are in the path export PATH PATH path to your dir u boot encore tools Apply all patches in mer nook kernel Build the kernel cd nook kernel copy mer nook kerne configs usb ethernet config config make oldconfig make jN uImage For a uRamdisk use the one found here http side 7 us files mer uRamdisk This uRamdisk consists of a disabled init and not much more Open question is this even

    Original URL path: https://wiki.merproject.org/wiki/Adaptation/Nook_Color (2016-02-01)
    Open archived version from archive