On Thu, Aug 01, 2013 at 09:59:47AM -0600, Stephen John Smoogen wrote:
On 1 August 2013 09:53, Peter Robinson pbrobinson@gmail.com wrote:
On Thu, Aug 1, 2013 at 4:48 PM, Stephen John Smoogen smooge@gmail.com wrote:
On 1 August 2013 08:42, Richard W.M. Jones rjones@redhat.com wrote:
I'm now doing quite a lot of compilation on my Chromebook and my Trim Slice. It's OK, provided that two processes don't try to hit the disk at the same time, at which point everything grinds to a halt.
I know that several ARMS talk to disks via the USB chain versus a dedicated SATA like connection. This causes all kinds of issues when 2 things talk down the bus to the disk drive (just like if it is a spinning disk). The same with network and other peripheals. It will depend on how the hardware sees it and talks to it to know if it will work well or not. [My kingdom for an ARM PCI bus :)]
Send me your kingdom... there's now a number of ARM devices with PCI-e buses, or SATA/NICs plugged directly into the SoC so not hanging off crappy USB/SPI/GPIO/i2c buses :-D
But are the devices Richard has those?
The Trim Slice *has* a PCI bus (apparently unusual for ARM). However mine doesn't have SATA because it's the cheaper model, and I'm not clear how the micro SD and SD card ports are routed.
Rich.