From: Govind Singh <govinds@codeaurora.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: niklas.cassel@linaro.org, Brian Norris <briannorris@chromium.org>,
linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
david.brown@linaro.org, andy.gross@linaro.org
Subject: Re: [PATCH v3 0/6] *** Add support for wifi QMI client handshakes ***
Date: Wed, 11 Jul 2018 10:31:43 +0530 [thread overview]
Message-ID: <0b1441507d2bb18ae267af65e13d98ec@codeaurora.org> (raw)
In-Reply-To: <20180711022425.GI2050@tuxbook-pro>
On 2018-07-11 07:54, Bjorn Andersson wrote:
> On Tue 10 Jul 18:26 PDT 2018, Brian Norris wrote:
>
>> Hi,
>>
>
> Hi Brian,
>
>> On Fri, Jul 06, 2018 at 02:26:17PM +0530, Govind Singh wrote:
> [..]
>> > https://github.com/andersson/tqftpserv
>>
>> FWIW, as of today, the tqftpserv implementation is missing a few
>> headers
>> (so it doesn't even build),
>
> Sorry about that, had those lingering in my repository. I've pushed a
> fix for this.
>
>> and once I hack things such that it can
>> build, it still doesn't work for me (whereas the closed source version
>> does). I see some BYE and DEL_CLIENT messages, but no read requests.
>
> I interpret this description as you're not seeing any prints at, beyond
> the "[TQFTP] got bye" and "[TQFTP] got del_client"?
>
> That would imply that the remote side doesn't even attempt to
> communicate with tqftpserv.
>
> Are you running pd-mapper (either proprietary or my version), is it
> complaining about anything?
>
> Can you run qrtr-lookup on the device after booting the modem? So that
> we see that the tqftpserv is registered properly and that the modem is
> in an appropriate state?
>
> Regards,
> Bjorn
For me below sequence is working. PD mapper is bypassed in the modem
binary that Brian is using, hence that
may not be required at this moment.
qrtr-cfg 1
qrtr-ns
mkdir -p /dev/block/bootdevice/by-name/
ln -s /dev/sda4 /dev/block/bootdevice/by-name/modemst1
ln -s /dev/sda5 /dev/block/bootdevice/by-name/modemst2
ln -s /dev/sda6 /dev/block/bootdevice/by-name/fsc
ln -s /dev/sda7 /dev/block/bootdevice/by-name/fsg
ln -s /var/log/ /readwrite
ln -s /lib/firmware/wlanmdsp.mbn /readonly/firmware/image/wlanmdsp.mbn
rmt_storage &
tqftpserv &
Thanks,
Govind
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Govind Singh <govinds@codeaurora.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Brian Norris <briannorris@chromium.org>,
david.brown@linaro.org, andy.gross@linaro.org,
niklas.cassel@linaro.org, ath10k@lists.infradead.org,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3 0/6] *** Add support for wifi QMI client handshakes ***
Date: Wed, 11 Jul 2018 10:31:43 +0530 [thread overview]
Message-ID: <0b1441507d2bb18ae267af65e13d98ec@codeaurora.org> (raw)
In-Reply-To: <20180711022425.GI2050@tuxbook-pro>
On 2018-07-11 07:54, Bjorn Andersson wrote:
> On Tue 10 Jul 18:26 PDT 2018, Brian Norris wrote:
>
>> Hi,
>>
>
> Hi Brian,
>
>> On Fri, Jul 06, 2018 at 02:26:17PM +0530, Govind Singh wrote:
> [..]
>> > https://github.com/andersson/tqftpserv
>>
>> FWIW, as of today, the tqftpserv implementation is missing a few
>> headers
>> (so it doesn't even build),
>
> Sorry about that, had those lingering in my repository. I've pushed a
> fix for this.
>
>> and once I hack things such that it can
>> build, it still doesn't work for me (whereas the closed source version
>> does). I see some BYE and DEL_CLIENT messages, but no read requests.
>
> I interpret this description as you're not seeing any prints at, beyond
> the "[TQFTP] got bye" and "[TQFTP] got del_client"?
>
> That would imply that the remote side doesn't even attempt to
> communicate with tqftpserv.
>
> Are you running pd-mapper (either proprietary or my version), is it
> complaining about anything?
>
> Can you run qrtr-lookup on the device after booting the modem? So that
> we see that the tqftpserv is registered properly and that the modem is
> in an appropriate state?
>
> Regards,
> Bjorn
For me below sequence is working. PD mapper is bypassed in the modem
binary that Brian is using, hence that
may not be required at this moment.
qrtr-cfg 1
qrtr-ns
mkdir -p /dev/block/bootdevice/by-name/
ln -s /dev/sda4 /dev/block/bootdevice/by-name/modemst1
ln -s /dev/sda5 /dev/block/bootdevice/by-name/modemst2
ln -s /dev/sda6 /dev/block/bootdevice/by-name/fsc
ln -s /dev/sda7 /dev/block/bootdevice/by-name/fsg
ln -s /var/log/ /readwrite
ln -s /lib/firmware/wlanmdsp.mbn /readonly/firmware/image/wlanmdsp.mbn
rmt_storage &
tqftpserv &
Thanks,
Govind
next prev parent reply other threads:[~2018-07-11 5:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 8:56 [PATCH v3 0/6] *** Add support for wifi QMI client handshakes *** Govind Singh
2018-07-06 8:56 ` Govind Singh
2018-07-06 8:56 ` [PATCH v3 1/6] ath10k: Add qmi service helpers for wcn3990 qmi client Govind Singh
2018-07-06 8:56 ` Govind Singh
2018-07-06 8:56 ` [PATCH v3 2/6] ath10k: Add support to create boardname for non-bmi target Govind Singh
2018-07-06 8:56 ` Govind Singh
2018-07-10 23:40 ` Brian Norris
2018-07-10 23:40 ` Brian Norris
2018-07-06 8:56 ` [PATCH v3 4/6] firmware: qcom: scm: Add WLAN VMID for Qualcomm SCM interface Govind Singh
2018-07-06 8:56 ` Govind Singh
2018-07-06 8:56 ` [PATCH v3 5/6] ath10k: Add debug mask for QMI layer Govind Singh
2018-07-06 8:56 ` Govind Singh
2018-07-06 8:56 ` [PATCH v3 6/6] ath10k: Add QMI message handshake for wcn3990 client Govind Singh
2018-07-06 8:56 ` Govind Singh
2018-07-11 1:26 ` [PATCH v3 0/6] *** Add support for wifi QMI client handshakes *** Brian Norris
2018-07-11 1:26 ` Brian Norris
2018-07-11 2:24 ` Bjorn Andersson
2018-07-11 2:24 ` Bjorn Andersson
2018-07-11 5:01 ` Govind Singh [this message]
2018-07-11 5:01 ` Govind Singh
2018-07-11 21:51 ` Brian Norris
2018-07-11 21:51 ` Brian Norris
2018-07-19 17:51 ` Niklas Cassel
2018-07-19 17:51 ` Niklas Cassel
2018-07-23 12:38 ` Govind Singh
2018-07-23 12:38 ` Govind Singh
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=0b1441507d2bb18ae267af65e13d98ec@codeaurora.org \
--to=govinds@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=ath10k@lists.infradead.org \
--cc=bjorn.andersson@linaro.org \
--cc=briannorris@chromium.org \
--cc=david.brown@linaro.org \
--cc=linux-wireless@vger.kernel.org \
--cc=niklas.cassel@linaro.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.