| 00:10.40 | *** join/#elinux dsaxena_ (n=dsaxena@71-38-142-179.ptld.qwest.net) |
| 00:48.54 | *** join/#elinux btraynor (n=btraynor@gromit.mixdown.ca) |
| 01:15.21 | *** join/#elinux thraxisp (n=thraxisp@24.139.16.154) |
| 01:25.14 | *** join/#elinux huaynac (n=huaynac@61.6.65.198) |
| 01:37.43 | *** join/#elinux duderonomy (n=duderono@c-71-202-149-191.hsd1.ca.comcast.net) |
| 01:44.05 | *** join/#elinux thraxisp (n=thraxisp@24.139.16.154) |
| 02:00.40 | *** join/#elinux landley (n=landley@cpe-72-177-114-214.austin.res.rr.com) |
| 02:18.26 | *** join/#elinux number2 (n=chatzill@75-163-200-45.clsp.qwest.net) |
| 03:57.03 | *** part/#elinux Newbuntu2 (n=chatzill@ppp-70-243-47-160.dsl.hstntx.swbell.net) |
| 04:27.04 | *** join/#elinux GPSFan (n=kenm@12.10.255.246) |
| 05:03.44 | *** join/#elinux Dr_Who (n=tgall@gentoo/developer/dr-who) |
| 05:27.28 | *** join/#elinux dsaxena (n=dsaxena@c-71-59-208-117.hsd1.or.comcast.net) |
| 06:08.58 | *** join/#elinux TimRiker (n=timr@rikers.org) |
| 06:08.58 | *** mode/#elinux [+o TimRiker] by ChanServ |
| 08:38.34 | *** join/#elinux shri (n=boom123@61.95.195.205) |
| 08:39.07 | shri | from where can i download mkfs utility to use in an arm target |
| 09:27.05 | *** join/#elinux lyakh (n=lyakh@p57BD2C95.dip0.t-ipconnect.de) |
| 09:51.21 | *** join/#elinux AD-N770 (n=jep@nat/fluendo/x-93693b64d6d2cf1e) |
| 11:45.58 | *** join/#elinux mnemoc (n=amery@kilo105.server4you.de) |
| 12:13.34 | *** join/#elinux sjhill (n=sjhill@real.realitydiluted.com) |
| 12:48.24 | *** join/#elinux ashes (n=ashes@2001:5c0:8fff:ffff:0:0:0:6b) |
| 13:27.05 | *** join/#elinux ico2 (n=ico2@modem-3019.chimpanzee.dialup.pol.co.uk) |
| 14:05.08 | *** join/#elinux GPSFan (n=kenm@12.10.255.246) |
| 15:16.27 | *** join/#elinux ico2 (n=ico2@modem-3019.chimpanzee.dialup.pol.co.uk) |
| 15:28.32 | *** join/#elinux svolpe (n=Gerrath_@unaffiliated/gerrath) |
| 15:43.44 | *** join/#elinux thraxisp (n=thraxisp@24.139.16.154) |
| 15:44.41 | *** join/#elinux TimRiker (n=timr@68.27.235.171) |
| 15:44.42 | *** mode/#elinux [+o TimRiker] by ChanServ |
| 16:27.46 | *** join/#elinux duderonomy (n=duderono@205.158.109.36.ptr.us.xo.net) |
| 16:51.02 | *** join/#elinux RobotGuy (n=robotguy@dsl093-038-072.pdx1.dsl.speakeasy.net) |
| 16:55.39 | *** join/#elinux RobotGuy (n=robotguy@dsl093-038-072.pdx1.dsl.speakeasy.net) |
| 17:04.42 | *** join/#elinux Dr_Who (n=tgall@gentoo/developer/dr-who) |
| 17:17.27 | *** join/#elinux ico2 (n=ico2@modem-3019.chimpanzee.dialup.pol.co.uk) |
| 17:57.28 | *** join/#elinux landley (n=landley@adsl-76-197-33-46.dsl.austtx.sbcglobal.net) |
| 18:40.04 | *** part/#elinux RobotGuy (n=robotguy@dsl093-038-072.pdx1.dsl.speakeasy.net) |
| 18:48.18 | *** join/#elinux pleemans (n=peter@d51A5E76A.access.telenet.be) |
| 18:59.01 | *** join/#elinux RobotGuy (n=robotguy@dsl093-038-072.pdx1.dsl.speakeasy.net) |
| 19:17.51 | *** join/#elinux ico2 (n=ico2@modem-3019.chimpanzee.dialup.pol.co.uk) |
| 19:38.59 | *** join/#elinux ashes (n=ashes@2001:5c0:8fff:ffff:0:0:0:6b) |
| 20:08.08 | *** join/#elinux Gerrath (n=Gerrath_@unaffiliated/gerrath) |
| 20:08.36 | *** join/#elinux pb_ (n=pb@88-110-232-164.dynamic.dsl.as9105.com) |
| 20:24.27 | *** join/#elinux TimRiker (n=timr@pdpc/supporter/bronze/TimRiker) |
| 20:24.27 | *** mode/#elinux [+o TimRiker] by ChanServ |
| 21:11.07 | *** join/#elinux wiLi (n=hkml@p5B2D6A26.dip.t-dialin.net) |
| 21:21.25 | *** join/#elinux ico2 (n=ico2@modem-3019.chimpanzee.dialup.pol.co.uk) |
| 21:23.43 | wiLi | Hi, I want to get my own firmware on my NAS. I found so called GPL packages that produced a new firmware, but what do I have to expect after uploading the new firmware? Is there any way to try out the new firmware using an emulator or the like? |
| 21:28.12 | landley | Depends what it does. |
| 21:28.33 | landley | You might try qemu, but it won't emulate the exact same hardware your NAS has (or if it can, you'll spend a while setting it up). |
| 21:28.51 | landley | In general, if you have the _old_ firmware to load back on it, then just try the new firmware and revert to the old one if you don't like it. |
| 21:29.10 | landley | (If a firmware upgrade from the manufacturer turns it into a brick, return it as defective.) |
| 21:34.50 | wiLi | Well, of course I have the _old_ firmware, but will I be able to reinstall it after uploading the new firmware? I assume the http service currently allowing me to upload firmware will be gone after I installed the new firmware(?) |
| 21:34.57 | *** join/#elinux Dr_Who (n=tgall@gentoo/developer/dr-who) |
| 21:37.54 | landley | Is this a firmware upgrade, or a totally different firmware from some other vendor? |
| 21:38.11 | landley | If it's just an upgrade, the new firmware should still have a similar way to install new firmware. |
| 21:38.16 | landley | If it doesn't, they removed a feature... |
| 21:44.47 | *** join/#elinux Dr{Who} (n=mathewss@dev.null.nutech.com) |
| 21:44.56 | wiLi | To be honest: I have no idea, where this so called GPL packages do originate from. I downloaded them from ftp://opensource.zyxel.com, but I don't know, if they were provided by Zyxel itself or anybody else. The readme did not conatin anything except the instructions how to build the firmware |
| 21:47.29 | *** join/#elinux markl__ (n=mark@c-24-10-221-6.hsd1.co.comcast.net) |
| 21:49.52 | landley | Ah, I have an open tab on my desktop to confirm license compliance for zyxel with busybox. |
| 21:50.04 | landley | (Provisionally what they supplied looks good, we just haven't confirmed it's complete yet.) |
| 21:50.10 | landley | It's on my todo list, if somebody else doesn't beat me to it. |
| 21:54.37 | wiLi | Hmm, did I understand that correctly: the software was provided by Zyxel itself? |
| 22:06.42 | landley | Or their upstream vendor. |
| 22:06.52 | landley | Honestly dunno if they contracted out the development work or not. |
| 22:07.10 | landley | I might know after examining the firmware, which remains on my todo list... :) |
| 22:15.12 | wiLi | Okay, I understand. After you examined the firmware, where will the results of your examination be published? Or in other words: where do I have to keep an eye on to get informed about things like this? |
| 22:26.20 | landley | Well, we'll be taking down the hall of shame on busybox.net (because we've brought some of those companies into compliance and they'd like us to stop saying they aren't). |
| 22:26.27 | landley | By "we" I mean "the SFLC did it and then told me". |
| 22:26.37 | landley | So there should be a link on busybox.net eventually. |
| 22:26.40 | landley | It's on my todo list. :) |
| 22:34.19 | *** join/#elinux Dr_Who (n=tgall@gentoo/developer/dr-who) |
| 22:35.13 | wiLi | Well, thanks a lot for these informations. At least things are starting to get clearer now. |
| 22:36.48 | landley | You're welcome. |
| 22:37.10 | landley | I don't code on busybox anymore (thanks to Bruce), but I'm still involved with licensing stuff for it. |
| 22:47.44 | *** join/#elinux Aliosa27 (n=Aliosa27@65.89.233.20) |
| 23:01.33 | *** part/#elinux wiLi (n=hkml@p5B2D6A26.dip.t-dialin.net) |
| 23:21.30 | *** join/#elinux nine_ (n=nine@bl7-6-41.dsl.telepac.pt) |
| 23:22.43 | Dr{Who} | if i wanted all projects in buildroot to use the config option ac_cv_func_malloc_0_nonnull=y what would be the best method to date. I see people discussing a new param or maybe using TARGET_CONFIGURE_OPTS but i see no direct reference as to how is best. I cant see anyplace where TARGET_CONFIGURE_OPTS is defined so it must be up to me to define it in my environment unless i missed something. |
| 23:23.45 | nine_ | how compile a c++ project for a coldfire board, m5282evb ? using m68k-elf-g++ -m5200 -elf2flt -o hello helloworld.cpp returns an error |
| 23:24.27 | Dr{Who} | whats the error |
| 23:29.12 | nine_ | ERROR: text=0x8aa0 overlaps data=0x0 ? |
| 23:29.42 | nine_ | only error and fatal error :( |
| 23:31.37 | Dr{Who} | the problem is in elf2flt conversion |
| 23:31.45 | Dr{Who} | build with out make sure it builds |
| 23:32.02 | Dr{Who} | then you need to figure out whats up with the realoction utility |
| 23:34.24 | nine_ | I am newbie |
| 23:35.54 | nine_ | can you carify the point ? |
| 23:36.24 | Dr{Who} | the problem is in converting the elf to BFD format |
| 23:36.41 | Dr{Who} | the elf2flt utility is generating the error. |
| 23:38.03 | nine_ | so what you recomend to do ? an don't understand the process of elf2flt |
| 23:41.04 | nine_ | can you point some direction ? tutorial, or documentation ? |
| 23:41.10 | Dr{Who} | im still reading |
| 23:41.17 | nine_ | sorry |
| 23:54.41 | Dr{Who} | can you add -Wl to your build line |
| 23:58.11 | Dr{Who} | try: m68k-elf-g++ -Wl, -elf2flt -m5200 -o hello helloworld.cpp -lstdc++ -lc -lgcc |
| 23:58.27 | nine_ | I can try but cant say the results to you now |
| 23:58.45 | nine_ | don't have the tools right now with me |
| 23:59.02 | nine_ | but I will try and tomorrow give you the results |
| 23:59.08 | nine_ | ok ? |
| 23:59.10 | Dr{Who} | k ill be around must msg me |
| 23:59.39 | nine_ | by irc or prefere email ? |
| 23:59.53 | Dr{Who} | here is fine just pm me |