From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bjorn Andersson Subject: Re: First steps with my Google Nexus-4 Date: Thu, 14 Jul 2016 11:00:50 -0700 Message-ID: <20160714180050.GA13516@tuxbot> References: <5025899.XqD1qA6xh1@wuerfel> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-pa0-f54.google.com ([209.85.220.54]:35067 "EHLO mail-pa0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751122AbcGNSBC (ORCPT ); Thu, 14 Jul 2016 14:01:02 -0400 Received: by mail-pa0-f54.google.com with SMTP id dx3so30935351pab.2 for ; Thu, 14 Jul 2016 11:01:02 -0700 (PDT) Content-Disposition: inline In-Reply-To: <5025899.XqD1qA6xh1@wuerfel> Sender: linux-arm-msm-owner@vger.kernel.org List-Id: linux-arm-msm@vger.kernel.org To: Arnd Bergmann Cc: sedat.dilek@gmail.com, Rob Clark , Stanimir Varbanov , Andy Gross , David Brown , linux-arm-msm@vger.kernel.org, John Stultz On Thu 14 Jul 04:03 PDT 2016, Arnd Bergmann wrote: [..] > I'm guessing that working Modem support is the biggest challenge here, > if you don't absolutely need to make phone calls you should be able > to get it working. > We have HSIC support on the way in, so I do expect to be able to bring up the modem rather soon. It's been a while since I worked on 8064, but I believe that with some userspace tinkering (like making libqmi talk PF_QIPCRTR) this would be good enough to camp on a network and send text messages. We will need a version of the rmnet driver (there's 5 different variants in CAF) to do data based on this. To get an audio call running we will have to figure out how to do DSP based Audio, something we have punted on until now. But with new requirements from DB820c we have to tackle this and I expect this to benefit 8064 as well. We do know how to load the DSP firmware, so that should be enough for the modem firmware not to go belly-up from the get-go :) Regards, Bjorn