From: =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont <remi@remlab.net>
To: ofono@ofono.org
Subject: Re: [PATCH] usbpnmodem: configure usbpn interfaces automatically
Date: Wed, 28 Apr 2010 19:08:08 +0300 [thread overview]
Message-ID: <201004281908.08781.remi@remlab.net> (raw)
In-Reply-To: <m2q80fd4e751004280715l548126e8w46a2886ff2a92219@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
Le mercredi 28 avril 2010 17:15:54 Pekka Pessi, vous avez écrit :
> 2010/4/28 Rémi Denis-Courmont <remi@remlab.net>:
> > I fail to see why we need this. usbpn is already autoconfigured by the
> > kernel. It only needs to be brought administratively up.
>
> This is not the case with 2.6.31. Does it hurt with later kernels?
Not all kernel versions support routing. And I'd hate to duplicate existing
kernel functionality in oFono user-space forever just for 2.6.31 (long term
support is 2.6.32 by the way). There's probably two users in the entire world
who care about the 2.6.31 + USB CDC Phonet + oFono - phonet-utils combination.
Not to mention that it is done in a much cleaner and compact way in kernel
space. Also this would prevent me or someone else from ever improving the
Phonet (auto)configuration later, which is certainly on my roadmap.
--
Rémi Denis-Courmont
http://www.remlab.net/
http://fi.linkedin.com/in/remidenis
next prev parent reply other threads:[~2010-04-28 16:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 15:05 [PATCH] usbpnmodem: configure usbpn interfaces automatically Pekka Pessi
2010-04-23 18:00 ` Denis Kenzior
2010-04-28 13:03 ` Pekka Pessi
2010-04-28 13:10 ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2010-04-28 14:15 ` Pekka Pessi
2010-04-28 16:08 ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont [this message]
2010-05-04 13:55 ` Pekka Pessi
-- strict thread matches above, loose matches on Subject: below --
2010-04-22 11:27 Pekka Pessi
2010-04-22 22:51 ` Denis Kenzior
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=201004281908.08781.remi@remlab.net \
--to=remi@remlab.net \
--cc=ofono@ofono.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox