**** BEGIN LOGGING AT Mon Sep 16 02:59:59 2013
Sep 16 03:36:41 <builder> build #399 of at91 is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/at91/builds/399
Sep 16 04:38:35 <builder> build #389 of brcm47xx is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx/builds/389
Sep 16 04:40:40 <builder> build #332 of sibyte is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/332
Sep 16 04:43:49 <Devastator> good morning zajec_, how are you?
Sep 16 04:48:53 <zajec_> Devastator: hello
Sep 16 04:50:01 <Devastator> zajec_ when you have the time, could you help me understand why I get "wl0: Invalid argument" 2 times, when I try wifi up, after wifi down?
Sep 16 04:51:01 <zajec_> i can't really
Sep 16 04:51:10 <zajec_> Devastator: i don't use, don't know wl
Sep 16 04:51:16 <zajec_> and don't like it ;)
Sep 16 04:51:29 <Devastator> I agree
Sep 16 04:51:58 <Devastator> I don't know if there are any broadcom devs here, but their driver are the worse :P
Sep 16 04:52:31 <Devastator> I was just following hauke advice which was: if you want n speeds, use proprietary driver
Sep 16 04:56:54 <Devastator> I will switch to b43 and test..
Sep 16 05:29:52 <Devastator> I bet Lightsword is James that was nagging on the list about patches on the proprietary driver..
Sep 16 05:32:45 <builder> build #371 of cobalt is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/cobalt/builds/371
Sep 16 05:36:50 <builder> build #381 of atheros is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/atheros/builds/381
Sep 16 06:38:09 <builder> build #342 of avr32 is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/342
Sep 16 08:11:53 <builder> build #403 of brcm63xx is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx/builds/403
Sep 16 08:58:32 <zajec_> morning Hauke
Sep 16 08:58:41 <zajec_> Morgen :)
Sep 16 08:58:41 <Hauke> morning zajec_
Sep 16 08:59:45 <zajec_> Hauke: ich lerne Deutsch ;)
Sep 16 09:00:59 <Hauke> zajec_:  ;-)
Sep 16 09:03:35 <zajec_> Hauke: do you know anything about BCM43217? https://forum.openwrt.org/viewtopic.php?pid=212494
Sep 16 09:06:22 <Hauke> zajec_: no I haven't heard of a BCM43217 before
Sep 16 09:11:35 <zajec_> Hauke: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=162802
Sep 16 09:11:50 <zajec_> PCI/PCIe coreunit 0 is set to bus 1.
Sep 16 09:11:53 <zajec_> PCI/PCIe coreunit 1 is set to bus 2.
Sep 16 09:11:59 <zajec_> there are 2 PCIe devices
Sep 16 09:12:03 <zajec_> so I think it's a softmac device
Sep 16 09:12:36 <Hauke> here are some information: http://wikidevi.com/wiki/Broadcom
Sep 16 09:13:02 <zajec_> so it's PCIe
Sep 16 09:13:08 <zajec_> too bad we don't know PHY
Sep 16 09:13:20 <zajec_> btw
Sep 16 09:13:24 <zajec_> Creating 4 MTD partitions on "nflash":
Sep 16 09:13:25 <zajec_>  0x00000000-0x02000000 : "linux"
Sep 16 09:13:27 <zajec_>  0x001e8514-0x02000000 : "rootfs"
Sep 16 09:13:28 <zajec_>  0x02000000-0x04000000 : "linux2"
Sep 16 09:13:30 <zajec_>  0x021e9874-0x04000000 : "rootfs2"
Sep 16 09:13:36 <zajec_> crazy layout.... wonder what is that
Sep 16 09:14:22 <Hauke> some backup partitions in case something went wrong while flashing new firmware
Sep 16 09:15:40 <zajec_> Hauke: "eth1: Broadcom BCM43a2 802.11 Wireless Controller 6.39.39.30 (r339230)"
Sep 16 09:15:47 <zajec_> Hauke: i think it's 14e4:43a2
Sep 16 09:15:57 <zajec_> http://wikidevi.com/wiki/ASUS_PCE-AC66 "14e4:43a2 (PCI ID of the BCM4360 module in the Buffalo WZR-D1800H)"
Sep 16 09:16:05 <zajec_> so it's probably just a BCM4360
Sep 16 09:17:13 <Hauke> this "Broadcom BCM43a2" is not always based on the pci id, I have often seen BCM4329, while it was not this device
Sep 16 09:23:25 <zajec_> oh, ok
Sep 16 09:24:01 <Hauke> zajec_: I am leaving now
Sep 16 09:25:07 <KanjiMonster> zajec_: 43217 is N-PHY (rev 17)
Sep 16 09:29:57 <zajec_> KanjiMonster: oh, thanks
Sep 16 09:30:09 <zajec_> you know interesting things :)
Sep 16 09:31:40 <KanjiMonster> the wifi core in 53572 seems to be also N-PHY rev 17
Sep 16 09:31:49 <zajec_> 0x1c...
Sep 16 09:32:15 <zajec_> ah, waiy
Sep 16 09:32:21 <zajec_> 0x1c is core revisino
Sep 16 09:32:33 <zajec_> ah, it's that faked PHY
Sep 16 09:32:36 <zajec_> KanjiMonster: it's a LCNXN/1
Sep 16 09:32:39 <KanjiMonster> I think broadcom refers to them as LCNXN
Sep 16 09:32:49 <zajec_> but Broadcom treats it as N rev 16 + n
Sep 16 09:32:51 <zajec_> n=1
Sep 16 09:32:56 <zajec_> so it becomes N rev 17 ;)
Sep 16 09:33:41 <zajec_> there is hack in their code
Sep 16 09:33:56 <zajec_> if (phy == LCNXN) { phy = N; rev = 16 + phyrev }
Sep 16 09:34:57 <KanjiMonster> so they created a new phy type, but then decided they actually don't need to treat them differently ;)
Sep 16 09:35:04 <zajec_> :P
Sep 16 09:35:59 <zajec_> maybe they were out of numbers
Sep 16 09:36:11 <zajec_> maybe mask for PHY rev is 0xF
Sep 16 09:36:16 <zajec_> it's likely
Sep 16 09:36:30 <zajec_> but they could name it "N2" at least or sth like that ;)
Sep 16 09:36:34 <KanjiMonster> maybe
Sep 16 09:36:39 <zajec_> LCNXN sounds like like LCN or LCN40
Sep 16 09:36:45 <zajec_> but it's much closer to the N-PHY
Sep 16 09:37:01 <KanjiMonster> LCN is single-stream 11n, LCNXN is 2-stream 11n
Sep 16 09:37:32 <KanjiMonster> SSN is also single-stream 11n
Sep 16 09:40:05 <KanjiMonster> also it looks like AC-PHY is based on HT-PHY (where 4331 seems to be the only released chip ;), so if broadcom ever adds 11ac support, they will have to almost add HT-PHY support at least
Sep 16 09:41:46 <KanjiMonster> zajec_: ah indeed, phyrev is only 4 bit wide, so they had to use a new phy type
Sep 16 09:46:19 <KanjiMonster> also it looks like bcm4313 is the only soft-mac lcn phy, all others are full-mac ones
Sep 16 09:47:43 <zajec_> yeah
Sep 16 09:48:12 <zajec_> and I found  only one SSN-PHY in some totally not known router ;)
Sep 16 10:00:49 <KanjiMonster> zajec_: btw, I think have an easy solution for the bcm4313 0x4313 pci id problem: add to ssb_pci_bridge in the probe a if (pciid == 0x4313 && pci_is_pcie(dev)) return -EINVAL; - this should allow bcma to probe and attach. The 0x4313 ssb card is probably old enough to not support pcie ever ;)
Sep 16 10:03:21 <zajec_> ah, sorry, i didn't track that dicsussion closely
Sep 16 10:09:25 <KanjiMonster> zajec_: there was not much discussion ;)
Sep 16 10:55:14 <zajec_> KanjiMonster: not a big chance for HT-PHY when releasing AC-PHY
Sep 16 10:55:53 <zajec_> KanjiMonster: http://svn.dd-wrt.com/browser/src/linux/universal/linux-3.11/brcm/mipsel/wl/phy
Sep 16 10:56:22 <zajec_> KanjiMonster: wlc_phytbl_ac.o
Sep 16 10:56:30 <zajec_> wlc_phy_ac.o
Sep 16 10:56:43 <zajec_> wlc_phy_ac.o is as big as wlc_phy_ht.o
Sep 16 10:56:49 <zajec_> so they probably dont's share the code
Sep 16 10:56:57 <zajec_> but i still hope the code is similar
Sep 16 10:57:07 <zajec_> so maybe we can RE sth
Sep 16 10:57:08 <zajec_> anything
Sep 16 11:08:47 <Devastator> zajec_ do you want me to call Lightsword to help you? :D
Sep 16 11:11:37 <zajec_> Devastator: ;)
Sep 16 12:02:18 <builder> build #354 of x86 is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/x86/builds/354
Sep 16 12:04:07 <builder> build #350 of ar7 is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/ar7/builds/350
Sep 16 12:06:46 <builder> build #289 of iop32x is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/289
Sep 16 12:21:00 <KanjiMonster> zajec_: if its as big that might mean that it's mostly a copy with little changes ;p
Sep 16 12:51:31 <zajec_> KanjiMonster: that would be great
Sep 16 12:51:40 <zajec_> i could easily spot differences in MMIO dump
Sep 16 12:51:44 <zajec_> and just re-use most of that
Sep 16 12:51:45 <zajec_> or share
Sep 16 12:54:21 <Devastator> hum, is this the right place to ask about broadcom-wl and b43 differences?
Sep 16 12:56:06 <KanjiMonster> broadcom-wl is the closed sources driver written by broadcom, b43 is the open source driver written mostly by zajec_ (based on reverse engineering broadcom-wl)
Sep 16 12:57:20 <KanjiMonster> of course in a white room enrivornment, i.e. zajec_ does not do the reverse engineering (to prevent "taint")
Sep 16 12:57:58 <Devastator> yes, but in regards of performance, b43 is similar/outpperforms broadcom-wl in b/g, right?
Sep 16 12:58:23 <KanjiMonster> no idea
Sep 16 12:58:40 <KanjiMonster> probably depends on the chip
Sep 16 12:59:33 <KanjiMonster> bcm4318 is quite well supported, the 11n chips might miss power/temperature compensation so they might performe less with b43
Sep 16 12:59:40 <Devastator> I wonder the N performance between the two, and if there is anything I could do to help improve b43 N performance if needed anyway
Sep 16 13:00:07 <zajec_> Devastator: b43 doesn't support 802.11n
Sep 16 13:00:13 <Devastator> I want to get rid of this crap called broadcom-wl
Sep 16 13:00:18 <zajec_> in 802.11g they worked similarly for me for most of the hardware
Sep 16 13:00:34 <KanjiMonster> so the n performance is zero ;p
Sep 16 13:00:38 <Devastator> heheh
Sep 16 13:01:28 <Devastator> I guess their opensource driver doesn't help as they don't support ap mode in opensource?!
Sep 16 13:01:42 <zajec_> Hauke added support for AP in brcmsmac
Sep 16 13:01:50 <zajec_> but they don't support much more hardware
Sep 16 13:01:54 <MartijnVdS> Broadcom, the Nvidia of the wifi world?
Sep 16 13:01:57 <KanjiMonster> I guess for 11n you "only" need to implement sending/receiving with HT-Rates to get anything, then probably > 1 stream, 40 MHz bandwidth, aggregation etc pp
Sep 16 13:01:58 <zajec_> but they support 802.11n :)
Sep 16 13:02:22 <zajec_> KanjiMonster: right
Sep 16 13:02:31 <zajec_> KanjiMonster: too bad noone want to work on that :(
Sep 16 13:02:40 <Devastator> well, I want to contribute
Sep 16 13:02:47 <KanjiMonster> zajec_: I would love to, but I lack the time
Sep 16 13:03:04 <Devastator> but my knowledge is zero, so I can only test and provide logs
Sep 16 13:03:14 <KanjiMonster> Devastator: the easiest target is if you can get your hands on a device with a bcm43222
Sep 16 13:03:38 <Devastator> KanjiMonster suggestions?
Sep 16 13:03:59 <KanjiMonster> bcm43222 is basically a bcm43224 with ssb instead of bcma to be able to support pci
Sep 16 13:04:26 <KanjiMonster> and bcm43224 is supported by brcmsmac
Sep 16 13:04:57 <KanjiMonster> so it should be possible to take most 11n logic from there and apply it to b43
Sep 16 13:05:06 <zajec_> that'st true
Sep 16 13:05:07 <Devastator> I will see what I can find
Sep 16 13:06:13 <KanjiMonster> the problem is that bcm43222 can be basically only found in bcm63xx devices ;)
Sep 16 13:06:23 <KanjiMonster> mostly vdsl devices
Sep 16 13:07:05 <KanjiMonster> because bcm6368 was the only vdsl chip, but had only pci (I think this is the reason for bcm43222's existence)
Sep 16 13:07:10 <KanjiMonster> back then
Sep 16 13:07:27 <KanjiMonster> nowadays theres bcm63268 which has pcie
Sep 16 13:07:33 <Devastator> I have a bcm63xx device
Sep 16 13:07:38 <KanjiMonster> so no need for any ssb based devices anymore
Sep 16 13:07:47 <KanjiMonster> but does it have a bcm43222?
Sep 16 13:08:06 <Devastator> I will have to check
Sep 16 13:08:09 <Devastator> lets see
Sep 16 13:10:35 <Devastator> KanjiMonster I will have to open it, it's d-link dsl-2640b I think
Sep 16 13:11:00 <Devastator> bcm6348 chipset..
Sep 16 13:11:57 <KanjiMonster> Devastator: then at best a bcm4321, but 6348 usually only comes with 11g cards, so more likely a bcm4318
Sep 16 13:12:11 <Devastator> humm]
Sep 16 13:12:27 <Devastator> the other modem I have is a sagecom
Sep 16 13:12:59 <Devastator> hum, ikanos+atheros
Sep 16 13:13:04 <zajec_> BCM4321 should be fine for adding 802.11n support
Sep 16 13:13:15 <zajec_> it works really well in 802.11g
Sep 16 13:13:20 <Devastator> my wrt310n is bcm4321
Sep 16 13:13:37 <zajec_> BCM43222, BCM43224 and BCM43225 suffer from some performance issue
Sep 16 13:13:43 <zajec_> probably some code lacking for rev 6
Sep 16 13:14:15 <Devastator> [   17.008000] wl0: Broadcom BCM4321 802.11 Wireless Controller 5.10.56.27
Sep 16 13:15:00 <KanjiMonster> zajec_: but for bcm432224 there is a "reference implementation" from which you can take code/logic directly
Sep 16 13:15:12 <Devastator> hum
Sep 16 13:15:15 <KanjiMonster> *43224/43222
Sep 16 13:16:05 <Devastator> looks like asus wl500gp has 43222
Sep 16 13:16:34 <KanjiMonster> wat?
Sep 16 13:16:40 <KanjiMonster> wl500gp has 4318
Sep 16 13:17:20 <Devastator> my search showed this: http://dd-wrt.com/forum/viewtopic.php?t=156747
Sep 16 13:17:35 <Devastator> brb
Sep 16 13:19:26 <KanjiMonster> the wl500gp has already full hands with 11g speed, 11n would probably bring not much speed improvement
Sep 16 13:52:50 <zajec_> KanjiMonster: Hauke: do you know what is 30/30/30 hard reset?
Sep 16 13:53:56 <Hauke> zajec_: some way to  reset the nvram to its default state
Sep 16 13:54:53 <zajec_> Hauke: does it put device in tftp?
Sep 16 13:54:55 <zajec_> tftpd
Sep 16 13:55:27 <zajec_> http://infodepot.wikia.com/wiki/Hard_reset_or_30/30/30
Sep 16 13:55:31 <zajec_> The following procedure will clear out the NVRAM and set dd-wrt back to default values:
Sep 16 13:55:40 <zajec_> sounds it's just that
Sep 16 13:55:43 <zajec_> nothing more
Sep 16 13:59:23 <zajec_> Hauke: can I get an account on dev.openwrt.org?
Sep 16 13:59:40 <zajec_> not for touching source
Sep 16 13:59:42 <zajec_> just for tickets
Sep 16 13:59:48 <zajec_> who handles that?
Sep 16 14:07:19 <KanjiMonster> an account usually comes with commit priviledges ;)
Sep 16 14:16:55 <Pteridium> [florian]: had the mail i've sent enough info for the bcm3380?
Sep 16 14:17:53 <[florian]> Pteridium: yes, if you did not get a mailer daemon notification, I got it :)
Sep 16 14:19:43 <Pteridium> good! i'm glad that the info can help you. What do you think about ethernet and usb in that SoC?
Sep 16 14:21:29 <[florian]> Pteridium: much different this does not use a traditional ethernet mac
Sep 16 14:25:17 <Pteridium> bad news :(
Sep 16 14:26:22 <Pteridium> recently i've found a project developed by Arrow Zhang called uswrt for the rtl8672 and based in openwrt, but he doen't share the source code.
Sep 16 14:26:25 <Pteridium> https://www.uswrt.com/download/dl/fw/rtl8672/
Sep 16 14:27:30 <Pteridium> and the binary images are prided under payment
Sep 16 14:27:42 <Pteridium> provided*
Sep 16 14:27:55 <[florian]> really, don't spend much time on these realtek SoCs
Sep 16 14:28:02 <[florian]> they require way too much effort for what it is worth
Sep 16 14:28:42 <Pteridium> you are right; realtek is a time waste
Sep 16 14:31:31 <FreeArtMan> i am work now on rtl8196c
Sep 16 14:32:40 <FreeArtMan> their have terrible thing there
Sep 16 14:32:57 <Pteridium> terrible thing?
Sep 16 14:33:23 <builder> build #324 of kirkwood is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/kirkwood/builds/324
Sep 16 14:33:36 <Pteridium> what do you mean?
Sep 16 14:33:46 <FreeArtMan> a lot of #if 0
Sep 16 14:33:55 <[florian]> their code is utter crap
Sep 16 14:34:01 <FreeArtMan> and gcc > *.S
Sep 16 14:34:48 <Pteridium> hehe, their code is horrible ;)
Sep 16 14:35:34 <FreeArtMan> and a lot of florian code copyright changed to realtek =D
Sep 16 14:38:05 <FreeArtMan> if some one is interested here is code that in future is planned to get into openwrt upstream
Sep 16 14:38:06 <FreeArtMan> http://git.nprove.in/rtl819xx/?h=realtek-unstable
Sep 16 14:38:12 <FreeArtMan> a lot work to do
Sep 16 14:39:00 <jow_laptop> the wireless driver api on that nprove SoC made me cry in terror
Sep 16 14:39:31 <Pteridium> sadly i can't help you in your efforts
Sep 16 14:39:31 <FreeArtMan> it somehow fixed it works "ok" now
Sep 16 14:40:17 <jow_laptop> somehow they patched in a new protocol type all over the kernel
Sep 16 14:40:27 <jow_laptop> which did some out of band communication with the wifi driver
Sep 16 14:40:48 <jow_laptop> looked like a retarted reinvention of netlink
Sep 16 14:40:55 <FreeArtMan> every theis release almost rewrite of previous wifi driver
Sep 16 14:40:58 <Pteridium> jow_laptop: what means nprove SoC?
Sep 16 14:41:20 <FreeArtMan> Pteridium, rtl8196c
Sep 16 14:42:39 <Pteridium> Ah!
Sep 16 14:43:02 <blogic> Pteridium: https://dev.openwrt.org/ticket/14163  <--- that is from you ?
Sep 16 14:43:11 <blogic> i will attach a patch later that you could test if possible
Sep 16 14:43:47 <Pteridium> blogic: ok, all you need
Sep 16 14:44:13 <blogic> i will ping you when i attached it
Sep 16 14:44:22 <Pteridium> perfect
Sep 16 15:03:49 <Pteridium> blogic: works fine the new init process with multithread and SMP? https://lists.openwrt.org/pipermail/openwrt-devel/2013-September/021247.html
Sep 16 15:20:00 <zajec_> Hauke: did you see my bgmac patch for unaligned rings?
Sep 16 15:20:07 <zajec_> Hauke: do you think it's acceptable for OpenWrt?
Sep 16 15:24:46 <builder> build #290 of ep93xx is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/ep93xx/builds/290
Sep 16 15:48:46 <Devastator> KanjiMonster I'm still searching for a BCM43222 device, if you have anything in mind I would be grateful :)
Sep 16 15:50:11 <KanjiMonster> dgnd3700v1/dgnd3800v1 ;p. but it isn't supported yet
Sep 16 15:50:25 <KanjiMonster> mostly because of netgear
Sep 16 15:50:30 <KanjiMonster> stuff
Sep 16 15:52:41 <Devastator> humm, I think I've found one
Sep 16 15:53:09 <Devastator> dsl-2760u: https://dev.openwrt.org/ticket/10887
Sep 16 15:56:43 <KanjiMonster> ah. well, IIRC the ~u devices are only available in russia, so no idea if you can actually buy one outside ;)
Sep 16 15:56:59 <Devastator> let's see
Sep 16 15:57:28 <Devastator> meh
Sep 16 15:57:41 <KanjiMonster> no idea about the mentioned comtrend one - that one might be spain only ;)
Sep 16 16:02:34 <Devastator> found a belkin, but not available here
Sep 16 16:06:28 <Devastator> brazil is the worst country to buy specific things..
Sep 16 16:06:47 <MartijnVdS> why? don
Sep 16 16:06:56 <MartijnVdS> 't Chinese ebayers ship there?
Sep 16 16:13:36 <builder> build #327 of ixp4xx is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/ixp4xx/builds/327
Sep 16 16:21:52 <builder> build #332 of xburst is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/xburst/builds/332
Sep 16 16:26:30 <Devastator> MartijnVdS a few heheh
Sep 16 17:00:29 <Hauke> zajec_: back again
Sep 16 17:01:44 <zajec_> Hauke: :)
Sep 16 17:01:52 <zajec_> Hauke: i know I spammed you with request
Sep 16 17:01:57 <zajec_> some IDs, some patches ;)
Sep 16 17:02:14 <zajec_> hope you don't lost in that :P
Sep 16 17:02:32 <Hauke> uayes I saw the bgmac patches and applied them locally, I will do some test runs with that and other patches after dinner and commit later
Sep 16 17:05:38 <Devastator> when the merge window closes?
Sep 16 17:05:47 <Devastator> or open..
Sep 16 17:14:25 <KanjiMonster> Devastator: which one, linux'? it opens with release of n-final, and closes with the release of (n+1)-rc1 - and when this happens is totally up to linus ;) (usually it happens after rc7, and stays open for about two weeks)
Sep 16 18:23:21 <zajec_> Hauke: now I have my router working I wanted to take a look at BCM43224
Sep 16 18:23:32 <zajec_> Hauke: of couse I hit that bug with addr handling ;)
Sep 16 18:23:56 <zajec_> testing "bcma: fix error code handling on 64 Bit systems" right now ;)
Sep 16 18:24:30 <Devastator> KanjiMonster openwrt
Sep 16 18:27:31 <KanjiMonster> Devastator: there are no merge windows per se, its just that we eventually decide that the current trunk looks sane enough, then try to make it a release (fix bugs until we feel this is rc1, then release and branch, then fix up the branch)
Sep 16 18:30:01 <Devastator> KanjiMonster thanks, I've send a patch and was wondering if I lost the merge window or something
Sep 16 18:46:51 <Pteridium> blogic: in AA, where is defined the VMMC gpio?
Sep 16 18:49:40 <Pteridium> for the lantiq danube
Sep 16 19:26:19 <DonkeyHotei> [Thu 2013-09-12 12:33:45 PM PDT]  <Pteridium> DonkeyHotei: i was wrong; only a ethernet driver: http://gpl.back2roots.org/source/fritzbox/7390_5.50/GPL-release_kernel/linux/drivers/net/avm_cpmac/ <----- looks like ar7 to me
Sep 16 19:27:50 <Pteridium> http://gpl.back2roots.org/source/fritzbox/7390_5.50/GPL-release_kernel/linux/drivers/net/avm_cpmac/cpmac_fusiv_if.c
Sep 16 19:29:32 <Pteridium> but there aren't a lot of stuff: http://gpl.back2roots.org/source/fritzbox/7390_5.50/GPL-release_kernel/linux/fusiv_src/
Sep 16 19:30:27 <Pteridium> seems that Ikanos doesn't want to cooperate :-/
Sep 16 19:32:40 <Devastator> Ikanos sucks..
Sep 16 19:47:16 <Pteridium> Devastator: maybe you can try with TI/Intel Puma5 ;)
Sep 16 19:47:28 <OpenWrt-Commits> hauke r38004 trunk/target/linux/ brcm47xx/patches-3.10/770-bgmac-phylib.patch brcm47xx/patches-3.10/712-bgmac_implement_unaligned_addressing.patch * brcm47xx: bgmac: implement unaligned addressing for DMA rings that support it
Sep 16 19:48:22 <OpenWrt-Commits> hauke r38005 trunk/target/linux/brcm47xx/patches-3.10/030-mtd-bcm47xxpart_detect_factory_partition.patch * brcm47xx: mtd: bcm47xxpart: detect "factory" partition
Sep 16 19:49:53 <OpenWrt-Commits> hauke r38006 trunk/target/linux/brcm47xx/patches-3.10/260-MIPS-BCM47XX-add-board-detection.patch * brcm47xx: detect Linksys E1200 V2
Sep 16 19:51:06 <OpenWrt-Commits> hauke r38007 trunk/package/kernel/broadcom-diag/src/diag.c * broadcom-diag: Add WRT310N v1 gpio leds and buttons
Sep 16 19:52:03 <Devastator> yeah! my patch was accepted
Sep 16 19:53:15 <OpenWrt-Commits> hauke r38008 trunk/package/kernel/broadcom-diag/src/diag.c * broadcom-diag: add GPIO configuration for Linksys E2000 V1
Sep 16 19:54:01 <OpenWrt-Commits> hauke r38009 trunk/target/linux/brcm47xx/patches-3.10/260-MIPS-BCM47XX-add-board-detection.patch * brcm47xx: add detection for Phicomm M1
Sep 16 20:03:24 <builder> build #39 of imx23 is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/imx23/builds/39
Sep 16 20:05:47 <builder> build #383 of orion is complete: Failure [failed compile_8]  Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/383
Sep 16 20:07:33 <Devastator> Hauke many thanks for your help, I wish I could send a gift to all dev team
Sep 16 20:08:01 <Hauke> Devastator: also thanks from my side for testing
Sep 16 20:09:47 <Devastator> testing is easy
Sep 16 20:21:40 <zajec_> Hauke: now, i'm really happy with bcm47xx state :)
Sep 16 20:21:58 <Hauke> zajec_: ;-)
Sep 16 20:47:50 <builder> build #314 of ar71xx is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/ar71xx/builds/314
Sep 16 20:53:18 <falstaff> nnoo I bricked my router the hard way... there is nomore u-boot :-)
Sep 16 21:08:44 <OpenWrt-Commits> hauke r38010 trunk/target/linux/ generic/patches-3.10/990-gpio_wdt.patch generic/config-3.10 * kernel: add generic GPIO watchdog driver
Sep 16 21:10:02 <OpenWrt-Commits> hauke r38011 trunk/target/linux/ brcm47xx/patches-3.10/830-huawei_e970_support.patch brcm47xx/image/Makefile brcm47xx/config-3.10 brcm47xx/patches-3.10/980-wnr834b_no_cardbus_invariant.patch * brcm47xx: Add support for Huawei E970
Sep 16 22:03:29 <builder> build #369 of ppc40x is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/ppc40x/builds/369
Sep 16 22:10:19 <builder> build #255 of octeon is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/octeon/builds/255
Sep 16 22:44:13 <neoraider> Hi, I'd like to have 34577 backported to Attitude Adjustment... what's the best way to request it? Should I open a ticket? Drop a mail on openwrt-devel?
Sep 16 23:15:50 <builder> build #280 of gemini is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/gemini/builds/280
Sep 16 23:40:32 <builder> build #372 of ramips is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/ramips/builds/372
Sep 17 00:19:12 <builder> build #315 of au1000 is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/au1000/builds/315
Sep 17 00:38:07 <builder> build #372 of lantiq is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/372
Sep 17 02:23:32 <builder> build #286 of mcs814x is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/mcs814x/builds/286
**** ENDING LOGGING AT Tue Sep 17 02:59:58 2013