[OpenWrt-Devel] [PATCH] update tor package
hi, updates the tor package to 2.0.35. I wrote the webmasters of tor that they should please put the current release into their archive, too. so the package does not break whenever a new release is done… but no change yet. regards poelzi Index: net/tor/Makefile === --- net/tor/Makefile (revision 16848) +++ net/tor/Makefile (working copy) @@ -8,12 +8,12 @@ include $(TOPDIR)/rules.mk PKG_NAME:=tor -PKG_VERSION:=0.2.0.34 +PKG_VERSION:=0.2.0.35 PKG_RELEASE:=1 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz PKG_SOURCE_URL:=http://www.torproject.org/dist/ -PKG_MD5SUM:=f20011be23d5a76988233df12c346f41 +PKG_MD5SUM:=d4841e1b4d54866495fd373e865b2d44 include $(INCLUDE_DIR)/package.mk ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] sysupgrade-ext2 sync before writing image, not after
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks for submitting the patch! It's applied to trunk in r16867 and merged to 8.09 in r16868. ~ JoW -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpfLuYACgkQdputYINPTPP7FwCgo1f49MVp1wLyP8NofiS2kFyG /2IAn3Q4HFM6gB38nqtqVlfa1Kzy+Hs1 =pVKa -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Add pxcab target (v2)
Hi, Le Thursday 16 July 2009 09:57:25 Akinobu Mita, vous avez écrit : > This patch adds a target for the IBM PowerXCell Accelerator Board. > (aka mvXCell-8i from MatrixVision or GigaAccel 180 from Fixstars) > > http://us.fixstars.com/products/gigaaccel/ > > This build will create zImage suitable for TFTP boot image. > > * v2 > - add axonram device driver > - switch to 2.6.30.1 > > Signed-off-by: Akinobu Mita Patch applied in changeset 16860 after compile testing the target. I slightly reworked the changes in toolchain/Config.in. -- Best regards, Florian Fainelli Email: flor...@openwrt.org Web: http://openwrt.org IRC: [florian] on irc.freenode.net --- signature.asc Description: This is a digitally signed message part. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Next Wiki IRCmeeting (was: Re: Wiki efforts)
On Thu, 2009-07-16 at 21:22 +1200, Peter Lambrechtsen wrote: > Going to attend the next meeting, Gregers said it was planned to be > next thursday 8pm CET? So that'd be Thu 23rd? Count me in! :) -- "I love deadlines. I especially like the whooshing sound they make as they fly by." — Douglas Adams signature.asc Description: This is a digitally signed message part ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] sysupgrade-ext2 sync before writing image, not after
Hi all,
Sysupgrade for ext2 currently flushes the filesystem buffers after an
image is written to the disk. This should happen before the image is
written.
This has already been fixed in default_do_upgrade in common.sh (see
r16488). Please apply, thanks.
Fabian
Index: target/linux/x86/base-files/lib/upgrade/platform.sh
===
--- target/linux/x86/base-files/lib/upgrade/platform.sh (revision 16857)
+++ target/linux/x86/base-files/lib/upgrade/platform.sh (working copy)
@@ -13,8 +13,8 @@
}
platform_do_upgrade() {
+ sync
get_image "$1" > /dev/hda
- sync
}
x86_prepare_ext2() {
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Wiki efforts
On Thu, Jul 16, 2009 at 8:54 PM, kloschi wrote: > On Thu, 2009-07-16 at 09:16 +0200, Johnny Halfmoon wrote: >> Hi, >> >> similar action to what you propose has already been taken. Check >> http://nuwiki.openwrt.org/meta/ircmeeting . Also, check out the posts >> from Gregers Petersen on the archive of this list. > > I know, I attended this meeting ;) > and I work together with Gregers .. > > my questions are targeted to this mailing lists' audience. I'd like to > hear your opinion on the subject! My 2 cents is the two things that need to get nailed first are: 1) Categories decided and put on a reference page. IE "broadcom/usb/100mb4x1/80211bg/" etc... 2) TOH Templates, then the existing devices can be migrated from the oldwiki to the new wiki with the correct formatting Then people who are up for it can start transitioning the existing TOH hardware from the oldwiki to the /toh. One other nice to have would be a downloads.openwrt.org/latest/ or /lateststable/ or /kamikaze/latest.. so we could link to those images in the TOH pages. That way we would never do dead or older version links.. unless we wanted to. Going to attend the next meeting, Gregers said it was planned to be next thursday 8pm CET? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Wiki efforts
On Thu, 2009-07-16 at 09:16 +0200, Johnny Halfmoon wrote: > Hi, > > similar action to what you propose has already been taken. Check > http://nuwiki.openwrt.org/meta/ircmeeting . Also, check out the posts > from Gregers Petersen on the archive of this list. I know, I attended this meeting ;) and I work together with Gregers .. my questions are targeted to this mailing lists' audience. I'd like to hear your opinion on the subject! grtz, .k -- "I love deadlines. I especially like the whooshing sound they make as they fly by." — Douglas Adams signature.asc Description: This is a digitally signed message part ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Automatically remounting USB devices on Reboot?
Hi Kunal, Remove storage devices are automagically mounted by a script, /sbin/usbstorage, via hotplug when a device is plugged in. I didn't test the change you're proposing on a real device with USB support, but I guess automounting with "mount -a" and having /sbin/usbstorage run aside will conflict at some point. A better option would be to let /sbin/usbstorage be aware of mountpoints defined in /etc/fstab. I know an enhanced automounter is on its way, I'll try to get more infos and keep you posted. Regards, -- Nico Kunal Punjabi wrote: > > We just ported our platform over to OpenWRT and have it running. > > I found that temporary storage devices like USB do not get mounted > when the OpenWRT router is rebooted, although the drives were properly > mounted prior to the reboot. This seems to happen because usbfs is > invoked after fstab does a "mount -a", in effect the mount point isn't > found. The fix for this would be to move S20fstab later on in the > initialization sequence..after S39usb. That would make sure the mount > -a gets executed after S39, and not before or even in it. > > > > Is such a reorder acceptable, i.e. can I move S20fstab **after** > S39USB? Is it likely to be accepted when we push our changes upstream > (to the openwrt sources)? Or was OpenWRT designed to NOT automatically > mount non-persistent storages like usb on reboot? > > > > Thanks > > Kunal > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Debrick utility
Hi, urjtag has indeed a version (0.10) which recognize BCM6358 but it seems that this is not enough... Here is what I got: jtag> cable ea253 parallel 0x378 Initializing parallel port at 0x378 jtag> detect IR length: 13 Chain length: 2 Device Id: 00100111000110010111 (0x2431817F) Manufacturer: Broadcom Unknown part! Device Id: 01100011010110010111 (0x0635817F) Manufacturer: Broadcom Part(1): BCM6358 Stepping: V1 Filename: /usr/share/urjtag/broadcom/bcm6358/bcm6358 chain.c(149) Part 0 without active instruction ## These lines repeats many times in almost chain.c(200) Part 0 without active instruction ## every output: I will suppress them ImpCode= EJTAG version: <= 2.0 EJTAG Implementation flags: R4k DMA MIPS32 Clear memory protection bit in DCR Clear Watchdog Potential flash base address: [0x0], [0x0] Processor successfully switched in debug mode. jtag> print No. Manufacturer Part Stepping Instruction Register -- 1 Broadcom BCM6358 V1 EJTAG_CONTROL EJCONTROL Active bus: *0: EJTAG compatible bus driver via DMA (JTAG part No. 1) start: 0x, length: 0x1E00, data width: 32 bit, (USEG : User addresses) start: 0x1E00, length: 0x0200, data width: 16 bit, (FLASH : Addresses in flash (boot=0x1FC00)) start: 0x2000, length: 0x6000, data width: 32 bit, (USEG : User addresses) start: 0x8000, length: 0x2000, data width: 32 bit, (KSEG0: Kernel Unmapped Cached) start: 0xA000, length: 0x2000, data width: 32 bit, (KSEG1: Kernel Unmapped Uncached) start: 0xC000, length: 0x2000, data width: 32 bit, (SSEG : Supervisor Mapped) start: 0xE000, length: 0x2000, data width: 32 bit, (KSEG3: Kernel Mapped) jtag> print chain No. Manufacturer Part Stepping Instruction Register -- 0 (none) (none) 1 Broadcom BCM6358 V1 EJTAG_CONTROL EJCONTROL jtag> detectflash 0xBE00 dev ID= man ID= amd_detect: mid 0, did 0 Flash not found! To summarize urjtag does not recognize the bcm4318 chip onboard and does not find any flash. I got 0xBE00 from the boot log of the original firmware: <--Snips--> C0GDTW WESTELL - ROM Bootloader (C) Copyright 2006 WESTELL, Inc. All Rights Reserved. CLEARING SDRAM ... . PASSED WESTELL - MAIN Bootloader Reboot command 60 Device 0 -- FLASH start addr BE00 Flash end addr BE3F Device 1 -- FLASH start addr BE40 Flash end addr BE5F Flash start BE00 end BE5F size 0060 No App Reboot Information found: 1 Linux version 2.6.8.1 (r...@uriel) (gcc version 3.4.4) #1 Tue Apr 22 13:57:08 IST 2008 Westell prom init get_ethernet_addr: 00:18:3a:af:15:09 Bootloader Watchdog State ON CPU revision is: 0002a010 Determined physical RAM map: memory: 01fa @ (usable) On node 0 totalpages: 8096 DMA zone: 8096 pages, LIFO batch:1 Normal zone: 0 pages, LIFO batch:1 HighMem zone: 0 pages, LIFO batch:1 Built 1 zonelists Kernel command line: root=/dev/mtdblock2 ro bootmode=prod boottype=wdog memsize=0x200 flashsize=0x62 ethaddr=00:18:3A:AF:15:09 ipaddr=192.168.1.1 wdog=on <--Snips--> I tried also detectflash with other values: every time I had the same result. I am not an expert of the subject so any advice is welcome. Thanks S. * Benjamin Henrion [2009-07-07 23:33:59]: > On Tue, Jul 7, 2009 at 11:23 PM, VulK wrote: > > Hi, > > I am trying to take a backup of the firmware of a westell 7500 adsl router > > via jtag; the board is based on BCM6358 and there are two flash memories: > > ST M29W320 and ST M29W160. > > Urjtag seems to have some working version for BCM6358: > > http://www.neufbox4.org/wiki/index.php?title=Interface_JTAG > > -- > Benjamin Henrion > FFII Brussels - +32-484-566109 - +32-2-4148403 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] Add pxcab target (v2)
This patch adds a target for the IBM PowerXCell Accelerator Board. (aka mvXCell-8i from MatrixVision or GigaAccel 180 from Fixstars) http://us.fixstars.com/products/gigaaccel/ This build will create zImage suitable for TFTP boot image. * v2 - add axonram device driver - switch to 2.6.30.1 Signed-off-by: Akinobu Mita --- package/kernel/modules/block.mk| 15 + target/linux/pxcab/Makefile| 29 ++ target/linux/pxcab/base-files/etc/preinit.arch |2 + target/linux/pxcab/config-2.6.30 | 497 target/linux/pxcab/image/Makefile | 20 + ...ic-Fix-mapping-of-DCR-based-MPIC-variants.patch | 107 + toolchain/Config.in|3 + toolchain/gcc/Config.in|1 + toolchain/gcc/Config.version |1 + 9 files changed, 675 insertions(+), 0 deletions(-) create mode 100644 target/linux/pxcab/Makefile create mode 100644 target/linux/pxcab/base-files/etc/preinit.arch create mode 100644 target/linux/pxcab/config-2.6.30 create mode 100644 target/linux/pxcab/image/Makefile create mode 100644 target/linux/pxcab/patches-2.6.30/0001-powerpc-mpic-Fix-mapping-of-DCR-based-MPIC-variants.patch diff --git a/package/kernel/modules/block.mk b/package/kernel/modules/block.mk index 3dabdfc..2d14e42 100644 --- a/package/kernel/modules/block.mk +++ b/package/kernel/modules/block.mk @@ -374,3 +374,18 @@ define KernelPackage/ps3vram/description endef $(eval $(call KernelPackage,ps3vram)) + +define KernelPackage/axonram + SUBMENU:=$(BLOCK_MENU) + TITLE:=Axon DDR2 memory device driver + DEPENDS:=...@target_pxcab + KCONFIG:=CONFIG_AXON_RAM + FILES:=$(LINUX_DIR)/arch/powerpc/sysdev/axonram.$(LINUX_KMOD_SUFFIX) + AUTOLOAD:=$(call AutoLoad,01,axonram) +endef + +define KernelPackage/axonram/description + Kernel support for Axon DDR2 memory device +endef + +$(eval $(call KernelPackage,axonram)) diff --git a/target/linux/pxcab/Makefile b/target/linux/pxcab/Makefile new file mode 100644 index 000..eeb08b2 --- /dev/null +++ b/target/linux/pxcab/Makefile @@ -0,0 +1,29 @@ +# +# Copyright (C) 2007 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# +include $(TOPDIR)/rules.mk + +ARCH:=powerpc +BOARD:=pxcab +BOARDNAME:=PowerXCell Accelerator Board +FEATURES:=fpu ramdisk + +LINUX_VERSION:=2.6.30.1 + +KERNEL_CC:= + +include $(INCLUDE_DIR)/target.mk + +define Target/Description + Build zImage for the IBM PowerXCell Accelerator Board + (aka mvXCell-8i from MatrixVision or GigaAccel 180 from Fixstars) +endef + +KERNELNAME:="zImage" + +DEFAULT_PACKAGES += kmod-tg3 + +$(eval $(call BuildTarget)) diff --git a/target/linux/pxcab/base-files/etc/preinit.arch b/target/linux/pxcab/base-files/etc/preinit.arch new file mode 100644 index 000..00db8b4 --- /dev/null +++ b/target/linux/pxcab/base-files/etc/preinit.arch @@ -0,0 +1,2 @@ +mount -t proc none /proc +grep 'failsafe=' /proc/cmdline > /dev/null && export FAILSAFE=true diff --git a/target/linux/pxcab/config-2.6.30 b/target/linux/pxcab/config-2.6.30 new file mode 100644 index 000..2d32d5b --- /dev/null +++ b/target/linux/pxcab/config-2.6.30 @@ -0,0 +1,497 @@ +CONFIG_64BIT=y +# CONFIG_AGP is not set +CONFIG_ALTIVEC=y +CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y +CONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=y +CONFIG_ARCH_HAS_ILOG2_U32=y +CONFIG_ARCH_HAS_ILOG2_U64=y +CONFIG_ARCH_HAS_WALK_MEMORY=y +CONFIG_ARCH_MAY_HAVE_PC_FDC=y +CONFIG_ARCH_MEMORY_PROBE=y +CONFIG_ARCH_NO_VIRT_TO_BUS=y +CONFIG_ARCH_PHYS_ADDR_T_64BIT=y +CONFIG_ARCH_POPULATES_NODE_MAP=y +CONFIG_ARCH_SELECT_MEMORY_MODEL=y +CONFIG_ARCH_SPARSEMEM_DEFAULT=y +CONFIG_ARCH_SPARSEMEM_ENABLE=y +CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y +CONFIG_ARCH_SUPPORTS_MSI=y +CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y +# CONFIG_ARPD is not set +CONFIG_AUDIT_ARCH=y +CONFIG_AXON_RAM=m +# CONFIG_BACKTRACE_SELF_TEST is not set +CONFIG_BASE_SMALL=0 +# CONFIG_BINARY_PRINTF is not set +CONFIG_BITREVERSE=y +CONFIG_BLK_DEV_LOOP=y +CONFIG_BLK_DEV_RAM=y +CONFIG_BLK_DEV_RAM_COUNT=16 +CONFIG_BLK_DEV_RAM_SIZE=65535 +CONFIG_BLK_DEV_SD=y +CONFIG_BLK_DEV_SR=y +# CONFIG_BLK_DEV_SR_VENDOR is not set +CONFIG_BLOCK_COMPAT=y +# CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not set +CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=0 +# CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set +CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0 +# CONFIG_BOOTX_TEXT is not set +# CONFIG_BOOT_PRINTK_DELAY is not set +CONFIG_BOUNCE=y +# CONFIG_BRIDGE is not set +# CONFIG_BSD_PROCESS_ACCT is not set +CONFIG_CBE_CPUFREQ=y +# CONFIG_CBE_CPUFREQ_PMI_ENABLE is not set +CONFIG_CBE_CPUFREQ_SPU_GOVERNOR=y +CONFIG_CBE_RAS=y +CONFIG_CBE_THERM=y +# CONFIG_CGROUP_SCHED is not set +CONFIG_CMDLINE_BOOL=y +# CONFIG_CODE_PATCHING_SELFTEST is not set +CONFIG_COMPAT=y +CONFIG_COMPAT_BINFMT_ELF=y +CONFIG_COMPAT_BRK=y +CONFIG_CONSOLE_TRANSLATIONS=y +CONFIG_CPU_FREQ=y +# CO
Re: [OpenWrt-Devel] Wiki efforts
Hi, similar action to what you propose has already been taken. Check http://nuwiki.openwrt.org/meta/ircmeeting . Also, check out the posts from Gregers Petersen on the archive of this list. Cheers, Johnny kloschi wrote: > Hi all, > > > as it stands there, just waiting for loads of content, there some things > I'd like to discuss here for a second. > > First I have heard sometimes the wish for a openwrt-docs mailing list. > This would be good for all users interested in and working on the docs, > meanwhile they don't fear to get overwhelmed by the traffic of > openwrt-devel. On the other hand another list means another separation > of channels. So, a not easy move .. > > Should this be voted on? > What's the OpenWrt standard procedure on this? > :) > > > Second, the interest / manpower which imho would be needed to get the > nuwiki rolling appropriately is not coming out of nowhere. Of course :) > So, what about having some "OpenWrt Wiki Days" or an "OpenWrt Wiki Week" > or $whatever title? > > Necessities for that would be: > - agreement on a date / week > - announcement > - heavy weight todo lists > - a coordination page for participants / groups > - a irc channel (one of the existing or extra one) > > just my 2 cents, > phaidros > > > > > > > ___ > 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] md5sums
Hiya, what you can do to temporarily resolve the issue, is to manually download the tarball(s), run md5sum on the files and then adjust the sum in the package Makefile. Cheers, Johnny Matthias Buecher / Germany wrote: > Currently several snapshot package repositories have this issue. > Also http://downloads.openwrt.org/snapshots/trunk/orion/packages/ > > Let's hope some developer/maintainer fixes the update process and we can > use them again on the next refresh (I'm just a user too). > > Maddes > > > On 15.07.2009 11:17, Kovesdi Gyorgy wrote: >> Hi, >> >> I found that md5sums (and file sizes) are incorrect at >> http://downloads.openwrt.org/snapshots/trunk/brcm-2.4/packages/ >> >> ...or i do something wrong? >> >> K. Gy. > > ___ > 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
