**** BEGIN LOGGING AT Tue Apr 24 02:59:58 2012
Apr 24 03:28:03 * mranostay goes out to fix the beer problem
Apr 24 04:01:38 <monkun> am I out? or everybody say nothing...
Apr 24 04:04:39 <_sundar_> the latter
Apr 24 04:05:17 <monkun> =)
Apr 24 04:25:43 * mranostay tosses mru a beer
Apr 24 04:51:57 <_av500_> hmm, beer
Apr 24 04:52:40 * _av500_ settles for PBJ
Apr 24 05:24:32 <monkun> does anybody have experience with PSP LCD & beagleboard?
Apr 24 05:45:40 <Russ> w00t, hardcore forking action
Apr 24 05:46:50 <_av500_> what the fork?
Apr 24 05:47:56 <Russ> http://i.imgur.com/VWFCB.png
Apr 24 05:48:15 <Russ> (only SFW if cats are ok)
Apr 24 05:49:50 <_av500_> ew, cats
Apr 24 05:51:58 <Russ> holy sh*t cats!
Apr 24 05:52:08 <Russ> hmm...I'm afraid
Apr 24 05:52:15 <Russ> it looks like google.com might be nsfw today
Apr 24 05:52:18 <Russ> do you dare?
Apr 24 05:56:41 <mranostay> Russ: i'm at home so sure
Apr 24 05:58:05 <hari__> is any 1 who can help us....regarding dev kit..
Apr 24 06:00:56 <HARI_> hi
Apr 24 06:03:21 <thurbad> if you have a question ask it.. some one may answer
Apr 24 06:03:46 <aholler> split brain
Apr 24 07:22:48 <borillion> Im trying to fix eGalax touch screen drivers, 2 chips with the same device and vendor id, and one has its packets reversed,  usbtouchscreen.cIm trying to fix eGalax touch screen drivers, 2 chips with the same device and vendor id exist, and one has its packets reversed, Im lost as to how to handle the issue :|
Apr 24 07:23:14 <stuk_gen> -.- one week for setup a lcd to beagleboard xM...and the problem in the end was the lcd
Apr 24 07:23:41 <av500> one week is nothing
Apr 24 07:25:03 <LetoThe2nd> not only nothing, even less than two weeks!
Apr 24 07:27:00 <stuk_gen> av500: yes when you have onky 3 weeks for a project :P
Apr 24 07:31:00 <aholler> must the project be succesfull? if not, just write down why it failed in the given time.
Apr 24 07:31:58 <av500> ...reason 7) too many irc trolls...
Apr 24 07:32:11 <aholler> describing failures is as important as describing success
Apr 24 07:32:20 <av500> but not as fun
Apr 24 07:32:39 <av500> tears smearing the ink and such
Apr 24 07:47:02 * koen checks BOFH excuses
Apr 24 07:47:07 <koen> solar flares
Apr 24 07:47:32 <aholler> are you in texas?
Apr 24 07:48:29 <aholler> I could write electronics got frozen at night
Apr 24 07:52:35 <ka6sox> koen, that was yesterday's excuse.
Apr 24 07:53:19 <koen> ka6sox: Imagine I said it 48 minutes earlier :)
Apr 24 07:53:45 <ka6sox> :-)
Apr 24 09:15:29 <_tasslehoff_> those of you openembedding, do you work on 32-bit or 64-bit hosts?
Apr 24 09:36:40 <koen> _tasslehoff_: both
Apr 24 09:49:05 <_tasslehoff_> koen: usually not a problem compiling for a 32-bit target on a 64-bit host? We're pondering The Switch from 32 to 64 here.
Apr 24 09:51:17 <jannau> _tasslehoff_: as much a problem as compiling arm code on x86
Apr 24 09:56:39 <_tasslehoff_> jannau: I guess :)
Apr 24 10:02:47 <av500> anybody know a wan router that can handle 128mbit/s?
Apr 24 10:03:38 <LetoThe2nd> av500: the cisco sales rep next door? ;)
Apr 24 10:07:27 <av500> funny enough, most of the wan routers now have 1gbit, but cannot route that to the lan
Apr 24 10:07:47 <av500> you need a beast like this: http://www.amazon.de/Netgear-SRX5308-ProSafe-Gigabit-Firewall/dp/B003IQSK6Y
Apr 24 10:07:57 <phh> av500: just take a linux box ... ?
Apr 24 10:08:58 <lpi> Hi, is anyone can explain me why we need a FAT partition to store bootloader, and why it could not be directly a ext3 partition?
Apr 24 10:09:25 <koen> because the ROM is really read only, not script kiddy ROM
Apr 24 10:10:04 <av500> phh: does not fit
Apr 24 10:10:12 <phh> av500: i'm using an old sun dual single core opteron to route ~ 300Mbps, load average never goes higher than 10%
Apr 24 10:10:22 <av500> maybe
Apr 24 10:10:26 <LetoThe2nd> koen: doesn't it mean ridiculously obscure memory?
Apr 24 10:10:38 <av500> random outcome memory
Apr 24 10:11:19 <av500> phh: does setting it up cost me less than €300 that I even dont have to pay?
Apr 24 10:11:23 <koen> LetoThe2nd: like 'porting', 'ROM' is another of my pet peeves
Apr 24 10:12:10 <lpi> koen: did you talk to me?
Apr 24 10:12:25 <LetoThe2nd> koen: i like port. it is interesting how many people think that there is only red port, whereas white is occasionally really fine for dessert.
Apr 24 10:13:32 <dm8tbr> av500: my WNDR3700 does handle 100M upstream quite fine, haven't checked with more as that's my current limit. 100M to the 10G backbone
Apr 24 10:14:21 <av500> dm8tbr: I need a wan/lan nat
Apr 24 10:14:31 <dm8tbr> yes, it does that too
Apr 24 10:14:46 <av500> cable upped us to 128mbit and the fritz they gave us cannot do it any more
Apr 24 10:14:51 <av500> so its fixed IP now
Apr 24 10:15:33 <phh> av500: well just any computer, with just a NAT iptables rule ...
Apr 24 10:15:41 <av500> phh: not an option
Apr 24 10:16:46 <av500> dm8tbr: hmm, netgear shows no wan2lan throughput
Apr 24 10:16:49 <av500> they do that for the "pro" stuff
Apr 24 10:18:07 <dm8tbr> av500: I get close to 100M over 802.11n from ftp.funet.fi
Apr 24 10:18:36 <dm8tbr> I can make a test run later today if you are interested
Apr 24 10:19:12 <dm8tbr> I suspect the upstream port might also supports gbit, so would be interesting to see how much I can squeeze out
Apr 24 10:19:35 <ant_work> av500: go with ZyWALL for a bit more money
Apr 24 10:19:59 * dm8tbr used the WNDR3700 because it runs openWRT
Apr 24 10:20:02 <jannau> av500: I think c't is usually testing wan to lan nat throughput
Apr 24 10:24:41 <lpi> Sorry, I re-ask my question: is anyone can explain me why we need a FAT partition to store bootloader, and why it could not be directly a ext3 partition?
Apr 24 10:25:13 <LetoThe2nd> lpi: it has been answered... because the rom code only knows fat.
Apr 24 10:25:20 <av500> because the rom code wants fat
Apr 24 10:25:23 <av500> or no-fs
Apr 24 10:25:25 <av500> but not ext3
Apr 24 10:25:25 <dm8tbr> you can also store it raw ;)
Apr 24 10:25:40 <av500> [12:25:03] <av500> or no-fs
Apr 24 10:25:40 <jannau> av500: c't 6/2012 for example
Apr 24 10:25:40 <dm8tbr> yup
Apr 24 10:27:10 <lpi> Ok thank you !
Apr 24 10:27:28 <jannau> Belkin f9k1103 and zyxel NBG5715 have more than 700mbit/s with PPPoE NAT
Apr 24 10:28:15 <ant_work> http://www.smallnetbuilder.com/lanwan/router-charts/view
Apr 24 10:28:32 <lpi> Rom code isn't flashable on the beaglkeboard xM, isn't it?
Apr 24 10:28:53 <dm8tbr> 10:09:25< koen> because the ROM is really read only, not script kiddy ROM
Apr 24 10:29:29 * koen has learned to anticipate questions about writing to Read Only Memory
Apr 24 10:29:35 <jannau> Netgear WNDR4500 has almost 400mbit/s, with IP/IP NAT all three are above 900mbit/s
Apr 24 10:29:45 <ogra_> <koen> because the ROM is really read only, not script kiddy ROM
Apr 24 10:29:45 <ogra_> *snap*
Apr 24 10:29:45 <lpi> sorry
Apr 24 10:29:45 <ogra_> :P
Apr 24 10:29:45 <lpi> lol
Apr 24 10:29:53 <lpi> Haven't my glasses today ^^
Apr 24 10:30:14 <av500> lpi: a glass of what?
Apr 24 10:30:35 <ogra_> port ?
Apr 24 10:30:41 <LetoThe2nd> koen: seems to be the same like whenever talks to me like "y r u"
Apr 24 10:30:42 <lpi> whiskey
Apr 24 10:30:53 <lpi> eyeglasses I mean :)
Apr 24 10:32:46 <av500> jannau: so netgear it is :)
Apr 24 10:33:44 <LetoThe2nd> what does this netgear stuff run as os anyway?
Apr 24 10:34:08 <jannau> linux
Apr 24 10:34:53 <LetoThe2nd> jannau: ah yeah? because whenever someone talks of {dd-,open}wrt, it is rarely on netgear things.
Apr 24 10:35:15 * koen reads http://www.omappedia.org/wiki/Power_Management_Device_Latencies_Measurement
Apr 24 10:35:18 <av500> i dont care for openwrt
Apr 24 10:35:39 * LetoThe2nd likes dd-wrt.
Apr 24 10:37:06 <av500> it should work out of the box
Apr 24 10:37:08 <av500> koen: tl:dr, what is the conclusion?
Apr 24 10:37:28 <jannau> LetoThe2nd: http://wiki.openwrt.org/toh/netgear/wndr4500 - not supported, still running linux 2.6.22 though
Apr 24 10:37:30 * dm8tbr is still running original firmware on his. which is also openWRT, just a bit dusty... worked OOtB
Apr 24 10:38:13 <av500> omg 2.6.22
Apr 24 10:38:21 <av500> that will miss all the latest android patches...
Apr 24 10:38:40 <av500> and no exabit ethernet support
Apr 24 10:38:48 <av500> it will do just fine :)
Apr 24 10:39:54 <koen> av500: use gptimer12
Apr 24 10:40:42 <av500> koen: I remember when ti implemented suspend/resume for the davinci dsp
Apr 24 10:40:58 <av500> and I wrote elaborate code to burst audio decoding to sleep it most of the time
Apr 24 10:41:16 <av500> in the end, just doing it on the arm was more efficient :)
Apr 24 10:41:37 <koen> I bet opencv would help there
Apr 24 10:41:47 <av500> yet, ti kept pushing dsp audio codecs up until omap3...
Apr 24 12:27:47 <_tasslehoff_> koen: on first boot of an Angstrom v2012.05 image, and "Started Recreate Volatile Files and Directories" takes a long time (>4 minutes). normal behaviour?
Apr 24 12:28:51 <koen> is it the volatile of the postinst step that is taking a while?
Apr 24 12:48:34 <_tasslehoff_> koen: I suspect so. But by "takes a long time" I mean "it hasn't finished yet" :)
Apr 24 12:48:38 <_tasslehoff_> so now > 10 minutes
Apr 24 13:01:21 <_tasslehoff_> serial output: http://pastebin.com/RYiL4Zhn
Apr 24 13:06:47 <koen> _tasslehoff_: Started Machine ID first boot configure                                [  OK  ]
Apr 24 13:07:30 <_tasslehoff_> koen: Machine ID should be something that makes more sense?
Apr 24 13:08:38 <koen> I pasted the wrong line
Apr 24 13:09:55 <koen> Started Machine ID first boot configure                                [  OK  ]
Apr 24 13:10:11 <koen> gah
Apr 24 13:10:15 <_tasslehoff_> :)
Apr 24 13:12:46 <av500> koen: I am still waiting for Boris to post a link to "editing the shell commandline on an Beaglebone demo image"
Apr 24 13:15:18 <_tasslehoff_> koen: "Failed to mount /sys/kernel/security: No such file or directory" ?
Apr 24 13:17:17 <koen> harmeless, unless you want selinux
Apr 24 13:18:03 <_tasslehoff_> koen: ok, but was there a line you meant to post that indicated an issue?
Apr 24 13:58:02 <aholler> stuff that matters: https://lkml.org/lkml/2012/4/24/215 ;)
Apr 24 13:59:27 <koen> aholler: cool! That save me an initscript :)
Apr 24 13:59:45 <aholler> you mean a shutdown-script
Apr 24 13:59:49 <mru> aholler: what if the kernel is just brain dead?
Apr 24 14:00:02 <aholler> haven't tested what happens on oops
Apr 24 14:00:22 <thurbad> heh
Apr 24 14:01:10 <mru> usually the heartbeat starts racing
Apr 24 14:01:54 <aholler> that i mean if that reboot_notifier is called
Apr 24 14:02:10 <aholler> but I assume so
Apr 24 14:03:50 <aholler> will test it with 3.3.3 ;)
Apr 24 14:04:23 <av500> aholler: is that a stable patch?
Apr 24 14:04:36 <aholler> not marked as such
Apr 24 14:05:19 <aholler> as it changes a critical behaviour
Apr 24 14:18:27 <mdp> aholler, contributing to mainline is setting a bad example for the rest of us, please stop
Apr 24 14:19:13 <aholler> just send a nack ;)
Apr 24 14:19:59 * mru stabs ftdi
Apr 24 14:20:20 <mdp> aholler, "This will break all my critical financial systems! NACK!"
Apr 24 14:21:41 <aholler> "I used to use the heartbeat in low power shutdown mode as waveform generator. NACK!"
Apr 24 14:23:49 <aholler> or "race in heartbeat_trig_init(). first register_led than register_notifier."
Apr 24 14:24:40 <av500> "my heartbeat LED is wired to my pacemaker....."
Apr 24 14:26:29 <mdp> av500, just don't tar cvf while wearing that pacemaker
Apr 24 14:26:43 <av500> I only wear it on sundays
Apr 24 14:26:46 <aholler> what made me always wonder is why the timer still runs after shutdown
Apr 24 14:26:47 <mru> koen: wtf is wrong with the ftdi on the bone?
Apr 24 14:26:57 <mru> well, probably the same thing that's wrong with _all_ ftdi
Apr 24 14:27:05 <av500> r-pi does not even need an ftdi
Apr 24 14:27:13 <mdp> r-pi++
Apr 24 14:27:14 <aholler> 3.3.3 had again patches
Apr 24 14:27:25 <mdp> av500, that alone makes it the clear winner to me
Apr 24 14:27:41 <aholler> (for ftdi)
Apr 24 14:28:36 <av500> eek, patches
Apr 24 14:28:38 <mru> aholler: my pc suddenly stopped receiving anything from either of my bones
Apr 24 14:28:39 <av500> begone!
Apr 24 14:29:06 <av500> maybe keyboard is broken
Apr 24 14:29:15 <mru> keyboard?
Apr 24 14:29:30 <av500> which you type on with your bony fingers....
Apr 24 14:29:42 <mru> one of the ttyUSBs used to print 'CCCCCCC' when connected
Apr 24 14:29:45 <mru> not so any more
Apr 24 14:29:58 <aholler> power supply ;)
Apr 24 14:30:13 <mru> I didn't change anything
Apr 24 14:30:19 <mru> it just stopped from one minute to the next
Apr 24 14:30:21 <av500> that's what they all say
Apr 24 14:30:32 <av500> let me cite the logs....
Apr 24 14:31:29 <aholler> news: power spike killed bones
Apr 24 14:32:43 <aholler> newer news: man collected living bones
Apr 24 14:32:45 <mru> short of an electric arc reaching across the room, no power spike can kill a bone sitting safely unpowered inside it's tin can
Apr 24 14:35:04 <av500> did you try to turn it off and on again?
Apr 24 14:35:15 <mru> works on laptop
Apr 24 14:35:16 <jsabeaudry> press the tiny button!
Apr 24 14:35:29 <mru> jsabeaudry: I already tried all the normal tricks
Apr 24 14:35:32 <mdp> jsabeaudry: I hired a tiny person to press that button
Apr 24 14:35:35 <mru> so spare me the sarcasm
Apr 24 14:36:40 <av500> check the serial lines before the FTDI with a scope...
Apr 24 14:37:17 <mru> it works on the laptop
Apr 24 14:37:23 <mru> so the bone is fine
Apr 24 14:38:12 <av500> so laptop vs pc?
Apr 24 14:38:21 <mru> it worked on the pc until 10 minutes ago
Apr 24 14:38:25 <mru> then it stopped
Apr 24 14:38:35 <av500> so pc usb dead?
Apr 24 14:38:43 <mru> no, other usb devices still work fine
Apr 24 14:39:03 <mru> like the *nice* pl2303 serials
Apr 24 14:39:11 <mru> those _always_ work
Apr 24 14:39:31 <av500> did you try to reinstall the driver dll?
Apr 24 14:40:03 <av500> or apt-get random things?
Apr 24 14:40:06 <mru> please
Apr 24 14:40:13 <av500> kk
Apr 24 14:40:58 <aholler>       USB: ftdi_sio: fix status line change handling for TIOCMIWAIT and TIOCGICOUNT
Apr 24 14:41:01 <aholler>       USB: ftdi_sio: fix race condition in TIOCMIWAIT, and abort of TIOCMIWAIT when the device is removed
Apr 24 14:41:11 <av500> mru: and dmesg says nothing?
Apr 24 14:41:54 <mru> only that it attched the ttyUSBx to the thing
Apr 24 14:42:37 <av500> rrmod the driver?
Apr 24 14:42:40 <av500> rm*
Apr 24 14:42:44 <koen> aholler: that's in 3.2.16, no?
Apr 24 14:42:51 <aholler> 3.3.3
Apr 24 14:42:59 <aholler> don't know if in 3.2.16 too
Apr 24 14:43:02 <mru> av500: what do you take me for?
Apr 24 14:47:55 <koen> jkridner: gatone is fixed with the python update
Apr 24 15:08:33 <aholler> ok, I sent a v2 which fixed that race ;)
Apr 24 15:09:02 <aholler> just to annoy people ;)
Apr 24 15:16:35 <koen> jkridner: is the dvi cape audio driver fixed already?
Apr 24 15:16:51 <jkridner> certainly not that I know of.
Apr 24 15:16:58 <neels> I can't seem to find the precise dimensions of the expansion header vs. the corner screw holes. Anyone got a link?
Apr 24 15:17:20 <neels> (the 14x2 expansion header near the edge)
Apr 24 15:17:41 <prpplague> neels: the dxf file has all the info
Apr 24 15:17:57 <prpplague> neels: you can also use the gerbers with a viewer to make measurements
Apr 24 15:18:47 <neels> I got that zip file BB-xM_REV_C-2011-05-23.zip -- but my software (kicad & friends) can't seem to be able to open any.
Apr 24 15:18:59 <neels> also no .dxf file inside if I looked correctly
Apr 24 15:19:43 * neels tries to find that .dxf file
Apr 24 15:20:04 <prpplague> neels: http://beagleboard.org/static/beaglebone/a3/Docs/Hardware/BONE_GER.zip
Apr 24 15:20:11 <prpplague> neels: oops sorry thats for bone
Apr 24 15:20:19 <neels> heh yeah :)
Apr 24 15:20:35 <prpplague> neels: http://beagle.s3.amazonaws.com/design/xM-A3/BB_xM_Gerbers_REV_A3.zip
Apr 24 15:21:12 <neels> ...and I can view those with gerbview?
Apr 24 15:21:21 <Crofton|work> er
Apr 24 15:21:25 <prpplague> yea or gerbv
Apr 24 15:21:27 <Crofton|work> can anyone give me one of these?
Apr 24 15:21:29 <Crofton|work> https://play.google.com/store/devices/details?id=galaxy_nexus_hspa
Apr 24 15:25:46 <neels> prpplague, hmm, totally not working. which file do I open? I tried a couple but apparently neither gerbv nor gerbview can make any sense of them (.ipc, .063, .drl)
Apr 24 15:27:34 <prpplague> the .063 are the layers
Apr 24 15:27:45 <mdp> Crofton|work: heh, I've had my verizon lte version for a couple days…first unit had DOA radios..intermittent on 3g/4g/BT/Wifi..second unit solid
Apr 24 15:28:21 <mdp> Crofton|work: massive price drop helped me
Apr 24 15:28:33 <neels> prpplague, yeah, that's what the readme.txt says, too, but it won't open. gerbv: could not read /home/neels/omap/datasheets/BB-xM REV C/ctclyr1.063[-1]
Apr 24 15:28:34 <Crofton|work> I use gsm phones, so I have dialtone when I travel
Apr 24 15:28:50 <Crofton|work> this annoys my cdma loving friend
Apr 24 15:29:00 <mdp> Crofton|work: I will switch to my d2g when I got to .eu..pretty simple
Apr 24 15:29:01 <prpplague> neels: how are you trying to open it?
Apr 24 15:29:08 <prpplague> neels: you have to open it as a layer
Apr 24 15:29:14 * Crofton|work is lazy
Apr 24 15:29:17 <prpplague> neels: i just tested it works fine
Apr 24 15:29:17 <neels> ok, trying that...
Apr 24 15:29:38 <mdp> Crofton|work: for places I got in .us, the gsm carriers don't even land on the radar map for coverage
Apr 24 15:29:53 <neels> yay! n00bs can be stupid sometimes. thanks for the hints!
Apr 24 15:29:56 <mdp> so it's pretty simple for me :)
Apr 24 15:35:05 <mdp> Crofton|work: the 4.65" display is top notch, but still carries well in front pocket of jeans..I'm happy
Apr 24 15:35:58 <mdp> I hear it even runs linux! :P
Apr 24 15:37:37 <Russ> aholler, that issue you mentioned is one that is really flakey
Apr 24 15:38:04 <Russ> aholler, I rebisected it with a 15 count boot test and got 'Merge branch 'for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl' instead
Apr 24 15:39:03 <aholler> Russ: yeah, I've tried to disable your first finding, but that didn't helped.
Apr 24 15:40:08 <Russ> good should be 'abce00f9', bad should be 'd52739c62'
Apr 24 15:40:18 <neels> for the record, beagleboard expansion header's pin 1's center is 0.025, 0.275 inches off the closest corner hole's center; that's 0.635x6.985 mm.
Apr 24 15:41:40 <aholler> something must be really loose in omap for 3.3.2 or 3.3.3. Maybe someone with a jtag could have look why it stops right after "booting kernel"
Apr 24 15:42:06 <av500> put a printk
Apr 24 15:42:33 <aholler> one wouldn't be enough
Apr 24 15:42:49 <aholler> bisecting the source with printks
Apr 24 15:43:02 <aholler> someone should write a script for that
Apr 24 15:46:28 <mdp> funny
Apr 24 15:46:50 * mdp imagines a ktest.pl test case that passed based on dmesg | grep foo
Apr 24 15:54:06 <aholler> does someone know if I can use FT2232 (not -H) as jtag? the documents for the arm-usb-ocd I have just says it works with 2V, but not if it will work with 1.8V too.
Apr 24 15:54:41 <av500> whats 0.2V between friends...
Apr 24 15:55:26 <aholler> seems to be enough to make a ft2232h ;)
Apr 24 15:58:03 <av500> well, I guess FTDI can make new part numbers as fast as TI
Apr 24 15:58:07 <aholler> ah, hmm, i wanted to try to enble all erratas, will do that now.
Apr 24 16:06:56 <stuk_gen> hi all :) after install touchscreen usb on beagleboard if i cat /dev/input/mouse2 i have some data to touchscree. But how can i use this like a mouse in gdm?
Apr 24 16:18:01 <stuk_gen> mmm ok i edit manually  xorg.conf and add some text...but i don't know if is this the correct mode
Apr 24 16:47:12 <aholler> av500: the real reason I've asked was that someone says "no, doesn't work" so that I have a reason not to build me a 14<->20 cable ;)
Apr 24 17:30:35 <aholler> mdp: not posting mainline-patches has an advantage, you don't get cought in dscussions ;)
Apr 24 17:31:42 <mdp> correct
Apr 24 17:40:39 <jsabeaudry> Anyone has made progress on a preemptive kernel for bone?
Apr 24 17:51:16 <aholler> enabling all erratas didn't help, it crashed in irq_enable
Apr 24 17:52:41 <mru> most of those errata workarounds either don't apply or require secure mode
Apr 24 17:53:54 <aholler> now it crashed somewhere else.
Apr 24 17:54:36 <aholler> in strcmp ;)
Apr 24 17:57:49 <mru> not good
Apr 24 17:58:01 <aholler> and now ust booting the kernel.
Apr 24 17:59:03 <aholler> Looks like the right time to finally build that cable and check out the 2v-jtag-thingy ;)
Apr 24 18:03:48 <prpplague> *cough* or purchase a flyswatter2
Apr 24 18:04:51 <mru> aholler: you didn't get a free flyswatter?
Apr 24 18:05:03 <aholler> that should offer power, thats what I like with that arm-usb-ocd.
Apr 24 18:05:24 <prpplague> aholler: we are looking at a revision to add power support
Apr 24 18:05:34 <prpplague> aholler: what kind of use case are you looking at?
Apr 24 18:05:43 <aholler> none ;)
Apr 24 18:06:05 <aholler> I use it often as serial and power for avr-stuff
Apr 24 18:06:22 <prpplague> aholler: thats what i meant
Apr 24 18:06:23 <aholler> because it just offers 500mA
Apr 24 18:06:43 <aholler> or even less
Apr 24 18:06:46 <prpplague> yea
Apr 24 18:07:18 <prpplague> we are looking at a rev of the flyswatter2 to allow for power on the jtag header so more types of adapters can be used
Apr 24 18:07:43 <aholler> sorry, can't follow ;)
Apr 24 18:11:25 <prpplague> aholler: are you familiar with the flyswatter2?
Apr 24 18:12:09 <aholler> no, I think it's almost the same as mine, just that it has a 2232h and no power
Apr 24 18:12:41 <prpplague> aholler: http://www.tincantools.com/images/D/Flyswatter2_800x534.JPG?1335291154313
Apr 24 18:13:00 <prpplague> aholler: yea we also have a very wide range of voltage support as well
Apr 24 18:13:06 <prpplague> aholler: 1.2V to 5v
Apr 24 18:13:55 <aholler> and a nice color ;)
Apr 24 18:14:08 <prpplague> aholler: we have a series of adapter boards for the different jtag configurations
Apr 24 18:14:12 <mru> bacon green
Apr 24 18:14:24 <prpplague> aholler: like for TI arm 14 - http://www.tincantools.com/images/D/ARM20TI14_800x638.JPG?1335291253335
Apr 24 18:14:43 <aholler> hmm kernel-panic doesn't call the reboot_notifier :(
Apr 24 18:15:14 <aholler> prpplague: I know that one ;)
Apr 24 18:15:18 <nemik> it doesn't happen to have SWD support does it?
Apr 24 18:15:24 <prpplague> aholler: we have some new adapters that will add features such as data collection for power consumption, i2c interfaces, avr programming, and possibly some dual trace o-scope functionality
Apr 24 18:16:11 <prpplague> nemik: not familiar with that acronym in this context
Apr 24 18:16:17 <ds2> wow... TI has a ARM14 core chip? which one? :D
Apr 24 18:16:27 <aholler> to replace a bus pirate?
Apr 24 18:16:31 <aholler> sounds nice
Apr 24 18:16:33 <prpplague> ds2: hehe
Apr 24 18:17:52 <nemik> prpplague: single-wire debug. a few ARM cores from i think Energy Micro don't use JTAG anymore but have that for debugging
Apr 24 18:18:23 <ds2> what about SpiBiWire?
Apr 24 18:18:24 <aholler> they just want to sell their own adapters
Apr 24 18:18:54 <prpplague> nemik: the hardware is compatible, however i don't know of any software that supports it currently
Apr 24 18:20:00 <nemik> prpplague: yea i heard there was starting to be some support for it in OpenOCD but not sure it's usable yet. seems like J-Link is what everyone uses for that now, just bundling it on eval boards
Apr 24 18:20:44 <prpplague> if it is supported with j-link, it will work fine with the flyswatter2
Apr 24 18:21:09 <ds2> jlink is evil
Apr 24 18:22:46 <koen> prpplague: excuse my ignorance, but how is i2c connected on the animal lvds?
Apr 24 18:23:13 <mru> with wires
Apr 24 18:26:31 <nemik> prpplague: awesome, i may pick up one of these. seems like no reason it wouldn't support cortex-M0 either, right? planning to use it for an LPC1114
Apr 24 18:27:34 <prpplague> koen: via the i2c pins on the expansion header, hehe
Apr 24 18:27:41 <nemik> ah nevermind, no JTAG on those :/ SWD only
Apr 24 18:27:43 <prpplague> koen: schematic is posted
Apr 24 18:29:33 <koen> prpplague: ah, i2c is also in the lcd headers
Apr 24 18:45:13 <aholler> ah, there is a panic-notifier too.
Apr 24 18:51:12 <aholler> so there will come a v3 of the heartbeat-trigger-patch ;)
Apr 24 19:05:38 <prpplague> ds2: hey, just fyi, i have a new version of the fb-test up on github
Apr 24 19:06:14 <prpplague> ds2: i've added a few command line options to do all red, all green, all blue, and all white
Apr 24 19:06:31 <prpplague> ds2: and tomba has added a font to display some text
Apr 24 19:06:51 <prpplague> ds2: https://github.com/prpplague/fb-test-app
Apr 24 19:23:58 <jsabeaudry> I just updated from 3.2.12 to 3.2.14 and I now get  a bunch of "gpmc_cs_read_reg invoked without initializing GPMC", Is there something new in order to get gpmc on a recent kernel like that?
Apr 24 19:28:26 <flug> hi
Apr 24 19:28:53 <flug> I'm alone ? :p
Apr 24 19:29:10 <prpplague> we are all alone in one way or another......
Apr 24 19:29:13 <smplman> I'm invisible when I'm alone
Apr 24 19:29:20 <flug> lol ;)
Apr 24 19:30:00 <flug> I just a question please :)
Apr 24 19:30:14 <smplman> ask, don't ask to ask
Apr 24 19:30:20 <flug> I'm French
Apr 24 19:30:27 <prpplague> flug: ask away, if someone knows the answer, is available, they will respond
Apr 24 19:30:32 <neels> http://www.mahdiyusuf.com/post/6176918750/survival-guide-irc-1
Apr 24 19:30:35 <prpplague> florian: i am sorry
Apr 24 19:30:41 <prpplague> oops
Apr 24 19:30:45 <prpplague> flug: i am sorry
Apr 24 19:31:02 <florian> prpplague: we are all sorry ;)
Apr 24 19:31:05 * prpplague jokes with flug 
Apr 24 19:31:09 <flug> ok
Apr 24 19:31:09 <prpplague> florian: hehe
Apr 24 19:31:20 <neels> yeah, we're all sorry in one way or another.......
Apr 24 19:31:54 <smplman> I'm sorry i didn't put it all on red 4
Apr 24 19:32:03 <flug> No question ? No Joke snif snif it's a bad world :p
Apr 24 19:32:51 <neels> flug: see #1 on http://www.mahdiyusuf.com/post/6176918750/survival-guide-irc-1
Apr 24 19:33:06 <flug> yes yes ;)
Apr 24 19:33:18 <smplman> i love numbers
Apr 24 19:33:37 <smplman> to bad it only comes on now at 4:30 am
Apr 24 19:34:00 <tasslehoff> koen: I'll bug you one last time today. Unstable network at work today, and I got disconnected. Did you try to paste something odd from my serial output?
Apr 24 19:36:49 <SilicaGel> i think north korea has developed a death ray.
Apr 24 19:36:58 <SilicaGel> they said they would "reduce all the rat-like groups and the bases for provocations to ashes in three or four minutes ... (or) in much shorter time, by unprecedented peculiar means and methods of our own style."
Apr 24 19:37:23 <djlewis> they have the Death Star parked just out of site
Apr 24 19:37:26 <smplman> SilicaGel: evidence?
Apr 24 19:37:45 <SilicaGel> I wonder if they use the PRU to control the charge pump in the main injec...
Apr 24 19:37:48 <SilicaGel> wait, I've said too much.
Apr 24 19:38:34 <smplman> fire le missile
Apr 24 19:38:45 <smplman> but I'm le tired
Apr 24 19:59:43 <zhivko> Hi everybody... I am seeing "NOTE: Preparing runqueue" for at least 5 minutes now building beagle angstrom on ubuntu... is this normal ?
Apr 24 20:03:11 <tasslehoff> zhivko: I have seen it take almost that long sometimes.
Apr 24 20:03:41 <JohnCope> you're building an operating system? i guess the answer is yes then
Apr 24 20:06:11 <zhivko> I break it and second time it went through ok...
Apr 24 20:22:52 <zhivko> I have: "[14928.802739] rtl8192cu: disagrees about version of symbol module_layout" in dmesg
Apr 24 20:23:12 <zhivko> Does it sound familiar? anybody ?
Apr 24 20:25:10 <aholler> get a module for your kernel
Apr 24 20:26:15 <zhivko> Has anbody rtl8192cu for 3.2.5+ ?
Apr 24 20:27:01 <zhivko> anybody :) ?
Apr 24 20:37:51 <mru> better yet, get a proper network adapter
Apr 24 20:52:46 <zhivko> what's proper network adapter on your opinion ?
Apr 24 20:52:59 <mru> a non-realtek one
Apr 24 20:53:06 <zhivko> and that is ?
Apr 24 20:53:52 <zhivko> HOw come that /lib/modules/3.2.13/kernel/drivers/net/wireless/rtlwifi/rtl8192cu/rtl8192cu.ko is there on beagle but I cannot load it to kernel 3.2.5+ ??
Apr 24 20:54:12 <aholler> read
Apr 24 20:54:16 <mru> because 3.2.13 != 3.2.5
Apr 24 20:54:37 <zhivko> I mean who put it there if it's not meant to be loaded with 3.2.5 - i know this could sound silly but anyway ?
Apr 24 20:55:22 <virals> zhivko: folder 3.2.13 is for 3.2.13 kernel. You might have 3.2.5+ anyways, right ?
Apr 24 20:55:33 <zhivko> sources on realtek are for 3.0.2 ! how can I build it then for 3.2.5+ ?
Apr 24 20:55:55 <zhivko> I mean on realtek site... ?
Apr 24 20:56:13 <virals> get src of 3.2.5+, patch with realtek src and compile.
Apr 24 20:56:38 <aholler> source != binary, you might try to compile them for your 3.2.5
Apr 24 20:56:50 <zhivko> you mean src for 3.2.5 angstrom kernel ?
Apr 24 20:57:35 <virals> zhivko: from where got 3.2.5+ it's src code. If it is from angstrom, get it from same src
Apr 24 20:57:44 <zhivko> OK another stupid one: will that give me sources for 3.2.5+? MACHINE=beaglebone ./oebb.sh bitbake systemd-image
Apr 24 20:57:46 <virals> zhivko: that's preferred
Apr 24 20:58:05 <virals> zhivko: not sure.
Apr 24 20:58:19 <zhivko> where do I get sources for 3.2.5+ ?
Apr 24 21:04:30 <jsabeaudry> opkg install kernel-headers? just a random guess not really advice
Apr 24 21:04:44 <zhivko> virals: how can I know wich version will: git clone git://git.angstrom-distribution.org/setup-scripts download ?
Apr 24 21:32:27 <ds2> prpplague: got static binaries checked in too? :)
Apr 24 21:41:23 <jsabeaudry> Wow, great news, it seems the 130ms peak IRQ latency is mostly gone on 3.2.14+ ! On 3.2.12+ it would happen every 8.75 seconds on average, but I've had a 200 seconds run without a glitch on 3.2.14
Apr 24 21:45:14 <ds2> did you do a RCA?
Apr 24 21:56:40 <jsabeaudry> define RCA
Apr 24 22:04:52 <jay6981> root cause analysis
Apr 24 22:08:21 <_av500_> root cavity abscess
Apr 24 22:13:38 <ds2> did either of those happen? :)
Apr 24 22:30:14 <ka6sox> Radio Corporation of America
Apr 24 22:33:10 <_av500_> yeah, 100ys ago :)
Apr 24 22:37:35 <ka6sox> some of us *might* be that old.
Apr 24 22:44:46 <jsabeaudry> No, the reason I rebuilt a kernel is to enable ftrace
Apr 24 22:45:07 <jsabeaudry> to do a irqsoff trace or something similar
Apr 24 22:46:51 <Russ> why can't everyone understand that to fix a problem, you have to understand the causes
Apr 24 22:47:01 <Russ> or at least measure
Apr 24 22:50:02 <_av500_> or at least fudge stuff
Apr 24 22:50:44 <aholler> heartbeat v3, now panic approved: https://lkml.org/lkml/2012/4/24/436
Apr 24 22:56:11 <aholler> thats what I really wanted ;)
Apr 24 23:00:17 <aholler> just had to sleep 2 hours ;)
Apr 24 23:03:41 <Russ> I like that, 'A halted kernel should not show a heartbeat.'
Apr 24 23:04:45 <emeb> ohoz! zomblies!
Apr 24 23:04:59 <aholler> that irritated me since I have the beagle
Apr 24 23:05:24 <aholler> but I never took the time to look at it.
Apr 24 23:09:05 <jsabeaudry> Anyone know of a http server that can serve a character device file, I've tried lighttpd and apache with little luck
Apr 24 23:10:21 <_av500_> //dev/mem?
Apr 24 23:10:33 <aholler> /dev/zero
Apr 24 23:10:43 <jsabeaudry> ya /dev/zero for example
Apr 24 23:11:11 <_av500_> return 0;
Apr 24 23:11:12 <_av500_> done
Apr 24 23:11:23 <aholler> I don't think that works because they use sendfile
Apr 24 23:11:36 <aholler> Presently (Linux 2.6.9): in_fd, must correspond to a file which supports mmap(2)-like operations (i.e., it cannot be a socket); and out_fd  must  refer to a socket.
Apr 24 23:12:22 <aholler> try the one from busybox
Apr 24 23:12:35 <jsabeaudry> aholler, Ah, interesting, that would explain why they both fail
Apr 24 23:12:58 <jsabeaudry> ah yes busybox, I'll give it a go
Apr 24 23:14:19 <aholler> another problem might be, that they usually want to know how large the file is
Apr 24 23:14:40 <aholler> to inform the receipient about what he will get
Apr 24 23:22:39 <jsabeaudry> ah, a bit better, busybox does not return a 404 but allows to download a file of 0 bytes
Apr 24 23:46:50 <Russ> what about a cgi script that just cats the file?
Apr 25 02:17:01 <Russ> geez this bisect is bad, I upped it to 15 boots for a success, and I've just noticed a failure on a boot 14...which means my bisect is useless
**** ENDING LOGGING AT Wed Apr 25 02:59:58 2012