[OpenWrt-Devel] [PATCH][RFC] mtd: bcm47xxpart: lower minimal blocksize to 4Ki (from 64Ki)
Some devices like Netgear WNR1000v3 or WGR614v10 have partitions aligned
to 0x1000. Using bigger blocksize stopped us from detecting some parts.
Signed-off-by: Rafał Miłecki zaj...@gmail.com
---
Most of supported devices use flashes with erasesize 0x1 (64Ki), so
this change shouldn't affect them (no regressions expected).
Any objections?
---
drivers/mtd/bcm47xxpart.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/mtd/bcm47xxpart.c b/drivers/mtd/bcm47xxpart.c
index dfd57a0..948f535 100644
--- a/drivers/mtd/bcm47xxpart.c
+++ b/drivers/mtd/bcm47xxpart.c
@@ -95,8 +95,12 @@ static int bcm47xxpart_parse(struct mtd_info *master,
int possible_nvram_sizes[] = { 0x8000, 0xF000, 0x1, };
bool found_nvram = false;
- if (blocksize = 0x1)
- blocksize = 0x1;
+ /*
+* Some really old flashes (like AT45DB*) had smaller erasesize-s, but
+* partitions were aligned to at least 0x1000 anyway.
+*/
+ if (blocksize 0x1000)
+ blocksize = 0x1000;
/* Alloc */
parts = kzalloc(sizeof(struct mtd_partition) * BCM47XXPART_MAX_PARTS,
--
1.8.4.5
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Hooks on wifi up/down for starting/stopping dependent functionality?
Hi,
I'm trying to start/stop our Wi-Fi sharing daemons [1] in tandem with wifi
up/down. On AA we used to patch /sbin/wifi, but on BB it seems this logic
has moved into netifd and that it may be possible to do it patchless,
perhaps by monitoring ubus for some event?
I tried just doing ubus listen in one shell and then running wifi from
another, but that doesn't give much to go on:
{ ubus.object.remove: {id:-1034588819,path:hostapd.wlan0} }
{ ubus.object.add: {id:-522709706,path:hostapd.wlan0} }
Is it possible to register with netifd or something to get more events?
1. Anyfi.net architecture http://anyfi.net/documentation#architecture
Many thanks,
Johan
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Hooks on wifi up/down for starting/stopping dependent functionality?
* Johan Almbladh j...@anyfi.net [12.11.2014 10:45]: I tried just doing ubus listen in one shell and then running wifi from another, but that doesn't give much to go on: which events do you need? a joining or leaving station? use 'iw event' an upcoming (or going down) interface? use '/etc/hotplug.d/iface/$yourscript' bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Hooks on wifi up/down for starting/stopping dependent functionality?
Thanks, Bastian. If I add a script /etc/hotplug.d/net/ I get up/down events for WLAN interfaces when /sbin/wifi is run. The hotplug scripts receive events for interface names, but they know nothing about the underlying configuration. Is there any way to map a WLAN interface name, e.g. wlan0, to the corresponding UCI config entry in /etc/config/wireless? Johan On Wed, Nov 12, 2014 at 10:53 AM, Bastian Bittorf bitt...@bluebottle.com wrote: * Johan Almbladh j...@anyfi.net [12.11.2014 10:45]: I tried just doing ubus listen in one shell and then running wifi from another, but that doesn't give much to go on: which events do you need? a joining or leaving station? use 'iw event' an upcoming (or going down) interface? use '/etc/hotplug.d/iface/$yourscript' bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] kernel oops with ath9k + shared irqs
Hey openwrt devs!
I'm observing 100% reproducible kernel oopses with a recent openwrt
(tested with trunk and barrier breaker) on a Mikrotik Routerboard RB435
which is equipped with 5 minipci cards. The board boots up fine if all
wifi devices are disabled in /etc/config/wireless and yields the
following interrupt mapping for the wifi devices:
root@OpenWrt:~# dmesg | grep AR9280
[19.34] ieee80211 phy0: Atheros AR9280 Rev:2 mem=0xb000, irq=40
[20.96] ieee80211 phy1: Atheros AR9280 Rev:2 mem=0xb001, irq=41
[22.66] ieee80211 phy2: Atheros AR9280 Rev:2 mem=0xb002, irq=42
[24.37] ieee80211 phy3: Atheros AR9280 Rev:2 mem=0xb003, irq=41
[25.99] ieee80211 phy4: Atheros AR9280 Rev:2 mem=0xb004, irq=42
(full dmesg can be found in [1])
If the devices are enabled in /etc/config/wireless such that no
interrupt is shared (e.g., enabled phy{0,1,2}, phy{0,1,4}, phy{0,2,3},
...) the board continues to operate normally; otherwise (e.g., enabled
phy{1,3}, phy{0,1,2,3}, phy{0,1,2,3,4}, ...) it crashes with a data bus
error, cf. [2] for a full log.
Any ideas?
cheers,
André
[1] http://paste.debian.net/131446/
[2] http://paste.debian.net/131449/
--
Homepage http://andre.gaul.io
GitHub https://github.com/andrenarchy
Twitterhttps://twitter.com/#!/andrenarchy
Diaspora https://diasp.org/u/andrenarchy
(you won't find me on facebook!)
Jabber g...@web-yard.de
PGP Key0x0FA9170E
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] image: default block size for squashfs
On 9 November 2014 10:16, Alexey N. Vinogradov a.n.vinogra...@gmail.com wrote: Where is squashfs ever necessary for initramfs? bcm53xx/image. The ubinize is invoked for any fs (initramfs, squashfs). And, in turn, in ubinize.conf the root.squashfs is reffered. So, if just ask to build initramfs (without any squash, etc.) it will invoke squashing, which would fail without default parameter. Couldn't you make it clear from the beginning? Fix the bcm53xx instead of finding hacky workarounds. -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Configuring ethernet auto-negotiation off, setting speeds explicitly
Thanks for that pointer, Aaron, but it looks like swconfig won't be of use to me, because it's for configuring specific switches (my usage is not a switch - it's the Intel ethernet port directly from the Rangeley SoC). Anyway, for now, I'm planning to write a small helper script that is invoked from from an early startup script, to invoke ethtool directly on the switch ports at startup. If I want to change the negotiation parameters, I'll have to re-invoke that script once for each change. Can't add a hotplug script for this, because those are invoked only after a successful negotiation and link sense. :-/. -Original Message- From: Aaron Z aczlan+open...@gmail.com To: Shankar Unni shankaru...@netscape.net Cc: OpenWrt Development List openwrt-devel@lists.openwrt.org Sent: Tue, Nov 11, 2014 8:21 pm Subject: Re: [OpenWrt-Devel] Configuring ethernet auto-negotiation off, setting speeds explicitly On Tue, Nov 11, 2014 at 9:09 PM, Shankar Unni shankaru...@netscape.net wrote: Is there any way to disable auto-negotiation on an ethernet interface and manually set the speed and duplex parameters for it via netifd? (some equivalent of option autonegotiate 0, etc.?) I couldn't find anything in netifd that would allow us to specify this directly. Failing this, are there any clever tricks that can allow us to do this? Have you looked into swconfig [1]? that looks like it should let you set link speeds on a per port basis. [1] http://wiki.openwrt.org/doc/techref/swconfig Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. — Robert Heinlein, Time Enough for Love ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] /etc/profile: add 'export PYTHONDONTWRITEBYTECODE=1'
Tells Python not to compile the source files.
The default behaviour is for the sources to be compiled
when the sources are run.
On small disks this can fill them up.
Although the performance of Python will suffer (it's not fast
to begin with) it's better to for it to be slow than to fill up
the disk and cause the target to be stuck.
Users can disable this at their own risk/expense/will/etc.
This works on both python and python3.
Signed-off-by: Alexandru Ardelean ardeleana...@gmail.com
---
package/base-files/files/etc/profile | 2 ++
1 file changed, 2 insertions(+)
diff --git a/package/base-files/files/etc/profile
b/package/base-files/files/etc/profile
index 3dd58e1..2655bea 100644
--- a/package/base-files/files/etc/profile
+++ b/package/base-files/files/etc/profile
@@ -6,6 +6,7 @@ export PATH=/usr/bin:/usr/sbin:/bin:/sbin
export HOME=$(grep -e ^${USER:-root}: /etc/passwd | cut -d : -f 6)
export HOME=${HOME:-/root}
export PS1='\u@\h:\w\$ '
+export PYTHONDONTWRITEBYTECODE=1
[ -x /bin/more ] || alias more=less
[ -x /usr/bin/vim ] alias vi=vim || alias vim=vi
@@ -14,3 +15,4 @@ export PS1='\u@\h:\w\$ '
[ -x /usr/bin/arp ] || arp() { cat /proc/net/arp; }
[ -x /usr/bin/ldd ] || ldd() { LD_TRACE_LOADED_OBJECTS=1 $*; }
+
--
1.8.4.5
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] /etc/profile: add 'export PYTHONDONTWRITEBYTECODE=1'
On 2014-11-12 21:08, Alexandru Ardelean wrote: Tells Python not to compile the source files. The default behaviour is for the sources to be compiled when the sources are run. On small disks this can fill them up. Although the performance of Python will suffer (it's not fast to begin with) it's better to for it to be slow than to fill up the disk and cause the target to be stuck. Users can disable this at their own risk/expense/will/etc. This works on both python and python3. Signed-off-by: Alexandru Ardelean ardeleana...@gmail.com I'd prefer patching python/python3 instead of adding workarounds to /etc/profile. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I'd like to donate a Netgear N150 WNR1000 v3
2014-11-11 23:51 GMT-07:00 Rafał Miłecki zaj...@gmail.com: On 11 November 2014 23:26, Alex Henrie alexhenri...@gmail.com wrote: Is no one interested? Come on, I'm offering free hardware to play with ;-) I already have about 10-20 Broadcom based boars in my drawer ;) Not that excited with another one. However I'd be happy to help adding support for WNR1000 v3. Could you attach serial console to it and test some patched OpenWrt builds? It sounds like a fun project, but SGT. Garcia darwinsker...@gmail.com volunteered to work on it, and I have already mailed the device to him. I'm sure SGT. Garcia will contact you for help once he receives the device. Thanks for your work on OpenWrt! -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] /etc/profile: add 'export PYTHONDONTWRITEBYTECODE=1'
Will do it that way. Thanks On Wed, Nov 12, 2014 at 11:01 PM, Felix Fietkau n...@openwrt.org wrote: On 2014-11-12 21:08, Alexandru Ardelean wrote: Tells Python not to compile the source files. The default behaviour is for the sources to be compiled when the sources are run. On small disks this can fill them up. Although the performance of Python will suffer (it's not fast to begin with) it's better to for it to be slow than to fill up the disk and cause the target to be stuck. Users can disable this at their own risk/expense/will/etc. This works on both python and python3. Signed-off-by: Alexandru Ardelean ardeleana...@gmail.com I'd prefer patching python/python3 instead of adding workarounds to /etc/profile. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [kernel] Add support for Iomega StorCenter ix2-200
Signed-off-by: Richard Kunze richard.ku...@web.de --- target/linux/kirkwood/image/Makefile | 3 +++ target/linux/kirkwood/profiles/110-nas.mk | 17 + 2 files changed, 20 insertions(+) diff --git a/target/linux/kirkwood/image/Makefile b/target/linux/kirkwood/image/Makefile index 3852cac..ec1b978 100644 --- a/target/linux/kirkwood/image/Makefile +++ b/target/linux/kirkwood/image/Makefile @@ -135,6 +135,9 @@ Image/InstallKernel/Template/ICONNECT=$(call Image/InstallKernel/Template,iconne Image/BuildKernel/Template/POGOE02=$(call Image/BuildKernel/Template,pogo_e02) Image/InstallKernel/Template/POGOE02=$(call Image/InstallKernel/Template,pogo_e02) +Image/BuildKernel/Template/IOMEGA_IX2_200=$(call Image/BuildKernel/Template,iomega_ix2_200) +Image/InstallKernel/Template/IOMEGA_IX2_200=$(call Image/InstallKernel/Template,iomega_ix2_200) + define Image/BuildKernel $(call Image/BuildKernel/Template/$(PROFILE)) endef diff --git a/target/linux/kirkwood/profiles/110-nas.mk b/target/linux/kirkwood/profiles/110-nas.mk index eff5952..b91368e 100644 --- a/target/linux/kirkwood/profiles/110-nas.mk +++ b/target/linux/kirkwood/profiles/110-nas.mk @@ -84,3 +84,20 @@ POGOE02_UBIFS_OPTS:=-m 2048 -e 126KiB -c 4096 POGOE02_UBI_OPTS:=-m 2048 -p 128KiB -s 512 $(eval $(call Profile,POGOE02)) + +define Profile/IOMEGA_IX2_200 + NAME:=Iomega StorCenter ix2-200 + PACKAGES:= \ + kmod-ata-core kmod-ata-marvell-sata \ + kmod-usb2 kmod-usb-storage \ + uboot-envtools +endef + +define Profile/IOMEGA_IX2_200/Description + Package set compatible with Iomega StorCenter ix2-200 board. +endef + +IOMEGA_IX2_200_UBIFS_OPTS:=-m 512 -e 15872 -c 2048 +IOMEGA_IX2_200_UBI_OPTS:=-m 512 -p 16384 -s 256 + +$(eval $(call Profile,IOMEGA_IX2_200)) -- 1.9.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Configuring ethernet auto-negotiation off, setting speeds explicitly
On Nov 11, 2014 6:09 PM, Shankar Unni shankaru...@netscape.net wrote: Our box has to deal with a few broken external switches that don't auto-negotiate properly. (Our box is based on an Intel Rangeley Atom, with the IGB driver for eth0/1, and we're running BB, more or less - tip of the barrier_breaker branch). Is there any way to disable auto-negotiation on an ethernet interface and manually set the speed and duplex parameters for it via netifd? (some equivalent of option autonegotiate 0, etc.?) I couldn't find anything in netifd that would allow us to specify this directly. Failing this, are there any clever tricks that can allow us to do this? I do not think netifd supports that but one way to do it is to invoke ethtool. That said, it should not be too hard to patch netifd to send the ethtool ioctl() to force the speed/duplex/autoneg on a specific interface I'm guessing this will come down to writing some hotplug scripts to read extra configs from /etc/config/network and invoke ethtool manually.. Right that's what I would do, unless you go patch netifd to do that. Thanks in advance! -- Shankar Unni. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
