arm December 2013

arm@lists.fedoraproject.org

31 participants
37 discussions

Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support
by Hans de Goede 26 Dec '13

26 Dec '13

Hi All, I'm very happy to announce the first release (r1) of my Fedora 19 ARM remix images for Allwinner A10, A10s, A13 and A20 based devices. This release is based on the official Fedora 19 Final for ARM images, with u-boot and kernel(s) from the linux-sunxi project: http://linux-sunxi.org/ Besides all the goodies from Fedora-19, this release also contains the following new items on the Allwinner / sunxi front: -Support for the new dual core A20 soc (tested with cubieboard2), this is based on forward porting the core machine code + various drivers from allwinners 3.3 kernel source dump to the sunxi-3.4 sources. The following has been ported / is supported: -uarts -mmc controllers -ehci and ohci usb controllers (usb controllers 1 and 2, controller 0 is an otg controller and is not supported yet. -video output block (hdmi, vga, lcd, composite out) -i2c controllers -axp pmic including cpu voltage scaling -rtc -sound: analog in/out, hdmi audio, spdif out (spdif untested) -ethernet controller (emac) -sata controller Note any functional blocks in the SOC which are not explictly listed as supported above are not supported atm -Support for a couple of new boards (38 boards in total now) You can download it here: http://scotland.proximity.on.ca/contrib-images/hansg/Fedora-19-a10-armhfp-r… sha1sum: a179afafd77c26c7022392d2fa72e3fd221dd33a It is important to read the README, the image standard comes without u-boot pre-loaded since u-boot is board specific. The image includes a user-friendly simple script to install the right u-boot for your board, but if you simply xzcat the image to an sdcard, and then boot your device with the sdcard, things will *not* work. See the README for a list of currently supported boards. Known Issues: -Many boards don't have an rtc (A10 and A20 have a builtin one), or at least no battery backup for it, resulting in the date + time being wrong. -If the date is of by more then a couple of months, "yum update" won't work because certificate validation fails for the https connection yum tries to make. So if yum fails to get its repodata first check (and fix) your date -The regular (host not otg) usb-port on A10s based boards can be a bit quirky. It is best to plug in a hub even when using only one device, otherwise the device may not be recognized. If this happens, after adding a hub, often a power-cycle is needed too. -The wifi chip on the Auxtek-T004 hdmi-stick is unsupported atm Enjoy, Hans And to make sure everyone reads the README, let me print it here in full: Fedora 19 ARM for Allwinner A10, A10s, A13 and A20 devices README ----------------------------------------------------------------- Quickstart guide ---------------- 1) Insert an sdcard, note any data on the card will be destroyed! 2) Make sure the card is not mounted, run "mount" and if the card shows up in the output umount its partitions 3) Write the img file to the card, ie as root do: xzcat Fedora-19-a10-armhfp-r1.img.xz > /dev/mmcblk0 sync 4) The card is not yet ready for use! Since the A10 u-boot is board specific, the image comes without any uboot install, follow the next steps to install the right u-boot for your board 5) Remove the card, and re-insert it. The uboot partition should get automatically mounted, if not mount it manually, 6) As root (or through sudo) run: <uboot-part-mount>/select-board.sh, ie: sudo /run/media/hans/uboot/select-board.sh If you've dialog installed the select-board.sh script will prompt for your board. If you don't have dialog installed, it will print the list of supported boards. Lookup your board and re-run the script with the shortname for your board as argument, ie: sudo /run/media/hans/uboot/select-board.sh mk802 7) umount the uboot and rootfs partitions, ie: umount /run/media/hans/uboot umount /run/media/hans/rootfs 8) Your sdcard is now ready for use 9) *Before* powering up your A10 device connect it to an hdmi or dvi monitor 10) When first booting from the sdcard inserted Fedora will automatically reboot once, this is part of the process to resize the root partition to fill the entire sdcard and is normal behavior. 11) After the automatic reboot Fedora will start with the initial-setup wizard: 11a) Configure networking, note: * If you've an A10 board with wired ethernet and you want to use dhcp you don't need to do anything. * If you've an A20 board, your ethernet will have a random mac-address, so if you want to configure a static ip-address and want it to stick across reboots, go to the ethernet-tab, select the mac-address field and delete its contents, so that the static ip address you're configuring does not get tied to the random mac-address. 11b) Setup the time zone 11c) Set a root password 11d) Create a user 12) Log in as the just created user 13) Enjoy Fedora on your A10 device Supported Devices: ------------------ Fedora 19 ARM for Allwinner A10 has been tested with the following devices: * A13-OLinuXino-MICRO (Olimex) * Auxtek T003 hdmi tv stick * Auxtek T004 hdmi tv stick * BA10 TV Box * Cubieboard development board 1024 MB RAM * Cubieboard2 (A20) development board * Gooseberry development board * Mele A1000G/A2000G 1024 MB RAM * Mini-X 1024 MB RAM * mk802 (with female mini hdmi) 512 MB RAM * mk802 with A10s (s with a circle around it on the barcode label) * mk802ii (with male normal hdmi) 1024 MB RAM * r7 hdmi tv stick * UHost U1A hdmi tv stick * Wobo i5 TV Box Fedora 19 ARM should also work on the following devices: * A10 tablet sold under various names (whitelabel) * A13 tablet sold under various names (whitelabel) * A10s-OLinuXino-MICRO (Olimex) * A13-OLinuXino (Olimex) * A20-OLinuXino-MICRO (Olimex) * Coby MID7042 tablet * Coby MID8042 tablet * Coby MID9742 tablet * Cubieboard development board 512 MB RAM * DNS AirTab M82 tablet * EOMA68 A10 CPU card * H6 netbook * Hackberry development board * Hyundai a7hd tablet * iNet-97F Rev.2 (and clones) tablet * Mele A1000/A2000 512 MB RAM * Mele A3700 * Mini-X 512 MB RAM * mk802 (with female mini hdmi) 1024 MB RAM * pcDuino development board * Point of View ProTab 2 IPS 9" tablet * Point of View ProTab 2 IPS tablet with 3g * XZPAD700 7" tablet Configuring the display output ------------------------------ Multiple video outputs at the same time are not supported. By default hdmi output with EDID is used for all devices, except for tablets/netbooks where the default output is the lcd. The default hdmi output with EDID will get the native resolution of your TV / monitor and use that. Note that in order for this to work your TV / monitor must be connected *and turned on*, before booting your device. The output resolution can be configured with the disp.screen0_output_mode kernel cmdline value, which can be found in the extrargs part of uEnv.txt in the uboot partition. The default uEnv.txt contains the following value: disp.screen0_output_mode=EDID:1280x720p60 This means try to use EDID and if no valid EDID info is found fallback to 1280x720p60. The used output can be changed by adding disp.screen0_output_type=X to the extraargs in uEnv.txt. With X being one of: 0:none; 1:lcd; 2:tv; 3:hdmi; 4:vga Some per display type notes: -lcd outputs: Hardcoded to the native mode, disp.screen0_output_mode is ignored -tv: For the cvbs output disp.screen0_output_mode must be set to one of the following: pal, pal-svideo, ntsc, ntsc-svideo, pal-m, pal-m-svideo, pal-nc, pal-nc-svideo. Note the -svideo variants should only be used on boards with an svideo connector, for composite out use the regular variants, ie: disp.screen0_output_type=2 disp.screen0_output_mode=pal -hdmi: To override the EDID detected mode, drop the "EDID:" from the disp.screen0_output_mode value and set it to the desired mode, ie: disp.screen0_output_type=3 disp.screen0_output_mode=1360x768p60 -vga: Does not support EDID, "EDID:" must be removed from the disp.screen0_output_mode value otherwise it will be ignored. interlaced progressive and refreshrate settings specified are ignored, each resolution has hardcoded values for these. Example usage: disp.screen0_output_type=4 disp.screen0_output_mode=1024x768 USB controller caveats ---------------------- The OTG USB controller in host mode only supports a limited number of devices, plugging in a hub + mouse + keyboard typically will make either the mouse or keyboard not work. This is a hardware limitation which we will likely not be able to work around. On tv-sticks and top-set boxes, simply avoid the otg connector, instead use a hub in a regular host usb connector. Note on the mini-x the otg / host marking is not always correct. If things don't work try using the OTG connector instead! On tablets and the gooseberry unfortunately only the otg connector is available. One solution there is using a single usb-device which is both a keyboard and a mouse at the same time. IE the receiver for logitech wireless desktop sets. Supported hardware components / features: ----------------------------------------- Fedora 19 ARM for Allwinner A10 supports the following components: * CPU + PMU + RAM * Serial ports * MMC cards * Internal NAND storage (*) * Framebuffer on lcd / vga / hdmi / composite video * Sound both analog out and over hdmi * OTG USB controller (*) * Both standard USB host controllers * Wifi * Wired Ethernet * SATA * IR (untested at this time) (*) *) Not supported on A20, the A20 support in the Fedora 19 A10 images is new, and as such the driver code for these has not been forward-ported from the Allwinner source dump to the sunxi-3.4 kernel the Fedora 19 A10 images use yet. Unsupported hardware components: -------------------------------- The following components require various proprietary blobs to be used, and as such are not supported in the Fedora images. The kernel drivers for them are present (usually as modules) (*), so if you add the necessary blobs you might get these to work: * Mali 400 GPU * Cedar hardware video & audio decoding and encoding engine * G2D 2d engine *) Except for the A20 Differences from stock Fedora ----------------------------- * Since the A10 is not a very powerful soc some services which are enabled by default on Fedora are disabled in the image, see build-image.sh for a list. * No plymouth: we log to a serial console for debugging so no pretty splash. Also we don't use an initrd, so removing the console=ttyS0,115200 from the extraargs in uEnv.txt will give plymouth, but so late it hardly matters. Rebuilding the Fedora 19 ARM for Allwinner A10 disk image --------------------------------------------------------- Building the Fedora 19 ARM for Allwinner A10 disk image consists of 2 steps 1) Building a uboot.tar.gz and rootfs.tar.gz "overlays", this is done bu the build-boot-root-sh script 2) Combining uboot.tar.gz and rootfs.tar.gz with an official Fedora 19 arm img, this combining is done by the build-image.sh script The a10 image you downloaded is based on Fedora-XFCE-armhfp-19-1-sda.raw These scripts are hosted here: https://github.com/jwrdegoede/sunxi-fedora-scripts.git A copy of the exact versions of these scripts used to build this Fedora A10 image can be found in the scripts directory of the uboot partition, the kernel config used during the build can be found here too. If you want to exactly reproduce this image it is important to use the scripts from the scripts dir of the uboot partition, as the scripts contain GIT tags used during the build to checkout the exact versions to build. The pre-conditions these scripts expect to be met, and the exact usage of them is documented in comments in the top of each script.

