<qi-bot> [commit] kyak: xburst-tools buffered output patch http://qi-hw.com/p/xburst-tools/a3a38ca
<rjeffries_> wpwrak did you see: http://shop.moderndevice.com/products/bub_ii
<rjeffries_> mumble: supporting h/w flow control on nxuart is prolly A Good Thing
<qi-bot> [commit] Xiangfu Liu: disable CONFIG_ALL, add Tile and gottet http://qi-hw.com/p/openwrt-xburst/4c23f2d
<qi-bot> [commit] kyak: config.full_system: add supertux, terminus-font http://qi-hw.com/p/openwrt-xburst/4c6dfc5
<qi-bot> [commit] kyak: config.full_system: build gcc-mips, make, binutils as modules. Remove http://qi-hw.com/p/openwrt-xburst/3916e5f
<qi-bot> [commit] kyak: config.full_system: remove "=m" packages http://qi-hw.com/p/openwrt-xburst/f2bfc5a
<qi-bot> [commit] kyak: don't include ghostscript and fbgs into rootfs, build as modules http://qi-hw.com/p/openwrt-xburst/38ae85f
<qi-bot> [commit] David Kühling: config.full_system: fix name of gnuplot package (was renamed a long time ago) http://qi-hw.com/p/openwrt-xburst/c014532
<qi-bot> [commit] Xiangfu Liu: add zgv, MPlayer, brainless http://qi-hw.com/p/openwrt-xburst/76010c7
<qi-bot> [commit] Xiangfu Liu: remove custum banner, focus on 100% upstream, http://qi-hw.com/p/openwrt-xburst/09a0a62
<qi-bot> [commit] kyak: config.full_system: add setterm http://qi-hw.com/p/openwrt-xburst/2cb0ceb
<qi-bot> [commit] kyak: config.full_system: include GNU tar http://qi-hw.com/p/openwrt-xburst/56c68f9
<qi-bot> [commit] Lars-Peter Clausen: [package] ks7010: Remove debug printks http://qi-hw.com/p/openwrt-xburst/4cd6a3c
<qi-bot> [commit] Lars-Peter Clausen: [xburst] jz_mmc: Drop warning about spares irqs. http://qi-hw.com/p/openwrt-xburst/0f173bc
<qi-bot> [commit] Lars-Peter Clausen: [xburst] Improve mounttime. http://qi-hw.com/p/openwrt-xburst/1526555
<qi-bot> [commit] kyak: have sound modules built in kernel http://qi-hw.com/p/openwrt-xburst/5db429d
<qi-bot> [commit] Xiangfu Liu: reflash_ben.sh, new option b k r, reboot device after reflash http://qi-hw.com/p/openwrt-xburst/40ce746
<qi-bot> [commit] kyak: add sound options to default config, so that it won't popup http://qi-hw.com/p/openwrt-xburst/f3b0c9b
<qi-bot> [commit] Xiangfu Liu: config.full_system: add openssh-sftp-server http://qi-hw.com/p/openwrt-xburst/190d239
<qi-bot> [commit] Xiangfu Liu: update opkg.conf, don't using /tmp keep packages information http://qi-hw.com/p/openwrt-xburst/ea1bf4f
<qi-bot> [commit] kyak: config.full_system: busybox enhancements http://qi-hw.com/p/openwrt-xburst/495b903
<qi-bot> [commit] kyak: config.full_system: more busybox options http://qi-hw.com/p/openwrt-xburst/b2bc487
<wpwrak> xiangfu: btw, not sure if you've seen this: i moved the avrdude patches and also added a new feature: http://lists.en.qi-hardware.com/pipermail/discussion/2011-March/007481.html
<wpwrak> xiangfu: i still have a few more things pending and then i'll see how avrdude upstream likes all this
<xiangfu> the email is on my TODO list later tonight :)
<xiangfu> wpwrak: I will update the openwrt package.
<wpwrak> xiangfu: (todo) kewl, thanks :)
<kyak> wow the crippled configure (after autorecond) from gtkhtml has managed to DoS my host
<kyak> *** Notice -- WARNING: Time jumped ~36 seconds ahead!
<kyak> heh, the case when configure gets patched rather then .in
<kyak> jow_laptop: xMff: please accept the patch: http://dpaste.com/481876/
<xMff> kyak: how do you generate your patches btw?
<kyak> xMff: svn diff from feeds/packages,desktop etc
<xMff> kyak: I mean patches within packages
<kyak> hm.. i unpack tarball to tmp, cp -r package_dir package_dir.orig, do changes in package_dir, then diff
<xMff> I see, I suggest to read http://wiki.openwrt.org/doc/devel/patches
<wpwrak> tuxbrain: hah, he lives ! been soldering all weekend ? :)
<xMff> as a side effect you get nice clean patch files without timestamps and stuff, so the final deltas have less noise
<tuxbrain> wpwrak: nop was carnival here :)
<kyak> xMff: nice! i've never used that before! libglade is the next failure, i will try to generate the patch quilt way :)
<tuxbrain> was also polishing 500 UBB with a cutter
<tuxbrain> yesterday I have sended all UPS ones today I will send using standard national postmail
<wpwrak> tuxbrain: (polish 500) heh, i had that picture in my mind. tuxbrain up to the elbows in FR4 dust ;-)
<tuxbrain> wpwrak: yep :), but well at least was a task I can do on the sofa
<tuxbrain> wpwrak: I think I have asked you already (sure) but don't let me digg in the irc logs,  where is the SPI->8:10 pin correspondence?
<wpwrak> tuxbrain: there is no SPI. there is only MMC/SD/SDIO
<wpwrak> tuxbrain: the latter is printed on the boards :)
<tuxbrain> ok you are a little picky today... where I can find SDIO->Atmega pins correspondence to flash it using your patched avrdude?.... better that way?
<wpwrak> aah, avrdude. that would be explained in avrdude.conf
<wpwrak> search for "nanonote"
<xMff> kyak: ok, committed
<wpwrak> the driver does not have a hard-coded assignment of SPI pins. instead, you define what the pins do in avrdude.conf
<wpwrak> i.e., atusb-pgm and nxuart have different pin assignments
<tuxbrain> but are related to SPI pins, isn't it?
<tuxbrain> also there is any place in your code to digg on SPI communication (not flashing)?
<kyak> xMff: thanks!
<tuxbrain> (mmm the previous question was already done some time ago I guess)
<wpwrak> tuxbrain: for spi comm, you could look at ben-wpan/lib/
<tuxbrain> ok
<wpwrak> err, ben-wpan/tools/lib/
<xMff> kyak: stupid question, why gconf-2.0 is left in configure when it is completely patched out with the next patch?
<wpwrak> it's not the most simple example, though. if you just want bit-banging, ben-blinkenlights/bbl/ is your friend
<tuxbrain> mmm damn when I try to compile with avr-gcc
<tuxbrain> /data/avr/bin/../lib/gcc/avr/4.3.4/../../../../avr/bin/ld: cannot find -lgcc
<tuxbrain> is and empty test.c file
<xMff> tuxbrain: on-target ?
<tuxbrain> ldd /data/avr/bin/../lib/gcc/avr/4.3.4/../../../
<xMff> tuxbrain: or crosscompile?
<tuxbrain> ../avr/bin/ld
<tuxbrain> ldd: can't open cache '/etc/ld.so.cache'
<tuxbrain> libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x2aabe000)
<tuxbrain> libc.so.0 => /lib/libc.so.0 (0x2aade000)
<tuxbrain> ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0x2aaa8000)
<tuxbrain> on the NN
<kyak> xMff: good question. And i don't really understand why gconf-2.0 is patched out.. It should work fine. Might want to have a closer look later
<wpwrak> xMff: it's tuxbrain's S&M edition ;-)
<xMff> tuxbrain: I think you must copy avr-gcc's libgcc too
<xMff> tuxbrain: and put it in /data/avr/lib
<wpwrak> wolfspraul: btw, what's the schedule on your (sharism's) side for ben-wpan. fedex say adam should have something to play with by tomorrow evening.
<wpwrak> wolfspraul: (roh's still seems to be sitting in the post office; richard's is waiting for roh's to leave the country)
<wolfspraul> good question
<wolfspraul> I think we are ready for the run of 100 each, no?
<tuxbrain> wolfspraul: givemegivemegiveme
<wolfspraul> the problem is that Adam is in the middle of the m1 rc3 run
<wpwrak> wolfspraul: from my side, i think the hw is good to go. adam will have to check manufacturability.
<wpwrak> wolfspraul: one open issue is the cover/case. if roh needs any modifications to the pcb for it, then we'd have to wait for his feedback.
<wpwrak> wolfspraul: of course, if we just dunk the boards in silicone, the silicone will adapt to any shape ;-)
<wpwrak> wolfspraul: the next step would be firmware flashing for atusb. the boot loader isn't ready yet, but that shouldn't take long. the sw and hw for the actual flashing is ready.
<wpwrak> wolfspraul: finally, functional testing. this still needs a bit of work. but there's even more time for that :)
<wolfspraul> wondering whether we can produce the 8:10 and usb version together in one pcb and smt run
<wolfspraul> that would save quite a bit of costs
<wpwrak> you could probably pre-panelize them. e.g., 2 atben plus 2 atusb as one "mini-panel"
<wpwrak> the L-shaped atben are best placed together. otherwise you'll waste quite a bit of board space
<wpwrak> lemme see if i have something in my discard pile ...
<tuxbrain> xMff: yeah! that was the issue :), seems than the failing install has also forgot to put the lib .a files , now it at least compiles an main(){} :P hope there was nothing more broken
<kyak> xMff: please accept the patch for libglade: http://dpaste.com/481917/ (created with quilt, then svn diffed :)
<wpwrak> wolfspraul: you could combine this with a pair of atusb. wouldn't give you maximum coverage, but it's probably still better than separate boards.
<wolfspraul> he, yes. very clear picture :-)
<wpwrak> these were positioned in the post-processing, so i don't have a single kicad or gerber file with multiple boards. not sure how one would make the tabs that connect boards. maybe that's something the fab provides routinely (they did in the case of UBB)
<wpwrak> adam would know such things
<jow_laptop> kyak: what does it do/fix?
<kyak> jow_laptop: the AM_PATH_GTK_2_0, defined in gtk-2.0.m4, cannot be found. It causes an error later during configure. Therefore, I used the check for gtk like in gtkhtml instead
<jow_laptop> ok
<jow_laptop> allright, will do it within the next half hour
<kyak> sure, thanks!
<tuxbrain> no make on openwrt?
<jow_laptop> tuxbrain: there is but currently restricted to x86
<kyak> opkg install make?
<jow_laptop> oh, actually not
<kyak> Package make (3.81-1) installed in root is up to date.
<kyak> :)
<tuxbrain> kyak: what image you are using?
<kyak> https://forum.openwrt.org/viewtopic.php?pid=46022#p46022 <- had fun reading the IRC log :)
<kyak> tuxbrain: hm.. the one i built yesterday at night :)
<kyak> tuxbrain: if you have troubles installing make, make sure it ran "opkg update" first
<tuxbrain> a precious Blink.hex has been generated :)
<tuxbrain> from arduino examples
<tuxbrain> using arduino libraries
<wpwrak> tuxbrain: now you just need to flash it :)
<tuxbrain> well seems is time to some serious soldering making a UBB->ArduinoSPI :)
<tuxbrain> cable
<tuxbrain> In theory I don't need the bootloader isn't it? but I can reflash the bootloader anytime (I have them copied on NN )
<wpwrak> sure. if you can flash directly, you have almost limitless power
<tuxbrain> well time to dress up a little the recording studio (euphemistic way to say I must enter the bulldozzer in the cave to retire tons of garbage) to make a proper howto make the cable video :)
<tuxbrain> also a good time to play some Metal and headbanging will doing so
<tuxbrain> is happy
<wpwrak> ;-)
<wolfspraul> Ornotermes: you there? I want to ping your brain with a question about lenses...
<Ornotermes> wolfspraul: i'm here
<wolfspraul> ah cool
<wolfspraul> I try to understand what different types of lenses exist, in general. what categories.
<wolfspraul> the easy thing is the focal length and viewing angle
<wolfspraul> but then there are special types, like telecentric lenses, or ultraviolet (?)
<wolfspraul> is fisheye the same as wide angle?
<wolfspraul> there are lenses with and without IR filter
<wolfspraul> it's confusing (to me)
<Ornotermes> basicly there is all kinds of lenses
<wolfspraul> :-)
<wolfspraul> ok but let's start with the most common ones. they just differ in focal length/field angle.
<wolfspraul> correct?
<wolfspraul> short focal length = big angle, long focal length = small angle
<wolfspraul> what other types do you find interesting, or make sense in certain typical applications?
<wolfspraul> nice, just the right netsplit. that was more like a communicationsplit.
<wolfspraul> Ornotermes: he, you are back
<Ornotermes> yeah, bad case of the splits
<wolfspraul> I found things like "uv quartz lenses" http://www.ukaoptics.com/uvquartz.html
<wolfspraul> which types of lenses do you find interesting/practical for yourself?
<Ornotermes> different kinds of glass block different wavelenghts
<wolfspraul> the cmos/ccd sensor will work with any kind of wavelength?
<wolfspraul> so it's up to the lense to decide whether the camera takes a IR or UV picture?
<Ornotermes> du you have a link to the datasheed för the sensor?
<Ornotermes> i think it have built in filters
<Ornotermes> http://en.wikipedia.org/wiki/Ultraviolet#Natural_sources_of_UV 2nd paragraph - about glass and UV-light
<wolfspraul> ok reading
<wolfspraul> what types of lenses do you use yourself, or find interesting?
<Ornotermes> normal cameras block IR, and most block UV
<Ornotermes> so i use regular glass optics
<wolfspraul> what blocks it?
<wolfspraul> the sensor?
<Ornotermes> a color filter on the photo sensor
<Ornotermes> usually looks kind of blue-green
<wolfspraul> ah yes. I remember Andrey told me he sens sensors to Russia where they remove this filter :-)
<wolfspraul> sends
<Ornotermes> i've done it on a couple of old pocket cameras, but it scres up the focus
<wolfspraul> ok, so using quartz glass for the lense is one thing
<wolfspraul> which only makes sense if the sensor doesn't block uv
<Ornotermes> it might not make sense for every one uven if it works
<Ornotermes> for normal photos you want to block light that the human eye can't see
<Ornotermes> but for technical use both IR and UV might be very useful
<wolfspraul> germanium lense and quartz lense are two different things?
<Ornotermes> i really don't know :P
<wolfspraul> 'fisheye' is just a fancy term for wide angle, right?
<Ornotermes> bot llok at the properies, thats what interesting
<wolfspraul> with 160o field angle, would be considered a fisheye lense?
<Ornotermes> as far as i know
<wolfspraul> ok cool
<wolfspraul> sorry for my brutal newbie questions...
<wolfspraul> I think your confidence already spilled over to me, I can read some more now :-)
<wolfspraul> thanks!
<Ornotermes> i think its pretty wide angle, but i'm not an optics expert
<Ornotermes> i haven't used winde angle lenses so i cant relate it to anything
<Ornotermes> but keep in mind that the lens have to be made to work with the sensor size you're using
<wolfspraul> sure, that I know
<wolfspraul> I visited Azure and got a nice full-day tour of everything
<wolfspraul> very impressive
<wolfspraul> unfortunately I was overwhelmed, would love to go again
<Ornotermes> whats the url for the sensor datasheet?
<wolfspraul> no sensor in mind
<Ornotermes> oh, ok
<Ornotermes> then i think one without filters would be best so the end user can select the spectrum
<Ornotermes> if possible
<wolfspraul> why do the normal sensors have filters then?
<Ornotermes> for instance a full spectrum all way up to IR light could be very useful for night surveillence
<Ornotermes> bevause (primarly IR) interfere with the "normal" colors
<wolfspraul> yes but the lense is still there, so the lense could filter that out?
<Ornotermes> in a full spectrum camera green plants look yrllow
<Ornotermes> no, a regular lens lets morst IR light pass
<wolfspraul> an IR filter on a lense is that redish looking film you can see when looking at the lense from the side, correct?
<Ornotermes> yes, the red you see is the lowest part of the light the filter reflect
<wolfspraul> ah, interesting
<Ornotermes> but i tou look throu the filter it looks kind of blue
<wolfspraul> so if you have a full spectrum sensor, and then a lense with such IR filter, then you are back to normal, and green plants are green?
<Ornotermes> yes
<wolfspraul> got it
<Ornotermes> as long as there is a filter anywhere along the way of light
<Ornotermes> or if one use only light without IR :P
<qi-bot> [commit] kyak: cxxtools: updated to 2.0, fix build issues http://qi-hw.com/p/openwrt-packages/cc7557c
<qi-bot> [commit] kyak: jbofihe: fix build http://qi-hw.com/p/openwrt-packages/c04a579
<qi-bot> [commit] kyak: libgii: fix build http://qi-hw.com/p/openwrt-packages/dcc4ef7
<qi-bot> [commit] kyak: tntnet: update to 2.0, fix build http://qi-hw.com/p/openwrt-packages/55b2647
<wpwrak> admires taiwan customs: package arrives at 12:25 am and is released at 12:25 am. unlike with argentine customs, this happens on the same day ...
<kristianpaul> pass pass pass !
<kristianpaul> wpwrak: in colombia takes from 2 hrs up to half day
<kristianpaul> may be argentina custom just like hold it in order to create some sign of ..
<wpwrak> kristianpaul: here, they often sit on it until the afternoon. sometimes also until the next day. many years ago, they were quicker and most things were cleared and delivered the day of their arrival
<kristianpaul> wpwrak: how long you had been in argentina btw?
<wpwrak> kristianpaul: sign of ... ? everyone knows that they're lazy, corrupt, and inefficient. you should have seen the comments in a newspaper article (online) when the boss of the customs office at ezeiza (argentina's main airport) was arrested for something a while ago
<kristianpaul> wpwrak: i was waiting you to say it :-)
<wpwrak> kristianpaul: about 9.1 years by now
<kristianpaul> oh, nice :-)
<wpwrak> time flies ;-)
<kristianpaul> oh yes :(
<M_Rojas> Argentina, as a country, is great, except that it's full of Argentines :-)
<kristianpaul> M_Rojas: ah you !!
<kristianpaul> Thats funny a venezuelan told me the same once :-) about his country
<Ornotermes> it would be cool with a nanonote with a clear case
<wpwrak> hates ubuntu. when trying to "upgrade away" a problem that made multiple virtual desktops almost unusable, i now got two of three screens that stay dark, xpdf still segfaults, and evince either fails with some mysterious dbus error (what the heck does a pdf viewer need dbus for ?) or crashes the x server. xrandr crashes x, too.
<tuxbrain> wpwrak: what version and what machine? I had been running an uncrashing ubuntu for years?
<tuxbrain> ?->!
<kristianpaul> tuxbrain: ubuntu 5.04? :)
<tuxbrain> wpwrak: he, I move from LTS to LTS so now 10.04 on main pc and I let the laptop taste the lastest releaases... no problem since 9.04
<Pregunton> Hello everyone
<Pregunton> I have a problem with my lap
<Pregunton> Anyone can help me?
<kristianpaul> #hardware
<kristianpaul> sorry not here :(
<aisa> That was strange.  Pregunton PM'd me asking for help.
<tuxbrain> alsa: maybe with audio problems?:P
<aisa> tuxbrain: ha!  right.  I think because I show up early alphabetically on the channel.
<tuxbrain> your nick is alsa on a whatever-hardware channel , it's no so illogical :P
<aisa> I really thought it was a troll; I understand 'lap' to mean 'I have a problem in my pants.'
<aisa> though at the end of the very brief conversation I think the person was earnest and in the wrong place.
<viric> aisa: yes, it looked like some kind of sex proposal
<wpwrak> tuxbrain: 11.04 ... (by accident)
<tuxbrain> wpwrak: on SPI, MOSI of one side has to be connected with MOSI in the other?
<tuxbrain> same aply to MISO, SCLK, CS, SS?
<wpwrak> tuxbrain: yes, no crossing
<tuxbrain> seems pretty straight forward with the avrdude how to make a cable but, I have a problem with the VTG, I guess is the where we have to supply 3V3 , so first question what UBB pin match this and second one
<tuxbrain> if arduino board is already powered the VTG ping throws 5V, I don't have too much knowledge on electronics but I'm sure this is a bad thing having somthing triying to put 3V3 volts in an already 5V active pin... any idea? I would like to use ISCP header to also communicate with the board once powered , maybe puting a diode will solve this?
<wpwrak> trying to put 5 V into the 3.3 V of the ben would actually be worse. not sure how it reacts to this. if you have a ben you don't like, maybe you can try ;-)
<tuxbrain> the UBB to ICSP correspondence:
<tuxbrain> DAT2->RST
<tuxbrain> DAT3->MOSI
<tuxbrain> GND->GND
<wpwrak> a diode would help, yes. you'd lose a few hundred mV over the diode, but that may still be okay
<tuxbrain> DAT0->SCK
<tuxbrain> DAT1->MISO
<tuxbrain> ?->VTG
<wpwrak> VDD -> >| -> VTG    where >| is a diode
<wpwrak> for DATAn, you can pick any order. you can also use CMD. they all get assigned in avrdude.conf
<wpwrak> and soon you'll even be able to use CLK :) (unless you need CLK to actually provide a clock, but that's not an issue here)
<tuxbrain> OK :) I take note to add a diode to the UBB->ISCP, and will see if another combination can maintain the flat cable with less crossings
<wpwrak> how does VTG connect to the arduino circuit ? the instructable seems a bit vague on it
<tuxbrain> wpwrak: arduino.cc/en/uploads/Main/arduino-uno-schematic.pdf
<wpwrak> curses
<wpwrak> tuxbrain: no PDF viewing :-(
<tuxbrain> you have mail
<wpwrak> thanks :)
<tuxbrain> mmm following the schema seems than VTG goes no where just throws 5V....
<wpwrak> looks good. it connects to the regulated side
<viric> tuxbrain: this is what I call a 'binary format schematic'
<viric> lacking it's "source"
<tuxbrain> viric: I think eagles files are also aviable
<wpwrak> charming ... seems that avrdude can't "jump ahead" when writing a boot loader
<wpwrak> ah, unless i tell it explicitly to select that area. very well, we can do that ...
<wpwrak> ... which of course only exists for other chips than the one i have. well, that answers the implicit question how it would find out which of the several possible destinations it should select.
<tuxbrain> wpwrak: are you working in firmware of what?(atben? atusb?nxuart?)
<wpwrak> atusb. atben has none :) and nxuart doesn't need a boot loader