From thenktor at gmx.de Fri Feb 4 09:59:20 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Fri, 4 Feb 2011 10:59:20 +0100 Subject: [ARMedslack] mfloat-abi In-Reply-To: References: <201101271538.22016.thenktor@gmx.de> Message-ID: <201102041059.20219.thenktor@gmx.de> Am Friday 28 January 2011 12:39:34 schrieb Stuart Winter: > > - soft: only software emulation > > - softfp + mfpu=xxx: enables the compiler to use FP > > instructions/registers inside functions, but not as function > > parameters. This way, code remains compatible with 'soft' libraries > > - hard: it's a different ABI, where parameters can be passed in FP > > registers, avoiding expensive moves between core and FP registers. But > > such code is not compatible with 'soft' libraries. > > You can also do > > gcc -dumpspecs > to see what the compiler's defaults are. > Hmm, I did not really see what's the default here (soft, softfp, hard)? BTW: A test with Ogg Vorbis decoding using mpd on my Dockstar gave me these results: - using libvorbis (floating point): ~20% CPU usage - using tremor (vorbis ported to integer only): ~2% CPU usage As soft/softfpe is some kind of porting floating point operations to integer I've assumed that Armed Slack uses mfloat-abi=hard, which forwards the floating point instructions to the slow kernel FP emulation. From m-lists at biscuit.org.uk Fri Feb 4 14:07:34 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 4 Feb 2011 14:07:34 +0000 (GMT) Subject: [ARMedslack] mfloat-abi In-Reply-To: <201102041059.20219.thenktor@gmx.de> References: <201101271538.22016.thenktor@gmx.de> <201102041059.20219.thenktor@gmx.de> Message-ID: > Hmm, I did not really see what's the default here (soft, softfp, hard)? Me neither - I thought that the specs there were what was used by default. I had a further quick read about it and that isn't the case. > As soft/softfpe is some kind of porting floating point operations to integer > I've assumed that Armed Slack uses mfloat-abi=hard, which forwards the > floating point instructions to the slow kernel FP emulation. Yes, it's been ages since I looked at the issue -- I know the oldabi ARMedslack used that method, but I'd forgotten about the EABI version. The floating point used is the same as Debian use for their armel port: http://wiki.debian.org/ArmEabiPort -- Stuart Winter Slackware ARM: www.armedslack.org From thenktor at gmx.de Fri Feb 4 14:34:57 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Fri, 4 Feb 2011 15:34:57 +0100 Subject: [ARMedslack] mfloat-abi In-Reply-To: References: <201101271538.22016.thenktor@gmx.de> <201102041059.20219.thenktor@gmx.de> Message-ID: <201102041534.57391.thenktor@gmx.de> Am Friday 04 February 2011 15:07:34 schrieb Stuart Winter: > > Hmm, I did not really see what's the default here (soft, softfp, hard)? > > Me neither - I thought that the specs there were what was used by default. > I had a further quick read about it and that isn't the case. > > > As soft/softfpe is some kind of porting floating point operations to > > integer I've assumed that Armed Slack uses mfloat-abi=hard, which > > forwards the floating point instructions to the slow kernel FP emulation. > > Yes, it's been ages since I looked at the issue -- I know the oldabi > ARMedslack used that method, but I'd forgotten about the EABI version. > > The floating point used is the same as Debian use for their armel port: > http://wiki.debian.org/ArmEabiPort They say: "Floating point performance, with or without an FPU is very much faster, and mixing soft and hardfloat code is possible". This was not possible with OABI but I've never tested this on EABI. Building libvorbis with soft, softfp & hard may enlighten me ;-) If it is possible to build these three then mixing is allowed and a cpu usage comparison can follow. From pino.otto at gmail.com Sun Feb 6 20:56:20 2011 From: pino.otto at gmail.com (Giovanni) Date: Sun, 6 Feb 2011 21:56:20 +0100 Subject: [ARMedslack] Slackware on Pandaboard In-Reply-To: References: <4D38CC0A.2000102@gmail.com> Message-ID: Today I did the following test on my pandaboard; - download the miniroot fs for armedslack-13.1 - chroot into it The result was successful. I tried to install a package (python), using wget and then installpkg. Python was installed and worked in the chroot-ed Slackware. I think that this means that Slackware ARM is compatible with the pandaboard. Now I would like to install a full Slackware ARM on the pandaboard. In order to boot, the pandaboard needs the following files in a FAT32 partition on an SD card: - MLO - u-boot.bin - uImage I used the files provided by Angstrom distro. My idea is to continue to use those 3 files for booting and then install a full Slackware by NFS or USB external hard disk. Note: the pandaboard can boot only from a SD card. My problem now is where to find the Slackware installer (setup) program to launch, after booting Angstrom kernel. I am not expert about playing with boot and installer yet. Can you please give me any instructions? Best regards, giovanni On Fri, Jan 21, 2011 at 9:40 AM, Stuart Winter wrote: > > > First of all, you have to check if your processor is supported by Linux > > kernel. Then try to compile the kernel for your CPU and try to boot it. I > see > > there is SD/MMC slot, so maybe it is possible to install OS there. > > first thing: if you have such a device already in your posession: > - download the miniroot fs for armedslack-current > - chroot into it > > Does it work? If not then it's either: > - because their kernel is older than linux 2.6.31 > - or the userland of armedslack just doesn't work on that board (which > would be sad, but possible). > > Ubuntu is on it already, so there's Kernel support for it -- the easiest > thing I would do is to take the latest 2.6.37 or 2.6.38rc1 and check > if the OMAP Panda Support is in the kernel - take which ever one has it > (if it's there -- if not, find the patches and apply them to the > appropriate kernel -- ensuring that it's at least linux 2.6.31). > > Compile the kernel: easiest thing first is to build a monolithic kernel > with all of the bits your device will need. It's easier to bootstrap this > way than to faff around with an initrd. > > Find out how to configure the boot loader to boot your own kernel. > Ideally if it can tftp load then setup a tftp server and boot the kernel > from there. > Some of the Slackware ARM installation docs explain how to do this. > > Once you've got that far you can then boot into a miniroot and see how far > you get. > This board looks interesting. If they sell it with a case, I'd be tempted > to get one. > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Sun Feb 6 21:42:14 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sun, 6 Feb 2011 21:42:14 +0000 (GMT) Subject: [ARMedslack] Slackware on Pandaboard In-Reply-To: References: <4D38CC0A.2000102@gmail.com> Message-ID: > Note: the pandaboard can boot only from a SD card. Hmm. That's a bit yuck. Perhaps a future boot loader version will increase the choices. > My problem now is where to find the Slackware installer (setup) program to > launch, after booting Angstrom kernel. > > I am not expert about playing with boot and installer yet. > > Can you please give me any instructions? Well, that's great news! I'd like to get a Pandaboard if I can get one in an enclosure (I'm not a fan of naked boards). The easiest thing to do is modify the installer script I use that creates the "kirkwood" installer. First of all ensure you have a full armedslack-current tree downloaded (without sources should be fine). Download this: http://stash.armedslack.org/scripts/mk-kirkwood.sh At the top of the script, put PKGSTORE=/pathto/armedslack-current/ Change SLKARCH to "pandaboard" or whatever you want. What this script does is to unpack the "Versatile" installer image, make a list of all the modules it has; wipe the modules; unpack the "kirkwood" kernel modules package and using the list of versatile modules, copy the same named kirkwood modules. Add a few more kirkwood specific modules; Package up as an initrd ready to be booted from u-Boot. So, what you'll need is a collection of the angstrom kernel modules. Since you've got quite far already, you'll probably be able to figure it out reasonably easy. If you have any questions, let me know! I'm excited to see if you can get dual CPU support working there. I was reading that you might need to set the max amount of RAM to 768MB or something like that, otherwise you get segfaults. From carlo.caione at gmail.com Mon Feb 7 09:18:09 2011 From: carlo.caione at gmail.com (Carlo Caione) Date: Mon, 07 Feb 2011 10:18:09 +0100 Subject: [ARMedslack] Slackware on Pandaboard In-Reply-To: References: <4D38CC0A.2000102@gmail.com> Message-ID: <4D4FB8D1.7010107@gmail.com> On 06/02/2011 21:56, Giovanni wrote: > I used the files provided by Angstrom distro. My idea is to continue to > use those 3 files for booting and then install a full Slackware by NFS > or USB external hard disk. Wouldn't it be easier to just copy the minirootfs on the sd card and update packages via NFS using the packages provided with ARMedslack? It worked for me on beagleboard. BTW I'll release the ARMedslack for beagleboard xM as soon as I have enough time to create a suitable sd image. I'll let you know. -- Carlo Caione From pino.otto at gmail.com Mon Feb 7 09:39:15 2011 From: pino.otto at gmail.com (Giovanni) Date: Mon, 7 Feb 2011 10:39:15 +0100 Subject: [ARMedslack] Slackware on Pandaboard In-Reply-To: <4D4FB8D1.7010107@gmail.com> References: <4D38CC0A.2000102@gmail.com> <4D4FB8D1.7010107@gmail.com> Message-ID: Do you mean the following procedure? - boot with angstrom - copy the slack arm minirootfs on the sd card - chroot on the minirootfs - connect to the host via NFS - install all the packages from the NFS exported ARMedslack tree Is this what you meant? What about the kernel and modules? Best regards, giovanni On Mon, Feb 7, 2011 at 10:18 AM, Carlo Caione wrote: > On 06/02/2011 21:56, Giovanni wrote: > > I used the files provided by Angstrom distro. My idea is to continue to >> use those 3 files for booting and then install a full Slackware by NFS >> or USB external hard disk. >> > > Wouldn't it be easier to just copy the minirootfs on the sd card and update > packages via NFS using the packages provided with ARMedslack? > It worked for me on beagleboard. > > BTW I'll release the ARMedslack for beagleboard xM as soon as I have enough > time to create a suitable sd image. I'll let you know. > > -- > Carlo Caione > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -------------- next part -------------- An HTML attachment was scrubbed... URL: From carlo.caione at gmail.com Mon Feb 7 16:41:38 2011 From: carlo.caione at gmail.com (Carlo Caione) Date: Mon, 07 Feb 2011 17:41:38 +0100 Subject: [ARMedslack] Slackware on Pandaboard In-Reply-To: References: <4D38CC0A.2000102@gmail.com> <4D4FB8D1.7010107@gmail.com> Message-ID: <4D5020C2.1000405@gmail.com> On 07/02/2011 10:39, Giovanni wrote: > Do you mean the following procedure? > > * boot with angstrom > * copy the slack arm minirootfs on the sd card > * chroot on the minirootfs > * connect to the host via NFS > * install all the packages from the NFS exported ARMedslack tree > Well, this is what I did: * sd with 2 partitions, one for bootloaders and zImage and the other one for minirootfs. * copy xloader, uboot and zImage on the first partition * copy minirootfs on the second partition with crosscompilated modules in the usual path (/lib/modules/...) (you have to crosscompile kernel and modules on a host machine) * boot in ARMedslack * install all the others packages via NFS This worked for me. PS: the standard minirootfs requires some changes: ftp://ftp.armedslack.org/armedslack/armedslack-devtools/minirootfs/README.txt -- Carlo Caione From pino.otto at gmail.com Mon Feb 7 20:31:43 2011 From: pino.otto at gmail.com (Giovanni) Date: Mon, 7 Feb 2011 21:31:43 +0100 Subject: [ARMedslack] Slackware on Pandaboard In-Reply-To: <4D5020C2.1000405@gmail.com> References: <4D38CC0A.2000102@gmail.com> <4D4FB8D1.7010107@gmail.com> <4D5020C2.1000405@gmail.com> Message-ID: What toolchain did you use for cross-compiling the kernel and modules? I have to start from the beginning with cross-compilation. So I accept advices from the people with more experience, Best regards, giovanni On Mon, Feb 7, 2011 at 5:41 PM, Carlo Caione wrote: > On 07/02/2011 10:39, Giovanni wrote: > >> Do you mean the following procedure? >> >> * boot with angstrom >> * copy the slack arm minirootfs on the sd card >> * chroot on the minirootfs >> * connect to the host via NFS >> * install all the packages from the NFS exported ARMedslack tree >> >> > Well, this is what I did: > > * sd with 2 partitions, one for bootloaders and zImage and the other one > for minirootfs. > * copy xloader, uboot and zImage on the first partition > * copy minirootfs on the second partition with crosscompilated modules in > the usual path (/lib/modules/...) (you have to crosscompile kernel and > modules on a host machine) > * boot in ARMedslack > * install all the others packages via NFS > > This worked for me. > > PS: the standard minirootfs requires some changes: > ftp://ftp.armedslack.org/armedslack/armedslack-devtools/minirootfs/README.txt > > > > -- > Carlo Caione > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -------------- next part -------------- An HTML attachment was scrubbed... URL: From carlo.caione at gmail.com Mon Feb 7 20:48:16 2011 From: carlo.caione at gmail.com (Carlo Caione) Date: Mon, 7 Feb 2011 21:48:16 +0100 Subject: [ARMedslack] Slackware on Pandaboard In-Reply-To: References: <4D38CC0A.2000102@gmail.com> <4D4FB8D1.7010107@gmail.com> <4D5020C2.1000405@gmail.com> Message-ID: <648CAE33-9393-48F2-BCF9-1A194177B951@gmail.com> On Feb 7, 2011, at 9:31 PM, Giovanni wrote: > What toolchain did you use for cross-compiling the kernel and modules? > > I have to start from the beginning with cross-compilation. So I accept advices from the people with more experience, I used crosstool-ng[1] [1] http://ymorin.is-a-geek.org/projects/crosstool -- Carlo Caione From pino.otto at gmail.com Sun Feb 13 12:12:02 2011 From: pino.otto at gmail.com (Giovanni) Date: Sun, 13 Feb 2011 13:12:02 +0100 Subject: [ARMedslack] Slackware on Pandaboard In-Reply-To: <648CAE33-9393-48F2-BCF9-1A194177B951@gmail.com> References: <4D38CC0A.2000102@gmail.com> <4D4FB8D1.7010107@gmail.com> <4D5020C2.1000405@gmail.com> <648CAE33-9393-48F2-BCF9-1A194177B951@gmail.com> Message-ID: I did not tried yet, but it seems possible now to boot from USB on pandaboard: http://pandaboard.org/content/usb-downloader-and-usb-second-stage-bootloader-omap4 Best regards, giovanni On Mon, Feb 7, 2011 at 9:48 PM, Carlo Caione wrote: > > On Feb 7, 2011, at 9:31 PM, Giovanni wrote: > >> What toolchain did you use for cross-compiling the kernel and modules? >> >> I have to start from the beginning with cross-compilation. So I accept advices from the people with more experience, > > I used crosstool-ng[1] > > [1] http://ymorin.is-a-geek.org/projects/crosstool > > -- > Carlo Caione > > > > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From pino.otto at gmail.com Sun Feb 13 17:04:33 2011 From: pino.otto at gmail.com (Giovanni) Date: Sun, 13 Feb 2011 18:04:33 +0100 Subject: [ARMedslack] Slackware on Pandaboard In-Reply-To: References: <4D38CC0A.2000102@gmail.com> <4D4FB8D1.7010107@gmail.com> <4D5020C2.1000405@gmail.com> <648CAE33-9393-48F2-BCF9-1A194177B951@gmail.com> Message-ID: I succeeded to install full Slackware ARM on the pandaboard. I did the following: * sd with 2 partitions, one (vfat) for bootloaders (MLO, u-boot.bin) and uImage and the other one (ext2) for minirootfs * copy xloader (MLO), uboot and uImage from Angstrom distro on the first partition * copy Slackware ARM minirootfs on the second partition with Angstrom modules in the usual path (/lib/modules/...) * boot in ARMedslack * install all the others packages via NFS I had to make some changes to configuration files as indicated here: http://giovanni.wordpress.com/pandaboard/ The next step is to build a kernel and modules for omap4 by myself and use them instead of the Angstrom ones. One question: is there any kind of package manager, such as slap-get, sbopkg, etc. for Slackware ARM? If not, can I use the SlackBuilds from slackbuilds.org? How to modify them? Best regards, giovanni On Sun, Feb 13, 2011 at 1:12 PM, Giovanni wrote: > I did not tried yet, but it seems possible now to boot from USB on pandaboard: > > http://pandaboard.org/content/usb-downloader-and-usb-second-stage-bootloader-omap4 > > Best regards, > giovanni > > > On Mon, Feb 7, 2011 at 9:48 PM, Carlo Caione wrote: >> >> On Feb 7, 2011, at 9:31 PM, Giovanni wrote: >> >>> What toolchain did you use for cross-compiling the kernel and modules? >>> >>> I have to start from the beginning with cross-compilation. So I accept advices from the people with more experience, >> >> I used crosstool-ng[1] >> >> [1] http://ymorin.is-a-geek.org/projects/crosstool >> >> -- >> Carlo Caione >> >> >> >> >> >> _______________________________________________ >> ARMedslack mailing list >> ARMedslack at lists.armedslack.org >> http://lists.armedslack.org/mailman/listinfo/armedslack >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pino.otto at gmail.com Mon Feb 14 10:46:52 2011 From: pino.otto at gmail.com (Giovanni) Date: Mon, 14 Feb 2011 11:46:52 +0100 Subject: [ARMedslack] Slackware on Pandaboard In-Reply-To: References: <4D38CC0A.2000102@gmail.com> <4D4FB8D1.7010107@gmail.com> <4D5020C2.1000405@gmail.com> <648CAE33-9393-48F2-BCF9-1A194177B951@gmail.com> Message-ID: Here is the project on the Pandaboard website: http://pandaboard.org/content/slackware-pandaboard I also found that sbopkg works fine on Slackware ARM. Best regards, giovanni On Sun, Feb 13, 2011 at 6:04 PM, Giovanni wrote: > I succeeded to install full Slackware ARM on the pandaboard. > > I did the following: > * sd with 2 partitions, one (vfat) for bootloaders (MLO, u-boot.bin) and > uImage and the other one (ext2) for minirootfs > * copy xloader (MLO), uboot and uImage from Angstrom distro on the first > partition > * copy Slackware ARM minirootfs on the second partition with Angstrom > modules in the usual path (/lib/modules/...) > > * boot in ARMedslack > * install all the others packages via NFS > > I had to make some changes to configuration files as indicated here: > http://giovanni.wordpress.com/pandaboard/ > > The next step is to build a kernel and modules for omap4 by myself and use > them instead of the Angstrom ones. > > One question: is there any kind of package manager, such as slap-get, > sbopkg, etc. for Slackware ARM? If not, can I use the SlackBuilds from > slackbuilds.org? How to modify them? > > Best regards, > giovanni > > > > > > On Sun, Feb 13, 2011 at 1:12 PM, Giovanni wrote: > > I did not tried yet, but it seems possible now to boot from USB on > pandaboard: > > > > > http://pandaboard.org/content/usb-downloader-and-usb-second-stage-bootloader-omap4 > > > > Best regards, > > giovanni > > > > > > On Mon, Feb 7, 2011 at 9:48 PM, Carlo Caione > wrote: > >> > >> On Feb 7, 2011, at 9:31 PM, Giovanni wrote: > >> > >>> What toolchain did you use for cross-compiling the kernel and modules? > >>> > >>> I have to start from the beginning with cross-compilation. So I accept > advices from the people with more experience, > >> > >> I used crosstool-ng[1] > >> > >> [1] http://ymorin.is-a-geek.org/projects/crosstool > >> > >> -- > >> Carlo Caione > >> > >> > >> > >> > >> > >> _______________________________________________ > >> ARMedslack mailing list > >> ARMedslack at lists.armedslack.org > >> http://lists.armedslack.org/mailman/listinfo/armedslack > >> > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Mon Feb 14 10:50:45 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 14 Feb 2011 10:50:45 +0000 (GMT) Subject: [ARMedslack] Slackware on Pandaboard In-Reply-To: References: <4D38CC0A.2000102@gmail.com> <4D4FB8D1.7010107@gmail.com> <4D5020C2.1000405@gmail.com> <648CAE33-9393-48F2-BCF9-1A194177B951@gmail.com> Message-ID: > One question: is there any kind of package manager, such as slap-get, > sbopkg, etc. for Slackware ARM? If not, can I use the SlackBuilds from > slackbuilds.org? How to modify them? All of the package managers included with Slackware x86 are included in the ARM port. You shouldn't need to modify the slackbuilds.org scripts -- many of them already have some script to detect and set the ARM architecture; but if they don't then you will need to edit them to put ARCH=arm You can leave the CFLAGS as default -- usually -O2 will do. From pino.otto at gmail.com Mon Feb 14 10:55:08 2011 From: pino.otto at gmail.com (Giovanni) Date: Mon, 14 Feb 2011 11:55:08 +0100 Subject: [ARMedslack] Slackware on Pandaboard In-Reply-To: References: <4D38CC0A.2000102@gmail.com> <4D4FB8D1.7010107@gmail.com> <4D5020C2.1000405@gmail.com> <648CAE33-9393-48F2-BCF9-1A194177B951@gmail.com> Message-ID: OK, thanks Stuart. I realized that and already built and installed some package with sbopkg, without changing anything. That is great! Best regards, giovanni On Mon, Feb 14, 2011 at 11:50 AM, Stuart Winter wrote: > > > One question: is there any kind of package manager, such as slap-get, > > sbopkg, etc. for Slackware ARM? If not, can I use the SlackBuilds from > > slackbuilds.org? How to modify them? > > All of the package managers included with Slackware x86 are included in > the ARM port. > > You shouldn't need to modify the slackbuilds.org scripts -- many of them > already have some script to detect and set the ARM architecture; but if > they don't then you will need to edit them to put > ARCH=arm > > You can leave the CFLAGS as default -- usually -O2 will do. > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thenktor at gmx.de Wed Feb 16 14:43:36 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Wed, 16 Feb 2011 15:43:36 +0100 Subject: [ARMedslack] mfloat-abi In-Reply-To: <201102041534.57391.thenktor@gmx.de> References: <201101271538.22016.thenktor@gmx.de> <201102041534.57391.thenktor@gmx.de> Message-ID: <201102161543.36942.thenktor@gmx.de> Am Friday 04 February 2011 15:34:57 schrieb Thorsten M?hlfelder: > They say: > "Floating point performance, with or without an FPU is very much faster, > and mixing soft and hardfloat code is possible". Here is a benchmark that I've found: http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/Why-ARMs-EABI-matters/ From unixjohn1969 at gmail.com Wed Feb 16 14:47:42 2011 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Wed, 16 Feb 2011 09:47:42 -0500 Subject: [ARMedslack] mfloat-abi In-Reply-To: <201102161543.36942.thenktor@gmx.de> References: <201101271538.22016.thenktor@gmx.de> <201102041534.57391.thenktor@gmx.de> <201102161543.36942.thenktor@gmx.de> Message-ID: <4D5BE38E.2030404@gmail.com> On 02/16/2011 09:43 AM, Thorsten M?hlfelder wrote: > Am Friday 04 February 2011 15:34:57 schrieb Thorsten M?hlfelder: >> They say: >> "Floating point performance, with or without an FPU is very much faster, >> and mixing soft and hardfloat code is possible". > > Here is a benchmark that I've found: > http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/Why-ARMs-EABI-matters/ Nice find! Thanks for the link! -- === Never ask a geek why, just nod your head and slowly back away.=== +================================+==================================+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1969 at gmail.com | +================================+==================================+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson From m-lists at biscuit.org.uk Wed Feb 16 14:57:34 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 16 Feb 2011 14:57:34 +0000 (GMT) Subject: [ARMedslack] mfloat-abi In-Reply-To: <4D5BE38E.2030404@gmail.com> References: <201101271538.22016.thenktor@gmx.de> <201102041534.57391.thenktor@gmx.de> <201102161543.36942.thenktor@gmx.de> <4D5BE38E.2030404@gmail.com> Message-ID: > > > "Floating point performance, with or without an FPU is very much faster, > > > and mixing soft and hardfloat code is possible". > > > > Here is a benchmark that I've found: > > http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/Why-ARMs-EABI-matters/ This is showing the difference between OldABI which last was used in armedslack 12.2, and the EABI which is in 13.1 and onwards. I don't think this is really what you're looking to compare, based on your previous post about compilation flags. -- Stuart Winter Slackware ARM: www.armedslack.org From thenktor at gmx.de Wed Feb 16 15:01:29 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Wed, 16 Feb 2011 16:01:29 +0100 Subject: [ARMedslack] U-Boot + UbiFS Message-ID: <201102161601.29434.thenktor@gmx.de> Hi, does anybody know if U_Boot already supports loading the kernel of a UbiFS partition? I've built U-Boot 2010.09 for an Atmel board and I've seen that there are some ubi sources included but the U-Boot binary does not offer any ubi related commands. From m-lists at biscuit.org.uk Wed Feb 16 15:37:47 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 16 Feb 2011 15:37:47 +0000 (GMT) Subject: [ARMedslack] U-Boot + UbiFS In-Reply-To: <201102161601.29434.thenktor@gmx.de> References: <201102161601.29434.thenktor@gmx.de> Message-ID: > does anybody know if U_Boot already supports loading the kernel of a UbiFS > partition? I've built U-Boot 2010.09 for an Atmel board and I've seen that > there are some ubi sources included but the U-Boot binary does not offer any > ubi related commands. For u-boot it seems that there are a lot of other trees around with vendor specific stuff and other features people have needed, and that eventually these patches get back to the root. You'd need to ask on the u-boot mailing list. -- Stuart Winter Slackware ARM: www.armedslack.org From richard.lapointe at gmail.com Thu Feb 17 11:20:44 2011 From: richard.lapointe at gmail.com (Richard Lapointe) Date: Thu, 17 Feb 2011 06:20:44 -0500 Subject: [ARMedslack] U-Boot + UbiFS In-Reply-To: References: <201102161601.29434.thenktor@gmx.de> Message-ID: I believe Jeff Doozan uboot is capable of doing this. http://jeff.doozan.com/debian/uboot/ Rich Lapointe On Wed, Feb 16, 2011 at 10:37 AM, Stuart Winter wrote: > > > > does anybody know if U_Boot already supports loading the kernel of a > UbiFS > > partition? I've built U-Boot 2010.09 for an Atmel board and I've seen > that > > there are some ubi sources included but the U-Boot binary does not offer > any > > ubi related commands. > > > For u-boot it seems that there are a lot of other trees around with vendor > specific stuff and other features people have needed, and that eventually > these patches get back to the root. > > You'd need to ask on the u-boot mailing list. > > -- > Stuart Winter > Slackware ARM: www.armedslack.org > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thenktor at gmx.de Fri Feb 18 08:34:47 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Fri, 18 Feb 2011 09:34:47 +0100 Subject: [ARMedslack] U-Boot + UbiFS In-Reply-To: References: <201102161601.29434.thenktor@gmx.de> Message-ID: <201102180934.47389.thenktor@gmx.de> Am Wednesday 16 February 2011 16:37:47 schrieb Stuart Winter: > > does anybody know if U_Boot already supports loading the kernel of a > > UbiFS partition? I've built U-Boot 2010.09 for an Atmel board and I've > > seen that there are some ubi sources included but the U-Boot binary does > > not offer any ubi related commands. > > For u-boot it seems that there are a lot of other trees around with vendor > specific stuff and other features people have needed, and that eventually > these patches get back to the root. > > You'd need to ask on the u-boot mailing list. OK, if it is for interest for anyone else. Here is the answer I got on the u-boot ML: > This means you have not yet activated > > #define CONFIG_CMD_UBI > #define CONFIG_CMD_UBIFS > > in your configuration file (and CONFIG_YAFFS2 as well for yaffs). And as far as I know the right file to add these includes is include/config.h in the u-boot sources. I could build u-boot 2010.09 with YAFFS2 support (not yet tested), it failed to build with UBIFS support. Greetings Thorsten From thenktor at gmx.de Fri Feb 18 08:48:38 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Fri, 18 Feb 2011 09:48:38 +0100 Subject: [ARMedslack] File system on my Freeagent Dockstar got corrupted Message-ID: <201102180948.38762.thenktor@gmx.de> Hi, yesterday I've logged in to my Dockstar via SSH and noticed that almost all commands fail for various reasons (e.g. segmentation faults). I tried to reboot the machine, which failed, too (it never rebooted, ping was still available, ssh was not reachable anymore). So I had to unplug the power. After power up the system did not boot again. I connected the hard disk to my PC and gparted told me that the file system (ext4) of the root and home partitions could not be recognized. Only the ext2 boot partition was still available. So I did a fsck run on both partitions, which showed _a lot of_ errors. Result: * the partitions could be recognized as ext4 again. * serious data loss on the root partition, e.g. the whole etc directory was gone. About 1600 files in lost+found. * nothing in lost+found of the home partition, so probably the data is ok there. But of course now I wonder what caused this serious fail: * Did the Linux system (ARMed Slack 13.1) freeze and therefore corrupt the file systems? * Did the USB connection somehow got lost/unstable? * Did the hard disk fail and therefore freeze the system? * Problem with ext4 on ARM (I never had problems with it on my main PC) Sadly I could not run samrtctl on the USB disk because it says "unknown USB chipset" or something like that. Did someone else ever have similiar problems? For now I've formatted the rootfs again with ext4 and copied the current mini-rootfs on it. At least the Dockstar boots again. From thenktor at gmx.de Fri Feb 18 08:51:36 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Fri, 18 Feb 2011 09:51:36 +0100 Subject: [ARMedslack] #armedslack IRC channel on freenode In-Reply-To: References: Message-ID: <201102180951.36652.thenktor@gmx.de> Am Wednesday 27 October 2010 19:16:14 schrieb Stuart Winter: > Hi > > Robby's setup an #armedslack channel on the irc.freenode.net IRC service > -- there had been some discussions about armedslack on #slackware, but it > was being lost in the noise. > Hopefully this might be useful -- I leave myself logged into IRC 24/7 and > check it every day or so so might see you around if you drop in! > > s. What about a jabber chat room? :-) From m-lists at biscuit.org.uk Fri Feb 18 09:20:44 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 18 Feb 2011 09:20:44 +0000 (GMT) Subject: [ARMedslack] File system on my Freeagent Dockstar got corrupted In-Reply-To: <201102180948.38762.thenktor@gmx.de> References: <201102180948.38762.thenktor@gmx.de> Message-ID: > But of course now I wonder what caused this serious fail: > * Did the Linux system (ARMed Slack 13.1) freeze and therefore corrupt the > file systems? > * Did the USB connection somehow got lost/unstable? > * Did the hard disk fail and therefore freeze the system? > * Problem with ext4 on ARM (I never had problems with it on my main PC) I've had Slackware arm 13.1 running on the box I use to build the eratta packages, since it was installed after 13.1 was released - I've had no problems with the ext4 filesystem on it. The problem could be anywhere -- perhaps take out the disc from the usb caddy and put it onto a bare IDE interface and try SMART? The disc or USB caddy could be faulty. -- Stuart Winter Slackware ARM: www.armedslack.org From m-lists at biscuit.org.uk Fri Feb 18 09:21:07 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 18 Feb 2011 09:21:07 +0000 (GMT) Subject: [ARMedslack] #armedslack IRC channel on freenode In-Reply-To: <201102180951.36652.thenktor@gmx.de> References: <201102180951.36652.thenktor@gmx.de> Message-ID: > > check it every day or so so might see you around if you drop in! > > > > s. > > What about a jabber chat room? :-) What about using a Jabber client to connect to IRC ? :) -- Stuart Winter Slackware ARM: www.armedslack.org From thenktor at gmx.de Fri Feb 18 09:45:01 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Fri, 18 Feb 2011 10:45:01 +0100 Subject: [ARMedslack] File system on my Freeagent Dockstar got corrupted In-Reply-To: References: <201102180948.38762.thenktor@gmx.de> Message-ID: <201102181045.01631.thenktor@gmx.de> Am Friday 18 February 2011 10:20:44 schrieb Stuart Winter: > > But of course now I wonder what caused this serious fail: > > * Did the Linux system (ARMed Slack 13.1) freeze and therefore corrupt > > the file systems? > > * Did the USB connection somehow got lost/unstable? > > * Did the hard disk fail and therefore freeze the system? > > * Problem with ext4 on ARM (I never had problems with it on my main PC) > > I've had Slackware arm 13.1 running on the box I use to build the eratta > packages, since it was installed after 13.1 was released - I've had no > problems with the ext4 filesystem on it. Yes, did not have problems for a very long time and it was running almost 24/7. I've build 424 packages on this machine :) > The problem could be anywhere -- perhaps take out the disc from the usb > caddy and put it onto a bare IDE interface and try SMART? > The disc or USB caddy could be faulty. I guess it's the only thing I can do now. I hope this Seagate drive is a SATA disk, otherwise I'll have problems to connect it to the PC. It's the original Dockstar disk, does anybody now what interface is used? From thenktor at gmx.de Fri Feb 18 09:45:46 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Fri, 18 Feb 2011 10:45:46 +0100 Subject: [ARMedslack] #armedslack IRC channel on freenode In-Reply-To: References: <201102180951.36652.thenktor@gmx.de> Message-ID: <201102181045.46475.thenktor@gmx.de> Am Friday 18 February 2011 10:21:07 schrieb Stuart Winter: > > > check it every day or so so might see you around if you drop in! > > > > > > s. > > > > What about a jabber chat room? :-) > > What about using a Jabber client to connect to IRC ? :) I'm still using Pidgin. So no problem. But IRC is the only non jabber account left in there :-D From thenktor at gmx.de Fri Feb 18 10:30:12 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Fri, 18 Feb 2011 11:30:12 +0100 Subject: [ARMedslack] DHCP as default Message-ID: <201102181130.12629.thenktor@gmx.de> Hi, maybe it would be a good idea to set DHCP as default for eth0 in the mini-rootfs images? It would simplify things for newcomers, especially when ARMed Slack is installed on devices without having a console. -- Thorsten M?hlfelder Salix OS: www.salixos.org From m-lists at biscuit.org.uk Fri Feb 18 11:00:36 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 18 Feb 2011 11:00:36 +0000 (GMT) Subject: [ARMedslack] DHCP as default In-Reply-To: <201102181130.12629.thenktor@gmx.de> References: <201102181130.12629.thenktor@gmx.de> Message-ID: > maybe it would be a good idea to set DHCP as default for eth0 in the > mini-rootfs images? It would simplify things for newcomers, especially when > ARMed Slack is installed on devices without having a console. Maybe but it's not like you can just boot the mini root filesystem and start having fun: the README includes a whole bunch of things that need doing prior to being able to boot into it -- fstab being the main one. Still, no harm either way. The next miniroot will have DHCP enabled by default and the README file updated to make this known. -- Stuart Winter Slackware ARM: www.armedslack.org From pino.otto at gmail.com Fri Feb 18 12:25:21 2011 From: pino.otto at gmail.com (Giovanni) Date: Fri, 18 Feb 2011 13:25:21 +0100 Subject: [ARMedslack] DHCP as default In-Reply-To: References: <201102181130.12629.thenktor@gmx.de> Message-ID: Good. Best regards, giovanni (aka alien jo) On Fri, Feb 18, 2011 at 12:00 PM, Stuart Winter wrote: > > > maybe it would be a good idea to set DHCP as default for eth0 in the > > mini-rootfs images? It would simplify things for newcomers, especially > when > > ARMed Slack is installed on devices without having a console. > > Maybe but it's not like you can just boot the mini root filesystem > and start having fun: the README includes a whole bunch of things > that need doing prior to being able to boot into it -- fstab being > the main one. > > Still, no harm either way. The next miniroot will have DHCP enabled by > default and the README file updated to make this known. > > -- > Stuart Winter > Slackware ARM: www.armedslack.org > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thenktor at gmx.de Wed Feb 23 20:26:10 2011 From: thenktor at gmx.de (=?utf-8?Q?Thorsten_M=C3=BChlfelder?=) Date: Wed, 23 Feb 2011 21:26:10 +0100 Subject: [ARMedslack] ARM board with PCIe slot Message-ID: Hi, is there any ARM board with a PCIe slot out there? From m-lists at biscuit.org.uk Thu Feb 24 09:31:15 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 24 Feb 2011 09:31:15 +0000 (GMT) Subject: [ARMedslack] ARM board with PCIe slot In-Reply-To: References: Message-ID: On Wed, 23 Feb 2011, Thorsten M?hlfelder wrote: > Hi, > is there any ARM board with a PCIe slot out there? http://www.globalscaletechnologies.com/t-openrdudetails.aspx It's supported by ARMedslack out of the box, too. You might have to faff around with u-boot though - there's a thread on the debian-arm mailing list at the moment about it. -- Stuart Winter Slackware ARM: www.armedslack.org From linuxswat at gmail.com Thu Feb 24 22:31:21 2011 From: linuxswat at gmail.com (machin truc) Date: Thu, 24 Feb 2011 23:31:21 +0100 Subject: [ARMedslack] ARMedslack on Open Pandora Message-ID: Hi all ! My first post on ARMedslack list :^) As a huge Slackware fan and recent Open Pandora owner, i had no other choice but installing my favorite OS on my shiny new awesome machine. Some links : http://openpandora.org/ http://pandorawiki.org/Main_Page And now my problem : http://boards.openpandora.org/index.php?/topic/1524-slackware-inside-pandora/ Any help/suggestion is welcome as i'm not able to go further than this kernel panic. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ktizzard at gmail.com Fri Feb 25 10:07:41 2011 From: ktizzard at gmail.com (Kristian Tizzard) Date: Fri, 25 Feb 2011 10:07:41 +0000 Subject: [ARMedslack] Install on tonido Message-ID: Hi all. Has anyone here succeeded in getting slack running on a tonido, if so, what method did you use? All the best, Kris -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Fri Feb 25 13:17:47 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 25 Feb 2011 13:17:47 +0000 (GMT) Subject: [ARMedslack] ARMedslack on Open Pandora In-Reply-To: References: Message-ID: > And now my problem : > http://boards.openpandora.org/index.php?/topic/1524-slackware-inside-pandora/ Have you been able to boot the root filesystems that have been tagged as actually working with the Pandora? I see a gentoo one on one of the linked pages - have you tried it? My feeling, based on a quick review of the messages in the thread, is that you've built a kernel, but it doesn't contain all of the support you need to boot the system. What I'd do as a first thing is to boot a pre-made distribution: http://neuvoo.org/wiki/index.php?title=Install_Pre-Built_Image and see what lsmod returns. This will indicate what some of the things that you need to build into your kernel. Once you've made a monolichic kernel, you should be able to boot the ARMedslack mini root without needing to load additional modules (since you won't *have* the modules relevant for your board in the mini root since ARMedslack doesn't provide kernel packages for this board). It took me ages to get good kernel configs for the packages shipped with ARMedslack. From linuxswat at gmail.com Sat Feb 26 23:58:18 2011 From: linuxswat at gmail.com (Linux-SWAT) Date: Sun, 27 Feb 2011 00:58:18 +0100 Subject: [ARMedslack] ARMedslack on Open Pandora In-Reply-To: References: Message-ID: > Have you been able to boot the root filesystems that have been tagged as > actually working with the Pandora? I see a gentoo one on one of the > linked pages - have you tried it? > Yes, it worked. Also took kernel from it, and put into the slack rootfs without success, although it worked with the official Pandora rootfs. > > My feeling, based on a quick review of the messages in the thread, is that > you've built a kernel, but it doesn't contain all of the support you need > to boot the system. > > What I'd do as a first thing is to boot a pre-made distribution: > http://neuvoo.org/wiki/index.php?title=Install_Pre-Built_Image > and see what lsmod returns. > > Here's the official Pandora rootfs lsmod : bufferclass_ti 6036 0 omaplfb 9408 0 pvrsrvkm 128360 2 bufferclass_ti,omaplfb ipv6 234600 10 ads7846 8960 0 hwmon 2516 1 ads7846 The one on gentoo is not interesting. Only sound and wifi modules. > This will indicate what some of the things that you need to build into > your kernel. Once you've made a monolichic kernel, you should be able to > boot the ARMedslack mini root without needing to load additional modules > (since you won't *have* the modules relevant for your board in the mini > root since ARMedslack doesn't provide kernel packages for this board). > Ok, i'll try this step. > > It took me ages to get good kernel configs for the packages shipped with > ARMedslack. > :/ hope i'll succeed soon. Thx for tips. -------------- next part -------------- An HTML attachment was scrubbed... URL: From linuxswat at gmail.com Sun Feb 27 18:58:59 2011 From: linuxswat at gmail.com (Linux-SWAT) Date: Sun, 27 Feb 2011 19:58:59 +0100 Subject: [ARMedslack] ARMedslack on Open Pandora In-Reply-To: References: Message-ID: I actually succeded : http://boards.openpandora.org/index.php?/topic/1524-slackware-inside-pandora/page__view__findpost__p__35949 Was impossible to run Slack because the 2.6.27 kernel was too old for it. The 2.6.37.2 made my day. And i was forced ^^ to run without modules because of : # INSTALL_MOD_PATH="/mnt/sd/1/" make modules_install cp: cannot stat `/home/me/pandora/pandora-kernel/modules.builtin': No such file or directory make: *** [_modinst_] Error 1 If someone have an idea about it... I'm not going to optimize ARMedslack for now. If any news follows, i'll post it. Thanks Stuart. -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Mon Feb 28 10:07:02 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 28 Feb 2011 10:07:02 +0000 (GMT) Subject: [ARMedslack] ARMedslack on Open Pandora In-Reply-To: References: Message-ID: > http://boards.openpandora.org/index.php?/topic/1524-slackware-inside-pandora/page__view__findpost__p__35949 > > Was impossible to run Slack because the 2.6.27 kernel was too old for it. Aha. I might have to add a section on the web site about that. What is it with people running these ancient kernels? ;-) > # INSTALL_MOD_PATH="/mnt/sd/1/" make modules_install > cp: cannot stat `/home/me/pandora/pandora-kernel/modules.builtin': No such > file or directory > make: *** [_modinst_] Error 1 I don't know what that's about but you can search for the error message. Also check what creates the modules.builtin file and see how it can be created. From jawkins at armedslack.org Mon Feb 28 10:21:39 2011 From: jawkins at armedslack.org (Jim Hawkins) Date: Mon, 28 Feb 2011 10:21:39 +0000 (GMT) Subject: [ARMedslack] ARMedslack on Open Pandora In-Reply-To: References: Message-ID: On Mon, 28 Feb 2011, Stuart Winter wrote: > > # INSTALL_MOD_PATH="/mnt/sd/1/" make modules_install > > cp: cannot stat `/home/me/pandora/pandora-kernel/modules.builtin': No such > > file or directory > > make: *** [_modinst_] Error 1 > > I don't know what that's about but you can search for the error message. > Also check what creates the modules.builtin file and see how it can be > created. Doesn't that normally mean that "make modules" hasn't been called? I don't think either "make uImage" or "make modules_install" actually build the kernel modules. Cheers, Jim From gwenhael.le.moine at gmail.com Mon Feb 28 10:21:42 2011 From: gwenhael.le.moine at gmail.com (Gwenhael Le Moine) Date: Mon, 28 Feb 2011 17:21:42 +0700 Subject: [ARMedslack] ARMedslack on Open Pandora In-Reply-To: References: Message-ID: > Aha. ?I might have to add a section on the web site about that. > What is it with people running these ancient kernels? ;-) Latest usable kernel for zaurus tosa is 2.6.31.14, everything after that has a broken display. Recently I had to downgrade udev to the version of 13.1 because latest udev requires at least a 2.6.32 kernel. That's my reason ;) From m-lists at biscuit.org.uk Mon Feb 28 11:20:46 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 28 Feb 2011 11:20:46 +0000 (GMT) Subject: [ARMedslack] ARMedslack on Open Pandora In-Reply-To: References: Message-ID: > Latest usable kernel for zaurus tosa is 2.6.31.14, everything after > that has a broken display. Recently I had to downgrade udev to the > version of 13.1 because latest udev requires at least a 2.6.32 kernel. This is why I'm very cautious with ARM hardware: the support has to be in kernel.org and the device have a community around it, demonstrating that it's actively maintained. I had this problem with the RiscPC where the kernel began panicing and since nobody cared about the RPC anymore, it was never going to be fixed: so the only choice is either to keep the OS at an old kernel or abandon support for that architecture. Now people can understand why I'm never going to go and provide kernels for random devices which have not have a thriving community. -- Stuart Winter Slackware ARM: www.armedslack.org