Dear johan&Williams
As we discuss about the question of zte_ev.c, are you sure how to modify.
Looking forward to your reply. thanks.
lei.liu
At 2014-06-25 04:35:28, "刘磊" wrote:
>
>
>At 2014-06-24 09:46:01, "Johan Hovold" wrote:
>>On Tue, Jun 24, 2014 at 08:43:36PM +0800, 刘磊 wrote:
>>> A
At 2014-06-24 09:46:01, "Johan Hovold" wrote:
>On Tue, Jun 24, 2014 at 08:43:36PM +0800, 刘磊 wrote:
>> At 2014-06-23 10:49:14, "Johan Hovold" wrote:
>> >On Mon, Jun 23, 2014 at 09:42:08AM -0500, Dan Williams wrote:
>> >> On Mon, 2014-06-23 at 18:15 +0800, 刘磊 wrote:
>
>> >> > i don't know why cre
On Tue, Jun 24, 2014 at 08:43:36PM +0800, 刘磊 wrote:
> At 2014-06-23 10:49:14, "Johan Hovold" wrote:
> >On Mon, Jun 23, 2014 at 09:42:08AM -0500, Dan Williams wrote:
> >> On Mon, 2014-06-23 at 18:15 +0800, 刘磊 wrote:
> >> > i don't know why create the file of zte_ev.c that is not
> >> > necessary.
At 2014-06-23 10:49:14, "Johan Hovold" wrote:
>On Mon, Jun 23, 2014 at 09:42:08AM -0500, Dan Williams wrote:
>> On Mon, 2014-06-23 at 18:15 +0800, 刘磊 wrote:
>> > >Could you try the first patch (only) and see if it fixes the problem?
>> > >Does it also fix the problem you're having with PID 0xfff
i'm sorry, i think you said is the patch of my submit yesterday.i misunderstand
you means.
At 2014-06-23 06:52:22, "Johan Hovold" wrote:
>On Mon, Jun 23, 2014 at 06:15:52PM +0800, 刘磊 wrote:
>>
>> >Could you try the first patch (only) and see if it fixes the problem?
>> >Does it also fix the p
On Mon, Jun 23, 2014 at 09:42:08AM -0500, Dan Williams wrote:
> On Mon, 2014-06-23 at 18:15 +0800, 刘磊 wrote:
> > >Could you try the first patch (only) and see if it fixes the problem?
> > >Does it also fix the problem you're having with PID 0xfffe?
> >
> > yes, the first patch could solve the prob
On Mon, 2014-06-23 at 18:15 +0800, 刘磊 wrote:
> >Could you try the first patch (only) and see if it fixes the problem?
> >Does it also fix the problem you're having with PID 0xfffe?
>
> yes, the first patch could solve the problem with pid 0xfffe.
>
>
> >When you you have tested the first patch,
On Mon, Jun 23, 2014 at 06:15:52PM +0800, 刘磊 wrote:
>
> >Could you try the first patch (only) and see if it fixes the problem?
> >Does it also fix the problem you're having with PID 0xfffe?
>
> yes, the first patch could solve the problem with pid 0xfffe.
Did you test my first patch ("USB: zte_e
>Could you try the first patch (only) and see if it fixes the problem?
>Does it also fix the problem you're having with PID 0xfffe?
yes, the first patch could solve the problem with pid 0xfffe.
>When you you have tested the first patch, could you test the second one
>as well and see if everythi
On Fri, Jun 20, 2014 at 06:30:23PM +0800, 刘磊 wrote:
> patch2: Modify the parameter from 0x0003 to 0x. you must submit patch1 at
> first.
> Reason:In the USB serial protocol, if set the control state
> (SET_CONTROL_LINE_STATE(22h)) and the parameter of RTS must be 0x
> that make the carri
dear linuxfoundation:
I'm very sorry, i think i had been according to the
Documentation/SubmittingPatches to submit.
The pid of 0xfffe device re-connect network failed when driven by zte_ev,
but work fine when driven by option if we move the pid 0xfffe to option.
in order to re-connect
On Fri, 2014-06-20 at 18:30 +0800, 刘磊 wrote:
> dear linuxfoundation:
> I'm very sorry has some problems in before's submit. now i divided the
> problems in two patches.
>
> patch1:move ZTE CDMA device pid from zte_ev.c back to option.c.
> reason: the p
dear linuxfoundation:
I'm very sorry has some problems in before's submit. now i divided the
problems in two patches.
patch1:move ZTE CDMA device pid from zte_ev.c back to option.c.
reason: the pid of 0xfffe device can't re-connect succusfull when driven by
zte_ev
On Wed, Jun 18, 2014 at 07:13:19PM +0800, 刘磊 wrote:
>
> dear linuxfoundation:
> Because of the usb driver parameters error that leads to failed in
> reconnect. now i want to modify the error parameter and
> move device pid fffe from zte_ev.c back to option.c for our company.
These are tw
dear linuxfoundation:
Because of the usb driver parameters error that leads to failed in
reconnect. now i want to modify the error parameter and
move device pid fffe from zte_ev.c back to option.c for our company.
modify reason:
1. Move device pid fffe from zte_ev.c back to option.c for ou
On Tue, Apr 08, 2014 at 07:59:28PM +0800, 刘磊 wrote:
> dear linuxfoundation:
> I'm not sure if you receive our mails in lase week , i resend it now.
> Please confirm whether it is correct format for submit.
> Looking forward to your reply.
>
> modify reason:
> 1. Move device pid fffe from
On Tue, Apr 08, 2014 at 07:59:28PM +0800, 刘磊 wrote:
> dear linuxfoundation:
> I'm not sure if you receive our mails in lase week , i resend it now.
> Please confirm whether it is correct format for submit.
> Looking forward to your reply.
>
> modify reason:
> 1. Move device pid fffe from
dear linuxfoundation:
I'm not sure if you receive our mails in lase week , i resend it now.
Please confirm whether it is correct format for submit.
Looking forward to your reply.
modify reason:
1. Move device pid fffe from zte_ev.c back to option.c for our company.
2. Modify the paramete
dear linuxfoundation:
I'm sorry, was not set format to text in before mails. Now resend it.
modify reason:
1. Move device pid fffe from zte_ev.c back to option.c for our company.
2. Modify the parameter from 0x0003 to 0x. the problem may cause the device
can not be close.
these two
On Thu, Mar 27, 2014 at 02:40:23PM +0800, 刘磊 wrote:
> dear linuxfoundation:
"Linux Foundation" is a non-profit group, not a person :)
And please don't send HTML email, the mailing list rejects it.
> Because of the time difference, can not respond promptly.
That's not an issue, don't worry a
20 matches
Mail list logo
