From: Marcel Holtmann <marcel@holtmann.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Tomas Winkler <tomasw@gmail.com>,
linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/1] rfkill: add the GPS radio type
Date: Sun, 02 Aug 2009 09:28:23 -0700 [thread overview]
Message-ID: <1249230503.3491.43.camel@localhost.localdomain> (raw)
In-Reply-To: <1249199143.2007.2.camel@johannes.local>
Hi Johannes,
> > > we don't have a GPS subsystem, but even without it, I think this is a
> > > good thing to have.
> >
> > GPS devices are usually serial devices.
>
> Yeah, this is interesting -- do we want something like /dev/urfkill
> (cf. /dev/uinput), so that gpsd or whatever is controlling the GPS (same
> applies for 3G) can be controlled with rfkill?
on one hand I think urfkill might be needed, on the other hand I think
we should not do it at all. Currently I would think it is better to
force the RFKILL integration in the kernel so that we have proper
subsystem integration, or platform RFKILL switches or in cases like GPS
and WWAN/3G it will be driver integration. For 3G we already have the
hso.ko driver which has a killswitch and we just need to fix the other
ones. I am actually looking into it, if this is possible without an AT
parser inside the kernel.
So the GPS world is evolving right now and that everybody implements
them as kernel-tty-passthrough pseudo driver and then a binary only
daemon and then gpsd/gypsy on top of it will only survive for certain
amount of time. The binary component will not get wide acceptance. And
even if the binary only userspace component stays, we might still need a
proper GPS subsystem since using TTY as pure transport is holding us
back. Could be that AF_GPS would have been a way better choice. This
will sort itself out over time.
Regards
Marcel
next prev parent reply other threads:[~2009-08-02 16:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-01 23:36 [PATCH 1/1] rfkill: add the GPS radio type Tomas Winkler
2009-08-02 0:04 ` Marcel Holtmann
2009-08-02 5:49 ` Tomas Winkler
2009-08-02 7:45 ` Johannes Berg
2009-08-02 10:43 ` Tomas Winkler
2009-08-02 16:18 ` Marcel Holtmann
2009-08-02 16:28 ` Marcel Holtmann [this message]
2009-08-03 14:23 ` Tomas Winkler
2009-08-03 16:24 ` Marcel Holtmann
2009-08-03 16:53 ` Tomas Winkler
2009-08-03 17:02 ` Marcel Holtmann
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=1249230503.3491.43.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tomasw@gmail.com \
/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