From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: PATCH: Enable udev-based autodetection of calypso modem on Freerunner
Date: Wed, 22 Dec 2010 05:37:09 -0800 [thread overview]
Message-ID: <1293025029.2658.70.camel@aeonflux> (raw)
In-Reply-To: <871v5aajzi.fsf@ossau.uklinux.net>
[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]
Hi Neil,
> >>> Then I didn't look far back enough (or I'm simply blind). But I still
> >>> prefer this to be inside the driver or HACKING.calypso for easier access.
> >>
> >> I am with you that this needs to be documented better than GIT commit
> >> logs.
> >>
> >> However I do prefer doc/calypso-modem.txt and doc/ifx-modem.txt though
> >> since I don't wanna clutter the root directory.
> >>
> >
> > Sounds good to me.
>
> Cool. Once I've worked out the simplest udev rule for calypso, I'll
> submit a patch to create doc/calypso-modem.txt to document that.
>
> (I don't yet understand why it makes sense for calypso to be handled
> differently from other cases in plugins/ofono.rules, but I'm happy to
> trust that there is a good reason for this.)
the other cases come from an unique vendor and product ID. The Calypso
and also IFX modems are based on device nodes. These are not unique.
They are platform specific. Not all platform will have a Calypso modem
behind /dev/ttySAC0 for example.
Regards
Marcel
next prev parent reply other threads:[~2010-12-22 13:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 22:12 PATCH: Enable udev-based autodetection of calypso modem on Freerunner Neil Jerram
2010-12-20 23:39 ` Denis Kenzior
2010-12-21 12:01 ` Neil Jerram
2010-12-21 18:01 ` Denis Kenzior
2010-12-21 18:13 ` Marcel Holtmann
2010-12-21 18:16 ` Denis Kenzior
2010-12-21 19:05 ` Marcel Holtmann
2010-12-21 19:18 ` Denis Kenzior
2010-12-21 19:22 ` Marcel Holtmann
2010-12-21 19:33 ` Denis Kenzior
2010-12-21 21:34 ` Neil Jerram
2010-12-22 13:37 ` Marcel Holtmann [this message]
2010-12-23 12:02 ` Neil Jerram
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=1293025029.2658.70.camel@aeonflux \
--to=marcel@holtmann.org \
--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.