From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 1/1] Huawei E176: Mark primary and secondary device at ofono.rules TODO: Fix sim_add detection, add E1552 idProduct to ofono.rules
Date: Tue, 01 Jun 2010 14:09:10 -0500 [thread overview]
Message-ID: <201006011409.11869.denkenz@gmail.com> (raw)
In-Reply-To: <87d3wc2etx.fsf@potku.valot.fi>
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
Hi Kalle,
> Marcel Holtmann <marcel@holtmann.org> writes:
> > Hi Kalle,
>
> Hallo Marcel,
>
> >> I personally would prefer a solution which would dynamically probe the
> >> ports and choose them based on results. I believe modemmanager does
> >> something like this, but I haven't looked in detail.
> >
> > we should do something like auto-detect at some point, but there are
> > limits in it.
>
> So what's the best option to go forward?
>
> And related to this, can we rely on the port numbering order provided by
> udev? For example, on my Huawei E1552 port 0 is the main chat port and
> port 2 is the "event" port. Is it certain that port numbering will be
> the same across all distributions and kernels?
>
I'm not the kernel expert, but the answer is probably 'no'. However, doing
any sort of port auto-detection inside plugins/udev.c is a bit nasty. Best we
can do is set all of the 2/3/4 ttys and let the plugin probe them. I
certainly have doubts we can do this reliably. If we can't, then we should
consider Florian's approach as a backup.
Regards,
-Denis
next prev parent reply other threads:[~2010-06-01 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-30 13:47 [PATCH 1/1] Huawei E176: Mark primary and secondary device at ofono.rules TODO: Fix sim_add detection, add E1552 idProduct to ofono.rules Florian Steinel
2010-05-31 12:29 ` Kalle Valo
2010-05-31 15:52 ` Marcel Holtmann
2010-05-31 16:52 ` Kalle Valo
2010-05-31 17:00 ` Daniel Oliveira Nascimento
2010-06-01 19:09 ` Denis Kenzior [this message]
2010-05-31 17:57 ` Florian Steinel
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=201006011409.11869.denkenz@gmail.com \
--to=denkenz@gmail.com \
--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 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.