Forwarding to the current list.
Here's my response:
Hmm...
I'm not crazy about it. I don't like the look of the box around the
Linaro logo. I'd rather it be a solid color or the graduate should be
changed so that it goes from the center out. As it is. its slightly
distracting.
---------- Forwarded message ----------
From: Joey STANFORD <joey(a)linaro.org>
Date: 8 March 2012 10:22
Subject: New artwork
To: linaro-android <linaro-android(a)linaro.org>
Zach,
Some updated artwork for you and the team to play with.
Joey
--
Joey STANFORD
Engineering Program Manager
Office: +1-303-800-6609
http://www.linaro.org/
Open source software for ARM SoCs
--
Zach Pfeffer
Android Platform Team Lead, Linaro Platform Teams
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linarohttp://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
So our current naming scheme is awful.
staging-
landing-
tracking-
ick ick ick
We'd like to make this better, here's the idea:
old
new
staging-vexpress-a9
ics-armlt-stable-gcc46-vexpress-a9
tracking-panda
ics-tilt-tracking-gcc46-panda
aosp-panda
ics-aosp-stable-gcc44-panda
staging-imx53
ics-freescalelt-stable-gcc46-imx53
panda-4.4
ics-tilt-upstream-gcc46-panda
landing-snowball
ics-igloo-stable-gcc46-panda
landing-panda
ics-omapzoom-stable-gcc46-panda, keep
staging-panda
ics-tilt-stable-gcc46-panda
staging-origen
ics-samsunglt-stable-gcc46-origen
panda
ics-kwg-upstream-gcc46-panda
panda-4.4
ics-aosp-stable-gcc44-panda
Its basically,
<type of Android>-<kernel source>-<kernel type>-<toolchain version>-<target>
Hopefully this will allow people to figure out what's what.
Comments, questions, concerns?
--
Zach Pfeffer
Android Platform Team Lead, Linaro Platform Teams
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linarohttp://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
On 1 March 2012 00:40, Subodh Nijsure <snijsure(a)grid-net.com> wrote:
> Hello,
>
> (Pardon if this is out-of-scope for linaro-dev mailing list )
>
> Is there anybody trying to get Linaro to run on "cheap" AuraSlate
> (http://www.auraslate.com/) tablet? If you are would be nice to
> collaborate...
I like their website: Mischief encouraged. Hackers welcome.
They should post the hardware schematic on the site or at least some
indication what the SoC is. If its one of our member's SoCs then it
may be interesting.
> This is the only affordable ARM tablet that I have found with bootrom so I
> am trying to figure out how one gets started running Linaro on brand new
> hardware... Any specific page I should look at on https://wiki.linaro.org?
>
> Regards,
> -Subodh Nijsure
>
> (NOT affiliated with AuraSlate in any way)
>
>
> _______________________________________________
> linaro-dev mailing list
> linaro-dev(a)lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-dev
>
--
Zach Pfeffer
Android Platform Team Lead, Linaro Platform Teams
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linarohttp://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
From: Benjamin Gaignard <benjamin.gaignard(a)linaro.org>
CMA heap needs to know misc device to be able to do the link between
ION heap and CMA area reserved in board configuration file.
Signed-off-by: Benjamin Gaignard <benjamin.gaignard(a)linaro.org>
---
drivers/gpu/ion/ion.c | 20 --------------------
drivers/gpu/ion/ion_priv.h | 22 ++++++++++++++++++++++
2 files changed, 22 insertions(+), 20 deletions(-)
diff --git a/drivers/gpu/ion/ion.c b/drivers/gpu/ion/ion.c
index 37b23af..dbfdd7e 100644
--- a/drivers/gpu/ion/ion.c
+++ b/drivers/gpu/ion/ion.c
@@ -34,26 +34,6 @@
#define DEBUG
/**
- * struct ion_device - the metadata of the ion device node
- * @dev: the actual misc device
- * @buffers: an rb tree of all the existing buffers
- * @lock: lock protecting the buffers & heaps trees
- * @heaps: list of all the heaps in the system
- * @user_clients: list of all the clients created from userspace
- */
-struct ion_device {
- struct miscdevice dev;
- struct rb_root buffers;
- struct mutex lock;
- struct rb_root heaps;
- long (*custom_ioctl) (struct ion_client *client, unsigned int cmd,
- unsigned long arg);
- struct rb_root user_clients;
- struct rb_root kernel_clients;
- struct dentry *debug_root;
-};
-
-/**
* struct ion_client - a process/hw block local address space
* @ref: for reference counting the client
* @node: node in the tree of all clients
diff --git a/drivers/gpu/ion/ion_priv.h b/drivers/gpu/ion/ion_priv.h
index 3323954..82e44ea 100644
--- a/drivers/gpu/ion/ion_priv.h
+++ b/drivers/gpu/ion/ion_priv.h
@@ -22,6 +22,8 @@
#include <linux/mutex.h>
#include <linux/rbtree.h>
#include <linux/ion.h>
+#include <linux/miscdevice.h>
+#include <linux/rbtree.h>
struct ion_mapping;
@@ -38,6 +40,26 @@ struct ion_kernel_mapping {
struct ion_buffer *ion_handle_buffer(struct ion_handle *handle);
/**
+ * struct ion_device - the metadata of the ion device node
+ * @dev: the actual misc device
+ * @buffers: an rb tree of all the existing buffers
+ * @lock: lock protecting the buffers & heaps trees
+ * @heaps: list of all the heaps in the system
+ * @user_clients: list of all the clients created from userspace
+ */
+struct ion_device {
+ struct miscdevice dev;
+ struct rb_root buffers;
+ struct mutex lock;
+ struct rb_root heaps;
+ long (*custom_ioctl) (struct ion_client *client, unsigned int cmd,
+ unsigned long arg);
+ struct rb_root user_clients;
+ struct rb_root kernel_clients;
+ struct dentry *debug_root;
+};
+
+/**
* struct ion_buffer - metadata for a particular buffer
* @ref: refernce count
* @node: node in the ion_device buffers tree
--
1.7.0.4