[OpenWrt-Devel] [PATCH] Support for jffs2 image in NAND flash
Hi, This patch adds support for building a jffs2 image to go in a NAND flash device with no cleanmarkers. Thanks, Matt 100-jffs2-rootfs-nand.patch Description: 100-jffs2-rootfs-nand.patch ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] 802.11n support for broadcom-wl
Hey, 11ng/11na is confusing for me, there is no something like 11ng/11na outside OpenWrt world (or I'm not aware of :)), there is 11n on 5 ghz band and 11n on 2.4 ghz band so in my opinion band selection is reasonable and means much more for end user. Imo this notation is inconsistent within itself. I mean 11a and 11b or 11g imply the band while 11n does not and needs an extra parameter. Also what happens if you set mode 11g and band to a? Even documenting the extra parameter, telling users when it does apply and when not what its implications are, that it only works with broadcom and only if 11n is available and selected is a hassle and I seriously doubt that it clears anything up. I too think you should stick to the 11ng/11na notation. If you think its too confusing for users it can still be relabelled to 11n (2.4GHz) and 11n (5GHz) in the gui. Correct but I think it should be marked as enabled in LuCI or other UI interfaces. For that we should set the LuCI widget to x.default = x.enabled . ~ Jow ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] Update libmodbus to latest stable release 3.0.2
Patch against backfire branch. Trunk is probably the same.
This patch updates libmodbus from version 2.0.3 to the latest stable
release 3.0.2
I needed modbus RTU and that seemed to be missing in the older version ?
Patch is also attached in case it is corrupt inline here!
Signed-off-by: Simon Gaynor open...@simong.net
Index: feeds/packages/libs/libmodbus/Makefile
===
--- feeds/packages/libs/libmodbus/Makefile (revision 30830)
+++ feeds/packages/libs/libmodbus/Makefile (working copy)
@@ -8,12 +8,12 @@
include $(TOPDIR)/rules.mk
PKG_NAME:=libmodbus
-PKG_VERSION:=2.0.3
+PKG_VERSION:=3.0.2
PKG_RELEASE:=1
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz
PKG_SOURCE_URL:=http://github.com/downloads/stephane/libmodbus/
-PKG_MD5SUM:=0646f3edca6d7783d0356dc2fc4f9f4c
+PKG_MD5SUM:=1aaacce9d9779d3a84f7d1a75774c943
PKG_FIXUP:=libtool
PKG_INSTALL:=1
@@ -39,7 +39,7 @@
$(INSTALL_DIR) $(1)/usr/lib
$(CP) $(PKG_INSTALL_DIR)/usr/lib/libmodbus.{so*,la} $(1)/usr/lib/
$(INSTALL_DIR) $(1)/usr/lib/pkgconfig
- $(CP) $(PKG_INSTALL_DIR)/usr/lib/pkgconfig/modbus.pc
$(1)/usr/lib/pkgconfig/
+ $(CP) $(PKG_INSTALL_DIR)/usr/lib/pkgconfig/libmodbus.pc
$(1)/usr/lib/pkgconfig/
endef
define Package/libmodbus/install
---
Index: feeds/packages/libs/libmodbus/Makefile
===
--- feeds/packages/libs/libmodbus/Makefile (revision 30830)
+++ feeds/packages/libs/libmodbus/Makefile (working copy)
@@ -8,12 +8,12 @@
include $(TOPDIR)/rules.mk
PKG_NAME:=libmodbus
-PKG_VERSION:=2.0.3
+PKG_VERSION:=3.0.2
PKG_RELEASE:=1
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz
PKG_SOURCE_URL:=http://github.com/downloads/stephane/libmodbus/
-PKG_MD5SUM:=0646f3edca6d7783d0356dc2fc4f9f4c
+PKG_MD5SUM:=1aaacce9d9779d3a84f7d1a75774c943
PKG_FIXUP:=libtool
PKG_INSTALL:=1
@@ -39,7 +39,7 @@
$(INSTALL_DIR) $(1)/usr/lib
$(CP) $(PKG_INSTALL_DIR)/usr/lib/libmodbus.{so*,la} $(1)/usr/lib/
$(INSTALL_DIR) $(1)/usr/lib/pkgconfig
- $(CP) $(PKG_INSTALL_DIR)/usr/lib/pkgconfig/modbus.pc $(1)/usr/lib/pkgconfig/
+ $(CP) $(PKG_INSTALL_DIR)/usr/lib/pkgconfig/libmodbus.pc $(1)/usr/lib/pkgconfig/
endef
define Package/libmodbus/install___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] 802.11n support for broadcom-wl
Dnia 2012-03-05, pon o godzinie 22:34 -0800, Nathan Hintz pisze:
On Mon, 2012-03-05 at 19:20 +0100, Łukasz Kwestarz wrote:
+ case $band in
+ a) band=1;;
+ b) band=2;;
+ esac
+
Is a new config option for band required (2.4G/5G) when it can be
derived from the existing channel #?
Right is not required. Maybe this is right way to go instead of
11na/11ng?
case $hwmode in
- *b) hwmode=0;;
- *bg) hwmode=1;;
- *g) hwmode=2;;
- *gst) hwmode=4;;
- *lrs) hwmode=5;;
- *)hwmode=1;;
+ *a) ;;
+ *b) gmode=0;;
+ *bg);;
+ *g) gmode=2;;
+ *gst) gmode=4;;
+ *lrs) gmode=5;;
+ *n)
+ nreqd=1
+ nmode=1
+ ;;
+ *)
+ nmode=-1
+ ;;
esac
for vif in $vifs; do
@@ -322,7 +342,11 @@
wlc ifname $device stdin EOF
$ifdown
-gmode ${hwmode:-1}
+leddc ${leddc}
+band ${band:-0}
+gmode ${gmode}
I realize this is the way it was before, but wlc throws an error when
you try to set gmode to any value (even -1) on a 5G interface (see
ticket #9531). Will any of the new cmd's you are adding throw
additional errors on H/W that doesn't support 11n? For gmode, you
could default it to a null value (5G) or to -1 (2.4G), set it
according to the hwmode (your new code), and then do this:
${gmode:+ gmode $gmode}
Not sure how you would handle the new ones (band, nmode, nreqd) if
they're not supported.
Yes probably it will cause some error messages, but that was not my
concern, already I have some from SSID setting method which in fact
works. But I agree that it should be fixed.
+nmode ${nmode}
+nreqd ${nreqd}
apsta $apsta
ap $ap
${mssid:+mssid $mssid}
@@ -386,6 +410,7 @@
option mode ap
option ssid OpenWrt${i#0}
option encryption none
+ option wmm 1
EOF
done
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] LuCI 802.11n support for broadcom-wl
Dnia 2012-03-05, pon o godzinie 22:39 -0800, Nathan Hintz pisze:
On Mon, 2012-03-05 at 19:30 +0100, Łukasz Kwestarz wrote:
Patch fixes also issue with order of options with dependencies.
Please as previous patch, review it carefully, it was my first time with
lua:).
Signed-off-by: Łukasz Kwestarz kwest...@me.com
Index: modules/admin-full/luasrc/model/cbi/admin_network/wifi.lua
===
--- modules/admin-full/luasrc/model/cbi/admin_network/wifi.lua (wersja
8324)
+++ modules/admin-full/luasrc/model/cbi/admin_network/wifi.lua (kopia
robocza)
@@ -316,12 +316,19 @@
tp:value(p.driver_dbm, %i dBm (%i mW)
%{ p.display_dbm, p.display_mw })
end
+
+ band = s:taboption(advanced, ListValue, band, translate(Radio
Band))
+ if hw_modes.b or hw_modes.g then band:value(b, 2.4 GHz) end
+ if hw_modes.a then band:value(a, 5 GHz) end
mode = s:taboption(advanced, ListValue, hwmode, translate(Mode))
- mode:value(11bg, 802.11b+g)
- mode:value(11b, 802.11b)
- mode:value(11g, 802.11g)
- mode:value(11gst, 802.11g + Turbo)
+ mode:value(auto, Auto)
+ if hw_modes.a then mode:value(11a, 802.11a, {band=a}) end
+ if hw_modes.b then mode:value(11b, 802.11b, {band=b}) end
+ if hw_modes.g then mode:value(11g, 802.11g, {band=b}) end
+ if hw_modes.g then mode:value(11gst, 802.11g + Turbo, {band=b})
end
+ if hw_modes.n and hw_modes.b and hw_modes.g then mode:value(11bg,
802.11b+g, {band=b}) end
Shouldn't the hw_modes.n condition be removed from the line above so
it handles both cases (w/ and w/o 11n)?
It is correct 11bg have no sense when 11n is not supported, it is then
equal to auto.
+ if hw_modes.n then mode:value(11n, 802.11n) end
ant1 = s:taboption(advanced, ListValue, txantenna,
translate(Transmitter Antenna))
ant1.widget = radio
Index: libs/web/luasrc/view/cbi/full_valuefooter.htm
===
--- libs/web/luasrc/view/cbi/full_valuefooter.htm (wersja 8324)
+++ libs/web/luasrc/view/cbi/full_valuefooter.htm (kopia robocza)
@@ -33,7 +33,7 @@
%-
end
-%
- },
cbip-%=self.config..-..section..-..self.option..d.add%);
+ }, %=d.next and
'cbi-'..self.config..-..section..-..self.option..d.next..'' or
null%);
%- end %
% for j, d in ipairs(self.deps) do -%
cbi_d_add(cbi-%=self.config..-..section..-..self.option..d.add%, {
Index: libs/web/luasrc/cbi.lua
===
--- libs/web/luasrc/cbi.lua (wersja 8324)
+++ libs/web/luasrc/cbi.lua (kopia robocza)
@@ -1579,9 +1579,31 @@
val = val or key
table.insert(self.keylist, tostring(key))
table.insert(self.vallist, tostring(val))
+
+ depends = select(#, ...) 0
+ for i, subdep in ipairs(self.subdeps) do
+ if not subdep.next then
+ if not depends then
+ subdep.next = -..key
+ else
+ for j, deps in ipairs({...}) do
+ equal = true;
+ for k, v in pairs(deps) do
+ if subdep.deps[k] ~= v then
+ equal = false
+ break
+ end
+ end
+ if equal then
+ subdep.next = -..key
+ end
+ end
+ end
+ end
+ end
for i, deps in ipairs({...}) do
- self.subdeps[#self.subdeps + 1] = {add = -..key, deps=deps}
+ self.subdeps[#self.subdeps + 1] = {add = -..key, deps = deps}
end
end
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] 802.11n support for broadcom-wl
Dnia 2012-03-06, wto o godzinie 09:59 +0100, Felix Fietkau pisze: On 2012-03-05 11:09 PM, Łukasz Kwestarz wrote: Index: package/broadcom-wl/files/lib/wifi/broadcom.sh === --- package/broadcom-wl/files/lib/wifi/broadcom.sh (wersja 30798) +++ package/broadcom-wl/files/lib/wifi/broadcom.sh (kopia robocza) @@ -161,13 +169,25 @@ ;; esac +case $band in +a) band=1;; +b) band=2;; +esac + case $hwmode in -*b) hwmode=0;; -*bg) hwmode=1;; -*g) hwmode=2;; -*gst) hwmode=4;; -*lrs) hwmode=5;; -*)hwmode=1;; +*a) ;; +*b) gmode=0;; +*bg);; +*g) gmode=2;; +*gst) gmode=4;; +*lrs) gmode=5;; +*n) +nreqd=1 +nmode=1 +;; +*) +nmode=-1 +;; esac for vif in $vifs; do What's lrs? And why gst with turbo - what's that for? And why no support for 11ng/11na similar to how it's done in mac80211? Those two settings were here before, so I didn't paid much attention to them, but you can find them in wl gmode man, also OpenWRT wiki contains few words about. 11ng/11na is confusing for me, there is no something like 11ng/11na outside OpenWrt world (or I'm not aware of :)), there is 11n on 5 ghz band and 11n on 2.4 ghz band so in my opinion band selection is reasonable and means much more for end user. These settings need to be compatible across different drivers. All mac80211 drivers (ath9k, rt2x00) are already using the 11na/11ng modes. Putting in yet another different variant for configuring the same thing is not acceptable. Please make the settings match the documentation in the wiki. - Felix Honestly I don't care how it is done so far, I think it should be done as best as possible and this is my concern. Dnia 2012-03-06, wto o godzinie 13:49 +0100, Jo-Philipp Wich pisze: Hey, 11ng/11na is confusing for me, there is no something like 11ng/11na outside OpenWrt world (or I'm not aware of :)), there is 11n on 5 ghz band and 11n on 2.4 ghz band so in my opinion band selection is reasonable and means much more for end user. Imo this notation is inconsistent within itself. I mean 11a and 11b or 11g imply the band while 11n does not and needs an extra parameter. Also what happens if you set mode 11g and band to a? What happens if user sets 11a and channel 1? or other way. Adding band option doesn't change anything in that case. Even documenting the extra parameter, telling users when it does apply and when not what its implications are, that it only works with broadcom and only if 11n is available and selected is a hassle and I seriously doubt that it clears anything up. I too think you should stick to the 11ng/11na notation. If you think its too confusing for users it can still be relabelled to 11n (2.4GHz) and 11n (5GHz) in the gui. Ok so we will have: 11a 11na 11an = auto band a 11b 11g 11gst 11bg 11ng 11bgn = auto band b in one select box. Really this is the way to go? :) We can as Nathan suggested use channel to distinguish 11na/11ng which is in my opinion better option, but I still think that adding band is best. Correct but I think it should be marked as enabled in LuCI or other UI interfaces. For that we should set the LuCI widget to x.default = x.enabled . ~ Jow Sure, better option, will change. Cheers, Łukasz Kwestarz ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] 802.11n support for broadcom-wl
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Honestly I don't care how it is done so far, I think it should be done as best as possible and this is my concern. We do care how its done so far - and mapping 11ng / 11na seems way simpler to me than introducing an explicit band selection. It also took great pains to somewhat unify the wifi driver config - I have absolutely no desire to handle it differently again. Ok so we will have: 11a 11na 11an = auto band a 11b 11g 11gst 11bg 11ng 11bgn = auto band b in one select box. Really this is the way to go? Only if the radio is actually abgn, On many router platforms there is one radio for 2.4ghz (bgn) and one for 5ghz (an); so you'd have 11b / 11g / 11bg / 11ng and 11a / 11na The other modes (gst, ast, lrs, bgn, ...) have no practical relevance and can be thrown out. Looks way simpler to me than having to set the band manually which is also of no use if the underlying radio is fixed to only one band anyway. :) We can as Nathan suggested use channel to distinguish 11na/11ng which is in my opinion better option, but I still think that adding band is best. Channel may be auto, or dictated by the sta in ap/sta configuration. ~ Jow -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9WTsYACgkQdputYINPTPOQ+wCcCXiDIG3PujSRh6hrEdQ3EH3w eRMAnjNp6pMepYwRpO9voDvxEaUIZUQR =yYXO -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] 802.11n support for broadcom-wl
Dnia 2012-03-06, wto o godzinie 18:52 +0100, Jo-Philipp Wich pisze: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Honestly I don't care how it is done so far, I think it should be done as best as possible and this is my concern. We do care how its done so far - and mapping 11ng / 11na seems way simpler to me than introducing an explicit band selection. It also took great pains to somewhat unify the wifi driver config - I have absolutely no desire to handle it differently again. Ok so we will have: 11a 11na 11an = auto band a 11b 11g 11gst 11bg 11ng 11bgn = auto band b in one select box. Really this is the way to go? Only if the radio is actually abgn, On many router platforms there is one radio for 2.4ghz (bgn) and one for 5ghz (an); so you'd have 11b / 11g / 11bg / 11ng and 11a / 11na The other modes (gst, ast, lrs, bgn, ...) have no practical relevance and can be thrown out. Looks way simpler to me than having to set the band manually which is also of no use if the underlying radio is fixed to only one band anyway. :) We can as Nathan suggested use channel to distinguish 11na/11ng which is in my opinion better option, but I still think that adding band is best. Channel may be auto, or dictated by the sta in ap/sta configuration. ~ Jow Ok ok, I will do it your way:). Cheers, Łukasz Kwestarz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9WTsYACgkQdputYINPTPOQ+wCcCXiDIG3PujSRh6hrEdQ3EH3w eRMAnjNp6pMepYwRpO9voDvxEaUIZUQR =yYXO -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] multiwan package: use less iptables -F
Hi
Even if qos-scripts package isn't installed, multiwan is flushing all the
mangle chains.
This patch correct this behavior to let people use mangle table if qos-scripts
is not there (to use there own qos script ...)
Info: For the moment the qos management of the multiwan package is broken (it's
speaks about IMQ, instead of IFB)
The package version go from 1.0.20 to 1.0.21 (and not 1.0.19) because there is
this patch also pending (http://patchwork.openwrt.org/patch/1740/)
Signed-off-by: Etienne CHAMPETIER etienne.champet...@free.fr
diff --git a/net/multiwan/Makefile b/net/multiwan/Makefile
index 76c61d8..bed8e6f 100644
--- a/net/multiwan/Makefile
+++ b/net/multiwan/Makefile
@@ -8,7 +8,7 @@
include $(TOPDIR)/rules.mk
PKG_NAME:=multiwan
-PKG_VERSION:=1.0.20
+PKG_VERSION:=1.0.21
PKG_RELEASE:=1
include $(INCLUDE_DIR)/package.mk
diff --git a/net/multiwan/files/usr/bin/multiwan
b/net/multiwan/files/usr/bin/multiwan
index c2fb3ab..75b2a2f 100755
--- a/net/multiwan/files/usr/bin/multiwan
+++ b/net/multiwan/files/usr/bin/multiwan
@@ -257,10 +257,10 @@ clear_rules() {
local restore_single=$1
local group
-iptables -t mangle -F PREROUTING
-iptables -t mangle -F FORWARD
-iptables -t mangle -F POSTROUTING
-iptables -t mangle -F OUTPUT
+iptables -t mangle -D PREROUTING -j MultiWan
+iptables -t mangle -D FORWARD -j MultiWan
+iptables -t mangle -D OUTPUT -j MultiWan
+iptables -t mangle -D POSTROUTING -j MultiWan
iptables -t mangle -F MultiWan
iptables -t mangle -X MultiWan
iptables -t mangle -F MultiWanRules
@@ -285,6 +285,10 @@ clear_rules() {
done
if [ ! -z $CHKFORQOS ]; then
+ iptables -t mangle -F PREROUTING
+ iptables -t mangle -F FORWARD
+ iptables -t mangle -F OUTPUT
+ iptables -t mangle -F POSTROUTING
iptables -t mangle -F MultiWanQoS
iptables -t mangle -X MultiWanQoS
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] parted disc partitioning utility
I haven't heard much from anyone. Are there any comments, any pointers on what I need to fix? Clark On Sun, 2012-03-04 at 17:43 -0500, Clark Rawlins wrote: This is a brown paper bag update of my previous patch. = Include the parted disc partitioning utility As disc drives can exceed 2TB in size the MSDOS partition table is not able to partition the entire drive. Adding the parted utility to openwrt makes it possible to manipulate the partition tables of EFI/GUID on a openwrt device. To use a EFI/GUID partition it is necessary to have support in the kernel for this partition type. So configuration options are available to enable EFI support. Signed-of-by: Clark Rawlins cl...@bit63.org Index: package/parted/Config.in === --- package/parted/Config.in (revision 0) +++ package/parted/Config.in (revision 0) @@ -0,0 +1,45 @@ +config KERNEL_AMIGA_PARTITION + bool Amiga partition table support + default n + +config KERNEL_MAC_PARTITION + bool Macintosh partition map support + default n + help + Say Y here if you would like to use hard disks under Linux which + were partitioned on a Macintosh. + +config KERNEL_MSDOS_PARTITION + bool PC BIOS (MSDOS partition tables) support + default n + +config KERNEL_BSD_DISKLABEL + depends KERNEL_MSDOS_PARTITION + bool BSD disklabel (FreeBSD partition tables) support + default n + help + FreeBSD uses its own hard disk partition scheme on your PC. It + requires only one entry in the primary partition table of your disk + and manages it similarly to DOS extended partitions, putting in its + first sector a new partition table in BSD disklabel format. Saying Y + here allows you to read these disklabels and further mount FreeBSD + partitions from within Linux if you have also said Y to UFS + file system support, above. If you don't know what all this is + about, say N. + +config KERNEL_SOLARIS_X86_PARTITION + depends KERNEL_MSDOS_PARTITION + bool Solaris (x86) partition table support + default n + help + Like most systems, Solaris x86 uses its own hard disk partition + table format, incompatible with all others. Saying Y here allows you + to read these partition tables and further mount Solaris x86 + partitions from within Linux if you have also said Y to UFS + file system support, above. + +config KERNEL_EFI_PARTITION + bool Enable EFI Partition parsing support in the kernel +default n + + Index: package/parted/Makefile === --- package/parted/Makefile (revision 0) +++ package/parted/Makefile (revision 0) @@ -0,0 +1,58 @@ +# +# Copyright (C) 2012 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# +include $(TOPDIR)/rules.mk + +PKG_NAME:=parted +PKG_VERSION:=2.4 +PKG_RELEASE:=1 + +PKG_BUILD_DIR:=$(BUILD_DIR)/parted-$(PKG_VERSION) +PKG_SOURCE:=parted-$(PKG_VERSION).tar.gz +PKG_SOURCE_URL:=@GNU/parted +PKG_MD5SUM:=76a6457ea88447d79d50ca331069b19c +PKG_CAT:=zcat + +include $(INCLUDE_DIR)/package.mk + +define Package/parted + SECTION:=utils + CATEGORY:=Utilities + SUBMENU:=disc + DEFAULT:=n + TITLE:=GNU Parted manipulates partition tables + URL:=http://www.gnu.org/software/parted/ + DEPENDS:= +libuuid +libreadline +libncurses +libdevmapper +endef + +define Package/parted/description + GNU Parted manipulates partition tables. This is useful for creating + space for new operating systems, reorganizing disk usage, copying data + on hard disks and disk imaging. The package contains a library, + libparted, as well as well as a command-line frontend, parted, + which can also be used in scripts. +endef + +define Package/parted/config + source $(SOURCE)/Config.in +endef + +define Build/Configure + $(call Build/Configure/Default, \ +--enable-static \ +) +endef + +define Package/parted/install + $(INSTALL_DIR) $(1)/usr/lib + $(INSTALL_BIN) $(PKG_BUILD_DIR)/libparted/.libs/libparted.so.0 $(1)/usr/lib + $(INSTALL_BIN) $(PKG_BUILD_DIR)/libparted/.libs/libparted.so.0 $(1)/usr/lib + $(INSTALL_BIN) $(PKG_BUILD_DIR)/libparted/.libs/libparted.so.0.0.2 $(1)/usr/lib + $(INSTALL_DIR) $(1)/usr/sbin + $(INSTALL_BIN) $(PKG_BUILD_DIR)/parted/.libs/parted $(1)/usr/sbin/ +endef + +$(eval $(call BuildPackage,parted)) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___
Re: [OpenWrt-Devel] [PATCH] parted disc partitioning utility
On Tue, Mar 6, 2012 at 4:39 PM, Clark Rawlins cl...@bit63.org wrote: I haven't heard much from anyone. Are there any comments, any pointers on what I need to fix? Clark just be patient, me or someone else will get to it On Sun, 2012-03-04 at 17:43 -0500, Clark Rawlins wrote: This is a brown paper bag update of my previous patch. = Include the parted disc partitioning utility As disc drives can exceed 2TB in size the MSDOS partition table is not able to partition the entire drive. Adding the parted utility to openwrt makes it possible to manipulate the partition tables of EFI/GUID on a openwrt device. To use a EFI/GUID partition it is necessary to have support in the kernel for this partition type. So configuration options are available to enable EFI support. Signed-of-by: Clark Rawlins cl...@bit63.org Index: package/parted/Config.in === --- package/parted/Config.in (revision 0) +++ package/parted/Config.in (revision 0) @@ -0,0 +1,45 @@ +config KERNEL_AMIGA_PARTITION + bool Amiga partition table support + default n + +config KERNEL_MAC_PARTITION + bool Macintosh partition map support + default n + help + Say Y here if you would like to use hard disks under Linux which + were partitioned on a Macintosh. + +config KERNEL_MSDOS_PARTITION + bool PC BIOS (MSDOS partition tables) support + default n + +config KERNEL_BSD_DISKLABEL + depends KERNEL_MSDOS_PARTITION + bool BSD disklabel (FreeBSD partition tables) support + default n + help + FreeBSD uses its own hard disk partition scheme on your PC. It + requires only one entry in the primary partition table of your disk + and manages it similarly to DOS extended partitions, putting in its + first sector a new partition table in BSD disklabel format. Saying Y + here allows you to read these disklabels and further mount FreeBSD + partitions from within Linux if you have also said Y to UFS + file system support, above. If you don't know what all this is + about, say N. + +config KERNEL_SOLARIS_X86_PARTITION + depends KERNEL_MSDOS_PARTITION + bool Solaris (x86) partition table support + default n + help + Like most systems, Solaris x86 uses its own hard disk partition + table format, incompatible with all others. Saying Y here allows you + to read these partition tables and further mount Solaris x86 + partitions from within Linux if you have also said Y to UFS + file system support, above. + +config KERNEL_EFI_PARTITION + bool Enable EFI Partition parsing support in the kernel +default n + + Index: package/parted/Makefile === --- package/parted/Makefile (revision 0) +++ package/parted/Makefile (revision 0) @@ -0,0 +1,58 @@ +# +# Copyright (C) 2012 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# +include $(TOPDIR)/rules.mk + +PKG_NAME:=parted +PKG_VERSION:=2.4 +PKG_RELEASE:=1 + +PKG_BUILD_DIR:=$(BUILD_DIR)/parted-$(PKG_VERSION) +PKG_SOURCE:=parted-$(PKG_VERSION).tar.gz +PKG_SOURCE_URL:=@GNU/parted +PKG_MD5SUM:=76a6457ea88447d79d50ca331069b19c +PKG_CAT:=zcat + +include $(INCLUDE_DIR)/package.mk + +define Package/parted + SECTION:=utils + CATEGORY:=Utilities + SUBMENU:=disc + DEFAULT:=n + TITLE:=GNU Parted manipulates partition tables + URL:=http://www.gnu.org/software/parted/ + DEPENDS:= +libuuid +libreadline +libncurses +libdevmapper +endef + +define Package/parted/description + GNU Parted manipulates partition tables. This is useful for creating + space for new operating systems, reorganizing disk usage, copying data + on hard disks and disk imaging. The package contains a library, + libparted, as well as well as a command-line frontend, parted, + which can also be used in scripts. +endef + +define Package/parted/config + source $(SOURCE)/Config.in +endef + +define Build/Configure + $(call Build/Configure/Default, \ +--enable-static \ +) +endef + +define Package/parted/install + $(INSTALL_DIR) $(1)/usr/lib + $(INSTALL_BIN) $(PKG_BUILD_DIR)/libparted/.libs/libparted.so.0 $(1)/usr/lib + $(INSTALL_BIN) $(PKG_BUILD_DIR)/libparted/.libs/libparted.so.0 $(1)/usr/lib + $(INSTALL_BIN) $(PKG_BUILD_DIR)/libparted/.libs/libparted.so.0.0.2 $(1)/usr/lib + $(INSTALL_DIR) $(1)/usr/sbin + $(INSTALL_BIN) $(PKG_BUILD_DIR)/parted/.libs/parted $(1)/usr/sbin/ +endef + +$(eval $(call BuildPackage,parted)) ___ openwrt-devel mailing list
[OpenWrt-Devel] Openwrt, New unsupported routers, AR7161 and AR5312A Chip-sets. porting tips.
Hello, I'm a bit new at this stuff so i've been trying to figure out how to get openwrt working on some routers i've managed to get my hands on. I'm affiliated with an organization who is organizing up-cycling hacking sessions with a local middle school. We maintain close ties with the local UNI (my Alma mater) and got permission from the sysadmin to go through the tech waste disposal and take whatever we wanted. After loading up on broken ink-jets and other neat electro-mechanical junk i noticed a decent sized bin full of APs. Apparently the Network Operations guys are upgrading the campus wireless network and just dumping the APs. I grabbed two on the off chance that we might be able to do something with em, at the very least crack it open and talk about board layout a little or pull out some LEDs or LDOs or something. So, When i got a chance I cracked two of the routers open and was a little surprised. There are two models of routers, Large Square ones (Trapeze MP-82s) and small puck-shaped round ones (Nortel 2330). The Square had an Atheros AR7161 and two 66 pin TSSOP DDR SDRAMS with a serial-flash. In addition to this, There where pads for a USB Host port that wasn't populated. There was a rj-45 connector labeled management interface that sat behind a rs232 level shiftier so i think that's a serial port. There was also a 14 pin connector in the vicinity of the CPU that looks a lot like a MIPS-EJTAG-2.5 14-pin interface. Grounds in all the right places. I did a search and it looks like this SOC is quite popular but no openwrt port for this router. The puck had a Atheros AR5312A one TSSOP DDR SDRAM and a parallel NAND Flash. I powered the thing on via a POE injector and started poking around, I found what looks like a MIPS-EJTAG-2.5 connector with the grounds in the right places and a reset pin that resets the router when pulled low. And i found a 3.3v serial port that informs me that the device is quite confused and upset because the Ethernet link is not up and it can't phone home for firmware but it doesn't look like u-boot and has no prompt. pics of me bringing up the puck and pics of the square's PCB here. http://acamilo.tumblr.com/post/18833966874/wireless-router-fun-time So, me and some friends went back and took a whole bunch of both kinds and i'm going to try to get openwrt running on them 'cause it might be kind of fun to make a robot out of these. I've installed buildroot in a VM using the instructions on ( http://wiki.openwrt.org/doc/howto/buildroot.exigence) got make menuconvig going. selected Target System (Atheros AR7xxx/AR9xxx) --- and i have my box chugging away running make -j 5 Since both of these boards and their supported cousins probably descent from the same reference designs How hard would it be to get these guys running. I've never done that before. Would you recommend trying to JTAG them with a similar router's u-boot and trying to boot over tftp? Do you have any pointers, tips? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
