17 23:48:00.407189000 +0800
> @@ -192,6 +192,7 @@
>
> ;;
>
> rt-n13u | \
> +hg256d| \
> fonera20n)
??
Doesn't seem all too right to me...
HTH,
Andreas Mohr
___
openwrt-devel mailing list
openwrt-
f-by: Michael Wileczka
Cc: stable
Signed-off-by: Greg Kroah-Hartman
might be a good example of where to find and how to treat such issues.
HTH,
Andreas Mohr
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
ome per-cputype comments to this
helper why (or why not) a certain CPU is thought to be (non-)coherent
(with a most authoritative reference added each if available, ideally!).
Thanks,
Andreas Mohr
___
openwrt-devel mailing list
openwrt-devel@lists.ope
directly,
if one cannot/does not want to have an explicite init line.
I.e., something like:
-F|--force) export FORCE="$((${FORCE:-0} + 1))";;
OTOH intermingling potential-init plus increment in one line
can be considered weird at a minimum.
So the best design would perhaps be
On Sun, Dec 15, 2013 at 01:49:47AM -0800, Cody P Schafer wrote:
> We already initialize FORCE to 0 at the top of the 'sysupgrade' script.
>
> export HELP=0
> export FORCE=0
> export TEST=0
Ah ok, nevermind then :)
(didn't have ready access to sourc
quot;bt"-type mail implicitly included ;)
Thanks for this very nice puzzle piece,
Andreas Mohr
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
OK, well, round robin, but...
(admittedly once every 5 minutes ought to be low enough,
but certain people might want to keep down flash wear as much as possible).
> bye, bastian
Andreas Mohr
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt
Hi,
[CC openwrt-devel, remove linux-kernel]
On Mon, Jan 06, 2014 at 03:09:27PM +0100, Johannes Berg wrote:
> On Mon, 2014-01-06 at 15:01 +0100, Andreas Mohr wrote:
>
> > config LIB80211
> > tristate
>
> > config LIB80211_CRYPT_WEP
> >
ty
expected to be standard by upstream, which in itself is worrisome already.
Also, what kind of space savings are we talking about here anyway?
I cannot imagine these measly strings to constitute a sufficiently high
percentage of module size...
(except for drastic candidates such as VI
Signed-off-by: Andreas Mohr
---
package/network/config/swconfig/src/cli.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Reason: standard switch device name changed from eth0 to switch0,
see e.g.
http://wiki.openwrt.org/toh/buffalo/wbmr-hp-g300h#wired.stations.cannot.ping.each.other
I
On Tue, Jan 07, 2014 at 10:27:40AM +0100, Nicolas Cavallari wrote:
> On 06/01/2014 20:18, Andreas Mohr wrote:
> > Can someone else confirm and/or elaborate on this improper visibility
> > problem
> > which seems to be specific to OpenWrt's kernel configuration mana
Hi,
On Mon, Jan 06, 2014 at 11:16:34PM +0100, Andreas Mohr wrote:
> Thus, while OpenWrt itself perhaps does not have much use for udev-based
> auto loading of modules (I guess modules usually are installed per-package,
> and then probably also registered for mechanical loading each),
&
to try to avoid hardware damage.
And of course: thanks for your nice support patch!
Andreas Mohr
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
ffected traces?
(not sure whether there would be any effect at such scale, but without
trying there's no knowledge...)
Given that the PCB's layout is completely broken already,
matters probably cannot get worse :)
Disclaimer: _not_ an experienced EDA engineer here :)
Andreas Mohr
reverting to 2.6.28.10 now (would anyone by chance know my odds
there?), but I'll first submit some 2.6.30 quilt stuff.
Working on brcm47xx (ASUS WL-500gP v2, external USB boot).
HTH,
Andreas Mohr
___
openwrt-devel mailing list
openwrt-devel@li
Hi,
first post. Please yell if something is awkward.
Acked-by: Andreas Mohr
--- /dev/null 2009-05-14 19:20:59.0 +0200
+++
target/linux/generic-2.6/patches-2.6.30/695-b44_netconsole_poll_bogus-irq-enable_fix.patch
2009-11-24 22:27:52.0 +0100
@@ -0,0 +1,67 @@
+From patchwork
More stuff to follow later.
Signed-off-by: Andreas Mohr
--- /dev/null 2009-05-14 19:20:59.0 +0200
+++
target/linux/generic-2.6/patches-2.6.30/696-b44_fix-wedge-when-using-netconsole.patch
2009-11-30 20:12:53.0 +0100
@@ -0,0 +1,58 @@
+From patchwork Mon Nov 30 08:15:41
ld find its way into mainline
pretty soon,
since this entire matter simply was a trivial but sadly effectful out-of-sync
with mainline issue.
Any thoughts?
Thanks,
Andreas Mohr
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
On Tue, Dec 22, 2009 at 11:16:35PM +0100, Michael Buesch wrote:
> On Tuesday 22 December 2009 22:29:32 Andreas Mohr wrote:
> > Now that this annoying issue is out of the way, how to go forward?
>
> By sending a patch?
Not the worst way to deal with it, admittedly.
> >
Hi,
On Fri, Dec 25, 2009 at 12:02:06PM -0700, Steve Brown wrote:
> On 12/23/2009 01:57 AM, Andreas Mohr wrote:
>>>> And I would be very pleased if ehci-ssb.c could find its way into mainline
>>>> pretty soon,
>>>>
>>> Yeah. Care to do so
ese devices to fail after the first close() due to these
missing cleanup callbacks. Works with that fix.
I wanted to get this ticket nailed, but it got delayed due to working on a
(even more relevant) resume issue on my (current) main machine.
Andreas Mohr
__
use %lu (or better %llu?) for
higher probability to get the correct value.
OTOH since an IPv4 address will always remain 32bit, %u is fully
sufficient and thus the exactly adapted and proper solution.
HTH,
Andreas Mohr
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
22 matches
Mail list logo
