From: Arnd Bergmann <arnd@arndb.de>
To: sedat.dilek@gmail.com
Cc: 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: Mon, 18 Jul 2016 11:01:46 +0200 [thread overview]
Message-ID: <1784147.bVhkVRAAJX@wuerfel> (raw)
In-Reply-To: <CA+icZUXyotvQiTNEPg8oUgV9AZQnFjnFk4_nLmV+fy-dwtDL9g@mail.gmail.com>
On Saturday, July 16, 2016 8:31:19 AM CEST Sedat Dilek wrote:
> On Thu, Jul 14, 2016 at 7:26 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Thursday, July 14, 2016 1:51:28 PM CEST Sedat Dilek wrote:
> >>
> >> what is the base for your flo-WIP Git branch?
> >> Linus tree? Linux-next? An ARM Git tree "for-next"?
> >>
> >> What "OS" are you running in that video (LWN article, see above)?
> >>
> >> FYI:
> >> I downloaded "flo-lmy48t" (Nexus-7) to compare with "occam-lmy48t"
> >> (Nexus-4) - both for Android v5.1.1 and the same build-nummer.
> >>
> >>
> >
> > One more thing: you will absolutely need a Nexus debug cable, there should
> > be several descriptions of that on the web.
> >
>
> Hi Arnd,
>
> Hmm, I asked aunt G00gle "nexus 4 uart debug cable" and [1] has the
> official description and [2] might be helpful in debugging.
>
> [3] sounds somehow funny "audio jack console cable".
Right, that's the cable. I think most people don't even use kgdb,
but use whatever works for you.
> I know there is here in Tübingen near to Metropol car park a lab
> offering 3d printing, electronic workshops etc.
> It is definitely not [4], but looks interesting.
> Maybe they can borrow or help in brazing/soldering such a cable
Interesting, I used to live in that street, never knew it was there.
> > Also, if you like, you can come visit me here in Dettenhausen so we can
> > look at the code together.
>
> Hey cool, thanks for this offer.
> I just looked at the monthly meetings of Linux User Group Tuebingen,
> it is next Tuesday (July, 19th).
> Will you come?
Sorry, my evenings are usually booked entertaining two small kids.
Arnd
next prev parent reply other threads:[~2016-07-18 9:01 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 [this message]
2016-07-19 2:06 ` Jeremy McNicoll
2016-07-19 7:47 ` Arnd Bergmann
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=1784147.bVhkVRAAJX@wuerfel \
--to=arnd@arndb.de \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--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 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.