5 5

Linux ARM hackfest Brno Thursday February 6th
by Hans de Goede 25 Dec '13

25 Dec '13

Hi All, I'm organizing a (small) ARM hackfest in Brno the day before devconf.cz: http://devconf.cz/ The hackfest will be held inside the Red Hat Office in Brno but visitors are very much welcome! I'll be focussing on: https://fedoraproject.org/wiki/Changes/AllwinnerSunxiSupport But anyone who wants to do any ARM related work is welcome. If you plan to attend, please drop me a mail so that I can keep track of how many people will be there and make sure I reserve a big enough conference room. Regards, Hans

1 0

F20 Beta 5 (XFCE) remix for PandaBoard
by Jaromir Capik 23 Dec '13

23 Dec '13

Hello everyone. I created a Fedora 20 Beta 5 remix for Panda and would appreciate some tests. The image is XFCE only (can add more later). You can download the image here: http://jcapik.fedorapeople.org/files/ARM/f20-remixes/ Please, let me know whether it works for you ... NOTE: It uses the old F19 kernel as the new F20 kernel doesn't boot on Panda -> do not update the kernel. Thanks in advance. Regards, Jaromir. -- Jaromir Capik Red Hat Czech, s.r.o. Software Engineer / Secondary Arch Email: jcapik(a)redhat.com Web: www.cz.redhat.com Red Hat Czech s.r.o., Purkynova 99/71, 612 45, Brno, Czech Republic IC: 27690016

