+1 for "Designated Driver"
On 15-04-07 12:47 PM, Hartmut Knaack wrote:
That Doodle poll turned out to be spamed/trolled, and everyone could even
change or delete other votes. Since this was just communicated over this
mailing list, and subscribers are at least basically verified, why not have a
Updated patch that fixes whitespace and supports kernel v3.3 too.
Signed-off-by: Owen Kirby
---
package/kernel/linux/modules/usb.mk | 38 ++---
target/linux/generic/config-3.18| 1 +
2 files changed, 24 insertions(+), 15 deletions(-)
diff --git a/package
On 15-02-19 05:48 PM, Daniel Golle wrote:
On Thu, Feb 19, 2015 at 02:41:57PM -0800, Owen Kirby wrote:
...
+ifeq ($(CONFIG_LINUX_3_8)$(CONFIG_LINUX_3_10),)
Note that there are (unfortunately) still targets stuck on 3.3.
I doubt that this is relevant, but as that whole legacy section
can most
arate subdirectories.
Signed-off-by: Owen Kirby
---
package/kernel/linux/modules/usb.mk | 42 ++---
target/linux/generic/config-3.18| 1 +
2 files changed, 26 insertions(+), 17 deletions(-)
diff --git a/package/kernel/linux/modules/usb.mk
b/package/kernel/linux/modules/u
Signed-off-by: Owen Kirby
---
.../at91/files/arch/arm/boot/dts/at91-q5xr5.dts| 193 +
target/linux/at91/image/Makefile | 4 +
.../patches/101-ARM-at91-build-dtb-for-q5xr5.patch | 10 ++
3 files changed, 207 insertions(+)
create mode 100644 target
Signed-off-by: Owen Kirby
---
target/linux/at91/config-default | 8
1 file changed, 8 insertions(+)
diff --git a/target/linux/at91/config-default b/target/linux/at91/config-default
index 89a9fc2..6972e80 100644
--- a/target/linux/at91/config-default
+++ b/target/linux/at91/config
Signed-off-by: Owen Kirby
---
target/linux/at91/Makefile | 4 +-
target/linux/at91/config-default | 8 ---
target/linux/at91/modules.mk | 18 +
.../100-ARM-at91-build-dtb-for-LMU5000.patch | 2 +-
.../200-ARM-at91-udc
was broken from changes in clock registration in
3.18,
so I have backported a patch to the at91_udc driver posted to the
linux-arm-kernel
mailing list a few months ago.
This was tested on an AT91SAM9G20-EK and an Exegin Q5x board.
Owen Kirby (3):
at91: Enable power and reset controller
The directory layout of the USB gadget subsystem changed between kernels 3.14
and
3.18, so the makefile for kmod-usb-eth-gadget and kmod-usb-serial-gadget need to
be adjusted to match.
Signed-off-by: Owen Kirby
---
package/kernel/linux/modules/usb.mk | 28 ++--
target
John,
I have been working with the AT91 target with a few boards, one of which
is our own custom Q70 board (http://www.exegin.com/pdf/q70_v01.pdf - if
you will pardon the crummy datasheet), and I have also been testing the
generic AT91 images on the Atmel AT91SAM9G20-EK.
We don't have any bo
John,
On 15-01-19 10:34 PM, John Crispin wrote:
On 20/01/2015 01:21, Owen Kirby wrote:
Add hotplug support for tty devices in /etc/inittab that are specified
by the askfirst
keyword so that terminals attached after boot time get console processes
started.
This was tested on an AT91 target
possible weirdness I encountered was that the
baud rates
and control modes sometimes need adjusting with a hotplug script after
reconnecting
the adapter. This is also only implemented for askfirst, but it might also make
sense
to do the same thing for respawn and askconsole.
Signed-off-by: Owen Kirby
magic delays is a no go
On 16/01/2015 04:15, Owen Kirby wrote:
If a process with a tty is specified in inittab, delay the worker
process until the tty exists.
This allows starting consoles with terminals that get delayed until
after procd is reads inittab,
and it also allows hotplugging USB-to-s
: Owen Kirby
---
inittab.c | 14 ++
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/inittab.c b/inittab.c
index 623103d..73c113f 100644
--- a/inittab.c
+++ b/inittab.c
@@ -99,9 +99,15 @@ static void fork_worker(struct init_action *a)
if (!a->proc.
Michel,
Thanks for the suggestion, this particular driver was being loaded from
/etc/modules.d, however even when I moved it into /etc/modules-boot.d it
still doesn't create /dev/ttyGS0 in time for procd to start the console.
I'll try fiddling around with the load order to see if I can get it
wo
On 15-01-09 09:51 AM, Karl Palsson wrote:
"Stam, Michel [FINT]" wrote:
This, to me, seems the most logical solution, as consoles should be
available to the init process early on during boot, and not hot-plugged
in afterwards. Do you agree?
Well, I don't. What about a usb serial port? I'd
Hi,
I'm not sure if this is a bug with procd's implementation of inittab or
if I'm just doing something wrong in my inittab. However, we have a
board that has multiple serial console ports, one of which relies on a
kernel module and procd refuses to start a console on the second port.
What se
It's been a while since I submitted this to the mailing list. Has anyone
had an opportunity to take a look at this patch? Anything I can do to
help move it forward?
Thanks,
Owen
On 14-06-11 02:38 PM, Owen Kirby wrote:
The AT91 family of SoCs have a USB device controller, this patch
s
On 14-07-16 08:09 AM, Gert Doering wrote:
Hi,
This actually is a somewhat moot arguments. Devices travel today, and
while your home network and office network might be behind a firewall,
the hotspot you're using while waiting for your train might not be.
So with todays devices, every device n
, though, the 'debug' network interface in the default config
is rather
useless.
Signed-off-by: Owen Kirby
---
diff --git a/target/linux/at91/Makefile b/target/linux/at91/Makefile
index 8340d2a..9aed19f 100644
--- a/target/linux/at91/Makefile
+++ b/target/linux/at91/Makefile
@@ -10,13 +10,
On 14-05-22 06:01 AM, Yousong Zhou wrote:
> I saw that link too when I found the pvpn project. If I understand
> the theory correctly, the problem is mainly that TCP as a
> connection-oriented protocol is not suitable for being used in
> long-alive, lossy environment because once the underlying co
JFFS2 is complaining that the partition you told it to mount is
essentially full of junk. JFFS2 is expecting there to be one of two
things in the partition that you tried to mount:Erased flash (which
would be full of nothing but 0xff bytes), or a valid JFFS2 image,
instead it's finding a bunch of d
On 14-05-08 11:09 PM, Luka Perkov wrote:
> On Thu, May 08, 2014 at 02:07:13PM -0700, Matthew Fatheree wrote:
>> From 4a9565f1139fbb585727638fd69a0437bdd212b6 Mon Sep 17 00:00:00 2001
>> From: Matthew Fatheree
>> Date: Sun, 4 May 2014 19:04:04 +0700
>> Subject: [PATCH 15/30] mamba mvebu: add fw_pri
s.
Cheers,
Owen
On 14-05-06 12:07 AM, Rafał Miłecki wrote:
> On 5 May 2014 19:59, Owen Kirby wrote:
>> I've got a WNDR3700v3 that I can try your patches on, but it's based on
>> the BCM4718A1 rather than the BCM4718 in the WNR3500L. Would that be
>> close enough fo
I've got a WNDR3700v3 that I can try your patches on, but it's based on
the BCM4718A1 rather than the BCM4718 in the WNR3500L. Would that be
close enough for you to work with?
Cheers,
Owen
On 14-05-05 05:50 AM, Rafał Miłecki wrote:
> Hi,
>
> A month ago we've pushed a patch for ethernet driver "b
A /64 prefix and SLAAC can only really be applied to a single link in
your network, so if you wanted to separate your network into multiple
links (ie: not bridging) then you would use a shorter prefix to get the
routing right between each of those links.
For example, the IPv6 prefix generated by y
This patch adds support for building the kernel modules for gadget serial
devices.
Signed-off-by: Owen Kirby
---
package/kernel/linux/modules/usb.mk | 26 ++
1 file changed, 26 insertions(+)
diff --git a/package/kernel/linux/modules/usb.mk
b/package/kernel/linux
This patch adds support for building support for cramfs filesystems as a kernel
module.
Signed-off-by: Owen Kirby
---
package/kernel/linux/modules/fs.mk | 14 ++
1 file changed, 14 insertions(+)
diff --git a/package/kernel/linux/modules/fs.mk
b/package/kernel/linux/modules
A difference in tx power like that is usually caused by the presence of an
external power amplifier on the board between the SoC and the antenna that
isn't getting turned on, or otherwise misconfigured.
Cheers,
Owen
On Sunday, April 20, 2014, Matthias Schiffer
wrote:
> Hi,
> I recently contribu
>From 272f548fe8d0b811e0589e535f650f0507f6bccd Mon Sep 17 00:00:00 2001
From: Owen Kirby
Date: Fri, 11 Apr 2014 17:59:55 -0700
Subject: [PATCH 2/3] [at91] AT91SAM9G20-EK fixes.
While testing the 3.10 kernel update, I found that the out-of-the-box device
tree for the
the AT91SAM9G20EK use
>From 9158e3282db592e78fb32a2c8a0903ef21b97f5c Mon Sep 17 00:00:00 2001
From: Owen Kirby
Date: Fri, 11 Apr 2014 18:28:56 -0700
Subject: [PATCH 3/3] [at91] Add AT91 board and model name to /tmp/sysinfo.
This patch extracts the board name and model information from the
/proc/device-tree
node
>From 2064e6d069ec8df7f5e988547fe7f2a1a7ad890f Mon Sep 17 00:00:00 2001
From: Owen Kirby
Date: Thu, 10 Apr 2014 19:02:15 -0700
Subject: [PATCH 1/3] [at91] Update AT91 kernel to 3.10.34.
This patch updates the kernel of the AT91 target to version 3.10.34.
Signed-off-by: Owen Kirby
---
tar
Hey Ken,
I seem to recall running into some similar issues the last time I found
myself writing some interface scripts for a custom tunnel. Our
particular protocol was tunnelling some IPv6 stuff over a serial port,
and we ran into the following two issues in getting the netifd scripts
to work as e
checkout fixes this problem.
Signed-off-by: Owen Kirby
---
Index: include/download.mk
===
--- include/download.mk (revision 37237)
+++ include/download.mk (working copy)
@@ -88,7 +88,7 @@
rm -rf $(SUBDIR) && \
On 13-03-09 09:41 PM, Owen Kirby wrote:
> This patch adds userspace support for the Exegin Q5x family of boards.
>
> Hopefully I've managed to do this without interfering with the
> existing AT91 targets.
>
> Signed-off-by: Owen Kirby
It appears that I made an error in my p
On 13-03-19 11:27 PM, Rafał Miłecki wrote:
> 2013/3/20 Owen Kirby :
>> I recently picked up a WNDR3700 to put OpenWRT on, and only after tearing
>> into the box did I find it
>> was one of the v3 boards, with poor OpenWRT support. This patch should add
>> the board
On 13-03-19 11:27 PM, Rafał Miłecki wrote:
> 2013/3/20 Owen Kirby :
>> I recently picked up a WNDR3700 to put OpenWRT on, and only after tearing
>> into the box did I find it
>> was one of the v3 boards, with poor OpenWRT support. This patch should add
>> the board
the
bootloader and stock firmware will accept.
The changes to the broadcom-diag module are more than a few lines because the
WNDR3700v3 is driving
its LEDs through an HC164 8-bit shift register.
Signed-off-by: Owen Kirby
Index: target/linux/brcm47xx/image/Makefile
This adds Configuration changes to support the Exegin Q5x family of boards.
Signed-off-by: Owen Kirby
Index: target/linux/at91/9g20/config-default
===
--- target/linux/at91/9g20/config-default (revision 35893)
+++ target
This adds Makefile changes to support the Exegin Q5x family of boards.
Signed-off-by: Owen Kirby
Index: target/linux/at91/Makefile
===
--- target/linux/at91/Makefile (revision 35893)
+++ target/linux/at91/Makefile (working copy
This adds userspace support for the Exegin Q5x family of boards.
Signed-off-by: Owen Kirby
Index: target/linux/at91/base-files/lib/at91.sh
===
--- target/linux/at91/base-files/lib/at91.sh(revision 0)
+++ target/linux/at91/base
This adds kernel support for the Exegin Q5x family of boards.
Signed-off-by: Owen Kirby
Index: target/linux/generic/patches-3.3/980-arm_openwrt_machtypes.patch
===
--- target/linux/generic/patches-3.3/980
42 matches
Mail list logo
