[00:43] <[mbm]> nbd: poke
[00:51] <nbd> yep?
[00:52] <[mbm]> was thinking about the make stuff
[00:52] <[mbm]> the lines are all structured like "$(MAKE) ..."
[00:53] <[mbm]> and not the old "$(MAKE) ... $(TRACE)"
[00:53] <[mbm]> but what happens if we do this -
[00:54] <[mbm]> MAKE:=cmd() { $(MAKE) $$* $(TRACE); }; cmd
[00:54] <nbd> makes sense
[00:54] <[mbm]> not exactly portable but it would allow us to trap ng errors better
[00:55] <nbd> yeah
[00:57] <[mbm]> the other thing that's odd about ng is that if there's an error with the package/*/Makefile you'll never see an error
[00:57] <[mbm]> the package just won't show up
[00:58] <florian___> where would be the best place in include/package.mk to put a template init.d script ?
[00:58] <[mbm]> careful, you don't want to include package.mk twice
[00:58] <florian___> that's right
[00:59] <[mbm]> (I'm guessing that any script that uses your init.d template also uses package.mk)
[00:59] <florian___> well in fact, I was thinking of putting the init.d template in package.mk ?
[01:01] <florian___> or maybe, just reference the init.d in template.mk and create init.mk ?
[01:52] <CIA-17> mbm * r4096 /branches/buildroot-ng/openwrt/include/verbose.mk: minor changes
[01:53] <CIA-17> nbd * r4097 /branches/buildroot-ng/openwrt/package/iptables/files/ (firewall.awk firewall.config firewall.init firewall.user): add missing copyright notices
[11:00] <florian___> the new downloads.openwrt.org page looks great
[11:00] <florian___> maybe a little bit too "nighty" ;)
[11:16] <[mbm]> florian___: you can change the colors
[11:22] <florian___> it's ok like that
[11:22] <[mbm]> :)
[11:28] <florian___> where is the best place to put the init.d template ? in a separate file, called when need by package.mk ?
[11:29] <[mbm]> should probably just be called by the makefile after package.mk
[11:29] <florian___> ok, so it would be package specific
[11:29] <[mbm]> well, at the point that it becomes called from package.mk it should just be in the packages.mk
[11:32] <florian___> ok
[14:13] <nbd> florian___: before you start adding lots of init scripts, i think we should maybe agree on a standard template, which moves most of the code into a common file
[15:39] <florian___> nbd: that's what I want
[15:43] <florian___> I did not meant I wanted to add lots of init scripts,just define a template to be used when it's convenient
[17:04] <nbd> florian___: but i'm talking about a template on the filesystem in openwrt, not a template in the build system
[17:04] <nbd> did you mean that as well?
[19:30] <CIA-17> nbd * r4098 /branches/buildroot-ng/openwrt/include/kernel-build.mk: add workaround for kernel module install
[19:52] <CIA-17> kaloz * r4099 /branches/buildroot-ng/openwrt/toolchain/ (17 files in 8 dirs): add binutils 2.17 and remove the beta versions, update some gcc 4.1.1 patches
[21:08] <florian___> nbd: ah no, I was just talking about a template in the build system
[21:08] <nbd> i mean why waste flash space with the same stuff over and over again
[21:08] <nbd> if we can move it into a common file
[21:09] <florian___> right
[21:10] <nbd> did you get my message?
[21:10] <florian___> with optionnal ovveridable options for particular programs
[22:05] <rezso> anyone experienced wrt55ag ?
[22:06] <rezso> got some serial console ?
[22:09] <[mbm]> there's multiple wrt55ag revisions
[22:09] <[mbm]> and the wiki has the serial pinout
[22:18] <rezso> yes i got it.
[22:18] <rezso> i have other issue.
[22:19] <rezso> strangely, i got the box with 1.30 installed. I cant put nor 1.10 or 1.67 on it .. Always poke about "Wrong firmware"
[22:19] <rezso> hearde that need 1.40 first ...
[22:19] <rezso> have someone 1.40 ?
[22:19] <rezso> well, guys if have some idea ?
[22:20] <[mbm]> we don't run the normal firmwares
[22:20] <rezso> well, of course tyed the GPL pack from tham i cant put that on it.
[22:20] <rezso> that is my final poit at all ...
[22:22] <rezso> BTW, i got a serial console [3.3V level shifter] with lots of equipment it work well, with this 55ag in 9600 8N1 i got to see what happen but the caracters written in minicom/hyperterm are somehow doubled by strange characters ...
[22:22] <rezso> is it plain 9600 8N1 ?
[22:22] <rezso> or 1.30 frm has something ?
[22:22] <h3sp4wn> 115200 8N1 (probably)
[22:22] <[mbm]> I don't even remember now, it's been over a year since I've used mine
[22:22] <rezso> tryed too ...
[22:22] <rezso> not work.
[22:22] <rezso> i try again now.
[22:23] <rezso> anyone know that thair GPL code [released recently] work fine ?
[22:24] <[mbm]> rezso: I think you're on your own when it comes to the wrt55ag
[22:24] <rezso> 115200 not work :=(
[22:24] <rezso> mbm: well, what to say.
[22:24] <malbon> rezso: it's 9600 8n1
[22:25] <rezso> can i reask [maybe someone can help], does anyone have 1.40 firmware for WT55ag ?
[22:25] <rezso> soory for this, i need to see if 1.30 is pikky about loading gpl code.
[22:26] <rezso> malbon: well in 9600 8n1 [flow ctrl OFF] i still see doubled strange chars, i cant use in that way the console.
[22:26] <rezso> i suspect this 1.30 firmware ...
[22:27] <rezso> or cable ? [hard to think becouse i have lot of succes with it]
[22:27] <malbon> rezso: have you got a broadcom one or atheros?
[22:27] <rezso> atheros v2.0
[22:27] <malbon> atheros is 9600 8N1
[22:27] <rezso> my cable work fine [used to develop lots of xilinx/arm stuff]
[22:28] <rezso> sorry for that ugly paste: Attaching to TFFS... 08|l<.~^[~.done.
[22:28] <rezso> something like this stangeness i got.
[22:28] <rezso> unbeliveble ...
[22:28] <rezso> is ejtag work ?
[22:29] <rezso> or leak of ejtag software ?
[22:29] <malbon> no, just escape the bootloader.
[22:30] <rezso> malbon: how far you reached with these atheros ?
[22:30] <rezso> tryed recently released linksys GPL codes for tham ?
[22:31] <malbon> linksys have released code? wow.
[22:32] <malbon> they run vxworks so it doesn't help you much.
[22:32] <malbon> Ih've had a kernel booted before.
[22:32] <malbon> try http://212.13.213.202/wrt55ag.ram :)
[22:32] <rezso> well, thay have something new at GPL part, for 55ag. I looked and really is something for v2 atheros.
[22:33] <[mbm]> don't get confused, there are multiple versions of the 55ag, some linux and some vxworks
[22:33] <rezso> ftp://ftp.linksys.com/opensourcecode/wrt55ag/1.1/wrt55ag.1.1.tar.gz
[22:34] <malbon> the version 1 (broadcom) was linux
[22:34] <malbon> the version 2 (atheros) is vxworx
[22:34] <rezso> if want take a look, as i am unable to get serial, its hard to try out.
[22:34] <[mbm]> right, and I think rezso is trying to load the broadcom code on the atheros
[22:34] <rezso> hmm wait.
[22:34] <malbon> that tarball is for the broadcom that's right.
[22:35] <rezso> shiit.
[22:35] <rezso> true !
[22:36] <rezso> in tar.gz its about BCM, now i take a look in .config of kernel ...
[22:36] <rezso> sorry.
[22:36] <rezso> the atheros port from openwrt support wireless >
[22:36] <rezso> ?
[22:37] <malbon> rezso: try the redboot image I just posted the link too. the switch driver doesn't work, but it'll allow you to back up the flash of your wrt55ag (very important) to protect the radio settings.
[22:37] <rezso> i downloaded .ram file.
[22:37] <rezso> its loadable from rs232 console only ?
[22:37] <[mbm]> if the board has a minipci card then madwifi will support the wireless, if it's integrated then you'll have to wait for madwifi to release a new hal
[22:37] <malbon> nope the atheros port is currently non functional, it's being worked on.
[22:38] <[mbm]> think only the original broadcom board had minipci
[22:38] <malbon> like the wrt54g v5 it uses the VXworks bsp, but the ram file is a redboot bootloader which is linux friendly.
[22:38] <[mbm]> and all the atheros ones were soc
[22:39] <rezso> v2 is atheros, SoC. no minipci.
[22:39] <malbon> follow the instructions on the wgt624 page to load it via tftp.
[22:39] <[mbm]> and no madwifi support for you
[22:39] <[mbm]> so no wireless
[22:39] <rezso> can i ask again if the .ram file is loadable from serial menu only ?
[22:39] <malbon> yes, you need to do it from the bootloader.
[22:40] <malbon> it's an elf.
[22:40] <rezso> uhm ... well need to see what has this cable wrong ...
[22:40] <malbon> using minicom?
[22:40] <rezso> yes, but same issue in Hypertem/w32 ...
[22:41] <malbon> ok.
[22:41] <rezso> dunno, i can swear myself for this cable ...
[22:41] <malbon> got local echo turned on?
[22:41] <rezso> i measured atheros is standard 3.3 TTL so no prblm.
[22:41] <[mbm]> turned flow control off?
[22:41] <rezso> where is local echo ?
[22:41] <rezso> [i take a look now]
[22:41] <[mbm]> in minicom local echo is ^a-e
[22:42] <rezso> mean [Esc]a-e ?
[22:42] <[mbm]> ctrl
[22:42] <[mbm]> hmm been ages since I used minicom
[22:42] Action: [mbm] looks
[22:42] <malbon> I did have something similar I think, can't remeber what I did. probably just pulled my usb serial convertor out and plugged it in again.
[22:43] <rezso> it is off [tryed on too, a]nd its worse]
[22:43] <rezso> tryed on 2 PC with native serial too.
[22:43] <malbon> you don't want it on.
[22:43] <[mbm]> (yeah, ctrl-a e)
[22:44] <malbon> which direction do they double?
[22:44] <rezso> let me paste:
[22:44] <malbon> from the device? or only when you type stuff?
[22:44] <rezso> here i typed "help" --> "h|~.e.l~.px|~."
[22:44] <rezso> from device too, and when i type too ...
[22:45] <rezso> very strange ...
[22:45] <[mbm]> sounds like you've miswired the serial
[22:45] <rezso> hmm, i tryed many combination, but followed openwrt pinout at last.
[22:45] <[mbm]> you can get similar errors if you use vcc-tx instead of tx-gnd
[22:45] <malbon> sounds like a short between rx and tx more like.
[22:46] <rezso> Incredible !!!
[22:46] <rezso> thx ! i unwirred my TX and now i can see clearly what device say on my RX ...
[22:46] <rezso> i waste 3 hours ...
[22:47] <rezso> malbon: thx !
[22:47] <rezso> you was more patient than me !
[22:47] <malbon> all my cables get too used, I am always patching up the solder. :)
[22:47] <rezso> shiit ...
[22:48] Action: [mbm] has switched to using actual headers
[22:48] <rezso> i will looking to see what has my cable ...
[22:48] <[mbm]> cables last longer
[22:48] <rezso> malbon, with their vxworks can i overpower in dB from serial console ?
[22:48] <malbon> yes I do that for the bit to the 'dev board' but the pc cable is just normal soldered.
[22:48] <malbon> rezso: nope
[22:48] <rezso> :-(
[22:49] <malbon> rezso: vxworks is evil, bad, wrong and evil.
[22:49] <rezso> are these device usable in 5Ghz with external antenna ? can i expect something good from tham ?
[22:49] <[mbm]> rezso: should
[22:49] <malbon> the 5Ghz radios are good in them.
[22:50] <malbon> especailly with a parabolic.
[22:50] <rezso> mbm: can tell how far i can foo with tham ?
[22:50] <rezso> yes i want 24dB parabolic antennas.
[22:50] Action: [mbm] has never had a problem with atheros chips
[22:50] <rezso> can i do something like 10km with tham ?
[22:51] <malbon> probably.
[22:52] <rezso> well, guys i think i runned out of ideas !
[22:52] <rezso> thanks for help ! was really great !
[22:53] <rezso> when to expect an openwrt port for these little boxes ? is there chance ?
[22:53] <malbon> rezso: Atheros port is a work in progress, keep checking the wiki page for more news.
[22:53] <rezso> i will.
[00:00] --- Thu Jun 29 2006
[00:51] <nbd> yep?
[00:52] <[mbm]> was thinking about the make stuff
[00:52] <[mbm]> the lines are all structured like "$(MAKE) ..."
[00:53] <[mbm]> and not the old "$(MAKE) ... $(TRACE)"
[00:53] <[mbm]> but what happens if we do this -
[00:54] <[mbm]> MAKE:=cmd() { $(MAKE) $$* $(TRACE); }; cmd
[00:54] <nbd> makes sense
[00:54] <[mbm]> not exactly portable but it would allow us to trap ng errors better
[00:55] <nbd> yeah
[00:57] <[mbm]> the other thing that's odd about ng is that if there's an error with the package/*/Makefile you'll never see an error
[00:57] <[mbm]> the package just won't show up
[00:58] <florian___> where would be the best place in include/package.mk to put a template init.d script ?
[00:58] <[mbm]> careful, you don't want to include package.mk twice
[00:58] <florian___> that's right
[00:59] <[mbm]> (I'm guessing that any script that uses your init.d template also uses package.mk)
[00:59] <florian___> well in fact, I was thinking of putting the init.d template in package.mk ?
[01:01] <florian___> or maybe, just reference the init.d in template.mk and create init.mk ?
[01:52] <CIA-17> mbm * r4096 /branches/buildroot-ng/openwrt/include/verbose.mk: minor changes
[01:53] <CIA-17> nbd * r4097 /branches/buildroot-ng/openwrt/package/iptables/files/ (firewall.awk firewall.config firewall.init firewall.user): add missing copyright notices
[11:00] <florian___> the new downloads.openwrt.org page looks great
[11:00] <florian___> maybe a little bit too "nighty" ;)
[11:16] <[mbm]> florian___: you can change the colors
[11:22] <florian___> it's ok like that
[11:22] <[mbm]> :)
[11:28] <florian___> where is the best place to put the init.d template ? in a separate file, called when need by package.mk ?
[11:29] <[mbm]> should probably just be called by the makefile after package.mk
[11:29] <florian___> ok, so it would be package specific
[11:29] <[mbm]> well, at the point that it becomes called from package.mk it should just be in the packages.mk
[11:32] <florian___> ok
[14:13] <nbd> florian___: before you start adding lots of init scripts, i think we should maybe agree on a standard template, which moves most of the code into a common file
[15:39] <florian___> nbd: that's what I want
[15:43] <florian___> I did not meant I wanted to add lots of init scripts,just define a template to be used when it's convenient
[17:04] <nbd> florian___: but i'm talking about a template on the filesystem in openwrt, not a template in the build system
[17:04] <nbd> did you mean that as well?
[19:30] <CIA-17> nbd * r4098 /branches/buildroot-ng/openwrt/include/kernel-build.mk: add workaround for kernel module install
[19:52] <CIA-17> kaloz * r4099 /branches/buildroot-ng/openwrt/toolchain/ (17 files in 8 dirs): add binutils 2.17 and remove the beta versions, update some gcc 4.1.1 patches
[21:08] <florian___> nbd: ah no, I was just talking about a template in the build system
[21:08] <nbd> i mean why waste flash space with the same stuff over and over again
[21:08] <nbd> if we can move it into a common file
[21:09] <florian___> right
[21:10] <nbd> did you get my message?
[21:10] <florian___> with optionnal ovveridable options for particular programs
[22:05] <rezso> anyone experienced wrt55ag ?
[22:06] <rezso> got some serial console ?
[22:09] <[mbm]> there's multiple wrt55ag revisions
[22:09] <[mbm]> and the wiki has the serial pinout
[22:18] <rezso> yes i got it.
[22:18] <rezso> i have other issue.
[22:19] <rezso> strangely, i got the box with 1.30 installed. I cant put nor 1.10 or 1.67 on it .. Always poke about "Wrong firmware"
[22:19] <rezso> hearde that need 1.40 first ...
[22:19] <rezso> have someone 1.40 ?
[22:19] <rezso> well, guys if have some idea ?
[22:20] <[mbm]> we don't run the normal firmwares
[22:20] <rezso> well, of course tyed the GPL pack from tham i cant put that on it.
[22:20] <rezso> that is my final poit at all ...
[22:22] <rezso> BTW, i got a serial console [3.3V level shifter] with lots of equipment it work well, with this 55ag in 9600 8N1 i got to see what happen but the caracters written in minicom/hyperterm are somehow doubled by strange characters ...
[22:22] <rezso> is it plain 9600 8N1 ?
[22:22] <rezso> or 1.30 frm has something ?
[22:22] <h3sp4wn> 115200 8N1 (probably)
[22:22] <[mbm]> I don't even remember now, it's been over a year since I've used mine
[22:22] <rezso> tryed too ...
[22:22] <rezso> not work.
[22:22] <rezso> i try again now.
[22:23] <rezso> anyone know that thair GPL code [released recently] work fine ?
[22:24] <[mbm]> rezso: I think you're on your own when it comes to the wrt55ag
[22:24] <rezso> 115200 not work :=(
[22:24] <rezso> mbm: well, what to say.
[22:24] <malbon> rezso: it's 9600 8n1
[22:25] <rezso> can i reask [maybe someone can help], does anyone have 1.40 firmware for WT55ag ?
[22:25] <rezso> soory for this, i need to see if 1.30 is pikky about loading gpl code.
[22:26] <rezso> malbon: well in 9600 8n1 [flow ctrl OFF] i still see doubled strange chars, i cant use in that way the console.
[22:26] <rezso> i suspect this 1.30 firmware ...
[22:27] <rezso> or cable ? [hard to think becouse i have lot of succes with it]
[22:27] <malbon> rezso: have you got a broadcom one or atheros?
[22:27] <rezso> atheros v2.0
[22:27] <malbon> atheros is 9600 8N1
[22:27] <rezso> my cable work fine [used to develop lots of xilinx/arm stuff]
[22:28] <rezso> sorry for that ugly paste: Attaching to TFFS... 08|l<.~^[~.done.
[22:28] <rezso> something like this stangeness i got.
[22:28] <rezso> unbeliveble ...
[22:28] <rezso> is ejtag work ?
[22:29] <rezso> or leak of ejtag software ?
[22:29] <malbon> no, just escape the bootloader.
[22:30] <rezso> malbon: how far you reached with these atheros ?
[22:30] <rezso> tryed recently released linksys GPL codes for tham ?
[22:31] <malbon> linksys have released code? wow.
[22:32] <malbon> they run vxworks so it doesn't help you much.
[22:32] <malbon> Ih've had a kernel booted before.
[22:32] <malbon> try http://212.13.213.202/wrt55ag.ram :)
[22:32] <rezso> well, thay have something new at GPL part, for 55ag. I looked and really is something for v2 atheros.
[22:33] <[mbm]> don't get confused, there are multiple versions of the 55ag, some linux and some vxworks
[22:33] <rezso> ftp://ftp.linksys.com/opensourcecode/wrt55ag/1.1/wrt55ag.1.1.tar.gz
[22:34] <malbon> the version 1 (broadcom) was linux
[22:34] <malbon> the version 2 (atheros) is vxworx
[22:34] <rezso> if want take a look, as i am unable to get serial, its hard to try out.
[22:34] <[mbm]> right, and I think rezso is trying to load the broadcom code on the atheros
[22:34] <rezso> hmm wait.
[22:34] <malbon> that tarball is for the broadcom that's right.
[22:35] <rezso> shiit.
[22:35] <rezso> true !
[22:36] <rezso> in tar.gz its about BCM, now i take a look in .config of kernel ...
[22:36] <rezso> sorry.
[22:36] <rezso> the atheros port from openwrt support wireless >
[22:36] <rezso> ?
[22:37] <malbon> rezso: try the redboot image I just posted the link too. the switch driver doesn't work, but it'll allow you to back up the flash of your wrt55ag (very important) to protect the radio settings.
[22:37] <rezso> i downloaded .ram file.
[22:37] <rezso> its loadable from rs232 console only ?
[22:37] <[mbm]> if the board has a minipci card then madwifi will support the wireless, if it's integrated then you'll have to wait for madwifi to release a new hal
[22:37] <malbon> nope the atheros port is currently non functional, it's being worked on.
[22:38] <[mbm]> think only the original broadcom board had minipci
[22:38] <malbon> like the wrt54g v5 it uses the VXworks bsp, but the ram file is a redboot bootloader which is linux friendly.
[22:38] <[mbm]> and all the atheros ones were soc
[22:39] <rezso> v2 is atheros, SoC. no minipci.
[22:39] <malbon> follow the instructions on the wgt624 page to load it via tftp.
[22:39] <[mbm]> and no madwifi support for you
[22:39] <[mbm]> so no wireless
[22:39] <rezso> can i ask again if the .ram file is loadable from serial menu only ?
[22:39] <malbon> yes, you need to do it from the bootloader.
[22:40] <malbon> it's an elf.
[22:40] <rezso> uhm ... well need to see what has this cable wrong ...
[22:40] <malbon> using minicom?
[22:40] <rezso> yes, but same issue in Hypertem/w32 ...
[22:41] <malbon> ok.
[22:41] <rezso> dunno, i can swear myself for this cable ...
[22:41] <malbon> got local echo turned on?
[22:41] <rezso> i measured atheros is standard 3.3 TTL so no prblm.
[22:41] <[mbm]> turned flow control off?
[22:41] <rezso> where is local echo ?
[22:41] <rezso> [i take a look now]
[22:41] <[mbm]> in minicom local echo is ^a-e
[22:42] <rezso> mean [Esc]a-e ?
[22:42] <[mbm]> ctrl
[22:42] <[mbm]> hmm been ages since I used minicom
[22:42] Action: [mbm] looks
[22:42] <malbon> I did have something similar I think, can't remeber what I did. probably just pulled my usb serial convertor out and plugged it in again.
[22:43] <rezso> it is off [tryed on too, a]nd its worse]
[22:43] <rezso> tryed on 2 PC with native serial too.
[22:43] <malbon> you don't want it on.
[22:43] <[mbm]> (yeah, ctrl-a e)
[22:44] <malbon> which direction do they double?
[22:44] <rezso> let me paste:
[22:44] <malbon> from the device? or only when you type stuff?
[22:44] <rezso> here i typed "help" --> "h|~.e.l~.px|~."
[22:44] <rezso> from device too, and when i type too ...
[22:45] <rezso> very strange ...
[22:45] <[mbm]> sounds like you've miswired the serial
[22:45] <rezso> hmm, i tryed many combination, but followed openwrt pinout at last.
[22:45] <[mbm]> you can get similar errors if you use vcc-tx instead of tx-gnd
[22:45] <malbon> sounds like a short between rx and tx more like.
[22:46] <rezso> Incredible !!!
[22:46] <rezso> thx ! i unwirred my TX and now i can see clearly what device say on my RX ...
[22:46] <rezso> i waste 3 hours ...
[22:47] <rezso> malbon: thx !
[22:47] <rezso> you was more patient than me !
[22:47] <malbon> all my cables get too used, I am always patching up the solder. :)
[22:47] <rezso> shiit ...
[22:48] Action: [mbm] has switched to using actual headers
[22:48] <rezso> i will looking to see what has my cable ...
[22:48] <[mbm]> cables last longer
[22:48] <rezso> malbon, with their vxworks can i overpower in dB from serial console ?
[22:48] <malbon> yes I do that for the bit to the 'dev board' but the pc cable is just normal soldered.
[22:48] <malbon> rezso: nope
[22:48] <rezso> :-(
[22:49] <malbon> rezso: vxworks is evil, bad, wrong and evil.
[22:49] <rezso> are these device usable in 5Ghz with external antenna ? can i expect something good from tham ?
[22:49] <[mbm]> rezso: should
[22:49] <malbon> the 5Ghz radios are good in them.
[22:50] <malbon> especailly with a parabolic.
[22:50] <rezso> mbm: can tell how far i can foo with tham ?
[22:50] <rezso> yes i want 24dB parabolic antennas.
[22:50] Action: [mbm] has never had a problem with atheros chips
[22:50] <rezso> can i do something like 10km with tham ?
[22:51] <malbon> probably.
[22:52] <rezso> well, guys i think i runned out of ideas !
[22:52] <rezso> thanks for help ! was really great !
[22:53] <rezso> when to expect an openwrt port for these little boxes ? is there chance ?
[22:53] <malbon> rezso: Atheros port is a work in progress, keep checking the wiki page for more news.
[22:53] <rezso> i will.
[00:00] --- Thu Jun 29 2006