From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: gpsd re-write
Date: Sun, 24 Jan 2010 16:09:45 +0100 [thread overview]
Message-ID: <hjhnrn$lpi$1@ger.gmane.org> (raw)
In-Reply-To: <fca63bcf1001240522q1863fb51xa1a041d3e0b8cdf@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 24-01-10 14:22, Michael Lippautz wrote:
> Hej,
>
> As I am re-writing the gpsd package, a few questions did come up.
>
> 1) gpsd can deal with multiple different gps devices (being served as
> different nodes). Is it sufficient to start gpsd with a control socket
> and add recipe for gps devices that just add init script that are
> executed after gpsd startup. These init scripts could add the device
> over the control socket. I.e. a recipe gpsd-device-... could add the
> /dev/ttyACM0 node, using the control socket.
>
> 2) Since gps devices can also be integrated into platforms (machines)
> a second approach using RDEPENDS_${PN}_machine can be used to build a
> machine specific package. This machine specific package could init the
> device and also attach it using the socket.
>
> Is it "ok" to create such machine specific packages, i.e.
> gpsd-hardware-om-gta01 ? How about "device" specific recipes (should
> they be done in an other way)?
>
> Additionally I can also add an /etc/default/gps-hardware file that
> uses update-alternative to add the device at program startup.
>
> Are these approaches correct? Don't want to sit and write these if
> they are rejected anyways ;)
Your approaches are a lot better than the current 'gpsd only starts if
it was built for your machine *AND* OE has a config for it'
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLXGK4MkyGM64RGpERAk7CAJ4kbdekGFkioFbpHZ/28fsmqcOqtACfQgx3
i5aHG9ULaUksACfO759u7sc=
=VAwM
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2010-01-24 15:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 13:22 gpsd re-write Michael Lippautz
2010-01-24 15:09 ` Koen Kooi [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='hjhnrn$lpi$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.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