Re: [ARMedslack] qemu memory limitation

2011-12-13 Thread Jim Hawkins
On Tue, 13 Dec 2011, John O'Donnell wrote:

 On 12/13/2011 04:56 AM, Ottavio wrote:
  I see these two options in the qemu manual:
  
  -mem-path path
   Allocate guest RAM from a temporarily created file in path.
  -mem-prealloc
   Preallocate memory when using -mem-path.
  
  I have never tried.
 
 hmmm nice find!  I suspect these only affect main ram usage within the guest
 as such the 256M qemu limitation would still apply, but I'll give it a try!

AIUI, the RAM limit in qemu is platform dependant. The versatilepb 
platform is limited to 256MB, but according to the following 
page, the vexpress-a9 platform supports up to 1GB RAM:

https://wiki.linaro.org/PeterMaydell/QemuVersatileExpress

Although it will probably will take a bit more effort to get working than 
just changing the machine type on the qemu command line.

Cheers,

Jim
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack


Re: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus

2011-01-06 Thread Jim Hawkins
On Thu, 6 Jan 2011, Stuart Winter wrote:

 I just tried rebooting one of the SPs and the drive times out and u-boot 
 reboots, then it works.

The spin-up timeout in u-boot is set to 5 seconds, which seems a bit low - 
the specs for my drive say the typical drive ready time is 13s. I've 
increased the timeout to 30s and now it seems to work reliably.

 The boot command in the docs has reset as the last command, but you
 never read my docs do you ;-)

Nope :)

Cheers,

Jim
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack


Re: [ARMedslack] Thinking about changing Slackware ARM to armv5t baseline

2011-01-04 Thread Jim Hawkins
On Tue, 4 Jan 2011, John O'Donnell wrote:

 On 01/04/2011 07:03 AM, Stuart Winter wrote:
  
It looks like Zipit uses an Xscale which is armv5, so it would work, as
far as I can tell.
   
   Zipit uses ARM720T (ARMv4T), the same as my GP2X primary processor (GP2X
   has a
   940T co-processor)
  
  http://en.wikipedia.org/wiki/Zipit_Wireless_Messenger_%28Z2%29
  
  So this must be a newer version?
  
  Even this version with 32MB RAM isn't suitable.  I don't even think
  Slackware on x86 can really run reliably in 32MB of RAM.
  
  So I'm not exactly concerned about this device :)
 
 Dunno.  I went off the entry in the
 http://en.wikipedia.org/wiki/ARM_architecture
 Which says ARM720T.  must be wrong.

That page states that the Zipit Wireless Messenger has an ARM720T and 
the Zipit Z2 has an XScale.

Cheers,

Jim
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack


Re: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus

2010-11-28 Thread Jim Hawkins
On Tue, 23 Nov 2010, Stuart Winter wrote:

 Jawkins - do you have the u-boot binary you built from the Marvell
 sources? does it have ext2  eSATA support?

I never actually got round to building it in the end, but looking at the 
latest u-boot git repo, it looks like the GuruPlug should have ext2 and 
SATA enabled by default.

Cheers,

Jim
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack


Re: [ARMedslack] Trying armedslack-current

2010-10-08 Thread Jim Hawkins
On Fri, 8 Oct 2010, John O'Donnell wrote:

 On 10/08/2010 03:19 AM, Stuart Winter wrote:
  I know Jim on this list has received his guruplug a week ago, and they've
  added a whopping fan to it which makes itself known in the room.
  Perhaps you shoud send yours back for a swap.
 
 Oh I have been following the forums and been in contact with Global Scale and
 know all about that little 20mm x 20mm x 6mm fan they added that is apparently
 quite noisy.  I guess I should have said BAD BAD GLOBAL SCALE!

It sounds like a hair dryer.

 From what I follow, there apparently are NO sources available to this uaputl
 program and I am VERY dubious of this.  I have also read that there are NO
 access controls and that you DONT have to be root to change the SSID or any
 other access point configurations with this utility and the way it talks to
 the kernel driver.  I dont like it but it is what I have to use.

I've not looked at it, but source is available from the bottom of this 
page:

http://www.plugcomputer.org/plugwiki/index.php/Setting_GuruPlug_to_be_a_WiFi_Access_Point

Cheers,

Jim
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack