Thanks for the info and explanation. No need for the pointers.
I'd already decided on dropping this request 'cause it did seem a bit hacky and was looking at a better solution. Your suggestion to
take a look at libusb seems like a good thing to do for this app.
/ted
-Original Message-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
"Ted Hess" wrote:
> After a bit more research - This is what I know:
>
> The upstream cp210x driver is not completely up-to-date with the driver
> silabs maintains on
> their site. In their own words: "... unfortunately GPIO is not something
> that h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Comments inline...
Drasko DRASKOVIC wrote:
> Signed-off-by: Drasko DRASKOVIC
> ---
Might just be my mail client, but might be yours, did you change
anything to send this? you seem to have lost all the commit message up
into the subject?
> targe
On 7 August 2015 at 17:40, Alexander Couzens wrote:
> lock -n is similiar to flock -n. If the lock was already taken,
> fail with exit code = 1 and write error message to stderr.
>
> example:
> if ! lock -n /tmp/foo ; then
> echo lock exits.
> else
> echo lock was free. But is lock
This patch adds support for (optionally) specifying ip family via a
command- line switch. The switch sends respective "Set IP Family" WDS
message to qmi-device before actually connecting.
Using this switch allows connecting to ipv6 enabled networks or networks
with dual-stack support with the a
Adding --get-current-settings switch which can be used to query
ip-settings among some other useful data obtained from remote end when
connected.
This is mainly useful with modems which do not provide a dhcp server for
nameserver or ip-information (especially in ipv6 networks).
Signed-off-by:
Here is a set of two patches which improve uqmi when connecting to ipv6
enabled networks.
The first patch adds the capability to select the ip-family that is used
when connecting (ipv4 or ipv6). The second patch can be used to output
the obtained ip information from connected networks.
With pr
On 2015-08-07 18:50, Mathieu Olivari wrote:
> Actually, I was asking myself the same questions yesterday. I was leaning
> towards dts for the reasons you mention below as well; the problem is on ref
> designs, there is no "standard" layout. The flash layout changes with time
> (an AP148 with an old
Using the postinst script for sanity checks and expecting opkg to fail
if the postinst didn't return 0 was possible in Barrier Breaker, propagate
the real postinst return code through default_postinst to restore this
behaviour.
Signed-off-by: Matthias Schiffer
---
package/base-files/files/lib/fu
Actually, I was asking myself the same questions yesterday. I was leaning
towards dts for the reasons you mention below as well; the problem is on ref
designs, there is no "standard" layout. The flash layout changes with time
(an AP148 with an old boot binary blob will have a different layout than
On Fri, Aug 7, 2015 at 5:40 PM, Alexander Couzens wrote:
> lock -n is similiar to flock -n. If the lock was already taken,
> fail with exit code = 1 and write error message to stderr.
>
> example:
> if ! lock -n /tmp/foo ; then
> echo lock exits.
> else
> echo lock was free. But is
lock -n is similiar to flock -n. If the lock was already taken,
fail with exit code = 1 and write error message to stderr.
example:
if ! lock -n /tmp/foo ; then
echo lock exits.
else
echo lock was free. But is locked now.
fi
> lock was free. But is locked now.
> lock exists.
v1: i
@Florian
So, I took some time today to patch a bit of support for OVS to compile on
OpenWRT with kernel 4.1
Can you pull this from my fork and test it out a bit ?
Branch is here: https://github.com/commodo/packages/tree/ovs-kernel-4.1
Commit is this one:
https://github.com/commodo/packages/commit/
Hi,
On Fri, Aug 7, 2015 at 4:28 AM, Mathieu Olivari wrote:
> These are cherry-picked & backported from LKML:
> *https://lkml.org/lkml/2015/3/17/19
>
> They are enabled on both 3.18 and 4.1 kernel. Patches 150 to 154 are
> applying changes merged since 3.18; they enable mechanisms used by the
> AD
On Thu, Aug 06, 2015 at 11:09:02PM +0200, Felix Fietkau wrote:
> On 2015-08-06 22:10, Linus Lüssing wrote:
> > On Wed, Aug 05, 2015 at 01:38:28PM +0200, Felix Fietkau wrote:
> >> On 2015-08-05 01:00, Linus Lüssing wrote:
> >> > With this patch the multicast_to_unicast feature can be disabled for al
On 2015-08-07 04:28, Mathieu Olivari wrote:
> This patch serie adds support for the integrated NAND flash controller
> available on AP148. Most of the patches are backported from LKML, with
> minor modifications.
>
> This is kernel level support & enablement for now. Support for proper
> MTD parti
In openwrt you are free to configure each and every radio as own unit, so
use whatever SSID you see fit for each radio. This is default basic OpenWrt
stuff :)
Sami Olmati
On Thu, Aug 6, 2015 at 6:59 PM, Afkar Rafique wrote:
> Hi Everyone,
>
> I am working on AR93XX openWrt project. I have to c
17 matches
Mail list logo
