[linaro-android][PATCH] system/core: Make adbd listen on network and usb gadget concurrently
>From a8e5da5a30290b63a5ead662d5fafa4905e8befc Mon Sep 17 00:00:00 2001
From: Jeremy Chang
Date: Mon, 14 Feb 2011 11:39:39 +0800
Subject: [PATCH] Make adbd listen on network and usb gadget concurrently
Device accessed by adb through usb and network concurrently is possible.
For both interfaces listening case, there will be two threads created.
Signed-off-by: Jeremy Chang
---
adb/adb.c |7 ---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/adb/adb.c b/adb/adb.c
index d9f96df..7f1b12a 100644
--- a/adb/adb.c
+++ b/adb/adb.c
@@ -946,13 +946,14 @@ int adb_main(int is_daemon, int server_port)
if (sscanf(value, "%d", &port) == 1 && port > 0) {
// listen on TCP port specified by service.adb.tcp.port property
local_init(port);
-} else if (access("/dev/android_adb", F_OK) == 0) {
-// listen on USB
-usb_init();
} else {
// listen on default port
local_init(DEFAULT_ADB_LOCAL_TRANSPORT_PORT);
}
+
+if (access("/dev/android_adb", F_OK) == 0) {
+usb_init();
+}
init_jdwp();
#endif
--
1.7.1
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Android prelink error by linaro gcc-4.5 + binutils-2.20
2011/1/26 Meng-Hsuan Cheng : > While Android WG was working on integrating Linaro toolchain to Android > system, we encountered prelink error since there are some empty symbols in > symtab produced by toolchain linaro gcc-4.5 + binutils-2.20. [...] > So I filed a bug in https://bugs.launchpad.net/binutils-linaro/+bug/707487. [...] hi luse, Thanks for reporting. To clarify, I just make list about the combination and test results. Original: csl-gcc + csl-binutils (binutils-2.20.51) => FAIL Once the version of linaro-gcc is set to gcc-linaro-4.5-2011.01-1, binutils tests: linaro-gcc + binutils-2.19 (FSF) => OK linaro-gcc + binutils-2.20.1 (FSF) => OK linaro-gcc + binutils-2.21 (FSF) => FAIL linaro-gcc + binutils-2.20.51 (CSL) => FAIL linaro-gcc + binutils-2.20.1 (Google) => OK Source: (1) FSF: upstream (2) CSL: CodeSourcery 2010q3 (3) Google: http://android.git.kernel.org/?p=toolchain/binutils.git;a=summary Since binutils is not yet maintained by Linaro directly, Android WG would just take binutils 2.20.1 from Google. Sincerely, Jim Huang (jserv) http://0xlab.org/ ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[linaro-android][PATCH] device/linaro/u8500href: Install 0xbench native applications
>From 78b170843eadf0e72d6b0d4cb0fc5f3be5edcae8 Mon Sep 17 00:00:00 2001 From: Jeremy Chang Date: Tue, 15 Feb 2011 12:17:16 +0800 Subject: [PATCH] Install 0xbench native applications Signed-off-by: Jeremy Chang --- ZeroXBenchmark.mk | 96 + u8500href.mk |5 ++- 2 files changed, 100 insertions(+), 1 deletions(-) create mode 100644 ZeroXBenchmark.mk diff --git a/ZeroXBenchmark.mk b/ZeroXBenchmark.mk new file mode 100644 index 000..e78047d --- /dev/null +++ b/ZeroXBenchmark.mk @@ -0,0 +1,96 @@ +UNIXBENCH_BENCH_APPS := \ +bench_ubench_hanoi \ +bench_ubench_syscall\ +bench_ubench_context1 \ +bench_ubench_pipe \ +bench_ubench_spawn \ +bench_ubench_execl \ +bench_ubench_looper \ +bench_ubench_fstime \ +bench_ubench_arithoh\ +bench_ubench_register \ +bench_ubench_short \ +bench_ubench_int\ +bench_ubench_long \ +bench_ubench_float \ +bench_ubench_double \ +bench_ubench_dhry2 \ +bench_ubench_dhry2reg \ +bench_ubench_whetstone-double + +LIBMICRO_BENCH_APPS := \ +bench_getpid\ +bench_bind \ +bench_cascade_mutex \ +bench_cascade_fcntl \ +bench_cascade_flock \ +bench_chdir \ +bench_close \ +bench_close_tcp \ +bench_connection\ +bench_dup \ +bench_exec \ +bench_exit \ +bench_exp \ +bench_fcntl \ +bench_fcntl_ndelay \ +bench_file_lock \ +bench_fork \ +bench_getenv\ +bench_gettimeofday \ +bench_getpeername \ +bench_getrusage \ +bench_getsockname \ +bench_isatty\ +bench_listen\ +bench_localtime_r \ +bench_log \ +bench_longjmp \ +bench_lrand48 \ +bench_lseek \ +bench_malloc\ +bench_memcpy\ +bench_memmove \ +bench_memrand \ +bench_memset\ +bench_mktime\ +bench_mprotect \ +bench_mmap \ +bench_msync \ +bench_munmap\ +bench_mutex \ +bench_nop \ +bench_open \ +bench_pipe \ +bench_poll \ +bench_pread \ +bench_pthread_create\ +bench_pwrite\ +bench_read \ +bench_realpath \ +bench_recurse \ +bench_select\ +bench_setsockopt\ +bench_sigaction \ +bench_siglongjmp\ +bench_signal\ +bench_sigprocmask \ +bench_socket\ +bench_socketpair\ +bench_stat \ +bench_strcasecmp\ +bench_strchr\ +bench_strcmp\ +bench_strcpy\ +bench_strftime \ +bench_strlen\ +bench_strtol\ +bench_system\ +bench_time \ +bench_times \ +bench_write \ +bench_writev + +ZEROXBENCHMARK_NATIVE_APPS := \ +$(UNIXBENCH_BENCH_APPS) \ +$(LIBMICRO_BENCH_APPS) diff --git a/u8500href.mk b/u8500href.mk index 3efd467..37a9eab 100644 --- a/u8500href.mk +++ b/u8500href.mk @@ -1,5 +1,7 @@ # The beagleboard product that is specialized for beagleboard. +include $(LOCAL_PATH)/ZeroXBenchmark.mk + PRODUCT_PACKAGES := \ ZeroXBenchmark \ libmicro \ @@ -22,7 +24,8 @@ PRODUCT_PACKAGES := \ Sync \ Updater \ CalendarProvider \ -SyncProvider +SyncProvider \ +$(ZEROXBENCHMARK_NATIVE_APPS) $(call inherit-product, $(SRC_TARGET_DIR)/product/core.mk) -- 1.7.1 ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[linaro-android][PATCH] device/linaro/pandaboard: Install 0xbench native applications
>From 8d63ba7ae90b3629dd60eeab12fdc28a8dcc58e7 Mon Sep 17 00:00:00 2001 From: Jeremy Chang Date: Tue, 15 Feb 2011 12:10:02 +0800 Subject: [PATCH] Install 0xbench native applications Signed-off-by: Jeremy Chang --- ZeroXBenchmark.mk | 96 + pandaboard.mk |5 ++- 2 files changed, 100 insertions(+), 1 deletions(-) create mode 100644 ZeroXBenchmark.mk diff --git a/ZeroXBenchmark.mk b/ZeroXBenchmark.mk new file mode 100644 index 000..e78047d --- /dev/null +++ b/ZeroXBenchmark.mk @@ -0,0 +1,96 @@ +UNIXBENCH_BENCH_APPS := \ +bench_ubench_hanoi \ +bench_ubench_syscall\ +bench_ubench_context1 \ +bench_ubench_pipe \ +bench_ubench_spawn \ +bench_ubench_execl \ +bench_ubench_looper \ +bench_ubench_fstime \ +bench_ubench_arithoh\ +bench_ubench_register \ +bench_ubench_short \ +bench_ubench_int\ +bench_ubench_long \ +bench_ubench_float \ +bench_ubench_double \ +bench_ubench_dhry2 \ +bench_ubench_dhry2reg \ +bench_ubench_whetstone-double + +LIBMICRO_BENCH_APPS := \ +bench_getpid\ +bench_bind \ +bench_cascade_mutex \ +bench_cascade_fcntl \ +bench_cascade_flock \ +bench_chdir \ +bench_close \ +bench_close_tcp \ +bench_connection\ +bench_dup \ +bench_exec \ +bench_exit \ +bench_exp \ +bench_fcntl \ +bench_fcntl_ndelay \ +bench_file_lock \ +bench_fork \ +bench_getenv\ +bench_gettimeofday \ +bench_getpeername \ +bench_getrusage \ +bench_getsockname \ +bench_isatty\ +bench_listen\ +bench_localtime_r \ +bench_log \ +bench_longjmp \ +bench_lrand48 \ +bench_lseek \ +bench_malloc\ +bench_memcpy\ +bench_memmove \ +bench_memrand \ +bench_memset\ +bench_mktime\ +bench_mprotect \ +bench_mmap \ +bench_msync \ +bench_munmap\ +bench_mutex \ +bench_nop \ +bench_open \ +bench_pipe \ +bench_poll \ +bench_pread \ +bench_pthread_create\ +bench_pwrite\ +bench_read \ +bench_realpath \ +bench_recurse \ +bench_select\ +bench_setsockopt\ +bench_sigaction \ +bench_siglongjmp\ +bench_signal\ +bench_sigprocmask \ +bench_socket\ +bench_socketpair\ +bench_stat \ +bench_strcasecmp\ +bench_strchr\ +bench_strcmp\ +bench_strcpy\ +bench_strftime \ +bench_strlen\ +bench_strtol\ +bench_system\ +bench_time \ +bench_times \ +bench_write \ +bench_writev + +ZEROXBENCHMARK_NATIVE_APPS := \ +$(UNIXBENCH_BENCH_APPS) \ +$(LIBMICRO_BENCH_APPS) diff --git a/pandaboard.mk b/pandaboard.mk index 2aca6a5..b7aab1c 100644 --- a/pandaboard.mk +++ b/pandaboard.mk @@ -1,5 +1,7 @@ # The pandaboard product that is specialized for pandaboard. +include $(LOCAL_PATH)/ZeroXBenchmark.mk + PRODUCT_PACKAGES := \ ZeroXBenchmark \ libmicro \ @@ -22,7 +24,8 @@ PRODUCT_PACKAGES := \ Sync \ Updater \ CalendarProvider \ -SyncProvider +SyncProvider \ +$(ZEROXBENCHMARK_NATIVE_APPS) $(call inherit-product, $(SRC_TARGET_DIR)/product/core.mk) -- 1.7.1 ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [linaro-android][PATCH] Enable ethernet interface during booting
Hi, Alexander: You're right. sleep's not needed. Actually "netcfg usb0 dhcp" is enough for enabling the ethernet and dhcp the ip address. Let's see how we can do this after we create the common directory for all the boards. This patch is only for enabling the ethernet during booting Android. If the wire is replugged, dhcp can not be triggered again. -Jeremy > > The sleep feels dirty. Whats the underlying root cause for this being > required? > > Also, is this something we can solve in a common fashion for all > boards with ethernet? > > Also, is netcfg smart enough to renew dhcp lease if i unplug/replug > the wire etc.? > > -- > > - Alexander > ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: /latest link now active on snapshots.linaro.org
On Mon, Feb 14, 2011, Paul Larson wrote: > Only if linaro-n-developer.tar.gz is a symlink to > linrao-n-developer-tar-DATESTAMP-BUILDID.tar.gz. It is still useful to have > some easy way to see which image we are pulling, even if it means pulling it > out of the filename. Another alternative, would be if we could drop some > buildstamp file in the image directory to pull this from. I personally don't like DATESTAMP in the filename; it makes rsync-ing harder as a start, and it only helps with local tarballs, not installed images. I think you want some build-stamp information in the tarball itself, no matter what, so you can as well "tar vtf linaro-n-dev.tar.gz|grep build-stamp" or something. The date of the build is only one of the important pieces of information which we want to see at a glance about a build, so I'd rather not clutter filenames with it. > Another thought too... if we are already going to this extent to make it > easier for people to stay up to date with the latest image, does it make > sense to go ahead and enable creation of .zsync files for the images? > Granted, these aren't nearly the size of an iso, but some of our folks with > slower connections might appreciate it. Good idea; there's also a request to consider .xz instead of .gz: https://bugs.launchpad.net/linaro-images/+bug/683849 -- Loïc Minier ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[GIT PULL] omap[34] Thumb-2 support for linux-linaro-2.6.37
This patch series enables Thumb-2 support for omap3 and omap4. It is not currently well tested, and is known to be faulty for certain power management operations including power-off suspend when CONFIG_THUMB2_KERNEL is enabled. Note that from the patch series, this subset are temporary workarounds and not likely to be merged upstream: ARM: Add local symbols in relocate_kernel.S to work around gas bugs ARM: omap3: Work around assembler errors in sleep34xx.S ARM: Avoid discarding sections that might have SMP_ON_UP fixups Full description follows. Cheers ---Dave The following changes since commit 9e9711855260b246ba31e79bf420a350bc652ab2: ARM: ptrace: remove single-step emulation code (2011-02-12 14:06:02 -0500) are available in the git repository at: git://git.linaro.org/people/dmart/linux-2.6-arm.git for-linaro-2.6.37/dirty/arm/omap-thumb2+merged Dave Martin (10): ARM: omap4: Provide do_wfi() for Thumb-2 ARM: omap4: Convert END() to ENDPROC() for correct linkage with CONFIG_THUMB2_KERNEL ARM: omap3: Remove hand-encoded SMC instructions ARM: omap3: Thumb-2 compatibility for sram34xx.S ARM: omap3: Thumb-2 compatibility for sleep34xx.S ARM: Thumb-2: Symbol manipulation macros for function body copying ARM: Correct WFE() in asm/spinlock.h for Thumb-2 ARM: Add local symbols in relocate_kernel.S to work around gas bugs ARM: omap3: Work around assembler errors in sleep34xx.S ARM: Avoid discarding sections that might have SMP_ON_UP fixups Jean Pihet (2): omap: use fncpy to copy the PM code functions to SRAM OMAP: fix fncpy API call Ming Lei (1): arm: fix oops in sched_clock_poll arch/arm/include/asm/fncpy.h| 94 +++ arch/arm/include/asm/spinlock.h | 18 - arch/arm/kernel/relocate_kernel.S | 12 ++- arch/arm/kernel/sched_clock.c |4 +- arch/arm/kernel/vmlinux.lds.S | 18 + arch/arm/mach-omap1/pm.h|6 +- arch/arm/mach-omap1/sleep.S |3 + arch/arm/mach-omap1/sram.S |1 + arch/arm/mach-omap2/include/mach/omap4-common.h |4 + arch/arm/mach-omap2/omap-headsmp.S |2 +- arch/arm/mach-omap2/omap44xx-smc.S |8 +- arch/arm/mach-omap2/pm.h|2 +- arch/arm/mach-omap2/sleep24xx.S |2 + arch/arm/mach-omap2/sleep34xx.S | 63 +++- arch/arm/mach-omap2/sram242x.S |3 + arch/arm/mach-omap2/sram243x.S |3 + arch/arm/mach-omap2/sram34xx.S | 29 +-- arch/arm/plat-omap/include/plat/sram.h | 14 +++- arch/arm/plat-omap/sram.c | 14 ++- 19 files changed, 253 insertions(+), 47 deletions(-) create mode 100644 arch/arm/include/asm/fncpy.h ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: /latest link now active on snapshots.linaro.org
On 02/14/11 at 06:39pm, Amit Kucheria wrote: > On 11 Feb 08, Steve Langasek wrote: > > Hi Jamie, > > > > On Tue, Feb 08, 2011 at 01:10:46PM +, Jamie Bennett wrote: > > > > > There is now a much easier way to download the daily Linaro images and > > > hardware packs, the /latest link. Inside each build directory a /latest > > > link will always point to the latest successful build. The following > > > urls are currently setup: > > > > > http://snapshots.linaro.org/11.05-daily/linaro-alip/latest > > > http://snapshots.linaro.org/11.05-daily/linaro-developer/latest > > > http://snapshots.linaro.org/11.05-daily/linaro-headless/latest > > > http://snapshots.linaro.org/11.05-daily/linaro-netbook-efl/latest > > > > Thanks for making this happen! > > > > +1 to Loïc's comment that this should link directly to the latest build, not > > just the latest day. > > The currently link needs the following navigation: > > http://snapshots.linaro.org/11.05-daily/linaro-developer/latest/0/images/tar/linaro-n-developer-tar-20110214-0.tar.gz > > Perhaps it's also be possible to simply that to > > http://snapshots.linaro.org/11.05-daily/linaro-developer/latest/linaro-n-developer.tar.gz > ? > > (note change to filename) This is beyond the capabilities of the current scripts we have for syncing images from Offspring to the snapshots server. The Infrastructure team have this on their plate to investigate whether or not we can add this to Offspring itself. I'll keep you informed. > /Amit > Regards, Jamie. -- Linaro Release Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: /latest link now active on snapshots.linaro.org
On Mon, Feb 14, 2011 at 10:39 AM, Amit Kucheria wrote: > The currently link needs the following navigation: > > > http://snapshots.linaro.org/11.05-daily/linaro-developer/latest/0/images/tar/linaro-n-developer-tar-20110214-0.tar.gz > > Perhaps it's also be possible to simply that to > > > http://snapshots.linaro.org/11.05-daily/linaro-developer/latest/linaro-n-developer.tar.gz? > Only if linaro-n-developer.tar.gz is a symlink to linrao-n-developer-tar-DATESTAMP-BUILDID.tar.gz. It is still useful to have some easy way to see which image we are pulling, even if it means pulling it out of the filename. Another alternative, would be if we could drop some buildstamp file in the image directory to pull this from. Another thought too... if we are already going to this extent to make it easier for people to stay up to date with the latest image, does it make sense to go ahead and enable creation of .zsync files for the images? Granted, these aren't nearly the size of an iso, but some of our folks with slower connections might appreciate it. Thanks, Paul Larson ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: /latest link now active on snapshots.linaro.org
On 11 Feb 08, Steve Langasek wrote: > Hi Jamie, > > On Tue, Feb 08, 2011 at 01:10:46PM +, Jamie Bennett wrote: > > > There is now a much easier way to download the daily Linaro images and > > hardware packs, the /latest link. Inside each build directory a /latest > > link will always point to the latest successful build. The following > > urls are currently setup: > > > http://snapshots.linaro.org/11.05-daily/linaro-alip/latest > > http://snapshots.linaro.org/11.05-daily/linaro-developer/latest > > http://snapshots.linaro.org/11.05-daily/linaro-headless/latest > > http://snapshots.linaro.org/11.05-daily/linaro-netbook-efl/latest > > Thanks for making this happen! > > +1 to Loïc's comment that this should link directly to the latest build, not > just the latest day. The currently link needs the following navigation: http://snapshots.linaro.org/11.05-daily/linaro-developer/latest/0/images/tar/linaro-n-developer-tar-20110214-0.tar.gz Perhaps it's also be possible to simply that to http://snapshots.linaro.org/11.05-daily/linaro-developer/latest/linaro-n-developer.tar.gz ? (note change to filename) /Amit ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Please review blueprint linaro-n-validation-job-dispatcher
On Mon, Feb 14, 2011 at 5:58 AM, Mirsad Vojnikovic < mirsad.vojniko...@linaro.org> wrote: > > I have a question regarding test job json file and messages from Scheduler > to Dispatcher: is this file created by Scheduler and put in the message > queue where Dispatcher will fetch it from, or how should this work? > > That's one possibility, yes, that the scheduler could create this from user input. Another of course, is that a user could submit a job control file directly to the scheduler rather than dealing with selecting options. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [linaro-android][PATCH] Make adbd listen on network interface
On 02/14/11 at 01:31pm, Alexander Sack wrote: > On Mon, Feb 14, 2011 at 12:52 PM, Jeremy Chang wrote: > > From dbeb9e14eb4b5d70775426a370681c90928d4d84 Mon Sep 17 00:00:00 2001 > > From: Jeremy Chang > > we should get you your @linaro.org address asap. > > > Date: Mon, 14 Feb 2011 11:28:12 +0800 > > Subject: [PATCH] Make adbd listen on network interface > > please indicate against what repo this is supposed to land; so here it > would be something like: > > [PATCH] device/linaro/beagleboard: make adbd listen on network interface > > Also while its OK to do things like this for now, we should soonish > come up with a mechanism that allows us to add these things either in > one "device/linaro/common-devboard" tree or a mechanism that allows us > to track what was added to what board - so our board features don't go > out of sync. These patches should also be cc'd to patc...@linaro.org > - Alexander Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [linaro-android][PATCH] Install 0xbench native applications
Hi Jeremy. Can you add ZEROXBENCHMARK_NATIVE_APPS to PRODUCT PACKAGES for the other boards also? I know you can not verify that it works. In this case I think it is enough that you have managed to build for all the boards. The code is not run until you start 0xbench so it should not prevent any other boards from booting. I will look at breaking out common stuff for all the boards, but create a patch for each board for now. /Patrik On 14 February 2011 12:39, Jeremy Chang wrote: > From 9a8781bb34fe1ff3463a1dc48f3b33b43e2f Mon Sep 17 00:00:00 2001 > From: Jeremy Chang > Date: Sun, 13 Feb 2011 20:49:26 +0800 > Subject: [PATCH] Install 0xbench native applications > > > Signed-off-by: Jeremy Chang > --- > ZeroXBenchmark.mk | 96 > + > beagleboard.mk|6 +++- > 2 files changed, 101 insertions(+), 1 deletions(-) > create mode 100644 ZeroXBenchmark.mk > > diff --git a/ZeroXBenchmark.mk b/ZeroXBenchmark.mk > new file mode 100644 > index 000..e78047d > --- /dev/null > +++ b/ZeroXBenchmark.mk > @@ -0,0 +1,96 @@ > +UNIXBENCH_BENCH_APPS := \ > +bench_ubench_hanoi \ > +bench_ubench_syscall\ > +bench_ubench_context1 \ > +bench_ubench_pipe \ > +bench_ubench_spawn \ > +bench_ubench_execl \ > +bench_ubench_looper \ > +bench_ubench_fstime \ > +bench_ubench_arithoh\ > +bench_ubench_register \ > +bench_ubench_short \ > +bench_ubench_int\ > +bench_ubench_long \ > +bench_ubench_float \ > +bench_ubench_double \ > +bench_ubench_dhry2 \ > +bench_ubench_dhry2reg \ > +bench_ubench_whetstone-double > + > +LIBMICRO_BENCH_APPS := \ > +bench_getpid\ > +bench_bind \ > +bench_cascade_mutex \ > +bench_cascade_fcntl \ > +bench_cascade_flock \ > +bench_chdir \ > +bench_close \ > +bench_close_tcp \ > +bench_connection\ > +bench_dup \ > +bench_exec \ > +bench_exit \ > +bench_exp \ > +bench_fcntl \ > +bench_fcntl_ndelay \ > +bench_file_lock \ > +bench_fork \ > +bench_getenv\ > +bench_gettimeofday \ > +bench_getpeername \ > +bench_getrusage \ > +bench_getsockname \ > +bench_isatty\ > +bench_listen\ > +bench_localtime_r \ > +bench_log \ > +bench_longjmp \ > +bench_lrand48 \ > +bench_lseek \ > +bench_malloc\ > +bench_memcpy\ > +bench_memmove \ > +bench_memrand \ > +bench_memset\ > +bench_mktime\ > +bench_mprotect \ > +bench_mmap \ > +bench_msync \ > +bench_munmap\ > +bench_mutex \ > +bench_nop \ > +bench_open \ > +bench_pipe \ > +bench_poll \ > +bench_pread \ > +bench_pthread_create\ > +bench_pwrite\ > +bench_read \ > +bench_realpath \ > +bench_recurse \ > +bench_select\ > +bench_setsockopt\ > +bench_sigaction \ > +bench_siglongjmp\ > +bench_signal\ > +bench_sigprocmask \ > +bench_socket\ > +bench_socketpair\ > +bench_stat \ > +bench_strcasecmp\ > +bench_strchr\ > +bench_strcmp\ > +bench_strcpy\ > +bench_strftime \ > +bench_strlen\ > +bench_strtol\ > +bench_system\ > +bench_time \ > +bench_times \ > +bench_write \ > +bench_writev > + > +ZEROXBENCHMARK_NATIVE_APPS := \ > +$(UNIXBENCH_BENCH_APPS) \ > +$(LIBMICRO_BENCH_APPS) > diff --git a/beagleboard.mk b/beagleboard.mk > index c10e0fa..f810f36 100644 > --- a/beagleboard.mk > +++ b/beagleboard.mk > @@ -1,5 +1,7 @@ > # The beagleboard product that is specialized for beagleboard. > > +include $(LOCAL_PATH)/ZeroXBenchmark.mk > + > PRODUCT_PACKAGES := \ > ZeroXBenchmark \ > libmicro \ > @@ -22,7 +24,9 @@ PRODUCT_PACKAGES := \ > Sync \ > Updater \ > CalendarProvider \ > -SyncProvider >
Re: [linaro-android][PATCH] Make adbd listen on network interface
On Mon, Feb 14, 2011 at 12:52 PM, Jeremy Chang wrote: > From dbeb9e14eb4b5d70775426a370681c90928d4d84 Mon Sep 17 00:00:00 2001 > From: Jeremy Chang we should get you your @linaro.org address asap. > Date: Mon, 14 Feb 2011 11:28:12 +0800 > Subject: [PATCH] Make adbd listen on network interface please indicate against what repo this is supposed to land; so here it would be something like: [PATCH] device/linaro/beagleboard: make adbd listen on network interface Also while its OK to do things like this for now, we should soonish come up with a mechanism that allows us to add these things either in one "device/linaro/common-devboard" tree or a mechanism that allows us to track what was added to what board - so our board features don't go out of sync. -- - Alexander ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Please review blueprint linaro-n-validation-job-dispatcher
On 9 February 2011 20:12, Paul Larson wrote:
> On Mon, Jan 31, 2011 at 11:58 AM, Paul Larson wrote:
>
>> 2. One queue TOTAL. One queue may seem like a bottleneck, but I don't
think it has to be in practice. One process can monitor that queue, then
launch a process or thread to handle each new job that comes in.
>>> I think RabbitMQ message can have the ability to include the board
>>> information in it to use one queue, and also we can use different queues for
>>> different types of boards.
>>>
>> Right, but my question was, if you are already encoding that information
>> in the job stream, what is the advantage to having a queue for each board
>> type, rather than a single queue?
>>
>>
>>>
Job description:
I'd like to see some more detail here. Can you provide an example of a
job file that would illustrate how you see it working? We also need to
specify the underlying mechanisms that will handle parsing what's in the
job
file, and calling [something?] to do those tasks. What we have here feels
like it might be a bit cumbersome.
>>> I added an detailed one on the spec, like:
>>>
>>>1.
>>>
>>>[Beagle-1,
>>>
>>> http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/imx51/20110131/0/images/hwpack/hwpack_linaro-imx51_20110131-0_armel_unsupported.tar.gz,
>>>
>>>
>>> http://snapshots.linaro.org/11.05-daily/linaro-headless/20110131/0/images/tar/linaro-natty-headless-tar-20110131-0.tar.gz,
>>>900, ["abrek", "LTP", 180], ["none", "echo 100 > abc", 1], ... ]
>>>2.
>>>
>>>[IMX51-2, 20100131, 900, ["abrek", "LTP", 180], ["none", "echo 100 >
>>>abc", 1], ... ]
>>>
>>> This looks almost like JSON, which is what Zygmunt was originally pushing
>> for IIRC. If we are already going down that path, seems it would be
>> sensible to take it a step further and have defined sections. For example:
>>
>> Tests:[
>> {
>> name:"LTP",
>> testsuite:"abrek",
>> subtest:"ltp", < not thrilled about that name "subtest",
>> but can't think of something better to call it at the moment
>> timeout:180,
>> reboot_after:True
>> },
>> {
>> name:"echo test",
>> testsuite:"shell",
>> timeout:20
>> reboot_after:False
>> }
>> ]
>> What do you think? Obviously, there would be other sections for things
>> like defining the host characteristics, the image to deploy, etc.
>>
>>
>>>
>>> Other questions...
What if we have a dependency, how does that get installed on the target
image? For example, if I want to do a test that requires bootchart be
installed before the system is booted, we should be able to specify that,
and have it installed before booting.
What about installing necessary test suites? How do we tell it, in
advance, what we need to have installed, and how does it get on the image
before we boot, or before we start testing?
>>> I think validation tools, test suites and necessary files are likely to
>>> install after test image deployment.
>>>
>> Yes, clearly they have to be installed after deployment, but we may also
>> need to consider them installing BEFORE we actually boot the test image.
>>
>> Had another thought on this tonight, I didn't hear much back on the
> previous proposal, but how about something more like this as an example of
> what a job description might look like. In this scenario, there would be
> some metadata for the job itself, such as timeout values, etc. Then steps
> that would define commands with parameters. That would allow us to be more
> flexible, and add support for more commands without changing the format.
> Hopefully the mailer doesn't mangle this too badly. :)
>
> {
> "job_name": "foo",
> "target": "panda01",
> "timeout": 18000,
> "steps": [
> {
> "command": "deploy",
> "parameters":
> {
> "rootfs": "
> http://snapshots.linaro.org/11.05-daily/linaro-developer/20110208/0/images/tar/linaro-n-developer-tar-20110208-0.tar.gz
> "
> "hwpack": "
> http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/panda/20110208/0/images/hwpack/hwpack_linaro-panda_20110208-0_armel_supported.tar.gz
> "
> }
> },
> {
> "command": "boot_test_image"
> },
> {
> "command": "test_abrek",
> "parameters":
> {
> "test_name": "ltp"
> }
> },
> {
> "command": "submit_results",
> "parameters":
> {
> "server": "http://dashboard.linaro.org";,
> "stream": "panda01-ltp"
> }
> }
> ]
> }
>
I have a question regarding test job json file and messages from Scheduler
to Dispatcher: is this file created by Scheduler and put in the message
queue where Dispatcher will fetch it from, or how should this work?
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/lina
[linaro-android][PATCH] Make adbd listen on network interface
>From dbeb9e14eb4b5d70775426a370681c90928d4d84 Mon Sep 17 00:00:00 2001 From: Jeremy Chang Date: Mon, 14 Feb 2011 11:28:12 +0800 Subject: [PATCH] Make adbd listen on network interface adb through ethernet is very common that we need. Set property service.adb.tcp.port to make adbd listen. The default port is . Signed-off-by: Jeremy Chang --- init.rc |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/init.rc b/init.rc index b6a92c5..50d2dc6 100644 --- a/init.rc +++ b/init.rc @@ -181,6 +181,7 @@ on boot ifup lo hostname localhost domainname localdomain +setprop service.adb.tcp.port # set RLIMIT_NICE to allow priorities from 19 to -20 setrlimit 13 40 40 -- 1.7.1 ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[linaro-android][PATCH] Install 0xbench native applications
>From 9a8781bb34fe1ff3463a1dc48f3b33b43e2f Mon Sep 17 00:00:00 2001 From: Jeremy Chang Date: Sun, 13 Feb 2011 20:49:26 +0800 Subject: [PATCH] Install 0xbench native applications Signed-off-by: Jeremy Chang --- ZeroXBenchmark.mk | 96 + beagleboard.mk|6 +++- 2 files changed, 101 insertions(+), 1 deletions(-) create mode 100644 ZeroXBenchmark.mk diff --git a/ZeroXBenchmark.mk b/ZeroXBenchmark.mk new file mode 100644 index 000..e78047d --- /dev/null +++ b/ZeroXBenchmark.mk @@ -0,0 +1,96 @@ +UNIXBENCH_BENCH_APPS := \ +bench_ubench_hanoi \ +bench_ubench_syscall\ +bench_ubench_context1 \ +bench_ubench_pipe \ +bench_ubench_spawn \ +bench_ubench_execl \ +bench_ubench_looper \ +bench_ubench_fstime \ +bench_ubench_arithoh\ +bench_ubench_register \ +bench_ubench_short \ +bench_ubench_int\ +bench_ubench_long \ +bench_ubench_float \ +bench_ubench_double \ +bench_ubench_dhry2 \ +bench_ubench_dhry2reg \ +bench_ubench_whetstone-double + +LIBMICRO_BENCH_APPS := \ +bench_getpid\ +bench_bind \ +bench_cascade_mutex \ +bench_cascade_fcntl \ +bench_cascade_flock \ +bench_chdir \ +bench_close \ +bench_close_tcp \ +bench_connection\ +bench_dup \ +bench_exec \ +bench_exit \ +bench_exp \ +bench_fcntl \ +bench_fcntl_ndelay \ +bench_file_lock \ +bench_fork \ +bench_getenv\ +bench_gettimeofday \ +bench_getpeername \ +bench_getrusage \ +bench_getsockname \ +bench_isatty\ +bench_listen\ +bench_localtime_r \ +bench_log \ +bench_longjmp \ +bench_lrand48 \ +bench_lseek \ +bench_malloc\ +bench_memcpy\ +bench_memmove \ +bench_memrand \ +bench_memset\ +bench_mktime\ +bench_mprotect \ +bench_mmap \ +bench_msync \ +bench_munmap\ +bench_mutex \ +bench_nop \ +bench_open \ +bench_pipe \ +bench_poll \ +bench_pread \ +bench_pthread_create\ +bench_pwrite\ +bench_read \ +bench_realpath \ +bench_recurse \ +bench_select\ +bench_setsockopt\ +bench_sigaction \ +bench_siglongjmp\ +bench_signal\ +bench_sigprocmask \ +bench_socket\ +bench_socketpair\ +bench_stat \ +bench_strcasecmp\ +bench_strchr\ +bench_strcmp\ +bench_strcpy\ +bench_strftime \ +bench_strlen\ +bench_strtol\ +bench_system\ +bench_time \ +bench_times \ +bench_write \ +bench_writev + +ZEROXBENCHMARK_NATIVE_APPS := \ +$(UNIXBENCH_BENCH_APPS) \ +$(LIBMICRO_BENCH_APPS) diff --git a/beagleboard.mk b/beagleboard.mk index c10e0fa..f810f36 100644 --- a/beagleboard.mk +++ b/beagleboard.mk @@ -1,5 +1,7 @@ # The beagleboard product that is specialized for beagleboard. +include $(LOCAL_PATH)/ZeroXBenchmark.mk + PRODUCT_PACKAGES := \ ZeroXBenchmark \ libmicro \ @@ -22,7 +24,9 @@ PRODUCT_PACKAGES := \ Sync \ Updater \ CalendarProvider \ -SyncProvider +SyncProvider \ +$(ZEROXBENCHMARK_NATIVE_APPS) + $(call inherit-product, $(SRC_TARGET_DIR)/product/core.mk) -- 1.7.1 ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [linaro-android][PATCH] Enable ethernet interface during booting
On Mon, Feb 14, 2011 at 12:09 PM, Jeremy Chang wrote: > From ab02ac9fd9dfcbc096636eb5ba357361c0689b31 Mon Sep 17 00:00:00 2001 > From: Jeremy Chang > Date: Mon, 14 Feb 2011 11:19:08 +0800 > Subject: [PATCH] Enable ethernet interface during booting > > Try to enable network and get ip by dhcp in boot script > > Signed-off-by: Jeremy Chang > --- > init.omap3.sh | 4 > 1 files changed, 4 insertions(+), 0 deletions(-) > > diff --git a/init.omap3.sh b/init.omap3.sh > index 997ee03..c91705b 100755 > --- a/init.omap3.sh > +++ b/init.omap3.sh > @@ -15,3 +15,7 @@ do > ;; > esac > done < /proc/cpuinfo > + > +netcfg usb0 up > +sleep 3 > +netcfg usb0 dhcp The sleep feels dirty. Whats the underlying root cause for this being required? Also, is this something we can solve in a common fashion for all boards with ethernet? Also, is netcfg smart enough to renew dhcp lease if i unplug/replug the wire etc.? -- - Alexander ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[linaro-android][PATCH] Enable ethernet interface during booting
>From ab02ac9fd9dfcbc096636eb5ba357361c0689b31 Mon Sep 17 00:00:00 2001 From: Jeremy Chang Date: Mon, 14 Feb 2011 11:19:08 +0800 Subject: [PATCH] Enable ethernet interface during booting Try to enable network and get ip by dhcp in boot script Signed-off-by: Jeremy Chang --- init.omap3.sh |4 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/init.omap3.sh b/init.omap3.sh index 997ee03..c91705b 100755 --- a/init.omap3.sh +++ b/init.omap3.sh @@ -15,3 +15,7 @@ do ;; esac done < /proc/cpuinfo + +netcfg usb0 up +sleep 3 +netcfg usb0 dhcp -- 1.7.1 ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: cpu supported
On 02/14/2011 10:06 AM, Somebody in the thread at some point said: On Tue, Feb 8, 2011 at 6:38 PM, Christian Robottom Reis wrote: On Sun, Jan 30, 2011 at 09:50:10AM +, Andy Green wrote: Offlist so as not to make myself unpopular ^^ You might want to look at Fedora ARM, it target armv5te. http://fedoraproject.org/wiki/Architectures/ARM Well, point taken though -- is anyboy talking to Fedora to see if they'd be interested in taking some of our components as their ARM upstreams? I'm an active Fedora contributor (yes black sheep in this Ubuntu-infested Linaro world...) but haven't used the ARM port much. Dude ^^ FWIW I used the ARM port for several years, Fedora since it started. RHAT don't put much resources into it so it bumps along and a Hero like Lennert / Marvell rises now and again to keep it going. Right now they just look delivery of a dozen Pandas for their build farm so they are rising up again. -Andy ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: cpu supported
On Tue, Feb 8, 2011 at 6:38 PM, Christian Robottom Reis wrote: > On Sun, Jan 30, 2011 at 09:50:10AM +, Andy Green wrote: >> Offlist so as not to make myself unpopular ^^ >> >> You might want to look at Fedora ARM, it target armv5te. >> >> http://fedoraproject.org/wiki/Architectures/ARM > > Well, point taken though -- is anyboy talking to Fedora to see if they'd > be interested in taking some of our components as their ARM upstreams? I'm an active Fedora contributor (yes black sheep in this Ubuntu-infested Linaro world...) but haven't used the ARM port much. I believe maybe Lennert can drop us a quick status on Fedora ARM? He was instrumental in making it happen anyways. Yours, Linus Walleij ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
