[ARMedslack] ARMedslack Digest, Vol 4, Issue 1

Wed Dec 23 19:43:40 UTC 2009

Hi man, i Flavio Roque, amateur Armedslack user.
i have a initial big problem with cf card (4gb). Format process example, i 
can´t format conclusion. how procedure i to do first?... (sorry for bad 
speach, im Brazilian guy).. thanks and happy new year man. thanks!!
----- Original Message ----- 
From: <armedslack-request at lists.armedslack.org>
To: <armedslack at lists.armedslack.org>
Sent: Wednesday, December 23, 2009 5:05 PM
Subject: ARMedslack Digest, Vol 4, Issue 1


> Send ARMedslack mailing list submissions to
> armedslack at lists.armedslack.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.armedslack.org/mailman/listinfo/armedslack
> or, via email, send a message with subject or body 'help' to
> armedslack-request at lists.armedslack.org
>
> You can reach the person managing the list at
> armedslack-owner at lists.armedslack.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ARMedslack digest..."
>
>
> Today's Topics:
>
>   1. ARMED kernel compile errors (Tibor Kendl)
>   2. Re: ARMED kernel compile errors (Stuart Winter)
>   3. Mounting root filesystem (Tibor Kendl)
>   4. Re: Mounting root filesystem (Stuart Winter)
>   5. Java SE embedded from Sun (Frank Guibert)
>   6. Re: Java SE embedded from Sun (Stuart Winter)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 03 Dec 2009 17:55:59 +0100
> From: Tibor Kendl <kendlt at hdsnet.hu>
> To: armedslack at lists.armedslack.org
> Subject: [ARMedslack] ARMED kernel compile errors
> Message-ID: <4B17ED9F.4010205 at hdsnet.hu>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Dear Stuart!
>
> Today i made a kernel configuration that suits my acer pda i mentioned a
> week before, and then i tried to build it in the ARMedslack i installed
> under qemu. I used the 2.6.30.5 kernel source .tgz you supplied with the
> ARMedslack 12.2 distribution. The compilation was stopped with error.
> The problematic file was vgacon.c. Since the vga text console is
> necessary for me, i could not take it out from the kernel options. How
> did you succeed to compile this kernel? What do you think i should do
> with that? This was the gcc error message:
>
> In file included from drivers/video/console/vgacon.c:51:
> include/video/vga.h: In function 'vga_io_r':
> include/video/vga.h:226: warning: comparison is always true due to
> limited range of data type
> include/video/vga.h: In function 'vga_io_w':
> include/video/vga.h:231: warning: comparison is always true due to
> limited range of data type
> include/video/vga.h: In function 'vga_io_w_fast':
> include/video/vga.h:237: warning: comparison is always true due to
> limited range of data type
> include/video/vga.h:237: warning: comparison is always true due to
> limited range of data type
> drivers/video/console/vgacon.c: In function 'write_vga':
> drivers/video/console/vgacon.c:166: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:166: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:167: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:167: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c: In function 'vgacon_startup':
> drivers/video/console/vgacon.c:510: error: 'PCIMEM_BASE' undeclared
> (first use in this function)
> drivers/video/console/vgacon.c:510: error: (Each undeclared identifier
> is reported only once
> drivers/video/console/vgacon.c:510: error: for each function it appears 
> in.)
> drivers/video/console/vgacon.c: In function 'vgacon_set_cursor_size':
> drivers/video/console/vgacon.c:668: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:669: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:670: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:671: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:680: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:681: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:682: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:683: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c: In function 'vgacon_doresize':
> drivers/video/console/vgacon.c:764: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:765: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:770: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:771: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:779: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:780: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:788: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:789: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:790: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:791: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:794: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:795: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:796: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:797: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:800: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:801: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:802: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:803: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:806: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:807: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c: In function 'vga_vesa_blank':
> drivers/video/console/vgacon.c:895: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:899: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:900: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:901: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:902: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:903: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:904: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:905: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:906: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:907: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:908: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:909: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:910: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:911: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:912: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:913: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:914: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:933: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:934: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:935: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:936: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:937: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:938: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:947: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:948: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:949: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:950: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:955: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c: In function 'vga_vesa_unblank':
> drivers/video/console/vgacon.c:965: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:966: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:967: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:968: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:969: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:970: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:971: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:972: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:973: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:974: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:975: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:976: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:977: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:978: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:979: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:980: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:986: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c: In function 'vgacon_do_font_op':
> drivers/video/console/vgacon.c:1068: error: 'PCIMEM_BASE' undeclared
> (first use in this function)
> drivers/video/console/vgacon.c:1181: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:1186: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c: In function 'vgacon_adjust_height':
> drivers/video/console/vgacon.c:1216: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:1217: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:1218: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:1219: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:1228: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:1229: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:1230: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:1231: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:1232: warning: comparison is always true
> due to limited range of data type
> drivers/video/console/vgacon.c:1233: warning: comparison is always true
> due to limited range of data type
> make[3]: *** [drivers/video/console/vgacon.o] Error 1
> make[2]: *** [drivers/video/console] Error 2
> make[1]: *** [drivers/video] Error 2
> make: *** [drivers] Error 2
>
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 3 Dec 2009 17:07:13 +0000 (GMT)
> From: Stuart Winter <m-lists at biscuit.org.uk>
> To: Slackware ARM port <armedslack at lists.armedslack.org>
> Subject: Re: [ARMedslack] ARMED kernel compile errors
> Message-ID:
> <alpine.LNX.2.00.0912031703060.28757 at bourbon.biscuit.org.uk>
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>>
>> Today i made a kernel configuration that suits my acer pda i mentioned a
>> week before, and then i tried to build it in the ARMedslack i installed
>> under qemu. I used the 2.6.30.5 kernel source .tgz you supplied with the
>> ARMedslack 12.2 distribution. The compilation was stopped with error.
>> The problematic file was vgacon.c. Since the vga text console is
>> necessary for me, i could not take it out from the kernel options. How
>> did you succeed to compile this kernel? What do you think i should do
>> with that? This was the gcc error message:
>
> Neither QEMU nor the Kirkwood platforms provide VGA, so the kernels
> don't have support for it.
>
> Does the PDA really have VGA?
>
> The default config for the N30 has not got VGA set -- it does have
> Framebuffer set though -- most ARM devices use framebuffer: try using
> that instead.
>
> prisere [arm] # pwd
> /usr/src/linux-2.6.32-rc8/arch/arm
> prisere [arm] # egrep "VGA|N30" ./configs/s3c2410_defconfig
> CONFIG_MACH_N30=y
> # CONFIG_VGASTATE is not set
> # CONFIG_FB_SVGALIB is not set
> # CONFIG_VGA_CONSOLE is not set
> prisere [arm] #
>
>
>
> ------------------------------
>
> Message: 3
> Date: Sat, 05 Dec 2009 00:32:30 +0100
> From: Tibor Kendl <kendlt at hdsnet.hu>
> To: armedslack at lists.armedslack.org
> Subject: [ARMedslack] Mounting root filesystem
> Message-ID: <4B199C0E.50700 at hdsnet.hu>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi Stuart, Everyone!
>
> I succeeded to compile the kernel with switching off the vga console as
> you advised. I copied the root filesystem from the qemu image with the
> installed ARMedslack onto an SD card. With fdisk i created three
> partitions on it. One dos type with the kernel and the bootloader
> (haret-0.3.8), one linux swap, and an ext2 with the root filesystem. I
> inserted the card into the pda and started the bootloader. After the
> penguin logo appeared and the kernel massages started coming up on the
> pda console, the  booting stopped with an error:
> VFS: Cannot open root device "mmcblk0p3" or unknown-block(0,0)
> On my laptop with x86 processor and Slackware 12.2, after i plug in an
> SD card it can be seen in /dev/mmcblk0, and the partitions on it are
> /dev/mmcblk0p1, /dev/mmcblk0p2, etc. Do you think this kind of naming
> convention is also valid under the ARM environment. What do you think
> could be the device name of an sd card inserted into a pda, and the
> device names of the partitions on it?
>
> Thanks:
> Tibor Kendl
>
>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 7 Dec 2009 14:22:07 +0000 (GMT)
> From: Stuart Winter <m-lists at biscuit.org.uk>
> To: Slackware ARM port <armedslack at lists.armedslack.org>
> Subject: Re: [ARMedslack] Mounting root filesystem
> Message-ID:
> <alpine.LNX.2.00.0912071413320.28757 at bourbon.biscuit.org.uk>
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>
> Hi
>
>> pda console, the booting stopped with an error: VFS: Cannot open root
>> device "mmcblk0p3" or unknown-block(0,0)
> [..]
>> /dev/mmcblk0, and the partitions on it are /dev/mmcblk0p1,
>> /dev/mmcblk0p2, etc. Do you think this kind of naming convention is also
>> valid under the ARM environment.
>
> It's most likely to be the same if you have just one of these devices.
>
> The first thing I would do is to check whether you have the support
> for the SD card compiled into the kernel.
>
> If you have compiled the driver into the kernel, you ought to see
> some output from it  -- at a minimum you ought to see this:
> [   36.873037] mmc0: mvsdio driver initialized, lacking card detect (fall
> back to polling)
>
> This is what I see on my sheevaplug which does not have an SD card
> in the slot.
>
> Some of the information here may be helpful regarding the SD card:
> http://nil-techno.blogspot.com/2009/10/installing-slackware-on-sheevaplug.html
>
> I hope that helps.
>
> -- 
> Stuart Winter
> Slackware ARM: www.armedslack.org
>
>
> ------------------------------
>
> Message: 5
> Date: Tue, 22 Dec 2009 11:10:35 +0100
> From: Frank Guibert <frank.guibert at gmail.com>
> To: armedslack at lists.armedslack.org
> Subject: [ARMedslack] Java SE embedded from Sun
> Message-ID:
> <a2ca2a150912220210s58a91d3ctf782bd16afe57b0 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi everybody,
>
> Sun released Java SE binaries for embedded devices :
> http://java.sun.com/javase/downloads/embedded.jsp
>
> The following one works fine for me on armedslack-current on my
> sheeva-plug (it is a month old install I have not been following
> -current since then) :
>
> ARMv5 Linux - Headless (Early Access)
>
>    * EABI, glibc 2.5, Soft Float, Little Endian
>
> Just untar the archive and add the bin folder to your PATH environment 
> variable.
>
> It requires registration and should stop working after 90 days.
>
> Cheers
>
> Frank
>
>
> ------------------------------
>
> Message: 6
> Date: Wed, 23 Dec 2009 19:05:20 +0000 (GMT)
> From: Stuart Winter <m-lists at biscuit.org.uk>
> To: Slackware ARM port <armedslack at lists.armedslack.org>
> Subject: Re: [ARMedslack] Java SE embedded from Sun
> Message-ID:
> <alpine.LNX.2.00.0912231904010.3522 at bourbon.biscuit.org.uk>
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>
> Hi Frank
>
>> Sun released Java SE binaries for embedded devices :
>> http://java.sun.com/javase/downloads/embedded.jsp
>
> Cool thanks - I did not know SUN were releasing Java
> binaries for ARM.
>
> Patrick asked directly for approval to include the x86 binary blobs into
> Slackware, so I'll try and do the same for ARMedslack.
> Beats the hell out of trying to compile the open source stuff ;-)
>
>
> ------------------------------
>
> _______________________________________________
> ARMedslack mailing list
> ARMedslack at lists.armedslack.org
> http://lists.armedslack.org/mailman/listinfo/armedslack
>
>
> End of ARMedslack Digest, Vol 4, Issue 1
> ****************************************
>