**** BEGIN LOGGING AT Wed Oct 10 02:59:58 2012 Oct 10 07:44:30 Hello, is there someone familiar with Ralink here? Oct 10 07:53:09 trying to port to a new board and may use some help from someone knowledgeable in the ramips environment Oct 10 08:59:35 <[florian]> TERROR: do you have a specific question? Oct 10 10:23:52 [florian]: I'm trying to port openwrt to a new board and having problems with the ethernet switch. I don't know which gpio pins are used to hookup the SoC with the ethernet switch chip. I have to original fw sources and the sources for u-boot, so the information should be somewhere in there, but I'm not to sure where to look for it. I've found a few possibilities, but I don't know what the mapping between memory addreses and GPIO pins ir for the RT3662. Oct 10 10:24:54 I'm sure someone experienced with these SoCs should be able to understand this memory offsets right away. Oct 10 10:25:45 <[florian]> TERROR: you can still ask juhosg in private, he did the porting on these SoCs Oct 10 10:26:12 does he hang around here? Oct 10 10:26:28 <[florian]> he must be queried/msged Oct 10 10:26:43 [florian] OK, thank you, I'll do that Oct 10 17:28:44 am I the only one getting an svn error with the latest trunk rev? Oct 10 17:29:12 during "svn up" ? Oct 10 17:29:19 yes Oct 10 17:29:25 no Oct 10 17:29:44 okay... Oct 10 17:29:55 is a bug filed on that? Oct 10 17:30:03 its nothing we can fix Oct 10 17:30:26 svn cleanup Oct 10 17:30:27 svn rm tools/firmware-utils/src/bcm_tag.h Oct 10 17:30:28 svn up Oct 10 17:30:38 purely a client issue Oct 10 17:31:44 it says about a conflict after these steps Oct 10 17:32:39 svn revert tools/firmware-utils/src/bcm_tag.h Oct 10 17:32:44 then rm it wout svn Oct 10 17:32:49 *without Oct 10 17:33:20 fixed. thanks a lot, jow Oct 10 18:16:36 someone remind me which image I need to use with sysupgrade? Oct 10 18:17:56 and what happened to package/firewall, package/dropbear, package/dnsmasq? Oct 10 18:18:15 philipp64|laptop: -sysupgrade.bin Oct 10 18:19:14 do I need to make any special target to get that? this is on x86/alix2. Oct 10 18:19:15 philipp64|laptop: it's in package/network Oct 10 18:19:24 all of it? Oct 10 18:19:28 yep Oct 10 18:19:31 they're in different folders Oct 10 18:19:40 package/network/services/dropbear, for example Oct 10 18:20:05 in case of ar71xx, sysupgrade is built together with a factory img Oct 10 18:20:12 i guess that should work for alix2 as well Oct 10 18:21:03 no need to choose anything extra in config Oct 10 18:23:11 the sysupgrade image for x86 is the combined one Oct 10 19:02:47 right. forgot that. thanks. Oct 10 20:30:03 fail. Oct 10 20:30:07 root@OpenWrt:/tmp# sysupgrade -v /tmp/openwrt-x86-alix2-combined-squashfs.img Oct 10 20:30:08 Invalid image type Oct 10 20:30:10 Image check 'platform_check_image' failed. Oct 10 20:30:12 root@OpenWrt:/tmp# Oct 10 20:32:01 this is a trunk/r33706 build that I'm trying to update to. Oct 10 20:40:19 sysupgrade support got introduced with r32465 Oct 10 20:40:35 so your running build must be >= that rev in order to sysupgrade Oct 10 20:43:48 ah... will need to reflash and start from scratch... is the original build number available on the system anywhere? Oct 10 20:45:09 opkg list_installed | grep base-files Oct 10 20:45:14 hmm... Oct 10 20:45:17 root@OpenWrt:/tmp# cat /etc/*release* Oct 10 20:45:19 DISTRIB_ID="OpenWrt" Oct 10 20:45:20 DISTRIB_RELEASE="Bleeding Edge" Oct 10 20:45:22 DISTRIB_REVISION="r33270" Oct 10 20:45:23 DISTRIB_CODENAME="attitude_adjustment" Oct 10 20:45:26 DISTRIB_TARGET="x86/alix2" Oct 10 20:45:26 DISTRIB_DESCRIPTION="OpenWrt Attitude Adjustment r33270" Oct 10 20:45:43 so this *should* have worked. Oct 10 22:38:54 jow_laptop: base-files - 115-r33270 Oct 10 22:39:16 so... sysupgrade on x86 is still broken then? Oct 11 00:57:20 are there any kind of statistics on how many openwrt users (installations?) there are? Oct 11 02:53:29 * swalker wonders if dgolle actually has trac & svn accounts **** ENDING LOGGING AT Thu Oct 11 02:59:58 2012