4 11

Pandaboard ES and Fedora
by Peter TB Brett 23 Dec '13

23 Dec '13

Hi all, I've been a happy user of Fedora 19 on a Pandaboard. However, I'm keen to upgrade to Fedora 20, and I'd also really like to get Fedora working on our Pandaboard ES rev B3 boards (the ones with the dodgy memory chip). I know that the topic was previously discussed briefly on this list back in August, but I was wondering whether anyone's aware of any work being done on Fedora on Pandaboard or any progress being made since then. I'd especially be interested in any info that's been gathered that points to where, exactly, the problem lies... Please also let me know if this is the wrong mailing list to be asking on! Thanks in advance for any info you can share! Regards, Peter -- Dr Peter Brett http://peter-b.co.uk/

4 9

Introduction
by Thiago Peixoto 22 Dec '13

22 Dec '13

Hi, everybody! I am Thiago Peixoto, a computer science student at Federal University of Alagoas (in Brazil) and a computer architecture enthusiast. I used to contribute with Fedora translations, but i really missed coding contributions. I recently bought a Raspberry Pi and i installed Pidora on it. My fun is run chunks of assembly code to learn about the instruction set, but i am looking for something useful to do with it. :) Am i at the right place? Could anyone, please, guide me on the first step? Thank you!

