|
»
« Return to Thread: Re: gpsd 3.x successfully ported to embedded MIPS (Netgear wndr3700v2 router)
Re: gpsd 3.x successfully ported to embedded MIPS (Netgear wndr3700v2 router)
by Dave Taht
::
Rate this Message:
On Sat, Sep 17, 2011 at 7:35 AM, Eric Raymond <esr@...> wrote:
While there are several packages in openwrt head that pull directly from a git commit
of a given package, I would personally prefer that gpsd 3.x baked a little more
(with people testing on arm, mips, mobile devices, etc) and I am also hoping
However, I note that I am not in any way a gatekeeper to the main openwrt feeds. Their requirements are different.
We (bufferbloat.net) spun up ceropackages specifically to enable those newer to openwrt development and
embedded development to be able to use github as a base, and 'screw up' freely while mastering the cross-development process, while not necessarily being able to do builds on or for their own hardware.
Well, that, plus we wanted to try out some crazy things like a variety of new test tools, multicast routing, using xinetd, etc.
A side goal is to get the developers of a given piece of software's heads around how different embedded development can be, and also get needed patches pushed up into those mainline packages.
It has been fun getting evan hunt (bind9 maintainer at isc.org) and your respective heads around life inside 8MB of flash.
> I note that you will have to install the right kmod-serial-* to
> get the right kernel support for your specific device,
in order for ttyUSB0 to be recognised by the openwrt/wndr3700v2 kernel. (I'm documenting this for your future builds)
I note many openwrt based devices have real serial ports, too. The wndr actually has one inside it that can be hacked onto.
I note that adding a kmod-usb-serial-* depenendency to the gpsd package is the wrong thing, as openwrt is more
like a 'distro to build hardware' distro, where the designer of the firmware would pick and choose the right kernel
modules for their particular hardware.
saving any and all space on precious flash is in large part what drives packaging for embedded firmware,
which is why I'd like to nuke the gpsd libusb dependency as it's only for one rarely used device.
Well... then it needs to be invertible somehow. And the gpsd openwrt package could merely have an option in the gpsd.config file to enable it where needed. I can certainly see cases where lo can be used by other apps on the router and no other access is needed.
That said, full ipv6 support would be nice, too.
Dave Taht <dave.taht@...>:
> After gpsd stablizes (gpsd 3.2?) we can get it into openwrt head, but in theWhat counts as stable? Changes since 3.0 have been minor, mostly tweaks
> meantime it would be good to know if gpsd 3.x worked well on other variants
> of openwrt.
to the build recipe. The biggest change I'm expecting in 3.2 is a bug
fix to the old (non-kernel) PPS code.
While there are several packages in openwrt head that pull directly from a git commit
of a given package, I would personally prefer that gpsd 3.x baked a little more
(with people testing on arm, mips, mobile devices, etc) and I am also hoping
However, I note that I am not in any way a gatekeeper to the main openwrt feeds. Their requirements are different.
We (bufferbloat.net) spun up ceropackages specifically to enable those newer to openwrt development and
embedded development to be able to use github as a base, and 'screw up' freely while mastering the cross-development process, while not necessarily being able to do builds on or for their own hardware.
Well, that, plus we wanted to try out some crazy things like a variety of new test tools, multicast routing, using xinetd, etc.
A side goal is to get the developers of a given piece of software's heads around how different embedded development can be, and also get needed patches pushed up into those mainline packages.
It has been fun getting evan hunt (bind9 maintainer at isc.org) and your respective heads around life inside 8MB of flash.
> I note that you will have to install the right kmod-serial-* to
> get the right kernel support for your specific device,
Bu "your specific device" you mean the router hardware? When we use that
phrase here we generally mean a make/model of GPS...
No, I meant the make/model of GPS that we tested, which required a
opkg install kmod-usb-serial-ftdi
opkg install kmod-usb-serial-ftdi
in order for ttyUSB0 to be recognised by the openwrt/wndr3700v2 kernel. (I'm documenting this for your future builds)
I note many openwrt based devices have real serial ports, too. The wndr actually has one inside it that can be hacked onto.
I note that adding a kmod-usb-serial-* depenendency to the gpsd package is the wrong thing, as openwrt is more
like a 'distro to build hardware' distro, where the designer of the firmware would pick and choose the right kernel
modules for their particular hardware.
saving any and all space on precious flash is in large part what drives packaging for embedded firmware,
which is why I'd like to nuke the gpsd libusb dependency as it's only for one rarely used device.
> and enabling the -GI've added a force_global configuration option to force -G on for deployments
> option to gpsd allows you to contact the router remotely with tools like
> cgpsd, etc.
like CeroWrt where listening only on loopback is not a good idea.
Well... then it needs to be invertible somehow. And the gpsd openwrt package could merely have an option in the gpsd.config file to enable it where needed. I can certainly see cases where lo can be used by other apps on the router and no other access is needed.
That said, full ipv6 support would be nice, too.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
_______________________________________________
Gpsd-dev mailing list
Gpsd-dev@...
https://lists.berlios.de/mailman/listinfo/gpsd-dev
« Return to Thread: Re: gpsd 3.x successfully ported to embedded MIPS (Netgear wndr3700v2 router)
| Free embeddable forum powered by Nabble | Forum Help |
