All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][PATCH 8/8] android-tools-conf: import one more improvement for android-gadget-setup from meta-luneos
Date: Thu, 23 May 2019 11:55:05 +0000	[thread overview]
Message-ID: <20190523115505.18245-8-Martin.Jansa@gmail.com> (raw)
In-Reply-To: <20190523115505.18245-1-Martin.Jansa@gmail.com>

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
---
 .../android-tools-conf/android-gadget-setup              | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/meta-oe/recipes-devtools/android-tools/android-tools-conf/android-gadget-setup b/meta-oe/recipes-devtools/android-tools/android-tools-conf/android-gadget-setup
index beca353e67..26cf30eddd 100644
--- a/meta-oe/recipes-devtools/android-tools/android-tools-conf/android-gadget-setup
+++ b/meta-oe/recipes-devtools/android-tools/android-tools-conf/android-gadget-setup
@@ -9,6 +9,15 @@
 # model=$(getprop ro.product.model Android)
 # serial=$(getprop ro.serialno 0123456789ABCDEF)
 
+#below are now needed in order to use FunctionFS for ADB, tested to work with 3.4+ kernels
+if grep -q functionfs /proc/filesystems; then
+    mkdir -p /dev/usb-ffs/adb
+    mount -t functionfs adb /dev/usb-ffs/adb
+    #android-gadget-setup doesn't provide below 2 and without them it won't work, so we provide them here.
+    echo adb > /sys/class/android_usb/android0/f_ffs/aliases
+    echo ffs > /sys/class/android_usb/android0/functions
+fi
+
 manufacturer="$(cat /system/build.prop | grep -o 'ro.product.manufacturer=.*' | cut -d'=' -f 2)"
 model="$(cat /system/build.prop | grep -o 'ro.product.model=.*' | cut -d'=' -f 2)"
 # get the device serial number from /proc/cmdline directly(since we have no getprop on
-- 
2.17.1



  parent reply	other threads:[~2019-05-23 11:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-23 11:54 [meta-oe][PATCH 1/8] uriparser: upgrade to 0.9.3 Martin Jansa
2019-05-23 11:54 ` [meta-oe][PATCH 2/8] pidgin: upgrade to 2.13.0 Martin Jansa
2019-05-23 11:55 ` [meta-oe][PATCH 3/8] funyahoo-plusplus, icyque, pidgin-sipe, purple-skypeweb: add couple plugins for pidgin Martin Jansa
2019-06-14 18:10   ` Khem Raj
2019-06-14 21:34     ` Martin Jansa
2019-06-18  7:12       ` Martin Jansa
2019-06-18 10:43         ` Martin Jansa
2019-06-18 13:06           ` Khem Raj
2019-06-18 15:37             ` Martin Jansa
2019-06-18 15:45               ` Khem Raj
2019-06-18 15:54                 ` Martin Jansa
2019-06-18 17:47                   ` Khem Raj
2019-06-19  1:46                     ` Khem Raj
2019-05-23 11:55 ` [meta-oe][PATCH 4/8] hunspell: use git fetcher instead of github archive Martin Jansa
2019-05-23 12:02   ` Andreas Müller
2019-05-23 11:55 ` [meta-oe][PATCH 5/8] hunspell-dictionaries: import from meta-luneos to make hunspell in meta-oe a bit more useful Martin Jansa
2019-05-23 12:27   ` Andreas Müller
2019-05-23 11:55 ` [meta-oe][PATCH 6/8] Geoclue: Update to 2.5.3 Martin Jansa
2019-05-23 11:55 ` [meta-oe][PATCH 7/8] ttf-mplus, ttf-vlgothic: add ttf-mplus license Martin Jansa
2019-05-23 11:55 ` Martin Jansa [this message]
2019-05-23 12:02 ` [meta-oe][PATCH 1/8] uriparser: upgrade to 0.9.3 Adrian Bunk
2019-05-24  0:37   ` Khem Raj

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190523115505.18245-8-Martin.Jansa@gmail.com \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.