From: Arnd Bergmann <arnd@arndb.de>
To: Jeremy McNicoll <jmcnicol@redhat.com>
Cc: sedat.dilek@gmail.com, Rob Clark <robdclark@gmail.com>,
Stanimir Varbanov <svarbanov@mm-sol.com>,
Andy Gross <andy.gross@linaro.org>,
David Brown <david.brown@linaro.org>,
linux-arm-msm@vger.kernel.org,
John Stultz <john.stultz@linaro.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: Re: First steps with my Google Nexus-4
Date: Tue, 19 Jul 2016 09:47:10 +0200 [thread overview]
Message-ID: <2412508.u5uv44vaGg@wuerfel> (raw)
In-Reply-To: <8a85a158-a4f9-4ba5-0879-417f81370a19@redhat.com>
On Monday, July 18, 2016 7:06:49 PM CEST Jeremy McNicoll wrote:
> >
> > [1] https://android.googlesource.com/device/google/debugcable/
> > [2] http://www.contextis.com/resources/blog/kgdb-android-debugging-kernel-boss/
> > [3] http://www.pabr.org/consolejack/consolejack.en.html
> > [4] http://www.offene-werkstaetten.org/werkstatt/fablab-neckar-alb-e-v
> > [5] http://tuebingen.linux.de/
>
> [6] http://people.redhat.com/jmcnicol/nexus_debug/
>
> No soldering needed, as its a skill I do not have. ;-)
That sounds like it would grill the rx line, as the FTDI breakout
board you use supplies 3.3v while the expected input is 1.8v.
As I understand it, you want to supply 3.3v to the microphone line
for detection but then run the rx/tx lines at 1.8v. I have not built
one of those cables myself yet, so I'm not sure. It probably works
using 3.3v, at least for a while, but there is a significant risk
of damaging the hw.
Arnd
next prev parent reply other threads:[~2016-07-19 7:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 10:25 First steps with my Google Nexus-4 Sedat Dilek
2016-07-14 11:03 ` Arnd Bergmann
2016-07-14 11:18 ` Sedat Dilek
2016-07-14 11:51 ` Sedat Dilek
2016-07-14 15:54 ` John Stultz
2016-07-14 17:26 ` Arnd Bergmann
2016-07-16 6:31 ` Sedat Dilek
2016-07-18 9:01 ` Arnd Bergmann
2016-07-19 2:06 ` Jeremy McNicoll
2016-07-19 7:47 ` Arnd Bergmann [this message]
2016-07-19 10:52 ` Jeremy McNicoll
2016-07-19 11:42 ` Bhushan Shah
2016-07-14 18:00 ` Bjorn Andersson
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=2412508.u5uv44vaGg@wuerfel \
--to=arnd@arndb.de \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=jmcnicol@redhat.com \
--cc=john.stultz@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=sedat.dilek@gmail.com \
--cc=svarbanov@mm-sol.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox