irclog2html for #elinux on 20060123

00:24.58*** mode/#elinux [+v file[laptop]] by ChanServ
01:04.07*** join/#elinux noclouds (n=mhfan@60.166.47.24)
02:03.40*** join/#elinux pigeon (n=pigeon@adsl-60-232.swiftdsl.com.au)
02:14.18*** join/#elinux Soopaman (n=soopaman@69.156.149.27)
02:51.58*** part/#elinux TorbaX (n=TorbaX@host-84-220-144-168.cust-adsl.tiscali.it)
02:57.47*** join/#elinux we0 (n=weo@p5499976E.dip0.t-ipconnect.de)
03:08.51*** join/#elinux Soopaman (n=soopaman@69.156.149.27)
03:11.29Russcosmicpenguin is in dresden at amd?
03:11.51file[laptop]^_^
03:35.46Genesisbonne nuit
03:46.51*** join/#elinux hufnus (n=slonsiki@DSL135-071.labridge.com)
05:18.34T0mWRuss: help!
05:18.43file[laptop]oh no, not help
05:19.01T0mWRuss: how do I decode what "stmia" and "stmdb" mean?
05:19.49cdmT0mW, get the ARM ARM
05:20.04T0mWcdm: got it, still cannot figure it out.
05:20.33cdmstmia - store multiple increment after
05:20.35T0mW"stm[<cond>]<addressing mode>
05:20.42T0mWthanks
05:20.54T0mWcouldn't think of the mnemonic
05:20.57cdmstmdb - store multiple decement before
05:21.07cdmdecrement
05:21.10T0mWWTF is that in the book, I looked under A3-5
05:22.08cdmhttp://www.arm.com/pdfs/QRC0001H_rvct_v2.1_arm.pdf
05:22.21cdmpage 5, Addressing Mode 4 table
05:23.02T0mWA3-21 mentions the modes for "load and store multiples", I'll have to dig deeper I guess.
05:24.21T0mWaha!
05:24.28T0mWpage A5-48
05:24.37cdmdid you check that PDF?
05:24.47cdmthe quick ref guide is a handy document to have around
05:24.48T0mWno, I've the paper copy at hand right now
05:25.06T0mWcdm: quick ref in the PDF?
05:25.12cdmthe pdf I liked
05:25.14cdmlinked
05:25.17cdmis a quick ref guide
05:25.29cdmfrom ARM
05:26.48T0mWcdm: printing it out now, thank you.
05:27.06T0mWI'm hand assembling my first "real" arm asm program..  :-/
05:27.39T0mWI know what I want to do, trouble is saying it ARM
05:27.44cdm:)
05:27.47cdmI love ARM assembly
05:27.50cdmit's really nice
05:28.10T0mWarm != 80c188 != 8051 != m68k != <various>
05:28.22T0mWanother language to learn <sigh>
05:29.54T0mWthis program is almost done.  Now, it has to detect that it was launched in low addr Flash, erase upper flash area and move itself up into that upper flash region.  hence the assembly lang.
05:30.41T0mWhmmm, maybe I should take another look at the -fPIC flag and write this stupid thing in C.
05:31.11T0mWcdm: naw! it is time to learn arm asm!
06:02.06*** join/#elinux Spetznaz (n=spetznaz@tac.mukachevo.net)
06:26.27*** part/#elinux cdm (n=cdm@adsl-69-236-127-131.dsl.pltn13.pacbell.net)
06:28.51*** join/#elinux cdm (n=cdm@adsl-69-236-127-131.dsl.pltn13.pacbell.net)
06:50.59Russif you learn arm assembly, you immediately can pick up so many others
06:51.24RussT0mW: did you get that 6 page quick reference yet?
06:51.29T0mWyes
06:51.44T0mWRuss: I already have many many other assemblers I know.
06:51.44Russdo you actually want to decode a hex instruction?
06:52.09T0mWnaw, just couldn't understand organization of the reference material
06:52.39T0mWI've done a ton of 8051, 80c188, 6502, ..., ...
06:52.57Russmips is really similar
06:53.13T0mWRuss: I just have to get my tail in gear and just do the ARM stuff.
06:53.15T0mWheh
06:54.15T0mWThe aritmatic functions, branches are similar, but the cond<ition> code and shifter fields are new to me.
06:54.33T0mWlike try this with 8051: mov r0, r0, lsr #12
06:54.40T0mWno workee
06:54.59Russwell, given you don't have a 32 bit register
06:55.03Russit'll take a while
06:55.27T0mWheh
06:56.27MonMothaT0mW: yeah, the whole predication thing was new to me
06:56.36T0mWI'm writing this flash mover in asm rather than c.  have to take about 40K of code and move from 0x0000:0000 to 0x0006:8000
06:56.39MonMothaand shifters
06:57.20Russinto ram?
06:57.54T0mWno, flash --> flash.  got to erase before, prog into upper flash, erase lower
06:57.59Russbummer
06:58.28T0mWnot really, the bootloader has the commands to mangle the flash in it.  you just make function calls.
06:58.42RussI did some asm that wrote out one 32 bit word to a specific location, and some that parsed the cfi table to find the end of flash
06:58.48Russbut thats about it on the asm<->flash
06:59.26T0mWyeah, I've done some of that, but I wrote it in C, compiled it, then copied the asm code. heh
06:59.49T0mWthis is from scratch so I can "punish" myself into knowing what I'm doing.
07:00.35T0mWsure is easier doing this stuff in 32bit instead of 8 / 16 though
07:01.12T0mWnice, big, fat registers to use!
07:02.14T0mWRuss: what still boggles my mind is the seperate sets of registers: FIQ, IRQ, Superv, etc.
07:03.09MonMothaT0mW: you've never done that on 8051?
07:04.22T0mWMonMotha: lots and lots of '51 asm
07:04.54T0mWMonMotha: I'll just have to think of this as an 8051 with 32bit registers and 8 potential DPTRs
07:05.30MonMothaheh
07:05.37T0mWheh, having only two methods of accessing external RAM (DPTR, P2:Rx) is a PITA
07:05.55T0mWespecially when doing block moves
07:05.56MonMothaI'm just curious that you've never done separate registers for normal and irq on 8051
07:06.09MonMothayes, I did like the EZ-USB's double DPTR
07:06.17T0mWno, the "fast" IRAM was too valuable as storage
07:06.24MonMothaah
07:06.54T0mWyeah, the app got very big very fast and I had to lose the register banking
07:07.13T0mWI always seem to run out of IRAM
07:07.28MonMothaI take it your system had a variable cycle count?
07:07.39MonMothathe original 8051 was 12 cycles/instruction no matter what
07:08.41T0mWfigure it this way: if you bank the registers you are reserving 8 bytes, but if you push a couple of regs onto the stack you can usually write most interrupt handlers in less than 8 registers
07:09.58MonMothaindeeed
07:10.05MonMothaat the expense of the time requierd to stack everything
07:10.18T0mWMonMotha: nope, still a standard 12.  We never could use the dallas stuff as most equipment needed lower power, not faster speed.  then, if you went with dallas, you were locked into a single vendor.
07:11.07T0mWAlthough, OKI was disqualified as a supplier as their 8051's had a mistake in the die
07:11.24MonMothathe interrupt handler I wrote with banked registers needed to be fairly fast since I was juggling two tasks at once
07:11.41MonMothawhat did OKI do?
07:12.53T0mWwell, you know how "movx acc, @Rx" works, right? P2 forms the high byte of the 16bit address to external RAM
07:13.33MonMothaactually, I wasn't aware of that particular instruction
07:14.27MonMothaok, yes
07:14.31MonMothathat's in my documentation though
07:14.58MonMothaI usually have all my IOs tied up :)
07:15.07Russwhen I wrote code for the 8051 that handled 4 tasks, I didn't bother with interrupts
07:15.07MonMothasince most of my uC apps are interfacing
07:15.11RussI just did time slices
07:15.17T0mWwell, it somewhat obscure, but the "movx" uses R0..R1 (Rx) to emit the lower 8 bits, the Port 2 pins (P2) becomes the upper address. P2 normally is used by the external ROM access to ghost the address counter onto the bus.  
07:15.55Russeach function excecuted for the amount of processor cycles for the time slice
07:15.58MonMothaRuss: I'm tempted to do that here.  I went with interrupts because I was using the serial port.  I'm thinking that may not be the best way to do things here
07:16.04Russand then jumped to the next function for the next time slice
07:16.09T0mWMonMotha: well, the OKI 8051s did not drive the value of the Port 2 latches out the upper address, they wrote a 0 instead.
07:16.27Russmine was a interceptor for ps/2 signals
07:17.20MonMothaRuss: I'm interfacing MIDI to an SPI bus
07:17.31MonMothaSPI with a bunch of extra handshaking
07:18.24MonMothaT0mW: that would effectively render that instruction useless, no?
07:18.45T0mWyup
07:19.21T0mWrenders the 8051 pretty useless as well, then you have to swap the h^ll out of DPTR when you want to move something
07:19.33MonMothaT0mW: indeed
07:19.36T0mWor copy, or fill
07:20.04MonMothayou can address dptrl directly on a normal 8051, right?
07:20.15T0mWah, erase code works, now to do the programming loop
07:20.39T0mWyou mean dpl and dph, not dptrl
07:20.52MonMothaok, the cypress stuff calls them differently
07:21.01MonMothaand the last thing I did major work with was the cypress
07:21.53T0mWwell, the compiler / assembler probably calls them differently: dptrl, dptrh instead of dpl, dph  correct?
07:22.16T0mWall 8051 assemblers / compilers are so different!
07:22.36T0mWall the ones I've run into, that is
07:22.47MonMothayeah
07:23.00MonMothaI tend to use as31, which I've gathered is far from standard
07:23.06MonMothaand for the cypress part, I just .equ'd them
07:23.07T0mWdifferent syntax for the asm opcodes, equates, defb vs db vs ??
07:23.17MonMothayeah, as31 is .db
07:24.04T0mWIIRC, the devtools that I use on the 8051 originally cost something like $2500 ?
07:24.21T0mWthat was 1990 dollars
07:24.36Russheh
07:24.39Russnow its all free
07:24.42T0mWbig money for a glorified Small C Compiler
07:24.43Russsucker
07:24.44MonMothano kidding
07:25.00MonMothayou have sdcc and a whole bunch of assemblers to choose from
07:25.48T0mWRuss: with this new controller, I will be able to, finally(!!!), put that freakin' 8051 system to rest.  And code onward in 32bit!
07:26.06T0mWI hate working in 8bit
07:26.15T0mWso tedious
07:27.34*** join/#elinux noclouds (n=mhfan@60.166.41.80)
07:31.14T`anyone know how i can setup a rule inside make to pass some #define to the compiler while compiling a file?
07:31.54T0mW-D
07:31.58T`something like $ make LINUX=1 .. and compiler can hopefully see some #define _FOR_LINUX or something like that for the file
07:32.10T`T0mW, is that a 1 eye bandit laughing ;-)
07:32.11T0mW-Dfoo=bar
07:32.19T0mW#ifdef foo
07:32.20T0mWor
07:32.23T`ah
07:32.35T`but i seen in some cases where it just works the way i said above.. no -D
07:32.55T0mWyeah
07:33.08T0mWyou can define foo as an environ var in the makefile
07:33.18T0mWe.g. export foo=bar
07:33.39T0mWbar is just to give foo a non-null value
07:33.57T`ah.. so how does it relate to $ make foo_en=1 for ex.
07:33.58T0mWno
07:34.07T`?
07:34.13T0mWif you export, you cannot test with #ifdef
07:34.26T0mW#ifdef only tests defines not environs
07:35.01T`uh right.. but i assume there can be some if statement for make? so i can see if some env variable is defined, and if it is, then i pass -Dfoo=bar to the compiler
07:35.16T0mWexports are only usefull when passing values between makefiles
07:35.35T0mWor, to child processes (/bin/sh)
07:35.50T`yea, i'm just looking into passing defined based on env variables
07:35.58T`s/defined/defines
07:36.00T0mWifeq ($foo, "bar")
07:36.04T0mWsomething like that
07:36.14T0mWifeq ($(foo), "bar")
07:36.16T`ah.. lemme try it
07:36.39T0mWI do a lot of that, conditional compile, conditional make
07:37.12T0mWifeq "$TOPLEVEL" ""
07:37.29T0mWtests to see if environ var $TOPLEVEL is null
07:37.58T0mWexport UPGRADE=-DUPGRADE
07:38.29T0mW$(CC) $(UPGRADE) blah blah
07:38.57T0mW#ifndef UPGRADE
07:39.18T0mWthe exported UPGRADE controls a conditional compile
07:40.36T0mWT`: I use the same source for two builds: one build is main binary, second is a bootloader binary.  So, I use conditional (UPGRADE) to modify the source
07:41.44T`aah cool.. that seemed to do something.. but getting some weird error all of a sudden.. hmm
07:41.51T`make: *** No rule to make target `vxjpeg.c', needed by `vxjpeg.o'.  Stop.
07:42.16T0mW:P now the fun begins!
07:42.33T`oh crap! i did a rm -rf vxjpeg.* .. which wiped the source :p
07:42.51T0mWoh, you have it cvs / svn, right?
07:43.08T`in make clean that is..
07:43.12T`yea, i got svn
07:45.25T`btw.. i dont use tabs in my vi setting.. and makefile need it annoyingly on each line.. anyway to do that easily in vi/
07:46.47T0mWT`: so, at the bottom of your makefile, put "# vi:tabstop=3:
07:47.33T0mWwhen you run vi, it will see the "# vi:" phrase and parse the remaining options for itself
07:48.56T`nop.. hmm.. didn't help
07:50.20T`you mean without the first \" right?
07:50.32T`well, it didn't do much either way :(
07:50.43T`may be vi should be told to parse these things in the file?
07:51.17T0mWany file, it must be either the first line or last line of the file.
07:51.42T`# vi:tabstop=3:
07:51.46T`.thats what i got on the first line
07:51.59T0mWwith vim (not vi), a comment followed by a space "vi:" (e.g. // vi:) flags vi to parse the line
07:52.11T0mWvi won't do it, only vim
07:52.27T`yup.. i'm trying it in vim for sure
07:52.34T`do i just type tab to get the special car?
07:52.37T`char*
07:52.56T`i just tried adding a new line to my make sequence, and it compiled about missing operator..
07:52.56T0mW?
07:53.02T`s/operator/seperator
07:53.44T`set expandtab
07:53.44T`set tabstop=4
07:53.44T`set softtabstop=4
07:53.50T`i got those in my vimrc btw..
07:54.01T`i think its that "expandtab" which is messing up
07:54.15T0mWthere is no escapement, just plain text, only put "# vi:expandtab:tabstop=4:softtabstop=4:" would do the same
07:54.33T0mW# vi:expandtab:tabstop=4:softtabstop=4:
07:54.36T0mWno quotes
07:55.03T`ok i did # vi:set noexpandtab: that seems to work
07:55.04T`:)
07:55.09T0mWaha
07:55.11T0mW:)
07:55.47T`very well.. now ifeq based thing looks nice.. heh thanks !
07:56.14T0mWT`: it makes life easier when you have to normally use tabstop=3 and someone wrote their code with blank tab fill + tabstops at 8, you can comment the file with: // vi:tabstop=8:
07:57.51T`yea, i agree.. this is a very nice feature... i ahve seen those lines before in files, but never really used them or given much taught to them
07:59.38T`another thing is.. if i had like.. A= file1.c file2.c file3.c
07:59.51T`prog.o: $(A)
07:59.55T`...
08:00.03T`A+=mymodule.c
08:00.12T`mymodule wont be evaluated into prog.o right?
08:00.35T`i was trying to keep all my changes to the bottom of the makefile, but that didn't work earlier.. i had to place those += before the prog.o was compiled
08:00.56T0mWmakefiles are magic
08:01.26T0mWIIRC, the makefile is two pass, pass one resolves references, pass two executes rules
08:02.21T`is that variable considered a reference
08:02.25T0mWtry:
08:02.41T0mWA=file1.o file2.o file3.o
08:02.43T`because i had some weird problems of my module file not being compiled with the rest of the files when i had those lines at the end of the file
08:02.48T0mWall: $(A)
08:02.59T0mW%.o: %.c
08:03.08T0mW<PROTECTED>
08:03.26T0mWit gets wierd
08:04.21T0mWthe logic flow does not follow what you learn to do a language, it has it's own logic
08:04.33T0mWs/a/with a/
08:04.47T0mWbah
08:04.53T`ibot, shut up
08:04.54ibotyes, Master t`
08:05.04T`ibot, T` damnit.. not t`
08:05.21T`heh
08:05.29T0mWmov lr, pc appears not be a ret
08:05.58T`if lr isn't stored on the stack
08:06.26T`which arch?
08:06.31T`arm?
08:06.40T0mWah, it is not on the stack
08:07.53T0mWlr contains the return address, so "b lr" ?
08:08.22T`hmm.. as long as you have the stack in original condition as caller
08:08.34T`and also perhaps the registers (you can't clobber them)
08:08.58T`i dunno, i never care about clobbering if i'm writing my own asm.. i make sure i dont touch registers which are used by caller in the called func
08:09.16T`but some people like to follow conventions like compilers
08:09.50T0mWmov pc, lr
08:09.59T`T0mW, also make sure b can branch to far locations.. PC is usually 64-bit, and some b instructions only have a 32-bit in-word
08:10.01T0mWthat works
08:10.23T0mWthank God that someone invented JTAG!
08:10.32T`hmm.. is this ATT or INTEL asm syntax?
08:10.40T0mWgcc
08:10.43T`pc = lr or lr = pc from that instructino
08:10.51T`well, then you just moved pc to lr
08:10.57T`what wont branch
08:10.59T0mWreverse
08:11.01T`s/what/that
08:11.06T0mWmoved lr to pc
08:11.14*** join/#elinux toi (n=pleemans@d5152D12D.access.telenet.be)
08:11.31T0mWmov [dest], [src]
08:11.51T`yea, but thats ATT ;)
08:11.56T`gcc is like mov src, dest
08:12.10T`err wait.. i think ATT is gcc.. intel is what you described
08:12.21MonMothayeah, gcc is the forsaken mess that is ATT
08:12.35T`MonMotha, wow really? i hate intel's syntax :/
08:12.40T`MonMotha, i got used to the gcc syntax
08:13.24T0mWany difference between "ldr r2, =CMD" and "ldr r2, CMD" ?
08:14.06T`toi, .. one more thing.. if i had this ifeq ($(DEBUG),1) CFLAGS+= -g... and if i did a make.. it will not use debug flag then.. but if i say make DEBUG=1.. it wont clean and recompile.. it will just not do anything since it compiled earlier.. anyway to force recompile on this flag?
08:14.23T`T0mW, if you have =, thats definetely Intel syntax i would say
08:14.48T`= is dereference i believe
08:15.45T`hmm.. i'm actually not sure.. or was it the literal...
08:16.22T0mWah, "ldr r2, =CMD" get the address of CMD, "ldr r2, CMD" gets what CMD contains
08:17.33T`ah'
08:17.48T`which architecture is this asm for btw?
08:20.34MonMothaT`: well, the first arch I learned was 8051, and that pretty much universally uses Intel's style
08:20.46MonMothathen I learned MIPS, which is similar to intel style x86 (at least, more similar than ATT style)
08:21.31T`yea, mostly i think this whole syntax thing arises from which one you started out first with
08:22.35T`but i did PIC assembly first, but its too basic to compared to PC (which i did next... )
08:23.00T`MonMotha, any ideas on my make question? T0mW seems to have fallen in love with asm ;)
08:23.24T0mWT`: more so than with Make
08:23.58T0mWI've been writing makefiles for many years.  It takes time to learn those things
08:24.19T`heh, tell me about it
08:24.41T`some things are obvious, but i should really read a proper tutorial.. i never did serious study on it
08:24.57T0mWone thing I use is something like this:
08:25.16T0mWall: $(PROGRAM)
08:25.22T0mW.
08:25.30T0mW$(PROGRAM):
08:25.31T0mW.
08:25.51T0mW<PROTECTED>
08:26.05T0mWnote, dots (.) are blank lines.
08:26.13T0mWdoh
08:26.19T0mW.
08:26.23T0mWall: $(PROGRAM)
08:26.25T0mW.
08:26.29T0mW$(PROGRAM):
08:26.33T0mW<PROTECTED>
08:26.36T0mW.
08:27.12T0mWT`: sometimes you have to use hidden files as a testpoint:
08:27.24T0mW`touch .foo`
08:27.47T0mWif [ -e ".foo" ] ; then \
08:27.56T0mW<PROTECTED>
08:27.58T0mWfi
08:28.03T`but i dont see how defining/undefining DEBUG env.. is going to recompile $(PROGRAM) in the above make
08:28.19T`yea, but can i include bash shell code into a make file?
08:28.32T0mWI don't know what is wrong with your makefile, I was just speaking in general
08:28.46T0mWI just showed you the bash code
08:28.58T0mWput it under a rule
08:29.11T0mWas when you do "$(CC) blah blah"
08:29.34T`ah
08:29.44T0mWif [ -e ".foo" ] ; then \
08:29.59T`yup i got it..
08:30.01T0mW$(CC) blah ; \
08:30.02T0mWfi
08:30.18T`and $(PROGRAM):
08:30.30T`does that mean it wont depend on anything like $(PROGRAM): program.c ?
08:30.43T0mWno
08:30.44T`so code below it will always be equaluated?
08:30.56T`s/qua/va/
08:31.16T0mWdependancies are from the output (desired result) tested against resource
08:31.24T0mWe.g. program.o: program.c
08:31.41T0mWso
08:31.48T`right, but what if you dont specify any..
08:31.54T0mWyou're dead
08:32.14T0mWyou need a "result" of some kind
08:32.17T`even if that $(PROGRAM) is in all:
08:32.32T0mWit doesn't have to be an executable.  makefiles can also run YACCs, etc.
08:32.41T0mWor text manglers
08:32.43T0mWor ...
08:33.00T0mWit is a "desired" against "input"
08:33.07T0mWs/input/resource/
08:33.25T`hmm ok
08:33.58T0mWnot "take this resource and build that" it is "if that is older than resource, build"
08:34.38T0mWoutput from input(s), not, input(s) to output
08:35.04T`yea, i sorta figured that from experimenting.. heh
08:35.14T`anyway... i got what i wanted to work :) that ifeq is perfect
08:35.15T`thanks
09:23.45*** join/#elinux ade|desk (n=adavey@194.200.143.249)
09:54.13*** join/#elinux masked (n=masked@static-203-87-16-192.vic.chariot.net.au)
11:07.12*** join/#elinux darkschneider (n=gab@213-140-6-96.ip.fastwebnet.it)
11:57.30*** join/#elinux mallum (n=mallum@host86-136-17-6.range86-136.btcentralplus.com)
11:57.30*** mode/#elinux [+v mallum] by ChanServ
12:09.58*** join/#elinux Genesis (n=genesis@dev.aimao.org)
12:11.31Genesisbonjour
12:12.06*** join/#elinux weo (n=weo@p5499976E.dip0.t-ipconnect.de)
12:12.34*** join/#elinux Sgt-Donan (n=Loutre@feu30-1-82-242-59-35.fbx.proxad.net)
12:55.36*** join/#elinux prpplague (n=billybob@72.22.143.75)
12:56.08*** mode/#elinux [+o prpplague] by ChanServ
12:58.02prpplague~seen sjhill
12:58.07ibotsjhill <n=sjhill@eth13.com-link.com> was last seen on IRC in channel #elinux, 6d 19h 13m 33s ago, saying: 'no big deal'.
13:03.32T0mWlast time he said something about going to a meeting about a new project.
13:03.45prpplagueahh
13:03.53prpplagueanyone here used libelf ?
13:03.54T0mWso, he is having fun and, I guess, we won't see him for a while
13:12.03prpplagueT0mW: hehe, i've been getting tons of email about making a commercial juicebox cart
13:12.28T0mWguess you'd better brush up on Eagle then
13:13.23prpplagueT0mW: hehe, naw, i'm not doing one
13:13.30prpplagueT0mW: got other fish to fry
13:19.33chouimatmorning
13:19.40*** join/#elinux dijenerate (n=dijenera@72.22.159.26)
13:22.30T0mWprpplague: hmm, if I erase the Flash sector, I guess that means if I try to single step code inside that sector, it gives NOPs...
13:22.38T0mWOh! I get it now!
13:22.40T0mWdoh
13:25.23T0mWdrat
13:29.36dijenerateprpplague: hey how's it going?
13:29.36prpplaguedijenerate: ssdd, its monday, hehe
13:29.55dijenerateprpplague: lol
13:31.24dijenerateprpplague: did you have a chance to check on anything for me?
13:31.41prpplaguedijenerate: yea i found a couple fpga pci based cards
13:31.49prpplaguedijenerate: just got the specs this morning
13:31.55prpplaguedijenerate: looking them over now
13:31.58dijenerateprpplague: ok, cool
13:32.04dijenerateprpplague: great thanx
13:32.08chouimathi prpplague T0mW
13:46.36*** join/#elinux GPSFan (n=Ken@65.121.49.208)
13:48.20prpplagueGPSFan: hey hey
13:48.41GPSFanprpplague: good morning..how'it?
13:49.30prpplagueGPSFan: hehe, i has 27 emails in my inbox with ppl wanting me to build them juicebox carts. heheh
13:51.17GPSFanprpplague: wow..
14:08.03chouimatROFL ... according to the elections law it's illegal to eat the paper on which you cast your vote
14:20.59*** join/#elinux eggers (n=eggers@pixpat.austin.ibm.com)
14:43.01MonMothaok, actual linux question for once
14:43.29MonMothaI have an application that I wish to link against multiple libraries.  Some of them I want to link statically and others dynamically.  What's the easiest way to go abotu this?
14:47.00Croftonhttp://news.yahoo.com/s/nm/20060123/tc_nm/manufacturing_mattel_dc
14:52.01*** join/#elinux CosmicPenguin (n=nobody@aus-ext-proxy01.amd.com)
14:52.01*** mode/#elinux [+v CosmicPenguin] by ChanServ
14:52.59CosmicPenguinfear!
14:53.43prpplagueCosmicPenguin: hehe
14:55.01chouimathi CosmicPenguin
14:57.37*** join/#elinux TorbaX (n=TorbaX@host-84-220-144-168.cust-adsl.tiscali.it)
14:58.22CosmicPenguinany suggestions?
15:03.17prpplagueCosmicPenguin: http://applications.linux.com/article.pl?sid=05/10/07/172259&tid=37
15:03.26prpplagueCosmicPenguin: see if that has anything to help
15:05.49CosmicPenguinprpplague: thanks - I'm still getting use to this whole kernel maintainer gig
15:06.51CosmicPenguinprpplague: no, thats pretty basic
15:07.11CosmicPenguinprpplague: I've been using mutt for a long time now, but I never figured out how to save off a message in a file
15:07.19CosmicPenguinand its not pratical for me to go finding it in my Mail driectory
15:08.56prpplagueCosmicPenguin: ahh
15:20.43prpplagueCosmicPenguin: hey, whats the rule-of-thumb with adding packages to OE? i.e. what applications are too end user specific for addition to the main branch?
15:20.57CosmicPenguinnothing
15:21.24CosmicPenguingenerally you don't want binary packages
15:21.38CosmicPenguinand if there is something that only has benefit to you personally, there isn't much reason to share it
15:21.49CosmicPenguinbut other then that, if other people can benefit from your code, then its legal
15:22.19prpplaguehmm
15:22.42CosmicPenguinby binary package, I mean, like the ICA tool or something
15:22.50prpplagueyea
15:22.59CosmicPenguinthough /me has written a .bb for ICA
15:23.06prpplagueCosmicPenguin: just trying to consider the rules for buildroot
15:23.35CosmicPenguinI think the best rules would be:  1) source based, 2) at least a minimal audience
15:23.42prpplagueCosmicPenguin: got a ton of submissions for packages that are very very specific to the end user that submitted it
15:24.10CosmicPenguinCan you give me an example?
15:24.29prpplagueCosmicPenguin: yea, i think there is one additional (imho) for buildroot as we want to keep the whole package light
15:24.40CosmicPenguinprpplague: granted
15:24.51CosmicPenguinprpplague: but eventually somebody will want to toss in Firefox or something, and I think thats cool
15:24.53prpplagueCosmicPenguin: an application to wipe magnetic material such as drives and tape
15:25.11CosmicPenguinprpplague: is it on freshmeat?
15:25.24CosmicPenguinI would say that if the package is on freshmeat, it warrents inclusion
15:25.37CosmicPenguinotherwise, ask the guy why anybody would care other then himself
15:25.57prpplagueyea its on freshmeat
15:26.04CosmicPenguinthen I say take it
15:26.25prpplaguethink i'll leave it up for a week for feedback
15:26.29CosmicPenguinYou know, there's also nothing saying you couldn't do a "buildroot-extra" and stick all the questionable packages in there
15:28.19prpplagueCosmicPenguin: yea, thats what i was considering
15:29.09CosmicPenguinbuildroot-overloaded
15:29.16prpplagueyep
15:29.26prpplagueCosmicPenguin: i've got like 137 open buildroot issues
15:29.33prpplagueCosmicPenguin: trying to get them under control
15:29.48prpplagueCosmicPenguin: i'd like to get them down to less than 30 at any one time
15:29.55CosmicPenguinbuildroot is like that cool kid who doesn't care what anybody else thinks
15:30.09prpplaguehehe
15:30.16CosmicPenguinEveryone is all like "oh, buildroot, can I use you" and buildroot is like "whatever"
15:30.24prpplagueHA
15:31.09prpplagueCosmicPenguin: yea i've found that most of the uclibc folks are very into the compile stuff, but not much for keeping up with bugs and features
15:31.41prpplagueCosmicPenguin: i'm trying to organize some more general rules as such to kinda give the buildroot some direction
15:32.26prpplagueCosmicPenguin: like right now for uclibc, if you need a toolchains for arm7tdmi, you have to select ARM720T and then select no mmu for uclibc to generate the proper tool chain
15:32.35prpplagueCosmicPenguin: which makes no sense at all
15:33.16*** part/#elinux TorbaX (n=TorbaX@host-84-220-144-168.cust-adsl.tiscali.it)
16:02.34*** join/#elinux jipi (n=jipi@cm44.gamma185.maxonline.com.sg)
16:40.49CosmicPenguinsigh - the spammers are starting to find my work address
16:41.08CosmicPenguinall spammers must be sent to the deepest darkest depths of hell
16:41.48chouimatCosmicPenguin: yup ... I'm tired of PE spams .... and now they are able to bypass spamassassin
16:42.49CroftonPE?
16:43.13chouimatCrofton: Penis Enlargement stuff
16:46.04*** join/#elinux TimRiker (n=timr@pdpc/supporter/bronze/TimRiker)
16:46.05*** mode/#elinux [+o TimRiker] by ChanServ
16:46.24Croftonhhe
16:46.36Croftonthe body bouncer guys are claiming the spam isn;t from them
16:47.43CosmicPenguinseems that everybody has finally emerged from the post holiday blues
16:47.47CosmicPenguinall the mailing lists are slammed
16:51.38prpplaguehehe
16:55.37prpplague123 cases
16:56.03CosmicPenguinI'm still deperately looking for programmers, if anybody knows anybody
16:57.19chouimatCosmicPenguin: for what?
16:57.49CosmicPenguinI need a junior level person as a lab rat, and a senior or very serior level programmer to be my peer
16:58.06chouimatk
16:58.28CosmicPenguinBoth gigs are in Colorado though, so individuals need to be on-site
16:58.42Croftonbummer :)
16:59.00chouimatCosmicPenguin: I thought so ...
16:59.14CosmicPenguinI'm just saying, is all... :)
17:00.08chouimatCosmicPenguin: it's ok ... it's just it's not in my current plan to move to the US
17:02.39CosmicPenguinprpplague: What I'm saying is that if you happened to move to Colorado and wanted a job, I would kill somebody here to get you one at AMD
17:02.53prpplagueCosmicPenguin: hehe, yea
17:02.55CosmicPenguinnot that you would need a job, or want to move to Colorado, I'm just making conversation
17:03.03prpplagueCosmicPenguin: just not all that interested in getting back into x86
17:04.04CosmicPenguinI wonder if Micah knows anybody in the CU comp sci department
17:18.15T0mWprpplague: hey Dave, CosmicPenguin going to be working for you?
17:19.20*** join/#elinux Crofton (n=balister@hc6521c84.dhcp.vt.edu)
17:39.18*** join/#elinux CosmicPenguin (n=nobody@aus-ext-proxy01.amd.com)
17:39.18*** mode/#elinux [+v CosmicPenguin] by ChanServ
17:39.41CosmicPenguinseesh
17:39.46CosmicPenguinthats the second time my box has locked up like that
17:40.15CosmicPenguinprpplague: do me a solid?
17:40.19CosmicPenguinprpplague: kick CP|Dresden, will ya?
17:42.41CosmicPenguinthere we go
17:42.43CosmicPenguinstupid screen
17:54.02*** join/#elinux Sgt-Donan (n=Loutre@mto30-1-82-242-53-8.fbx.proxad.net)
17:56.47prpplagueCosmicPenguin: sorry was on the phone
17:57.30CosmicPenguindanm - I had this todo list all done, and I lost it
17:59.14prpplaguedoh
18:00.01prpplagueCosmicPenguin: i love it when there are these frantic posts from ppl who need help with some simple issue, and you do a traceroute and find out they are working for a big "embedded specialist"
18:00.06prpplagueCosmicPenguin: you ok?
18:00.27CosmicPenguinprpplague: jet lagged
18:00.37CosmicPenguinprpplague: yeah
18:00.44CosmicPenguinprpplague: the nano-x maililng list is full of them
18:00.47CosmicPenguinso is the lkml
18:01.03CosmicPenguin"I have big job porting OTG to <blah>.  Can you help me find documentation on OTG?"
18:01.14CosmicPenguinWell, geez - probably shouldn't have accepted the job if you didn't know what it was there, champ
18:03.10prpplaguetoo cool - http://www.cnn.com/2006/WORLD/europe/01/23/uk.russia.row/index.html
18:13.44CosmicPenguinargh!
18:17.24*** join/#elinux Sgt-Donan (n=Loutre@mto30-1-82-242-53-8.fbx.proxad.net)
18:29.56T0mWprpplague: it is done, the last section of code has been writ
18:33.04prpplaguehehe
18:38.12*** join/#elinux T`2 (n=total@pdpc/supporter/student/T)
19:13.56*** join/#elinux Crofton|770 (n=balister@mprg5213.mprg.ee.vt.edu)
20:28.44Genesisbonne nuit
20:30.39*** join/#elinux T`2 (n=total@pdpc/supporter/student/T)
20:39.28*** join/#elinux thraxisp (n=thraxisp@ottgate.precidia.com)
20:58.11*** join/#elinux T`2 (i=debian-t@pdpc/supporter/student/T)
21:33.03*** join/#elinux CosmicPenguin (n=nobody@aus-ext-proxy01.amd.com)
21:33.04*** mode/#elinux [+v CosmicPenguin] by ChanServ
21:49.32*** join/#elinux Crofton (n=balister@66-207-66-26.black.dmt.ntelos.net)
22:44.27*** join/#elinux CosmicPenguin (n=nobody@aus-ext-proxy02.amd.com)
22:44.27*** mode/#elinux [+v CosmicPenguin] by ChanServ
23:18.22*** join/#elinux bryankemp (n=bryan@cpe-70-123-129-170.austin.res.rr.com)
23:18.29*** join/#elinux andersee (n=andersee@codepoet.org)
23:18.30*** mode/#elinux [+o andersee] by ChanServ
23:18.37bryankempanyone using buildroot?
23:20.57CosmicPenguinYou've found the right room
23:21.08CosmicPenguinunfortunately our main buildroot dude is gone for theday
23:21.19bryankempAnyone have a good generic init script for loading a build root image?
23:21.23CosmicPenguinunless andersee is really alive and not just here automatically
23:22.33bryankempI am building a small 2.6.9 based kernel (which I have compiling properly) and an rootfs from buildroot, but I am having trouble getting the rootfs mounted and switched to...
23:23.12bryankempits for x86.
23:36.47*** join/#elinux zx80user (n=adrian@81.170.29.134)
23:36.55MonMothaI take it you are using an initrd?
23:37.10zx80userIs anybody else having uname fail on them or other problems with busybox?
23:37.48CosmicPenguinzx80user: you need to be wayyy more specific then that
23:38.40bryankempMonMotha: I am
23:38.50zx80userCosmicPenguin, sorry I was referring to my email to the list :) uname -r is failing in the first line of my boot time hotplug script, but there are lots of other problems too - on SH build with pthreads
23:39.23CosmicPenguinzx80user: not many people in here are on that list
23:39.52zx80userIf I comment out the offending uname -r the script still fails, but in a different way - claiming there is no /sys on the system when there is one in plain sight
23:40.11zx80userCosmicPenguin, my mistake, apologies
23:41.45CosmicPenguinzx80user: when you say uname fails, what do you mean?
23:43.15MonMothabryankemp: does it successfully bring the initrd up?
23:44.06zx80userCosmicPenguin instead of running uname -r it spews out the help text - it doesn't like the -r: this seems to be a general problem with recent BB builds - commands not understanding options, suggests some code is up the spout
23:44.37CosmicPenguinhave you tried building a native build to verify that the code itself is broken, and not your system?
23:45.16bryankempMonMotha: It does and it starts running the init scrip in the initrd, but I can't get that to work.
23:48.53zx80userCosmicPenguin -- on a Dreamcast?? Or do you mean on an i686 box? No, but then I was building and running code fine until a few days ago
23:49.21CosmicPenguinThen that points at a configuration issue on your part
23:50.10MonMothabryankemp: well, what does it do, and where does it go wrong?
23:52.04bryankempMonMotha, I'll be right back. I am going to open irc on my mac (I need this machine to run the new images)
23:54.10*** join/#elinux thraxisp (n=thraxisp@ottawa-hs-64-26-147-146.d-ip.magma.ca)
23:54.38zx80userCosmicPenguin I don't think so. The builds failed after I updated by buildroot
23:55.26CosmicPenguinzx80user: so what changed in the buildroot then?
23:56.01zx80userWell, presumably the uClibc and Busybox sources were updated
23:56.14CosmicPenguinpresumably?
23:57.03zx80userCosmicPenguin, ok they were. i know they were. Not least because I flagged up some bugs in the uClibc code
23:57.16*** join/#elinux ircleuser (n=fpyanbur@cpe-70-123-129-170.austin.res.rr.com)
23:57.44ircleuserMonMotha: ok I am on my mac
23:57.46CosmicPenguinand what do the commit logs have to say about these updates?
23:58.02CosmicPenguinAnd like I said, try the busybox code on your host - if it breaks there, then you have a problem
23:58.14CosmicPenguinif it doesn't, then its time to check the changelogs
23:58.30bryankempok. I got all that worked out.
23:59.30zx80userThat I don't know because my first reaction was to come on here (and the linux-sh channel) and ask whether anyone else was seeing something similar on SH or any other platform. Anyway, got to go now, it's midnight here, see ya and thanks for help
23:59.41CosmicPenguinhave a good night

Generated by irclog2html.pl by Jeff Waugh - find it at freshmeat.net! Modified by Tim Riker to work with blootbot logs, split per channel, etc.