Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.ports.arm > #10754

Re: armel/marvell kernel size

Cross-posted to 2 groups.

Show all headers | View raw

On Mar 28, 2018, at 2:22 AM, Rick Thomas <rbthomas@pobox.com> wrote:

>> What filesystems do you use? Do you use any (para)virtualization? What
>> about addon hardware that you have? Any USB dongles? Anything that you
>> can think of? Sound?
>> 
>> Do you use NFS? (I do) What kind of compressed ramdisk do you use? The
>> loaded modules that you have with lsmod would be nice to know.
> 

Filesystems:  ext2 and ext4

Vitrualization: Nope.  These are way too small for anything fancy like that.

Addon hardware:
	USB2 ports useful for disk and/or flash drives and other stuff (I don’t do the “other stuff” myself but I suppose there are folks who might).
	They have 1000BaseT ports.  Two ports on the OpenRD Client, one on the SheevaPlug.
	They each have a mini-USB serial port that they use for serial console.
	The Client has a headphone jack.  I’ve used it in the past for listening to streaming radio.  The SheevaPlug has no audio i/o.
	Both machines have SD-card slots that can be used in booting or as aux data storage.
	Both get their uboot from mtd, not mmc, so updating uboot requires re-flashing.
	The Client has 512MB RAM.  The SheevaPlug has the same.

	CPU info for SheevaPlug —
> root@sheeva:~# cat /proc/cpuinfo
> processor	: 0
> model name	: Feroceon 88FR131 rev 1 (v5l)
> BogoMIPS	: 1185.79
> Features	: swp half thumb fastmult edsp 
> CPU implementer	: 0x56
> CPU architecture: 5TE
> CPU variant	: 0x2
> CPU part	: 0x131
> CPU revision	: 1
> 
> Hardware	: Marvell Kirkwood (Flattened Device Tree)
> Revision	: 0000
> Serial		: 0000000000000000

	CPU info for OpenRD Client —
> rbthomas@client:~$ cat /proc/cpuinfo 

> processor	: 0
> model name	: Feroceon 88FR131 rev 1 (v5l)
> BogoMIPS	: 1191.93
> Features	: swp half thumb fastmult edsp 
> CPU implementer	: 0x56
> CPU architecture: 5TE
> CPU variant	: 0x2
> CPU part	: 0x131
> CPU revision	: 1
> 
> Hardware	: Marvell Kirkwood (Flattened Device Tree)
> Revision	: 0000
> Serial		: 0000000000000000

	Uboot details on SheevaPlug —
> U-Boot 2016.01-rc3+dfsg1-3 (Jan 02 2016 - 23:19:11 +0000)
> Marvell-Sheevaplug
> 
> SoC:   Kirkwood 88F6281_A0
> DRAM:  512 MiB (ECC not enabled)
> WARNING: Caches not enabled
> NAND:  512 MiB
> MMC:   MVEBU_MMC: 0
> In:    serial
> Out:   serial
> Err:   serial
> Net:   egiga0

	and on OpenRD Client —
> U-Boot 2016.11+dfsg1-4~20170308~1 (Mar 09 2017 - 01:27:49 +0000)
> OpenRD-Client
> 
> SoC:   Kirkwood 88F6281_A0
> DRAM:  512 MiB
> WARNING: Caches not enabled
> NAND:  512 MiB
> MMC:   MVEBU_MMC: 0
> In:    serial
> Out:   serial
> Err:   serial
> Net:   egiga0, egiga1
> 


I use the SheevaPlug as a backup DHCP/DNS server for my home network.  The Client is reserved for experimenting.

I don’t currently use NFS on either, but I have in the past.

I’m not sure what you mean by “What kind of compressed ramdisk do you use?”.  As a stab in the dark —

> rbthomas@client:~$ file /boot/initrd.img-4.9.0-6-marvell
> /boot/initrd.img-4.9.0-6-marvell: gzip compressed data, last modified: Sun Mar  4 14:29:43 2018, from Unix

and

> root@sheeva:~# file /boot/initrd.img-4.9.0-6-marvell
> /boot/initrd.img-4.9.0-6-marvell: gzip compressed data, last modified: Sat Mar 10 10:12:39 2018, from Unix

In other words, nothing fancy!

Does that help?
Rick

Back to linux.debian.ports.arm | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Re: armel/marvell kernel size Ben Hutchings <ben@decadent.org.uk> - 2018-03-24 03:00 +0100
  Re: armel/marvell kernel size Rogério Brito <rbrito@gmail.com> - 2018-03-27 07:50 +0200
    Re: armel/marvell kernel size Stefan Monnier <monnier@iro.umontreal.ca> - 2018-03-27 14:40 +0200
      Re: armel/marvell kernel size Rogério Brito <rbrito@ime.usp.br> - 2018-03-27 22:30 +0200
        Re: armel/marvell kernel size Rick Thomas <rbthomas@pobox.com> - 2018-03-27 22:50 +0200
          Re: armel/marvell kernel size Rogério Brito <rbrito@ime.usp.br> - 2018-03-27 23:30 +0200
            Re: armel/marvell kernel size Rick Thomas <rbthomas@pobox.com> - 2018-03-28 11:30 +0200
              Re: armel/marvell kernel size Federico Pietro Briata <federico@briata.org> - 2018-03-28 14:30 +0200
                Re: armel/marvell kernel size Roger Shimizu <rogershimizu@gmail.com> - 2018-04-01 15:30 +0200
                Re: armel/marvell kernel size Rogério Brito <rbrito@ime.usp.br> - 2018-04-03 08:00 +0200
                Re: armel/marvell kernel size Roger Shimizu <rogershimizu@gmail.com> - 2018-04-07 16:20 +0200
                Re: armel/marvell kernel size Roger Shimizu <rogershimizu@gmail.com> - 2018-04-07 17:00 +0200
                Re: armel/marvell kernel size Roger Shimizu <rogershimizu@gmail.com> - 2018-04-13 02:10 +0200
                Re: armel/marvell kernel size Roger Shimizu <rogershimizu@gmail.com> - 2018-04-15 18:30 +0200
              Re: armel/marvell kernel size Rick Thomas <rbthomas@pobox.com> - 2018-04-02 01:50 +0200
        Re: armel/marvell kernel size Stefan Monnier <monnier@iro.umontreal.ca> - 2018-03-27 23:30 +0200
    Re: armel/marvell kernel size Ben Hutchings <ben@decadent.org.uk> - 2018-03-27 21:10 +0200
      Re: armel not to be released anymore? (was: armel/marvell kernel  size) Ben Hutchings <ben@decadent.org.uk> - 2018-03-27 21:30 +0200
      armel not to be released anymore? (was: armel/marvell kernel size) "W. Martin Borgert" <debacle@debian.org> - 2018-03-27 21:40 +0200
        Re: armel not to be released anymore? (was: armel/marvell kernel size) Paul Wise <pabs@debian.org> - 2018-03-28 06:40 +0200
      Re: armel/marvell kernel size Rogério Brito <rbrito@ime.usp.br> - 2018-03-27 22:50 +0200

csiph-web