From: Greg KH <greg@kroah.com>
To: Fabio Fumi <ffumi68@googlemail.com>
Cc: linux-serial@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: Connection to a 3G USB Module using USB-Serial
Date: Mon, 10 Jun 2013 10:23:37 -0700 [thread overview]
Message-ID: <20130610172337.GA1934@kroah.com> (raw)
In-Reply-To: <CA+y4WrRcrnYNHsFEZ2aTPGyPB1e9z508wzMp0Cf3-kxXPoNEBg@mail.gmail.com>
On Mon, Jun 10, 2013 at 03:58:38PM +0200, Fabio Fumi wrote:
> Thanks Greg for taking som etime to answer.
>
> My kernel is an old 2.6.35.7 and migrating it entirely to 3+ one is a
> real mess (given the number of platfomr customization it includes).
Ick, really old obsolete kernels like that one are not good for trying
to run new hardware with. I suggest contacting the company that is
forcing you to stick with that version, and getting support from them to
do the needed backporting of this driver.
> So probably the best is to try back-porting the ZTE usb-serial
> driver... I guess. Is it "drivers/usb/serial/zte_ev.c" what you're
> referring to? My device is a ZTE MF-210... does the same driver
> really apply for this device too?
I think it does, what is the device/vendor id of it?
> Does the same driver rely on some kernel 3.x-only features?
Yes, all drivers are tied tightly to the specific kernel version they
are released with.
> I can always give it a *blind* try, of course... but better knowing in
> advance, if it won't work.
You can try to backport it, it shouldn't be that hard, but your really
going to be on your own here, sorry.
best of luck,
greg k-h
prev parent reply other threads:[~2013-06-10 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 12:54 Connection to a 3G USB Module using USB-Serial Fabio Fumi
[not found] ` <CA+y4WrSC0Z5hFodTDNL0KGu2_pZtu3WB98re-yQJOsFCo21nRw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-08 18:22 ` Greg KH
2013-06-10 13:58 ` Fabio Fumi
2013-06-10 17:23 ` Greg KH [this message]
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=20130610172337.GA1934@kroah.com \
--to=greg@kroah.com \
--cc=ffumi68@googlemail.com \
--cc=linux-serial@vger.kernel.org \
--cc=linux-usb@vger.kernel.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.