**** BEGIN LOGGING AT Tue Aug 26 02:59:57 2008
Aug 26 07:23:38 <CIA-9> blogic * r12391 /trunk/package/firewall/files/ (firewall.config uci_firewall.sh): use proto instead of protocol in uci firewall
Aug 26 11:07:10 <CIA-9> blogic * r12392 /trunk/package/firewall/files/uci_firewall.sh: adds more sanity checks to uci firewall
Aug 26 11:36:13 <CIA-9> blogic * r12393 /trunk/ (5 files in 3 dirs): adds several fixes to etrax, make openssl work on etrax
Aug 26 13:08:24 <mb___> oh, wl500g ships with boot_wait=on
Aug 26 13:09:14 <nbd> yes, all asus devices do, imho
Aug 26 13:09:31 <nbd> and they go into tftp-wait mode if you press reset while plugging in power
Aug 26 13:09:34 <nbd> ;)
Aug 26 13:09:42 <mb___> cool
Aug 26 13:10:09 <mb___> anything special needed for flashing an image?
Aug 26 13:10:38 <mb___> Loader:raw Filesys:memory Dev:eth0 File::0x8049a790 Options:(null)
Aug 26 13:10:39 <mb___> Loading: . 0 bytes read
Aug 26 13:10:39 <mb___> Failed.
Aug 26 13:10:39 <mb___> Could not load :0x8049a790: Error
Aug 26 13:12:11 <nbd> just push a .trx file to the tftp server of the boot loader
Aug 26 13:12:24 <mb___> oh crap trx
Aug 26 13:12:38 <mb___> I pushed one with a linksys header :D
Aug 26 13:12:41 <nbd> heh
Aug 26 13:14:10 <mb___> yeah right. That works way better :)
Aug 26 13:16:31 <mb___> does openwrt with 2.6 kernel boot on it?
Aug 26 13:16:40 <mb___> I can't see anything in the serial console
Aug 26 13:17:02 <nbd> last time i tried it, it wokred
Aug 26 13:17:06 <nbd> but that was before 2.6.25
Aug 26 13:17:09 <nbd> quite a while ago
Aug 26 13:17:46 <nbd> so you have a uart module with which you can actually see the boot loader on the wl-500g?
Aug 26 13:18:00 <nbd> with my module i can only see kernel messages, not boot loader stuff
Aug 26 13:18:39 <nbd> i just have a small board with an old 16540 uart module on it
Aug 26 13:19:06 <mb___> the wl500g has serial built in
Aug 26 13:19:11 <mb___> This is version 2
Aug 26 13:19:35 <nbd> are you really talking about the wl-500g or do you have a wl-500g premium or deluxe?
Aug 26 13:19:39 <mb___> I bought it to work with wireless LP-PHY
Aug 26 13:19:43 <mb___> premium
Aug 26 13:19:45 <nbd> ah, wl-500g premium
Aug 26 13:19:56 <nbd> i never tested that one
Aug 26 13:20:02 <nbd> don't have the hw
Aug 26 13:20:05 <mb___> ok
Aug 26 13:20:10 <mb___> Seems it doesn't work :P
Aug 26 13:20:27 <nbd> wl-500g is the old thing with 4710, no uart and bcm4306 minipci card
Aug 26 13:20:49 <mb___> ah I see
Aug 26 13:20:49 <nbd> btw. there were patches on our mailing list that update b43 and fix it up for the ssb version that we're using
Aug 26 13:20:52 <nbd> did you take a look at that
Aug 26 13:20:53 <nbd> ?
Aug 26 13:20:56 <mb___> This is 5354
Aug 26 13:21:03 <nbd> i think i've seen some 5354 patches in our trac as well at some point
Aug 26 13:21:05 <nbd> for 2.6
Aug 26 13:21:32 <mb___> yeah well. It's simply impossible to keep track of patches sent by random people to openwrt
Aug 26 13:21:51 <nbd> that's why i'm pointing you at them
Aug 26 13:21:54 <nbd> do you want the subject name?
Aug 26 13:21:56 <nbd> i can look i up
Aug 26 13:22:28 <mb___> I most likely deleted them, as I hardly read anything on the lists
Aug 26 13:22:45 <mb___> what was this about?
Aug 26 13:22:54 <mb___> Just updating to mainline versions?
Aug 26 13:23:14 <mb___> The last UART changes I made to ssb were back when I fixed the 250n
Aug 26 13:23:16 <mb___> 350n
Aug 26 13:23:19 <nbd> yes, and fixing up ssb stuff so it works with our brcm47xx port
Aug 26 13:23:34 <mb___> "works with our brcm47xx port"??
Aug 26 13:23:52 <nbd> well with the ssb version that we use there
Aug 26 13:23:59 <nbd> seems like he backported some ssb stuff in b43
Aug 26 13:24:06 <mb___> ah well, you mean the arch bits that access ssb
Aug 26 13:24:08 <nbd> yes
Aug 26 13:24:26 <mb___> well yeah. I don't believe that fixes this.
Aug 26 13:24:40 <mb___> I think it simply fails to setup the uart correctly in the mips core code
Aug 26 13:24:49 <nbd> i wasn't referring to this particular issue
Aug 26 13:24:52 <mb___> ah
Aug 26 13:24:55 <nbd> different topic, sorry ;)
Aug 26 13:25:07 <mb___> yeah ok.
Aug 26 13:25:14 <nbd> i hope i get around to testing it soon
Aug 26 13:25:19 <mb___> Well, if there are any patches, feel free to apply them
Aug 26 13:25:33 <nbd> just wanted to check in with you in case you had already taken a look
Aug 26 13:25:37 <nbd> you know more about b43 than me ;)
Aug 26 13:27:30 <mb___> so well. Let's hack some CFE printks into the code :)
Aug 26 13:30:31 <mb___> Unrelated question: do you know what a maxim c78091 does? I cannot find anything in google.
Aug 26 13:31:00 <mb___> it is some rs232 thing, but I need pinout
Aug 26 13:31:09 <blogic> mb___: i sec ....
Aug 26 13:31:13 * blogic gets ref sheets
Aug 26 13:35:51 <blogic> mb___: sure it is not a voltage regulator ?
Aug 26 13:36:15 <mb___> well, with google you find references to a PCMCIA voltage regulator :)
Aug 26 13:36:23 <blogic> whats the package ?
Aug 26 13:36:25 <mb___> But it is used on a RS232->USB converter device
Aug 26 13:36:29 <blogic> soic28 ?
Aug 26 13:36:43 <mb___> yeah
Aug 26 13:36:57 <blogic> hmmz
Aug 26 13:36:59 <blogic> 1 sec
Aug 26 13:37:09 <mb___> the maxim chip converts the RS232 signals to be used by the PL2303
Aug 26 13:37:26 <blogic> ok
Aug 26 13:37:29 <mb___> so I wonder if it converts it to 5V TTL
Aug 26 13:37:48 <mb___> In this case I could get rid of it _and_ of the other maxim that converts from 5V TTL to RS232 :)
Aug 26 13:38:38 <mb___> This is important, as this is a device for carrying in one hand. So less chips makes mb's PCB design less messy :)
Aug 26 13:38:54 <blogic> ah
Aug 26 13:39:06 <blogic> you are looking for ttl or rs232, levels when you are done ?
Aug 26 13:39:19 <blogic> mb___: are you making your own pcb ?
Aug 26 13:39:28 <blogic> if so, i can give you ftdi pcbs
Aug 26 13:39:31 <mb___> I have serial on TTL level and want to get to USB
Aug 26 13:39:41 <blogic> ok
Aug 26 13:39:41 <mb___> Yeah, but I do have this one.
Aug 26 13:39:52 <blogic> erm ...
Aug 26 13:39:56 <mb___> I know that you can also get spare ftdis
Aug 26 13:40:02 <blogic> yes
Aug 26 13:40:10 <blogic> let me ask differently ...
Aug 26 13:40:22 <blogic> a) you are hacking an exisiting pcb ?
Aug 26 13:40:28 <mb___> no
Aug 26 13:40:40 <blogic> b) you are making a new one from scratch and wanna use a prolific
Aug 26 13:40:47 <mb___> It is to be designed, but there's not a lot of space in the case
Aug 26 13:40:53 <blogic> ok
Aug 26 13:40:57 <blogic> in that case ....
Aug 26 13:41:15 <mb___> No I mean, in the surrounding case
Aug 26 13:41:17 <blogic> when do you need it by ?
Aug 26 13:41:26 <blogic> my pcbs are 3cm x 1,2cm
Aug 26 13:41:37 <blogic> including a usb-b connector
Aug 26 13:41:38 <mb___> No I don't need anything.
Aug 26 13:41:42 <mb___> I have everything I need.
Aug 26 13:41:43 <blogic> ok
Aug 26 13:41:45 <blogic> ok
Aug 26 13:41:47 <blogic> fine
Aug 26 13:41:54 <mb___> I'm just wondering if I can get rid of these two useless chips
Aug 26 13:42:08 <nbd> i'm pretty sure you can
Aug 26 13:42:11 <mb___> because of one converts from TTL to RS232 and one back, it's basically useless
Aug 26 13:42:11 <blogic> yes
Aug 26 13:42:13 <blogic> you can
Aug 26 13:42:25 <blogic> prolific has direct 3,3V level, that are 5V tolerant
Aug 26 13:42:31 <mb___> ok
Aug 26 13:42:40 <blogic> and if your target system uses 5V, it will 95% be 3,3v toleratn
Aug 26 13:42:44 <mb___> I think I'll just check the pinout with the scope
Aug 26 13:42:49 <blogic> fine
Aug 26 13:42:58 <blogic> my ftdis have 2 caps + chip :)
Aug 26 13:43:08 <mb___> yeah 3.3V should be fine. The target is an atmel mega32
Aug 26 13:43:13 <blogic> lol
Aug 26 13:43:14 <blogic> ok
Aug 26 13:43:30 <blogic> in taht case, it is 3,3V tolerant if you drive it with a max of 5,4V
Aug 26 13:43:46 <blogic> at 5,5V VCC on the avr, it starts to have issues with 3,3V
Aug 26 13:43:58 <mb___> ok
Aug 26 13:44:14 <blogic> 30% tolerance is what i normally go with and it has worked so for
Aug 26 13:44:16 <mb___> I'll drive it with 5V USB power
Aug 26 13:44:20 <blogic> sue
Aug 26 13:44:22 <blogic> sure
Aug 26 13:44:37 <blogic> what are you building ? just out of noseyness
Aug 26 13:44:38 <blogic> :)
Aug 26 13:44:42 * blogic lover avrs
Aug 26 13:44:47 * blogic loves avr
Aug 26 13:45:29 <mb___> a tiny handcarried device to control a CNC machine based on emc2 (linuxcnc.org)
Aug 26 13:46:04 <mb___> The device basically has a few knobs to tell the machine where to travel and an LCD for status
Aug 26 13:46:23 <blogic> nice
Aug 26 13:46:32 * blogic drives his cnc using win95 :)
Aug 26 13:46:38 <mb___> :)
Aug 26 13:46:44 <blogic> in dos mode :)
Aug 26 13:46:47 <blogic> using pcnc
Aug 26 13:46:51 <blogic> \o/
Aug 26 13:46:53 <mb___> emc2 is quite nice and mature
Aug 26 13:46:59 <blogic> what lcd ? hd44780 ?
Aug 26 13:47:02 <mb___> yeah
Aug 26 13:47:04 <blogic> or summin more cmplex ?
Aug 26 13:47:05 <blogic> ok
Aug 26 13:47:14 <mb___> 2x16 chars
Aug 26 13:47:14 <blogic> what size is the cnc ?
Aug 26 13:47:21 <mb___> tiny
Aug 26 13:47:22 <mb___> :)
Aug 26 13:47:32 <blogic> i wanna make a GPIO_GENERIC_LCD driver :)
Aug 26 13:47:51 <mb___> x200 y70 z maybe 300 to 400, dunno
Aug 26 13:48:41 <blogic> nice
Aug 26 13:48:43 <mb___> for AVR or what?
Aug 26 13:48:50 <blogic> no, linux
Aug 26 13:49:01 <blogic> to drive hd44780 over generic_gpio
Aug 26 13:49:03 <mb___> ah for driving hd44780 over GPIO
Aug 26 13:49:06 <blogic> and some other display
Aug 26 13:49:19 <mb___> nice
Aug 26 13:49:21 <blogic> i have a lot of old avr code for several of the common lcd controllers
Aug 26 13:49:34 <blogic> just needs to be ported really but as usual its a matter of time :)
Aug 26 13:49:46 <mb___> Also for graphical displays?
Aug 26 13:50:15 <blogic> yeah
Aug 26 13:50:41 <blogic> the code i have includes several lcds used inside mobile phones
Aug 26 13:50:46 <blogic> the S65 has a nice display
Aug 26 13:51:14 <mb___> SED1530 by chance?
Aug 26 13:51:15 <mb___> :)
Aug 26 13:52:06 <mb___> or LH155
Aug 26 13:52:43 <blogic> SED1530 yes
Aug 26 13:52:47 <mb___> You can get these for 3EUR at pollin.de. That's why I ask :)
Aug 26 13:52:53 <blogic> i know
Aug 26 13:52:56 <mb___> cool. Can you send me the code?
Aug 26 13:53:06 <blogic> i will have to go looking for it, but yes
Aug 26 13:53:29 <mb___> Ok, if you don't find it, it's also OK
Aug 26 13:55:14 <mb___> actually, I wrote some graphical LCD driver some time ago, I don't know what controller it is. I simply reverse engineered the original firmware of the device.
Aug 26 13:55:24 <mb___> So I wonder if I some day find out :)
Aug 26 13:55:37 <mb___> because there's a lot of stuff I don't understand without docs :DE
Aug 26 13:55:54 <blogic> :)
Aug 26 13:56:01 <mb___> http://bu3sch.de/gitweb?p=wifiscanner.git;a=blob;f=m168_firmware/lcd.c;h=f2a3469c3ed525722fd25e05c81583f6297a78af;hb=HEAD
Aug 26 14:08:18 <mb___> dah, stupid CFE :(
Aug 26 14:08:23 <mb___> That's soooo broken
Aug 26 14:13:13 <mb___> doesn't want to flash anymore :(
Aug 26 14:13:36 <farnz> blogic: I know I'm being a pain, but how are negotiations with Infineon over Danube DSL drivers going?
Aug 26 14:14:00 <blogic> :)
Aug 26 14:14:18 <blogic> farnz: i hope to have time to test the current code on the weekend, apparently it is working :)
Aug 26 14:14:28 <farnz> And they'll let you upstream it?
Aug 26 14:14:30 <blogic> if so, i will do my best to get binaries release asao
Aug 26 14:14:37 <blogic> as binaries probably yes
Aug 26 14:14:52 <blogic> and maybe we can compile those binaries ourselves ? :)
Aug 26 14:15:32 <farnz> I can live with binaries :)
Aug 26 14:15:50 <blogic> so can i, especially if i can compile them myself :)
Aug 26 14:16:07 <blogic> its not a good solution in the long run, but better than none
Aug 26 14:16:26 <farnz> If we get the source publically distributable (although not GPL), that's still good.
Aug 26 14:20:04 <mb___> gaaah, I'll try to flash another CFE. That is soooo fscking buggy. It doesn't work at all
Aug 26 15:25:25 <sn9> farnz: are there generic ar7 bootloaders available anywhere? the pspboot in my wag54gp2 does not have network support of any kind compiled in
Aug 26 15:27:40 <farnz> sn9: http://www.seattlewireless.net/moin.cgi/ADAM2#head-e3839784f0a6069b71cdcb39fc4d775d47ee0124
Aug 26 15:30:51 <sn9> downloading...
Aug 26 15:48:23 <fish_> re
Aug 26 15:51:47 <x-alina> nbd: Is the httpd patch so okay?
Aug 26 15:56:48 <sn9> farnz: this might be better: ftp://ftp.a-link.com/opensource/RR2x/371/nsp_371.p0.AVK.tgz
Aug 26 15:57:23 <farnz> sn9: Probably - I've never needed to change the bootloader.
Aug 26 15:57:42 <farnz> I just have the seattlewireless link to hand, as it documents the bootloader I've got.
Aug 26 15:58:04 <sn9> so, you only use adam2?
Aug 26 15:59:04 <farnz> Yes.
Aug 26 15:59:18 <sn9> on how many models?
Aug 26 15:59:43 <farnz> Just two D-Links.
Aug 26 15:59:52 <sn9> both g604t?
Aug 26 16:00:21 <farnz> No, G604T and 502T.
Aug 26 16:00:40 <nbd> x-alina: on a first look, yes. i'll commit it later
Aug 26 16:00:59 <x-alina> nbd: okay, thanks :)
Aug 26 16:01:07 <sn9> have you seen the howto for changing bootloaders on the 502t?
Aug 26 16:01:34 <farnz> Nope.
Aug 26 16:01:50 <farnz> And both my D-Links now have failing flash, so I don't dare change the bootloader.
Aug 26 16:02:03 <sn9> :(
Aug 26 17:19:43 <CIA-9> florian * r12394 /trunk/package/hostapd/files/hostapd.sh:
Aug 26 17:19:43 <CIA-9> A WPA(2) pre-shared key can either be specified as a 8 to 63 character
Aug 26 17:19:43 <CIA-9> passphrase which is hashed to a 256 bit key together with the SSID, or a 64
Aug 26 17:19:43 <CIA-9> character hex key. Currently, the latter option is supported by the broadcom
Aug 26 17:19:43 <CIA-9> wifi type, but no by hostapd. The attached patch allows using a 64 character hex
Aug 26 17:19:46 <CIA-9> key. (#3935)
Aug 26 17:19:48 <CIA-9> Signed-off-by: thomas@archlinux.org
Aug 26 17:20:36 <sn9> [florian]: what about multiple ssid's?
Aug 26 17:20:44 <blogic> sn9: ?
Aug 26 17:20:55 <blogic> that requires 2 hostapd instances
Aug 26 17:21:16 <sn9> then mac80211.sh could be patched for that
Aug 26 17:44:13 <sn9> now flashing this, in the hopes that it will work: http://www.dynamode.co.uk/support/drivers/beta/psbl.AR7WRD.bin
Aug 26 18:11:16 <sn9> now flashing pspboot from this, in the hopes that it will work: http://star.oai.pp.ru/dlinkt/dsl300t-intel-acorp.zip
Aug 26 19:14:05 <[florian]> sn9: I will fix that later
Aug 26 19:26:36 <sn9> now flashing a self-compiled pspboot, in the hopes that it will work
Aug 26 21:19:26 <exovii> Hi people !
Aug 26 21:19:33 <wrt> hey
Aug 26 21:52:28 <exovii> Do you know if a GPLed driver for BCM5380 switch exists ?
Aug 26 21:55:05 <[florian]> bcm5380 ?
Aug 26 21:55:22 <[florian]> try bcm57xx maybe
Aug 26 21:56:00 <[florian]> it should be relatively similar
Aug 26 22:14:18 <exovii> but isn't bcm57xx a cpu ?
Aug 26 22:18:33 <exovii> I saw that bcm57xx are a line of ethernet controller. bcm53xx are a line of ethernet switches... :(
Aug 26 22:24:44 <exovii> What is BCM5380: http://www.broadcom.com/products/Small-Medium-Business/Fast-Ethernet-Switching-Products/BCM5380
Aug 26 22:25:19 <exovii> FYI, this is the switch on Netgear FVX538v1
Aug 26 22:45:35 <sn9> exovii: in the 2.4 branch, there is a driver for the 57xx switches (47xx are cpu's)
Aug 26 22:45:51 <sn9> that includes the 5380, iirc
Aug 26 22:46:30 <exovii> ok, but i'm afraid 5380 is not in the 57xx line as it has a gigabit port...
Aug 26 22:47:53 <sn9> all your 57xx are belong to gigabit
Aug 26 22:50:39 <exovii> you're tight, 57xx are gigabit, but they are ethernet controllers and not switch, as the BCM5380
Aug 26 22:50:51 <exovii> Will the 57xx driver work with a switch ?
Aug 26 22:51:01 <exovii> s/tight/right
Aug 26 22:51:39 <sn9> the 53xx switches are handled by the 57xx driver under 2.4
Aug 26 22:52:19 <exovii> ok
Aug 26 22:52:22 <sn9> under 2.6, they would be handled by tigon3, if they were handled at all, which they're not
Aug 26 22:53:14 <exovii> do you mean icould try tigon3 ?
Aug 26 22:53:46 <sn9> it won't work; i tried
Aug 26 22:54:09 <sn9> some kind of off-by-one bug
Aug 26 22:55:14 <exovii> ok. Looks like you have the same problem...
Aug 26 22:55:31 <sn9> works in 2.4
Aug 26 22:55:53 <exovii> But is intel ixp4xx supported under 2.4 ?
Aug 26 22:56:45 <sn9> no, that needs 2.6
Aug 26 22:57:04 <sn9> so, someone has to fix tigon3
Aug 26 22:57:05 <exovii> he he ! So i'm out of luck...
Aug 26 23:00:01 <exovii> i don't understand: isn't tigon3 just for broadcom gigabit ethernet controllers ?
Aug 26 23:00:27 <sn9> yes, but that's where the switch support would need to go
Aug 26 23:01:15 <sn9> with the strange ssb bus broadcom devices have
Aug 26 23:01:33 <exovii> ok, you mean that tigon3 misses switch support...
Aug 26 23:02:29 <sn9> yep
Aug 26 23:04:17 <exovii> So i have to go with my poor NPE-C and RTL8110...
Aug 26 23:07:47 <exovii> i just saw that tigon3.c in bcm57xx package has to deal with robocfg (bcm5380 is a roboswitch)...
Aug 26 23:09:16 <sn9> i mean tg3, not tigon3
Aug 26 23:12:36 <exovii> yes, but both are drivers for broadcom gigabit, isn't it ?
Aug 26 23:12:49 <exovii> one for 2.4, the other for 2.6, nope ?
Aug 26 23:13:29 <sn9> right
Aug 26 23:16:33 <exovii> Many thanks for these explanations !
**** ENDING LOGGING AT Wed Aug 27 02:59:56 2008