Hi John,
Should we update our existing Android config fragment to what google recommends ? Atleast the base config as per google's documentation: http://source.android.com/devices/tech/kernel.html
I see that one of the Landing team kernel which is derived from linux-linaro builds with our android config fragment but fails to compile with the one mentioned in above link.
Regards, Vishal
On 08/21/2013 09:56 PM, Vishal Bhoj wrote:
Hi John,
Should we update our existing Android config fragment to what google recommends ? Atleast the base config as per google's documentation: http://source.android.com/devices/tech/kernel.html
I suspect its probably a good idea.
I see that one of the Landing team kernel which is derived from linux-linaro builds with our android config fragment but fails to compile with the one mentioned in above link.
Thanks for the heads up. I think I've reproduced it: drivers/usb/gadget/android.c: In function ‘rndis_function_bind_config’: drivers/usb/gadget/android.c:599:2: error: too few arguments to function ‘gether_setup_name’ In file included from drivers/usb/gadget/android.c:41:0: drivers/usb/gadget/u_ether.c:758:17: note: declared here
right?
I noticed right before I went on vacation that there seems to also be boot issues with the Android Gadget Driver when its enabled (slightly different config, as that one compiled), but didn't have a chance to chase it down. So it seems like that driver didn't get fwd ported properly.
I'll take a closer look at it tomorrow.
thanks again! -john
On 22 August 2013 10:56, John Stultz john.stultz@linaro.org wrote:
On 08/21/2013 09:56 PM, Vishal Bhoj wrote:
Hi John,
Should we update our existing Android config fragment to what google recommends ? Atleast the base config as per google's documentation: http://source.android.com/devices/tech/kernel.html
I suspect its probably a good idea.
I see that one of the Landing team kernel which is derived from linux-linaro builds with our android config fragment but fails to compile with the one mentioned in above link.
Thanks for the heads up. I think I've reproduced it: drivers/usb/gadget/android.c: In function ‘rndis_function_bind_config’: drivers/usb/gadget/android.c:599:2: error: too few arguments to function ‘gether_setup_name’ In file included from drivers/usb/gadget/android.c:41:0: drivers/usb/gadget/u_ether.c:758:17: note: declared here
right?
Yes this was one of the issue. I saw 2 more errors: wrt XT module, there was an error was in xt_socket.c: /home/vishal.bhoj/android/xyz/kernel/linaro/xyz/net/netfilter/xt_socket.c:180:49: error: 'protocol' undeclared (first use in this function) sk = nf_tproxy_get_sock_v4(dev_net(skb->dev), protocol,
another wrt sync driver in MALI ... (may be issue is with the mali driver itself and not forward porting of sync driver): fatal error: linux/sync.h: No such file or directory
I noticed right before I went on vacation that there seems to also be boot issues with the Android Gadget Driver when its enabled (slightly different config, as that one compiled), but didn't have a chance to chase it down. So it seems like that driver didn't get fwd ported properly.
I'll take a closer look at it tomorrow.
thanks again! -john
On 08/21/2013 10:34 PM, Vishal Bhoj wrote:
On 22 August 2013 10:56, John Stultz john.stultz@linaro.org wrote:
On 08/21/2013 09:56 PM, Vishal Bhoj wrote:
Hi John,
Should we update our existing Android config fragment to what google recommends ? Atleast the base config as per google's documentation: http://source.android.com/devices/tech/kernel.html
I suspect its probably a good idea.
I see that one of the Landing team kernel which is derived from linux-linaro builds with our android config fragment but fails to compile with the one mentioned in above link.
Thanks for the heads up. I think I've reproduced it: drivers/usb/gadget/android.c: In function ‘rndis_function_bind_config’: drivers/usb/gadget/android.c:599:2: error: too few arguments to function ‘gether_setup_name’ In file included from drivers/usb/gadget/android.c:41:0: drivers/usb/gadget/u_ether.c:758:17: note: declared here
right?
Yes this was one of the issue. I saw 2 more errors: wrt XT module, there was an error was in xt_socket.c: /home/vishal.bhoj/android/xyz/kernel/linaro/xyz/net/netfilter/xt_socket.c:180:49: error: 'protocol' undeclared (first use in this function) sk = nf_tproxy_get_sock_v4(dev_net(skb->dev), protocol,
Ok, will look at this one as well.
another wrt sync driver in MALI ... (may be issue is with the mali driver itself and not forward porting of sync driver): fatal error: linux/sync.h: No such file or directory
Yea, the Mali folks just need to update their driver, as the sync.h header is now in drivers/staging/android/ upstream as of 3.10.
thanks -john
On 08/21/2013 10:34 PM, Vishal Bhoj wrote:
On 22 August 2013 10:56, John Stultz john.stultz@linaro.org wrote:
On 08/21/2013 09:56 PM, Vishal Bhoj wrote:
Hi John,
Should we update our existing Android config fragment to what google recommends ? Atleast the base config as per google's documentation: http://source.android.com/devices/tech/kernel.html
I suspect its probably a good idea.
I see that one of the Landing team kernel which is derived from linux-linaro builds with our android config fragment but fails to compile with the one mentioned in above link.
Thanks for the heads up. I think I've reproduced it: drivers/usb/gadget/android.c: In function ‘rndis_function_bind_config’: drivers/usb/gadget/android.c:599:2: error: too few arguments to function ‘gether_setup_name’ In file included from drivers/usb/gadget/android.c:41:0: drivers/usb/gadget/u_ether.c:758:17: note: declared here
right?
Yes this was one of the issue.
Ok, I've just committed a fix to that here: https://git.linaro.org/gitweb?p=people/jstultz/android.git%3Ba=commitdiff%3B...
I saw 2 more errors: wrt XT module, there was an error was in xt_socket.c: /home/vishal.bhoj/android/xyz/kernel/linaro/xyz/net/netfilter/xt_socket.c:180:49: error: 'protocol' undeclared (first use in this function) sk = nf_tproxy_get_sock_v4(dev_net(skb->dev), protocol,
This one I wasn't able to trigger. Could you send me the .config?
thanks -john
On 23 August 2013 00:09, John Stultz john.stultz@linaro.org wrote:
On 08/21/2013 10:34 PM, Vishal Bhoj wrote:
On 22 August 2013 10:56, John Stultz john.stultz@linaro.org wrote:
On 08/21/2013 09:56 PM, Vishal Bhoj wrote:
Hi John,
Should we update our existing Android config fragment to what google recommends ? Atleast the base config as per google's documentation: http://source.android.com/devices/tech/kernel.html
I suspect its probably a good idea.
I see that one of the Landing team kernel which is derived from linux-linaro builds with our android config fragment but fails to
compile
with the one mentioned in above link.
Thanks for the heads up. I think I've reproduced it: drivers/usb/gadget/android.c: In function ‘rndis_function_bind_config’: drivers/usb/gadget/android.c:599:2: error: too few arguments to function ‘gether_setup_name’ In file included from drivers/usb/gadget/android.c:41:0: drivers/usb/gadget/u_ether.c:758:17: note: declared here
right?
Yes this was one of the issue.
Ok, I've just committed a fix to that here:
https://git.linaro.org/gitweb?p=people/jstultz/android.git%3Ba=commitdiff%3B...
I saw 2 more errors: wrt XT module, there was an error was in xt_socket.c:
/home/vishal.bhoj/android/xyz/kernel/linaro/xyz/net/netfilter/xt_socket.c:180:49:
error: 'protocol' undeclared (first use in this function) sk = nf_tproxy_get_sock_v4(dev_net(skb->dev), protocol,
This one I wasn't able to trigger. Could you send me the .config?
I couldn't reproduce this on linux-linaro today. The issue was shown up on LT kernel which was based on older linux-linaro tree.
thanks -john
linaro-android@lists.linaro.org
-
John Stultz -
Vishal Bhoj