1 0

Running aarch64 Fedora on x86-64 host with qemu
by Richard W.M. Jones 22 Dec '13

22 Dec '13

Userspace only, but it works ... http://rwmj.wordpress.com/2013/12/22/how-to-run-aarch64-binaries-on-an-x86-… Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v

1 0

Fedora 20 on older "Beagle" boards
by Peter TB Brett 20 Dec '13

20 Dec '13

Hi, Quick query -- has Fedora 20 been tested on any older "Beagle" boards, such as the BeagleBoard-xM? Would this be worth doing? I can probably find some boards lying around the lab somewhere. Peter -- Dr Peter Brett http://peter-b.co.uk/

3 2

Re: [fedora-arm] Pandaboard ES and Fedora
by Peter TB Brett 20 Dec '13

20 Dec '13

[ Resending, this time to list ] On Fri, 20 Dec 2013 12:52:30 +0000, Peter Robinson <pbrobinson(a)gmail.com> wrote: > On Fri, Dec 20, 2013 at 12:12 PM, Peter TB Brett <peter(a)peter-b.co.uk> >> Have you by any chance collated any information on what exactly "not >> working" entails during your experiments? I'd really like to avoid >> duplicating any work that other people have already done. At the moment >> I'd be happy just to get the kernel to boot to a shell on a serial >> console...! > > Well the current status for 3.11+ is that there's no output on the > serial console, it doesn't boot, or at least appear to boot with > anything on any console. Well, that sucks. > [snip] > >> Are you still stuck on the memory chip issues, or have those now been >> fixed? > > Well at least for me on the ES I never had that working on the > 3.7-3.10 releases that would vaguely sort of attempt to boot on my > devices. In theory the DT should possibly resolve those issues but as > we're not getting even to the point I had with 3.7-3.10 it's not under > consideration. From my PoV we need to get to the point where we're at > least getting console output. > > I poke at it randomly but my time is limited and there's a lot newer > platforms that are also needing my time. Okay, that's more-or-less completely useless to me. Without proper support from TI engineers (and probably SVTronics too) I doubt I'd be able to do anything useful towards getting it working. Maybe our stack of Pandaboards are best used to prop doors open. I have probably got a few day to spend poking, but I'd need some pointers because I've done very little kernel work. I guess our best bet for our application will be to get Beaglebone Blacks instead, but it's very disappointing because they really don't have anything like as good a specification as the Pandaboards and there's a pretty long lead time at the moment. :-( Peter -- Dr Peter Brett http://peter-b.co.uk/

1 0

Next Fedora ARM Status Meeting - 2014-01-08
by Paul Whalen 18 Dec '13

18 Dec '13

Good day folks, The first Fedora ARM Status Meeting in 2014 will be on January 8th, at 4PM EST (9PM UTC) due to the holiday on January 1st. Thanks everyone for a great year- not only for Fedora, but in particular for Fedora ARM. Have a Safe and Happy Holiday! Paul

1 0

FUSE appears non-functional on ARM
by Richard W.M. Jones 12 Dec '13

12 Dec '13

https://bugzilla.redhat.com/show_bug.cgi?id=1040945 Could I ask someone to look at the simple test case in that bug and see if they can reproduce it on another ARM host; in case it's some peculiarity of me / my hardware / my kernel. I'm not using the Fedora kernel -- I'm using an upstream kernel with sunxi patches -- so that might affect things. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm December 2013