-------- Original Message --------
Subject: Re: [fedora-arm] SunXI kernel 3.16 - Re: Device support for
Date: Thu, 14 Aug 2014 01:19:54 +1000
From: Adrian <vk4tux(a)bigpond.com>
To: Robert Moskowitz <rgm(a)htt-consult.com>
On 14/08/14 01:04, Robert Moskowitz wrote:
> On 08/13/2014 10:47 AM, Robert Nelson wrote:
>>> armv7, min 1Gb memory, Sata support, under $100? Please tell me
>>> what other
>>> devices I should consider? I have gleaned the few lists that I have
>>> followed for discussion on devices. I have read the list of supported
>>> devices for F21 and in most cases went to the device site to see
>>> what it
>>> offered. But I know I can miss things.
>> wandboard quad's go for around $100 on ebay. or just spend the extra
>> $29 for a new one..
> Thanks. I did look at these, and I like the people at Freescale; I
> work with them in the IEEE. But you need the Wandboard quad to get
> Sata which is the $129.
No both devices I mentioned have Sata 2T support and I use Sata drives
with mine also.
Adrian ... vk4tux
The commit d1c912c1001f was made into tegra_defconfig and later
forwared to multi_v7_deconfig as 0c86f089e66a93
Quoting original commit into the kernel tree:
- Allocate 64 MiB for CMA by default; the default 16MiB is not enough
for the majority of use-cases. This can still be overridden by the cma
If this patch is not applied, KMS drivers using CMA would
rapidly exhaust the allocated memory. This was seen on tegra_drm
(from tagr libdrm/opentegra with exa support on freedesktop.org)
kernel: host1x drm: failed to allocate buffer with size 2457600
On the other side, CMA allocated memory can easily be freed
"Freeing memory is much simpler process..."
Whereas they can only be allocated at boot time
"CMA is introduced to provide physically contiguous pages at runtime.
For this purpose, it reserves memory at boot time."
This patch is about to have a convenient generic default
and to match upstream kernel default value.
Everything can be setup back into fedora tools such as arm-boot-config
At some point, tegra revisions that can support IOMMU will not
rely on CMA. This is not the case for tegra20
Tested on Toshiba AC100 (with 512M RAM with cma=128M zram=1x128M)
with opentegra DDX driver
config-arm-generic | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/config-arm-generic b/config-arm-generic
index 0c5242c..158ea5c 100644
@@ -162,7 +162,7 @@ CONFIG_THERMAL_GOV_USER_SPACE=y
# CONFIG_CMA_DEBUG is not set
# CONFIG_CMA_SIZE_SEL_PERCENTAGE is not set
# CONFIG_CMA_SIZE_SEL_MIN is not set