On Wed, Apr 06, 2016 at 03:35:41PM +0200, Yegor Yefremov wrote: > On Wed, Apr 6, 2016 at 3:26 PM, Bin Liu <b-liu@xxxxxx> wrote: > > On Wed, Apr 06, 2016 at 03:17:48PM +0200, Yegor Yefremov wrote: > >> On Wed, Apr 6, 2016 at 3:09 PM, Bin Liu <b-liu@xxxxxx> wrote: > >> > On Wed, Apr 06, 2016 at 11:53:26AM +0200, Yegor Yefremov wrote: > >> >> > Thanks for the tip. Yes, mmcli can aleays find the SIM card. > >> >> > >> >> I've got SIM7100E card working with ModemManager. It also provokes the > >> >> same tx fifo error, but wwan0 is working afterwards. At least I could > >> >> make a connection, get IP address over DHCP and ping an URL. > >> >> > >> >> mmcli -m 0 --simple-connect="apn=internet.eplus.de" > >> > > >> > So this tx fifo flush warning can be ignored, right? > >> > >> This is difficult to say. Could you make a connection with MA260? And > >> I must also make a test with HackRF hardware. I'll let you know, as > >> soon as I've tested it. > >> > >> Do you have an idea, how one can fix this nevertheless? > > > > No. As Felipe mentioned in this thread earlier, we don't get much help > > from the MUSB document. Unless this issue caused any functional problem, > > I wouldn't spend more time on it. > > What should we do with the warning message? It will make users worry > about the system. We decided to use WARN() until we have enuogh data to conclude the flush error does not break any function. But we are not there yet. > > Could you then look at the freeze issue with removing FTDI device > during it is working? I can. I will have to first locate a FT4243H device. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
