* mike's going to get 5 EOMA68-A20 rev 2.6 samples done quickly, hopefully before the big holiday beginning october. * we could *potentially* get the 800 EOMA68-A20 computer cards done within a couple of months (have to arrange testing) * microdesktop submitted for cost evaluation * PCB1 rework of laptop is underway, using connectors (SMT R/A) from morecrafts.com.tw * marco from frida is checking MOQ 1k on the 3.5in LCD+CTP * tracking down the S5P6818 octa-core supplier, investigating if Reference Design is available
l.
--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On 14 Sep 2016, at 03:56, Luke Kenneth Casson Leighton lkcl@lkcl.net wrote:
- tracking down the S5P6818 octa-core supplier, investigating if
Reference Design is available
Is this for a new EOMA68 board?
I stuck S5P6818 in the search at http://elinux.org/ (nope) and http://rhombus-tech.net/ (yep). Looks like a 64 bit chip with no 64 bit support.
http://rhombus-tech.net/samsung/s5p6818/
http://lists.phcomp.co.uk/pipermail/arm-netbook/2016-August/011771.html
https://community.arm.com/community/arm-partner-directory/partner-graperain/...
--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Thu, Sep 15, 2016 at 2:55 PM, Nick Hardiman nick@internetmachines.co.uk wrote:
On 14 Sep 2016, at 03:56, Luke Kenneth Casson Leighton lkcl@lkcl.net wrote:
- tracking down the S5P6818 octa-core supplier, investigating if
Reference Design is available
Is this for a new EOMA68 board?
yes.
I stuck S5P6818 in the search at http://elinux.org/ (nope) and http://rhombus-tech.net/ (yep). Looks like a 64 bit chip with no 64 bit support.
correct. given that it can only address 2GB of RAM that really doesn't matter.
l.
On 09/15/2016 04:01 PM, Luke Kenneth Casson Leighton wrote:
I stuck S5P6818 in the search at http://elinux.org/ (nope) and http://rhombus-tech.net/ (yep). Looks like a 64 bit chip with no 64 bit support.
correct. given that it can only address 2GB of RAM that really doesn't matter.
l.
What about virtual addressing / swap space? Then you may want more than 2GB address space.
--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Thu, Sep 15, 2016 at 3:38 PM, pelzflorian (Florian Pelz) pelzflorian@pelzflorian.de wrote:
On 09/15/2016 04:01 PM, Luke Kenneth Casson Leighton wrote:
I stuck S5P6818 in the search at http://elinux.org/ (nope) and http://rhombus-tech.net/ (yep). Looks like a 64 bit chip with no 64 bit support.
correct. given that it can only address 2GB of RAM that really doesn't matter.
l.
What about virtual addressing / swap space? Then you may want more than 2GB address space.
you do _not_ want to be using swap space on raw nand or even eMMC. or USB-based external storage media. in fact, you don't want to be using swap space at all... with the exception possibly of compswap (the much better version of zram, which linus torvalds refused to allow the full set of patches for, into the linux kernel).
l.
you do _not_ want to be using swap space on raw nand or even eMMC. or USB-based external storage media. in fact, you don't want to be using swap space at all... with the exception possibly of compswap (the much better version of zram, which linus torvalds refused to allow the full set of patches for, into the linux kernel).
NBD-based (network block device) swap is also a viable solution with Gb eth, and is better than getting OOM-killed...
--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Fri, Sep 16, 2016 at 9:51 AM, Vincent Legoll vincent.legoll@gmail.com wrote:
you do _not_ want to be using swap space on raw nand or even eMMC. or USB-based external storage media. in fact, you don't want to be using swap space at all... with the exception possibly of compswap (the much better version of zram, which linus torvalds refused to allow the full set of patches for, into the linux kernel).
NBD-based (network block device) swap is also a viable solution with Gb eth, and is better than getting OOM-killed...
that would work. egads i haven't used network-based swap since imperial college back in 1988-1991, on the sunos 4.1.3 workstations we had in the lab :)
l.
2016-09-16 0:59 GMT+02:00 Luke Kenneth Casson Leighton lkcl@lkcl.net:
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Thu, Sep 15, 2016 at 3:38 PM, pelzflorian (Florian Pelz) pelzflorian@pelzflorian.de wrote:
On 09/15/2016 04:01 PM, Luke Kenneth Casson Leighton wrote:
I stuck S5P6818 in the search at http://elinux.org/ (nope) and
http://rhombus-tech.net/ (yep). Looks like a 64 bit chip with no 64 bit support.
correct. given that it can only address 2GB of RAM that really
doesn't matter.
l.
What about virtual addressing / swap space? Then you may want more than 2GB address space.
you do _not_ want to be using swap space on raw nand or even eMMC.
Well, Google has released statistical data on their SSD usage and it seems that there is no correlation between number of writes and failure. It's more dependent on 'age'.
But SSD are 'less' reliable than HDD because of bad cell and bad writes. So error correction becomes more important.
http://www.zdnet.com/article/ssd-reliability-in-the-real-world-googles-exper...
Raw NAND access means you have to do the ECC. With and SSD that taken care of by.....firmware.....
Now the 3.4 (Lichee)kernel from AW has, AFAICT, shady NAND support. And mainline is growing, proper, NAND support.
Most bootloaders depend on fixed addresses region without ECC. So if the boot region gets "bad" you're device is toast. A20 still boots from SD though.
Still on low speed machines try to avoid swap to any medium. All will get very slow; I/O contention. Memory usually has it's separate/private bus/tracs/connection. The rest, Network, Sata, USB, GPIO, SPI etc. shares a common bus.
So keep away from high profile desktops/compositors like Gnome and KDE on low memory systems.
IOS and Andriod have very strict policies on apps to get exit the system if not used to keep memory free for the active application.
or USB-based external storage media. in fact, you don't want to be using swap space at all... with the exception possibly of compswap (the much better version of zram, which linus torvalds refused to allow the full set of patches for, into the linux kernel).
l.
arm-netbook mailing list arm-netbook@lists.phcomp.co.uk http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook Send large attachments to arm-netbook@files.phcomp.co.uk
On 09/19/2016 12:38 PM, mike.valk@gmail.com wrote:
Still on low speed machines try to avoid swap to any medium. All will get very slow; I/O contention. Memory usually has it's separate/private bus/tracs/connection. The rest, Network, Sata, USB, GPIO, SPI etc. shares a common bus.
Swap should be avoided as Lkcl said, but a crash may be worse than waiting for swap. Web, LaTeX, GNOME Builder usage can be expensive. Well, I’ll see.
So keep away from high profile desktops/compositors like Gnome and KDE on low memory systems.
GNOME isn’t that bad. Of course LXDE uses less memory, but not by much. The choice of Web browser seems much more important.
arm-netbook@lists.phcomp.co.uk
-
Luke Kenneth Casson Leighton -
mike.valk＠gmail.com -
Nick Hardiman -
pelzflorian (Florian Pelz) -
Vincent Legoll