**** BEGIN LOGGING AT Fri Jun 08 02:59:59 2012
Jun 08 03:04:01 <waltermixxx> was cloud9 removed from the repository? ( is that the correct term? )
Jun 08 03:04:13 <waltermixxx> i just tried an opkg install cloud9
Jun 08 03:04:21 <waltermixxx> and it was working yesterday...
Jun 08 03:06:40 <waltermixxx> http://feeds.angstrom-distribution.org/
Jun 08 03:12:18 <mranostay> does everyone have ADD in here or just post too much?
Jun 08 03:44:50 <kilovolt> hello everyone, I'm having a hell of a time getting GDB and openOCD working with the beaglebone. I can provide some more specific errors if anyone thinks they can help, but google has yielded nothing...
Jun 08 03:45:26 <prpplague> kilovolt: hey bud
Jun 08 03:45:34 <prpplague> kilovolt: just missed you in #openocd
Jun 08 03:45:50 <prpplague> kilovolt: there is a new openocd mailing list specifically for users not developers
Jun 08 03:46:03 <prpplague> kilovolt: please post your issue there, with any logs you might have
Jun 08 03:46:03 <kilovolt> oh, haha yeah I wasn't sure if the channel was alive. and ok, sorry, missed that memo i guess...
Jun 08 03:46:24 <kilovolt> i'll do that then, but before you go, i have a simple question..
Jun 08 03:46:33 <prpplague> kilovolt: TI and a wide number of folks are monitoring the new list to assist in getting a bunch of the beagle related openocd issue addressed
Jun 08 03:46:47 <prpplague> kilovolt: in addition elinux.org has a wide range of openocd pages
Jun 08 03:46:56 <prpplague> kilovolt: there is a new beaglebone page as well
Jun 08 03:47:24 <prpplague> kilovolt: please register there, it is free, and your assistance is appreatiated in documenting issues
Jun 08 03:48:08 <prpplague> kilovolt: http://elinux.org/OpenOCD#Technical_Support
Jun 08 03:48:28 <kilovolt> is there any version of gdb/openocd that you know work well together? ive compiled gdb7.4 from source and that didnt play nicely with openocd 0.5 from the ubuntu repositories
Jun 08 03:48:47 <prpplague> ubuntu builds of openocd are wonky
Jun 08 03:49:14 <prpplague> please try some of the build instructions from the wiki for pulling from git or as a tarball
Jun 08 03:49:20 <prpplague> kilovolt: http://elinux.org/OpenOCD
Jun 08 03:49:20 <kilovolt> i switched to the most recent codesourcery gdb and it worked ok, but openocd 0.6 worked with neither my gdb build or the sourcery one
Jun 08 03:49:41 <kilovolt> ive tried a lot on the elinux site. great stuff, but i am still having issues
Jun 08 03:49:45 <prpplague> there is not 0.6 release as of yet, some of the instructions as you to force a version number
Jun 08 03:50:06 <prpplague> kilovolt: ok, no worries, please post to the list, we have a bunch of folks monitoring the list
Jun 08 03:50:11 <kilovolt> well, it was whatever was in the git repository
Jun 08 03:50:18 <kilovolt> ok, ill do that then, thanks!
Jun 08 03:50:41 <prpplague> kilovolt: you can reach several of us on #openocd , you just didn;t stay long enough
Jun 08 03:51:03 <prpplague> kilovolt: average resolution time right now is about 3-5 days
Jun 08 03:51:36 <kilovolt> i see... sorry about that then. ill post to the list you mentioned and see if someone there has any ideas first
Jun 08 03:56:10 <prpplague> kilovolt: no worries
Jun 08 03:56:14 <prpplague> kilovolt: :)
Jun 08 04:03:52 <ds2> you could always get a lauterbach for quicker support ;)
Jun 08 04:25:15 <prpplague> ds2: where is the fun in that?
Jun 08 04:28:09 <Russ> the fun is here my friends http://sphotos.xx.fbcdn.net/hphotos-ash3/582288_3937920134112_1119054323_n.jpg
Jun 08 04:28:43 <Russ> (not real...)
Jun 08 04:42:02 <prpplague> Russ: tasty!
Jun 08 04:58:50 <ds2> prpplague: lauterbach's have their own 'fun'
Jun 08 04:58:53 <ds2> ;)
Jun 08 07:59:39 <ARM_ROOKIE> is it possible to do in circuit code stepping using Code Composer Studio and the FT2232H JTAG connection? Or do i need to buy a debugger?
Jun 08 08:35:20 <Borillion> is it ok to increase the mem in bootscr to 512M ?
Jun 08 08:36:37 <mru> uh?
Jun 08 08:37:00 <mru> which board are you using?
Jun 08 08:37:28 <jacekowski> Borillion: try it
Jun 08 08:37:35 <jacekowski> Borillion: and you will have your answer
Jun 08 08:37:45 <mru> aka koen rule #3
Jun 08 08:37:48 <Borillion> the beagleboard xm
Jun 08 08:38:05 <mru> why are you passing a mem parameter at all?
Jun 08 08:38:11 <jacekowski> but honestly, i wish it would work that way
Jun 08 08:38:35 <Borillion> Its in the boot.scr by default I didnt add it
Jun 08 08:39:07 <Borillion> I figure it maybe a cause of laggy-ness even on the demo build
Jun 08 08:39:36 <jacekowski> xm  only has 256M doesn't it?
Jun 08 08:39:45 <Borillion> not sure
Jun 08 08:39:45 <jacekowski> like normal bb?
Jun 08 08:40:09 <Borillion> its 512
Jun 08 08:40:30 <mru> xm has 512M
Jun 08 08:40:33 <Borillion> why not use all of what you have
Jun 08 08:40:38 <Borillion> yea I thought so
Jun 08 08:40:45 <mru> what is the full command line?
Jun 08 08:41:04 <Borillion> setenv bootargs 'console=ttyO2,115200n8 androidboot.console=ttyO2 mem=256M root=/dev/mmcblk0p2 rw rootfstype=ext3 rootdelay=1 init=/init \
Jun 08 08:41:04 <Borillion>   ip=off omap_vout.vid1_static_vrfb_alloc=y vram=8M omapfb.vram=0:8M omapdss.def_disp=dvi omapfb.mode=dvi:1024x768-16'
Jun 08 08:41:23 <aholler> rowboat was done in times xm doesn't exist
Jun 08 08:41:36 <mru> oh ffs why didn't you say you were using that piece of crap?
Jun 08 08:41:44 <Borillion> LOL
Jun 08 08:41:52 <aholler> he ikes to fool us with his android
Jun 08 08:41:59 * mru makes note
Jun 08 08:42:04 <Borillion> ^ Im using the crap
Jun 08 08:42:24 <Borillion> I was using what ti recommended
Jun 08 08:42:35 <Borillion> didn't know better
Jun 08 08:44:55 <Borillion> Only other thing I heard of is Linaro, but dunno if they provide a build for the beagleboard
Jun 08 08:47:30 <Borillion> if anyone wants to recommend anything else they are welcome
Jun 08 08:47:45 <Borillion> linaro is only for the pandaboard as far as I recall
Jun 08 08:55:52 <Borillion> mru, what do you recommend ?
Jun 08 08:56:05 <mru> what do you need to do?
Jun 08 09:05:37 <Borillion> mru an android build you recommend?
Jun 08 09:06:14 <mru> I don't know what works best on the xm these days
Jun 08 09:13:02 <Borillion> is there anything better than rowboat android, well thats android?
Jun 08 10:34:42 <m0erk> hello again
Jun 08 10:35:07 <m0erk> i am not able to playback any sound in angstrom
Jun 08 10:35:27 <m0erk> kenel: 3.2.18
Jun 08 10:35:49 <m0erk> console image.. is there any trick or so?=
Jun 08 10:36:11 <m0erk> [AO_ALSA] alsa-lib: confmisc.c:768:(parse_card) cannot find card '0' [AO_ALSA] alsa-lib: conf.c:4241:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory [AO_ALSA] alsa-lib: confmisc.c:392:(snd_func_concat) error evaluating strings [AO_ALSA] alsa-lib: conf.c:4241:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory [AO_ALSA] alsa-lib: confmisc.c:1251:(snd_f
Jun 08 10:36:39 <m0erk> anything missing?
Jun 08 10:36:49 <m0erk> google just give me no hint
Jun 08 10:37:15 <dm8tbr> and on which hardware?
Jun 08 10:44:28 <m0erk> beagleboard-xm
Jun 08 10:44:45 <m0erk> angstrom with kernel 3.2.18
Jun 08 10:52:25 <m0erk> anyone got an idea?
Jun 08 10:52:37 <m0erk> is sound genrally supported=?
Jun 08 11:00:03 <m0erk> its weird... the alsa pakets are installed but if i try to execute the amixer it says
Jun 08 11:00:14 <m0erk> amixer: Mixer attach default error: No such file or directory
Jun 08 11:00:28 <m0erk> isn't it installed correctly?
Jun 08 11:00:38 <m0erk> amixer: Mixer attach default error: No such file or directory
Jun 08 12:19:49 <Tamilarasi> hi, i trying to port uimage u-boot MLO and rootfs.ext2(already compile binary) on deveopemrnt  XAM3359ZCZ beagle board.it's been ported, but unable to get debug message on the serial port .where is the problem.
Jun 08 12:20:25 <Tamilarasi> it's only showing C on the terminal
Jun 08 12:21:07 <aholler> there is a new beagleboard available?
Jun 08 12:21:44 <Tamilarasi> yes,i am using new beagle board
Jun 08 12:22:46 <ogra_> i think thats a bone not a beagleboard
Jun 08 12:24:38 <Tamilarasi> sorry,it's beagle bone
Jun 08 12:32:04 <Tamilarasi> solutio pls
Jun 08 12:32:15 <Tamilarasi> solution pls
Jun 08 12:32:32 <bradfa> C on terminal means it's looking for a boot source and can't find one
Jun 08 12:48:23 <champ> anyone der?
Jun 08 12:49:17 <champ> can anyone help me in configuring mail server on beagleboard??
Jun 08 12:50:07 <aleek> champ: is it strictly beagle related? maybe find channel for you mail serwer?
Jun 08 12:50:59 <champ> yes..beagle related
Jun 08 12:51:26 <aleek> so tell us, whats the problem:]
Jun 08 12:52:12 <champ> i'm trying to configure postfix MTA on beagleboard xM..so that i ll b able to send mail using command line from BB..
Jun 08 12:52:45 <champ> but i don't know how to set the configuration file of postfix?
Jun 08 12:54:18 <champ> has anyone tried this before? or is there any other way to send emails from beagleboard??
Jun 08 12:54:21 <ogra_> configuring postfix on a beagle doesnt differ from configuring postfix on a xeon based intel server
Jun 08 12:54:24 <aholler> use ssmtp
Jun 08 12:54:26 <ogra_> not really beagle related
Jun 08 12:54:39 <mdp> http://www.postfix.org/BASIC_CONFIGURATION_README.html
Jun 08 12:54:40 <mru> aholler: ssmtp is not a real mta
Jun 08 12:54:45 * mdp wins with the first google hit
Jun 08 12:55:01 <champ> postfix supports smtp..
Jun 08 12:55:03 <aholler> but it's enough to send mails from the command line
Jun 08 12:55:28 <mru> oh, if that's all he needs
Jun 08 12:55:34 <mru> postfix is way overkill then
Jun 08 12:55:45 <mru> although ssmtp needs a real mta running nearby
Jun 08 12:55:50 <mdp> it may be for hack value though
Jun 08 12:56:16 <champ> so is there any simpler option ??
Jun 08 12:56:34 <aholler> as I said, try if your are able to use ssmtp
Jun 08 12:56:47 <mru> do you have a local mta on the network?
Jun 08 12:58:02 <champ> i ll try ssmtp..i have sendmail on local network..
Jun 08 12:59:16 <champ> ssmtp sounds easy and perfect for my application..
Jun 08 12:59:47 <champ> i hope i ll be able to implement it on BB...thank you aholler..
Jun 08 13:05:06 <yegorich> mdp: I'm back again
Jun 08 13:05:59 <mdp> wb
Jun 08 13:06:11 <yegorich> mdp: any ideas?
Jun 08 13:06:38 <mdp> your PC meant your host PC in your earlier statement?
Jun 08 13:08:14 <yegorich> mdp: yes ;-)
Jun 08 13:08:25 <yegorich> mdp: my Windows host. Brrr ...
Jun 08 13:08:54 <aholler> the future underground
Jun 08 13:09:13 <mdp> yegorich: oh, linux in a VM? ;)
Jun 08 13:09:31 * ogra_ usually more thinks toilet than underground ... somehow tiles indicate that ...
Jun 08 13:09:50 <yegorich> mdp: no, Linux host is an extra embedded x86 PC, connected via SSH
Jun 08 13:09:57 <mru> the future ain't what it used to be
Jun 08 13:09:59 <mdp> ok
Jun 08 13:10:25 <yegorich> mdp: are there any conditions, that would enable RTC address space?
Jun 08 13:11:24 <yegorich> mdp: this patch brakes booting on our prototype: http://arago-project.org/git/projects/u-boot-am33x.git?p=projects/u-boot-am33x.git;a=commit;h=e3f1bbc6c38ffa1e0ea75c45e883a6771f731848
Jun 08 13:11:50 <yegorich> mdp: but on beaglebone it doesn't make any problems
Jun 08 13:12:13 <yegorich> mdp: I compared both CPU and ROM boot revisions and they both are the same
Jun 08 13:14:33 <mdp> interesting…I see why it was added
Jun 08 13:15:04 <mdp> incidentally, I notice it's a duplication of code from davinci…but that's another story (same rtc h/w there)
Jun 08 13:15:54 <mdp> yegorich, one issue was that I was looking at the not yet complete mainline u-boot source as a reference
Jun 08 13:16:34 <mdp> so that's not there, but in any case…are you planning to support PM in the kernel on your custom board?
Jun 08 13:16:49 <yegorich> mdp: it is not really complete. There is almost nothing in the mainline
Jun 08 13:16:55 <tasslehoff> anyone got suspend/resume working on linux-mainline or linux-sakoman 3.2?
Jun 08 13:17:11 <mdp> u-boot, I mean…yegorich, u-boot will be complete first.
Jun 08 13:17:40 <mdp> but yeah, Tartarus keeps reminding me it's incomplete ;)
Jun 08 13:19:15 <aholler> ogra_: maybe we could agree on underground toilet ;)
Jun 08 13:19:22 <ogra_> ++
Jun 08 13:19:23 <ogra_> !
Jun 08 13:19:30 <mdp> yegorich, I guess my point about PM is that if you don't need system suspend / deep sleep on your custom board, then you can disregard that patch
Jun 08 13:20:31 <mdp> yegorich, I suppose you'll tell me PM is important to you though
Jun 08 13:21:14 <tasslehoff> ah, pm is already the topic. /me sits back and reads backlog
Jun 08 13:22:40 <yegorich> mdp: the system is not battery powered
Jun 08 13:22:53 <yegorich> mdp: at least not in theory ;-)
Jun 08 13:23:06 <yegorich> mdp: what you mean PM path?
Jun 08 13:23:50 <mdp> the whole point of that patch is to support having the 32khz clock settled for use in deep sleep by the kernel
Jun 08 13:24:08 <yegorich> mdp: O.K. I see now
Jun 08 13:24:13 <mdp> the way PM "works" on am335x is that is the only source active when the m3 powers down the a8 power domain
Jun 08 13:24:38 <mdp> and vaibhav is pointing out that you have to have u-boot fire it up because it has an enormous settling time
Jun 08 13:25:14 <mdp> tasslehoff, am335x specific fwiw…and not talking about bone itself fwiw
Jun 08 13:25:57 <yegorich> mdp: if I don't enable RTC in SPL, then my kernel crashes during RTC probing/activation. But O.K. I think I can live without RTC and use the one I have on our 65910A PMIC
Jun 08 13:26:45 <mdp> hrm, ok, I guess they would have relied on that being configured..
Jun 08 13:27:04 <mdp> hrm, I'll have to do some more reading
Jun 08 13:29:39 <mdp> yegorich, only thing I can think of is that somehow the pll didn't get initialized (though unlikely due to the busy read) or something similar to make the write to kick0 timeout/fail.
Jun 08 13:34:17 <yegorich> mdp: how can I check if pll got initialized?
Jun 08 13:34:49 <mru> read the status register?
Jun 08 13:36:32 <mdp> yegorich, that's it in fact… https://github.com/pgibson/u-boot-innotech/commit/fe82626badd17515fc17899f2fce7ff9f9ae68f0
Jun 08 13:36:55 <mdp> I thought that looked suspicious but I'm not familiar with it…found the above correction
Jun 08 13:37:06 <mdp> if I read it correctly ;)
Jun 08 13:37:08 <yegorich> mdp: while (__raw_readl(CM_RTC_RTC_CLKCTRL) != PRCM_MOD_EN);
Jun 08 13:37:32 <arcanescu> how many amps does the beagle take i cant seem to find that figure :/
Jun 08 13:38:19 <yegorich> mdp: I noticed that too and fixed, but that didn't help
Jun 08 13:39:31 <mdp> bummer
Jun 08 13:43:01 <mdp> yegorich: you've stumped my limited knowledge..I'll poke Tartarus about it
Jun 08 13:43:32 <mdp> he actually works on am335x stuff
Jun 08 13:44:21 <yegorich> mdp: thanks
Jun 08 14:04:30 <jkridner_> ugh.  why is connman wifi so hard to configure?
Jun 08 14:07:57 <riskable> Well, I'm done modifying the tin that came with my Beaglebone so that I can put the 'bone inside while still keeping everything connected.  I can even swap out the microSD card
Jun 08 14:08:19 <riskable> It is a bit ugly...  I think I need to paint it
Jun 08 14:08:42 <jkridner_> make sure nothing shorts
Jun 08 14:09:08 <riskable> Nice and solid though!  Turns out that two popsicle sticks glued together are just the right size for acting as standoffs to screw the 'bone into
Jun 08 14:09:22 <jkridner_> nice.
Jun 08 14:09:33 <jkridner_> would be great for instructables.com
Jun 08 14:09:43 <riskable> Yeah, I took lots of pictures
Jun 08 14:10:00 <riskable> I even deburred the sharp edges that were left after making cuts/bends with my snips/pliers
Jun 08 14:10:41 <riskable> The only thing I need now are tiny little wood screws.  I pre-drilled some holes for screws I thought I had but I just couldn't find them!  My garage is a mess
Jun 08 14:11:33 <riskable> Actually, while I wait for this (work) build to finish I think I'll go look again.  brb
Jun 08 14:15:21 <Tartarus> re am335x U-Boot, all I can say is that it's good enough for the am335x GP EVM, beaglebone and EVM-SK, but there's certainly some assumptions made that aren't strictly required, sakoman_ has posted patches to fix a few of these
Jun 08 14:15:26 <Tartarus> yegorich: ^^^
Jun 08 14:15:49 <riskable> Damn, no screws to be found
Jun 08 14:15:56 <riskable> I hate having to go to the hardware store
Jun 08 14:16:45 * riskable starts looking around for something he can cannibalize
Jun 08 14:19:15 * jkridner_ finally finds http://git.kernel.org/?p=network/connman/connman.git;a=blob;f=doc/config-format.txt;h=1e03f787fb7ce035c5188cac3c526ae517c43efa;hb=HEAD
Jun 08 14:20:17 <riskable> Maybe I should turn my 'bone tin into a belt buckle
Jun 08 14:21:18 <angs> riskable: have you ever tried to create ad-hoc network with beaglebones?
Jun 08 14:21:24 <angs> with the usb wifi doggle
Jun 08 14:21:31 <riskable> angs: No, have you?
Jun 08 14:22:26 <angs> Yes, but I could not manage
Jun 08 14:22:56 <angs> Connman does not support ad-hoc mode, I wonder what to do with connman
Jun 08 14:23:17 <mru> kill it with fire
Jun 08 14:23:21 <angs> :)
Jun 08 14:23:43 <aholler> I'm unable to understand why someone wants to use something which wants it's configuration somewhere in /var
Jun 08 14:23:43 <angs> opkg fire connman?
Jun 08 14:24:29 <riskable> I personally severely dislike connman
Jun 08 14:24:42 <koen> angs: it does do wifi-direct
Jun 08 14:24:51 <mru> aholler: permanent config in /var?
Jun 08 14:24:53 <mru> that's weird
Jun 08 14:24:58 <koen> jkridner_: I just use the gui to config wifi :)
Jun 08 14:25:12 <mru> koen: so do I, my gui is xterm
Jun 08 14:25:31 <jkridner_> do you ship with vncserver now so I can reach the GUI?
Jun 08 14:26:51 <koen> jkridner_: I have an lcd or dvi
Jun 08 14:26:56 * jkridner_ tries opkg install angstrom-x11vnc-xinit
Jun 08 14:28:58 <jkridner_> hmmm... Fatal server error: [3429599.460] no screens found
Jun 08 14:29:33 <koen> jkridner_: is not a bad time to point out that most wifi dongles won't work anyway due to musb?
Jun 08 14:29:38 <koen> now*
Jun 08 14:30:01 <jkridner_> well, that is what I was actually trying to test. :)
Jun 08 14:30:14 <mru> koen: what sets "most" apart from "all"?
Jun 08 14:31:00 <koen> mru: I hear rumours of some dongles working
Jun 08 14:31:07 <jkridner_> I guess it really isn't much of a test, since my USB host wasn't working at all until I switched boards.
Jun 08 14:31:12 <aholler> maybe idle dongles
Jun 08 14:31:23 <aholler> dmesg shows them => success
Jun 08 14:31:37 <aholler> like omap-ehci in 3.4 ;)
Jun 08 14:32:03 <jkridner_> I believe much more is possible with software improvements, but I really have very little visibility into where the issues are.
Jun 08 14:32:09 * riskable is wondering what else he could fit inside the tin along with the Beaglebone.
Jun 08 14:32:21 <riskable> A LiPoly battery for sure
Jun 08 14:33:37 <jkridner_> koen: can I not run X11 w/o a display attached?
Jun 08 14:34:02 <aholler> sure you can
Jun 08 14:34:19 <jkridner_> aholler: do you know how to do it without /dev/fb0?
Jun 08 14:34:33 <aholler> xvfb
Jun 08 14:35:58 <koen> jkridner_: if you have unsecured or only WEP, iw can handle it for testing
Jun 08 14:36:10 <jkridner_> hmmmm.... http://www.angstrom-distribution.org/repo/?pkgname=xserver-xorg-xvfb seems to be built for core...
Jun 08 14:36:22 <aholler> jkridner_: there is alsoxvnc
Jun 08 14:36:31 <jkridner_> but doesn't seem to be in the package feeds with opkg install xserver-xorg-xvfb'
Jun 08 14:37:09 <jkridner_> seems like those would be great things to have in the distro.
Jun 08 14:38:19 <yegorich> Tartarus: Sorry. I'm here, but haven't seen the notification
Jun 08 14:38:27 <Tartarus> yegorich: no worries
Jun 08 14:39:38 <yegorich> Tartarus: can wrong value of RTC_PORZ have inpact at RTC registers not being accessed?
Jun 08 14:40:20 <Tartarus> yegorich: I'm not sure what you've done custom on your board, sorry.  You're trying to use the on chip one, rather than one you've wired up elsewhere, yes?
Jun 08 14:40:32 <Tartarus> Did you change the base clock rate?
Jun 08 14:40:53 <Tartarus> as in http://patchwork.ozlabs.org/patch/162044/ would be helpful
Jun 08 14:41:08 <yegorich> Tartarus: I'm using 24MHz as by BeagleBone
Jun 08 14:41:32 <yegorich> Tartarus: but I use another PMIC, that has built-in RTC
Jun 08 14:41:44 <Tartarus> ok
Jun 08 14:41:46 <yegorich> Tartarus: but for now I'm not using it
Jun 08 14:42:18 <yegorich> Tartarus: I'll measure RTC_PORZ and compare it to the one of BeagleBone
Jun 08 14:42:28 <Tartarus> ok
Jun 08 14:43:01 <Tartarus> Are you using the arago-project tree or mainline u-boot?
Jun 08 14:44:50 <Tartarus> yegorich: If I remember everything right, the beaglebone and the GP EVM use different PMICs
Jun 08 14:45:04 <Tartarus> and the arago-project tree deal with setting up the right PMIC, spl_board_init
Jun 08 14:45:16 <Tartarus> mainline u-boot doesn't have this worry or code yet
Jun 08 14:50:13 <riskable> Is there a way I can feed 5V to the Beaglebone without using the barrel plug or the USB connector?
Jun 08 14:50:29 <riskable> (without having to solder some wires to the underside of the barrel plug)
Jun 08 14:50:42 <koen> riskable: sys_5v or vdd_5v, I forget which, check the schematics
Jun 08 14:51:09 <koen> one of the top P9 pins
Jun 08 14:51:20 <riskable> koen: Excellent, thanks
Jun 08 14:51:34 <jkridner_> koen: I was able to manually install the xserver-xorg-xvfb and invoke x11vnc, but, naturally, I don't have a window manager or anything else running. Any quick way to reuse the X11 config?
Jun 08 14:51:35 <koen> I connected the sparkfun lipo thing that way
Jun 08 14:51:37 <riskable> I have the BONESRM_latest.pdf open but I was having trouble finding that info
Jun 08 14:52:56 <yegorich> Tartarus: I'm using arago-project tree and 65910 PMIC
Jun 08 14:53:07 <Tartarus> ok
Jun 08 14:53:33 <koen> riskable: it's hidden in the schematics :)
Jun 08 14:54:06 <riskable> koen: Well, I just found it:  Page 76 has it listed...  On P9, it is the 3rd row down from the top
Jun 08 14:54:49 <koen> VDD_5V is connected to the input of the barrel
Jun 08 14:54:58 <koen> SYS_5V comes from the PMIC
Jun 08 14:54:59 <riskable> I'm going to wire my LiPoly charger directly to the 'bone and stick it under the lid of the tin
Jun 08 14:55:08 * jkridner_ looks at startx
Jun 08 14:56:07 <riskable> I'm also going to wire the 5V output from the 'bone to the input of the LiPoly charger so I can charge it using just the Beaglebone's connectors
Jun 08 14:58:36 <jkridner_> whoa! talk about cruft.  /usr/lib/X11/xinit/xinitrc invokes twm!
Jun 08 14:59:06 * jkridner_ guesses that 'startx' is NOT how koen is invoking X.
Jun 08 15:02:35 <Tartarus> yegorich: Did you make sure spl_board_init does the right thing for your board?  If you don't have the EEPROM plugged in and with the right contents, stuff could be "interesting"
Jun 08 15:02:55 <Tartarus> I'm not 100% sure if it defaults to GP EVM or bone as what it assumes the board is
Jun 08 15:03:06 <jkridner_> doing xinit -- /usr/bin/Xvfb doesn't seem to invoke the /etc/xinit tasks. :(
Jun 08 15:04:05 <aholler> jkridner_: Xvnc might be better suited for you
Jun 08 15:04:17 <jkridner_> aholler: it isn't in koen's feed.
Jun 08 15:06:18 <jkridner_> koen: why is startx there if it isn't used and references things like twm?
Jun 08 15:08:23 <koen> it's there for people who want to sure startx
Jun 08 15:08:42 <koen> and the upstream default is twm and friends
Jun 08 15:09:18 <jkridner_> but twm isn't even in the feeds.
Jun 08 15:09:23 <koen> I guess I was wrong in assuming people who are still using 'startx' know what it does and doesn't do
Jun 08 15:10:00 <yegorich> Tartarus: spl_board_init is it before rtc32k_enable() or after?
Jun 08 15:10:04 <jkridner_> how are you invoking X?
Jun 08 15:10:13 <koen> I let gdm to it for me
Jun 08 15:10:13 <jkridner_> I know graphical.target has something to do with it.
Jun 08 15:10:19 <koen> do*
Jun 08 15:10:26 <Tartarus> yegorich: Lets see...
Jun 08 15:10:31 <yegorich> Tartarus: if I don't activate RTC, then I can boot into Linux
Jun 08 15:11:11 <yegorich> Tartarus: I have EEPROM, but for now it has no content and in the future it will have other velues
Jun 08 15:11:30 <Tartarus> yegorich: after
Jun 08 15:11:49 <yegorich> Tartarus: so EEPROM content and so on is not relevant
Jun 08 15:11:50 <Tartarus> yegorich: I think you need to program it as a bone to fake it out, to start with
Jun 08 15:12:04 <Tartarus> yegorich: U-Boot reads the EEPROM to decide what board we're on
Jun 08 15:12:06 <yegorich> Tartarus: rtc32k_enable() is part of s_init()
Jun 08 15:12:16 <Tartarus> and I'm not 100% sure it's consistent in what it does if the EEPROM is blank
Jun 08 15:13:31 <jkridner_> koen: how do you invoke gdm and where does it set its X server?
Jun 08 15:13:39 <koen> I don't invoke it
Jun 08 15:13:43 <koen> it starts on boot
Jun 08 15:14:01 <jkridner_> what starts it on boot?
Jun 08 15:14:04 <jkridner_> me reads http://tldp.org/HOWTO/XFree-Local-multi-user-HOWTO/dm_conf-gdm.html
Jun 08 15:14:08 <koen> pid 0
Jun 08 15:15:11 <yegorich> Tartarus: I must leave now and will try some other things next week and let you know, if I could solve the problem. Thanks for your help. Have a nice weekend!
Jun 08 15:17:07 <jkridner_> koen: per /lib/systemd/system/gdm.service then?
Jun 08 15:21:42 <jkridner_> adding 0=/usr/bin/Xvfb to gdm.conf and doing systemctl restart gdm.service didn't do the trick.
Jun 08 15:26:52 <waltermixxx> hi there...
Jun 08 15:28:46 <waltermixxx> just wondering what it means when  my beagle board boots up from the Angstrom Narcissus i create...  i get the angstrom splash screen,  then I get the large login screen on a white background with on screen keyboard... i login....
Jun 08 15:29:03 <waltermixxx> the screen goes black, with an X mouse cursor
Jun 08 15:29:08 <waltermixxx> then it changes to a pointer arrow
Jun 08 15:29:22 <waltermixxx> the screen remains black with just the pointer
Jun 08 15:29:28 <waltermixxx> which I can move around with my mouse
Jun 08 15:29:31 <waltermixxx> but that's it.
Jun 08 15:30:11 <waltermixxx> when I first booted it up there was no uEnv.txt file,  but the resolution was 640 x 480
Jun 08 15:30:46 <waltermixxx> i copied the uEnv.txt from the  sd card that came with my beagleboard xM
Jun 08 15:31:30 <waltermixxx> and the resolution for the angstrom splash screen and login screen was HD720,  but after that, no desktop, no menu bar... just a pointer on a black screen..
Jun 08 15:32:18 <waltermixxx> I will have to sign into my linux laptop so I Can copy and paste the uEnv.txt here
Jun 08 15:32:27 <waltermixxx> incase there is someting I need to change?
Jun 08 15:34:02 <waltermixxx2> ok will grab the file and paste it in
Jun 08 15:34:43 <waltermixxx2> mpurate=1000  dvimode="hd720 omapfb.vram=0:8M,1:4M,2:4M" vram=16M optargs="consoleblank=0" console="tty0 console=ttyS2,115200n8"
Jun 08 15:35:14 <waltermixxx2> works great with the test sd card provided by beagleboard.org
Jun 08 15:35:43 <waltermixxx2> but not with the Angstrom Narsissus
Jun 08 15:39:15 * jkridner_ tries ln -s /usr/bin/Xvfb /usr/bin/X, because I can't figure out where gdm picks up the path to X.
Jun 08 15:40:21 <mru> just like the old days!
Jun 08 15:40:30 <aholler> who put those quotes into the line with optargs?
Jun 08 15:40:54 <waltermixxx> it was already there
Jun 08 15:41:04 <mru> since the dawn of time?
Jun 08 15:41:53 <waltermixxx> oddly enough I removed the dvimode="hd720 omapfb.vram=0:8M,1:4M,2:4M" and now I get no screen at all :(
Jun 08 15:46:33 <waltermixxx> my micro sd card reader on my beagle board xM is getting a work out... how many ejects and inserts is it rated at?
Jun 08 15:47:11 <mru> whatever makes it fail at the most inconvenient moment
Jun 08 15:47:40 <waltermixxx> has anyone seen this black screen with mouse cursor thing before?
Jun 08 15:47:48 <riskable> Well, in my experience the only thing that breaks is the spring mechanism...  So you can still make it work pretty much forever if that breaks by just forcing the sucker in there
Jun 08 15:48:34 <waltermixxx> well if I can get the main gui working, the card will most likely remain in there...
Jun 08 15:48:48 <waltermixxx> but this black screen after login is driving me nuts :(
Jun 08 15:50:09 <waltermixxx> is it possible this angstrom narsissus build is not designed to be used in conjuction with a uEnv.txt file?
Jun 08 15:50:14 <waltermixxx> without it seems to work
Jun 08 15:50:24 <waltermixxx> but I was limited to 640 resolution
Jun 08 15:50:32 <waltermixxx> and unable to increase it in the gui
Jun 08 15:52:35 <waltermixxx> jason, is your comment above directed at me:tries ln -s /usr/bin/Xvfb /usr/bin/X, because I can't figure out where gdm picks up the path to X.
Jun 08 15:52:41 <waltermixxx> or was that for someone else?
Jun 08 15:56:46 <waltermixxx> is there a keyboard sequence I can put in to get back to the terminal view? when at the black screen with movable mouse cursor?    ctrl alt F1 does not get me into the terminal
Jun 08 15:58:11 <waltermixxx> i suppose i could try and ssh into it
Jun 08 15:59:45 <waltermixxx> ok I'm connected to it from my other laptop via ssh... just not sure what to try
Jun 08 16:10:10 <riskable> waltermixxx: What you messed up is the base tty settings...  So ctrl-alt-FX won't work
Jun 08 16:10:15 <riskable> You need to fix your boot line
Jun 08 16:10:36 <riskable> ...or start up X :)
Jun 08 16:19:13 <jkridner_> ugh.  the reason X wasn't starting was because Xvfb doesn't like the -verbose option. :(
Jun 08 16:19:27 <jkridner_> that was a pain in the ass.
Jun 08 16:24:44 <jkridner_> ugh.  the screen is still black, even though gdm invoked X.
Jun 08 16:25:13 <mdp> try directfb
Jun 08 16:25:25 * mdp invokes the rule of Friday
Jun 08 16:25:37 <jkridner_> why would directfb work if I don't have /dev/fb0?
Jun 08 16:25:55 <jkridner_> by 'screen', I mean vnc.
Jun 08 16:26:32 <waltermixxx> sorry had to step away
Jun 08 16:26:36 <waltermixxx> fix my boot line?
Jun 08 16:26:49 <mru> if you need vnc, you're doing something wrong
Jun 08 16:27:21 <jkridner_> by not having a display?
Jun 08 16:27:30 <mru> I fail to see the connection
Jun 08 16:27:59 <mranostay> mdp: Friday! :)
Jun 08 16:28:20 * mranostay pokes the trolls. wake up _av500_ and mru 
Jun 08 16:28:50 * jkridner_ goes to do something a bit more productive, like eat lunch.
Jun 08 16:28:50 <waltermixxx> i have a display, it's just a black screen with a moveable mouse pointer
Jun 08 16:28:59 <waltermixxx> i am able to ssh onto the beagleboard xM
Jun 08 16:29:02 <waltermixxx> from another laptop
Jun 08 16:29:15 <waltermixxx> i need to fix my uEnv.txt
Jun 08 16:30:10 <waltermixxx> Riskable,  when it starts up, I get the Angstrom splash screen
Jun 08 16:30:23 <waltermixxx> followed by the login screen ( with the onscreen keyboard)
Jun 08 16:30:26 <waltermixxx> i login
Jun 08 16:30:45 <waltermixxx> and then all I get is a black screen with a mouse pointer which I can move around with my mosue
Jun 08 16:30:46 <waltermixxx> mosue
Jun 08 16:30:49 <waltermixxx> mouse
Jun 08 16:30:51 <waltermixxx> sorry
Jun 08 16:30:52 <waltermixxx> he he
Jun 08 16:30:57 <mranostay> stop spamming!
Jun 08 16:31:01 <aholler> 1
Jun 08 16:31:02 <riskable> Ahh, so X is what's failing to start properly...  Do you have a log in /var/log/Xorg.0.log?
Jun 08 16:31:02 <aholler> 2
Jun 08 16:31:03 <aholler> 3
Jun 08 16:31:04 <aholler> 4
Jun 08 16:31:04 <aholler> 5
Jun 08 16:31:06 <_troll_> 6
Jun 08 16:31:07 <aholler> 6
Jun 08 16:31:09 <aholler> 7
Jun 08 16:31:12 <aholler> 8
Jun 08 16:31:14 <aholler> 9
Jun 08 16:31:19 <aholler> kaboom
Jun 08 16:31:25 <riskable> hehe
Jun 08 16:31:37 <waltermixxx> i will check riskable
Jun 08 16:31:45 <riskable> waltermixxx: Actually, it sounds like X is starting just fine.  What *isn't* starting is your window manager/applications
Jun 08 16:32:02 <riskable> If you see a mouse and can move it around X started just fine...  It just didn't know what to do after it started :)
Jun 08 16:32:31 <ogra_> if your issue is after login, check ~/.xsession-errors
Jun 08 16:32:52 <riskable> Typically you have a script that launches X and then launches a login manager (e.g. xdm or gdm or kdm) or you use something like startx which launches X and then launches your window manager of choice
Jun 08 16:33:17 <riskable> ogra_ is right...  Check .xsession-errors.  You might be missing something or the path to some executable is wrong
Jun 08 16:33:21 <mru> starts is just a wrapper for xinit
Jun 08 16:33:34 <mru> *startx
Jun 08 16:33:44 <riskable> mru: Right, it calls xinit and then calls whatever window manager you've got configured
Jun 08 16:34:10 <mru> no, xinit runs ~/.xinitrc
Jun 08 16:34:18 <mru> from there you typically start the wm
Jun 08 16:34:32 <waltermixxx> where do i find xsession-errors
Jun 08 16:35:35 <ogra_> in your homedir
Jun 08 16:35:39 <ogra_> its a hidden file
Jun 08 16:36:03 <ogra_> (the filename starts with a dot)
Jun 08 16:36:06 <_troll_> unix filesystems don't have a concept of hidden files
Jun 08 16:36:24 <waltermixxx> foudn it
Jun 08 16:36:29 <ogra_> ls wont show it by default
Jun 08 16:36:37 <ogra_> unless you use the -a switch
Jun 08 16:36:46 <_troll_> but that's a property of ls, not of the filesystem
Jun 08 16:37:02 <ogra_> did i say anything about filesystems ?
Jun 08 16:37:17 <Crofton|work> _troll_, is this a relative of yours: http://www.badassoftheweek.com/turgeis.html
Jun 08 16:37:27 <_troll_> you said "hidden file" without providing any other context
Jun 08 16:37:30 <Crofton|work> it is hidden from ls
Jun 08 16:37:38 <ogra_> tools wont show it, so its hidden from a user POV
Jun 08 16:37:47 <_troll_> Crofton|work: no, it is hidden _by_ ls
Jun 08 16:37:54 <waltermixxx> i have the sd card in my linux laptop
Jun 08 16:38:03 <Crofton|work> _troll_, you win
Jun 08 16:38:04 <waltermixxx> so i was able to select view hidden files when
Jun 08 16:38:11 <waltermixxx> browsing the home directory on the card
Jun 08 16:38:21 <ogra_> right
Jun 08 16:38:24 <ogra_> :)
Jun 08 16:38:25 <_troll_> any tool used for displaying directory entries may choose to apply whatever filter it pleases
Jun 08 16:40:08 <waltermixxx2> here is the error i have
Jun 08 16:40:15 <ogra_> well, the result for the enduser is the same no matter if the filesystem or the tools hide the file, they are not easily seen
Jun 08 16:40:18 <waltermixxx2> in the xsession error log
Jun 08 16:40:22 <waltermixxx2> QString&, const QString&, const QMap<QString, QVariant>&): Application sent an update but we don't seem to have it in the launcher: "application://nautilus.desktop"
Jun 08 16:40:35 <waltermixxx2> that is a copy paste from the log
Jun 08 16:41:16 <waltermixxx2> hold on
Jun 08 16:41:24 <waltermixxx2> that might be from my laptop
Jun 08 16:41:24 <aholler> no
Jun 08 16:41:28 <waltermixxx2> let me double check
Jun 08 16:41:39 <aholler> please think silent
Jun 08 16:42:05 <ogra_> well, think aloud if you like ... just not in typing :)
Jun 08 16:43:42 <waltermixxx> wrong log file
Jun 08 16:44:31 <waltermixxx> the log file from sd card  is a shortcut to home/root/ramdisk folder
Jun 08 16:44:39 <waltermixxx> which is not there
Jun 08 16:53:23 <waltermixxx> the sd card that comes with the beagleboard xM
Jun 08 16:53:31 <waltermixxx> what version of linux is it?
Jun 08 16:54:06 <waltermixxx> can I use the files in it's boot partion in my Angstrom Narcissus boot partion instead?
Jun 08 16:57:42 <Sh0rtWave> o/
Jun 08 16:58:07 <ferre> hello
Jun 08 16:58:18 <ferre> I am having trouble using the UART2 port
Jun 08 16:58:34 <ferre> I believe all pins are configured for UART2 by default
Jun 08 16:58:46 <ferre> on the xm rev c with a linaro kernel
Jun 08 16:58:52 <ferre> but it seems that i can't write on the port
Jun 08 16:59:31 <ferre> Has anyone been able to use the RX TX CTS and RTS pins?
Jun 08 17:01:37 <djlewis> another $8 dev board, STM32F0DISCOVERY
Jun 08 17:02:21 <ogra_> are 4 of them more powerful than a Pi then ?
Jun 08 17:02:48 <mru> that's a cortex-m0
Jun 08 17:03:40 <ogra_> ah
Jun 08 17:03:49 <djlewis> did I speak sacrilege?
Jun 08 17:04:07 <ogra_> sacrilege? no that was me :)
Jun 08 17:04:16 <ogra_> i said Pi :)
Jun 08 17:04:22 <mru> http://www.st.com/internet/evalboard/product/253215.jsp
Jun 08 17:04:32 <mdp> cost is the important part
Jun 08 17:04:35 <djlewis> umm pi, i'm hungry
Jun 08 17:04:42 <mdp> doesn't matter what it can do
Jun 08 17:04:51 <mru> it has FOUR LEDs!!!11!
Jun 08 17:05:02 <mdp> that crushes the launchpad now...wow!
Jun 08 17:05:45 <djlewis> like one needs a led to show it is plugged into usb
Jun 08 17:09:41 <icota> might as well put this here: http://e2e.ti.com/support/dsp/sitara_arm174_microprocessors/f/791/t/193860.aspx
Jun 08 17:14:12 <mdp> djlewis, it is, however, a red/green led…so don't hate on it
Jun 08 17:14:34 <djlewis> if it were blue then i'd hate it
Jun 08 17:15:44 <mdp> I know that's why you can't even speak of LD4
Jun 08 17:16:53 * djlewis shutters
Jun 08 17:26:04 <riskable> Great:  I've got my Beaglebone powered off of a breadboard power rail.  Thank you P9 pin 5!
Jun 08 17:28:11 <riskable> What is everyone else using as semi-permanent ways to connect things to the pins on the Beaglebone?  I've got some male headers that rise up into little pins I can connect to with a wire wrap tool but I don't want the pin exposed like that
Jun 08 17:28:29 <Sh0rtWave> Aight, completely weird problem
Jun 08 17:28:32 <jeshwanth> hello
Jun 08 17:28:38 <jeshwanth> anybody there ?
Jun 08 17:28:44 * riskable guesses he could just wrap the exposed part of the pin with an insulator (liquid electrical tape)
Jun 08 17:28:55 <riskable> jeshwanth: Lots of people here today I think
Jun 08 17:28:59 <Sh0rtWave> Got my xM wired up, got X running on my mac, xhost+ FTW, got gnome-terminal running from the beagleboard using my mac as the display, and oddly
Jun 08 17:29:06 <Sh0rtWave> It's like my keyboard map is 10 kinds of screwed
Jun 08 17:29:31 <mranostay> nobody is here
Jun 08 17:30:30 <jeshwanth> oh cool, some day before mt friend ugrrades the beaglebone amstrong, after that the sys interface for pwm is not there so where can I get it ?
Jun 08 17:31:10 <riskable> koen: I noticed a minor error in http://beagleboard.org/static/BONESRM_latest.pdf System Reference Manual...  The table numbers are off.  For example on page 76, "The  Table 19 describes the voltages from the main board..."  the correct table is number 20, not 19.  It looks like the table numbering is off all the way through the manual
Jun 08 17:31:28 <riskable> jeshwanth: modprobe pwm
Jun 08 17:32:46 <jeshwanth> @riskable oh ya I will try this :) ... I am new to device driver n stuffs :) ll try :)
Jun 08 17:33:37 <Sh0rtWave> Ah, looks like I fixed it
Jun 08 17:33:39 <Sh0rtWave> Sexcellent
Jun 08 17:33:40 <riskable> jeshwanth: No problem.  I'm new to the Beaglebone (and electronics in general--mostly =) but I'm an old hat when it comes to Unix/Linux :)
Jun 08 17:35:18 <Dhiraj_> hi jkridner_, I have read throught the link you told me to refer yesterday, it was helpfull. but as you said we will not be requring mtd drivers i did not get that part. the link you pointed to http://processors.wiki.ti.com/index.php/AM335x_NAND_Driver's_Guide advisied to used mtd drivers.
Jun 08 17:36:56 <Sh0rtWave> Advice for the unwary: Unless you are running a full XDMCP config, do NOT run the gnome-control-center on a remote X session to a mac and try to configure anything. It will toast your X keybindings on XQuartz.
Jun 08 17:38:16 <aholler> most apple users are unwary ;)
Jun 08 17:39:18 <Sh0rtWave> I'm not your average apple user
Jun 08 17:44:20 <spow> hey, someone here working at TI ?
Jun 08 17:44:46 <mranostay> not on a Friday
Jun 08 17:52:49 <Crofton> no one here works
Jun 08 17:56:35 * djlewis is working at getting off early
Jun 08 18:26:57 <Sh0rtWave> Right so
Jun 08 18:27:04 <Sh0rtWave> I found the kernel module for the leopard imaging board
Jun 08 18:27:10 <Sh0rtWave> but I can't seem to get it to load
Jun 08 18:27:20 <Sh0rtWave> I presume I'm doing something wrong and that there's not something hugely wrong with the board
Jun 08 18:28:12 <djlewis> nine times of ten, its the loose screws behind the keyboard ;)
Jun 08 18:29:41 <Russ> are you sure you don't mean in front of the keyboard?
Jun 08 18:29:55 <djlewis> hmmm
Jun 08 18:29:59 <riskable> I just googled "leopard imaging board"...  Cool!  Anything like that for the Beaglebone?
Jun 08 18:30:23 <riskable> From the perspective of the computer, it is behind the keyboard :)
Jun 08 18:34:22 <mdp> it's hard to imagine that there's not ten capes in design with similar sensors
Jun 08 18:35:59 <ds2> Hmmmm
Jun 08 18:36:18 <mdp> except for the lack of on chip input
Jun 08 18:43:20 <riskable> One can always just hook up a USB webcam to a Beaglebone I guess
Jun 08 18:44:07 <mdp> I hear that's one thing that works via USB
Jun 08 18:44:56 <djlewis> mdp: no intermittent issues?
Jun 08 18:46:01 <mdp> from my experience, I would have doubt that it works as well as claimed
Jun 08 18:46:36 <ds2> works or not is overrated
Jun 08 18:46:37 <mdp> but I can't counter the shouts of joy over "UVC works!" ;)
Jun 08 18:47:28 <mdp> 90% of my experience with this is on am335x's close [usb] cousin, am180x
Jun 08 18:47:30 <riskable> Interesting:  If you're powering your Beaglebone via VDD_5V and you plug in the USB client cable it will continue to work.  However, if you subsequently unplug that USB cable your Beaglebone will lose power for a moment and reboot
Jun 08 18:47:37 <djlewis> my older Logitech gspca webcams were pretty steady on the BB
Jun 08 18:47:48 <djlewis> If one leaves OpenCV out of the equation
Jun 08 18:48:01 <ds2> gspca cams can get iffy in full streaming mode
Jun 08 18:48:02 <mru> but how do you detect green without opencv?
Jun 08 18:48:30 <djlewis> :)
Jun 08 18:48:40 <mranostay> mru: troll much?
Jun 08 18:48:48 <mru> only a little
Jun 08 18:48:52 <mdp> ds2, I have to remind myself that "works" in the beaglebone world means it operated as expected for a couple minutes…doesn't mean production ready :)
Jun 08 18:48:53 <mru> and mostly on fridays
Jun 08 18:48:59 <mru> logical fridays
Jun 08 18:49:17 <djlewis> and any other day as is needed or not
Jun 08 18:49:21 <ds2> mdp: :)
Jun 08 18:49:35 <mru> a logical friday can be mapped to any physical day
Jun 08 18:49:36 <ds2> I'd like to extend to long enough to put together a youtube video ;)
Jun 08 18:49:38 <riskable> I have an old Logitech webcam here...  I'm going to plug it in and see how it goes
Jun 08 18:49:39 <djlewis> right
Jun 08 18:49:55 <djlewis> everyone under their desk, NOW!!!
Jun 08 18:50:00 <mdp> ds2, you just need a good video production staff to loop it seamlessly
Jun 08 18:50:27 <ds2> now I see where I should be improving!
Jun 08 18:50:45 <mru> we need better video editors
Jun 08 18:50:55 <mdp> ds2, I'm here to help..sometimes in unexpected ways
Jun 08 18:50:56 <djlewis> better video might help too
Jun 08 18:51:09 <mdp> mru, people or tools?
Jun 08 18:51:15 <mdp> mru, or are they one in the same?
Jun 08 18:51:16 <mru> I hear they're doing cool stuff over at novacut
Jun 08 18:52:31 <djlewis> four laptops with virus removal apps running stretched out before me
Jun 08 18:52:51 <mdp> cool, hadn't heard of it…I had some horrible experiences with common 1080i mpeg2-ts in some other foss editors
Jun 08 18:53:18 <mru> it's still very much work in progress
Jun 08 18:53:26 <mru> but the guys seem to know what they're doing
Jun 08 18:53:32 <mranostay> mru: one to many mapping?
Jun 08 18:53:49 <mru> whatever is necessary
Jun 08 18:53:55 <ds2> mru: hey... is the beaglewall code on a repo somewhere?
Jun 08 18:54:05 <mru> which code?
Jun 08 18:54:08 <mdp> hrm, a kickstarter project…that association is starting to turn my brain off
Jun 08 18:54:14 <ds2> mru: all of it
Jun 08 18:54:15 <djlewis> customer griping about me leaving a voice mail on his phone cuz he doesnt check his vmail
Jun 08 18:54:38 <mru> mdp: they're doing a kickstarter run, but that's not how they started iirc
Jun 08 18:54:49 <mdp> ok, good
Jun 08 18:55:00 <mru> they actually have stuff that works _now_
Jun 08 18:55:12 <mdp> collaborative video editing…oh yes, that's a great feature
Jun 08 18:55:30 <nemik> http://www.beagleface.com/beaglewall/
Jun 08 18:56:42 <ds2> mru: trying to figure out hard it is to show exactly every other frame on 2 beagles (stereo, even frames for left, odd frames for right)
Jun 08 18:56:56 <mru> the omapfbplay code is on my git
Jun 08 18:57:04 <mru> I don't know where koen's scripts are
Jun 08 18:57:23 <djlewis> ooh stereo
Jun 08 18:57:26 <ds2> the sync/node stuff is in koen's scripts, isn't it?
Jun 08 18:57:35 * mru demands 5.1 surround video
Jun 08 18:57:53 <djlewis> now that would be cool
Jun 08 18:58:05 <mru> ds2: the frame sync code is part of omapfbplay
Jun 08 18:58:28 <mru> koen made the scripts to start it up on all the beagles
Jun 08 18:58:40 <djlewis> submersive rather than emersive
Jun 08 18:59:17 <mru> years ago someone did a cube with video projected on all sides
Jun 08 18:59:19 <mru> from the outside
Jun 08 18:59:28 <mru> the viewer was on the inside
Jun 08 18:59:41 <djlewis> a canadian company
Jun 08 18:59:57 <mru> probably been done more than once
Jun 08 19:00:02 <koen> it's just a combination of ssh, avahi and killall
Jun 08 19:00:02 <djlewis> yeah
Jun 08 19:00:09 <mru> the one I remember was back when sgi was hot
Jun 08 19:00:37 <djlewis> I installed a SGI refrigerator and single projection screen
Jun 08 19:00:39 <mru> well, my sgi machine still runs hot...
Jun 08 19:02:08 <jkridner_> Dhiraj_: did you look at the gumstix example?
Jun 08 19:08:40 <jkridner_> Dhiraj_: did you look at http://elinux.org/images/7/7b/Omap3-fpga.pdf ?
Jun 08 19:12:57 <ds2> oh... then all I care about is omapfbplay
Jun 08 19:13:22 <ds2> the beagles need to enter into the 3rd dimension!
Jun 08 19:16:20 <mdp> RPi will leapfrog to 4d
Jun 08 19:17:03 <ds2> but that requires the 4D accelerator block
Jun 08 19:19:43 <dm8tbr> there's a binary blob for that, I'm sure...
Jun 08 19:22:11 <waltermixxx> joining you live from my beagleboard xM
Jun 08 19:23:40 <waltermixxx> using one of the Angstrom distribution demo location (Angstrom Ti Gnome image 2012.01)
Jun 08 19:23:54 <waltermixxx> at 1280 x 720
Jun 08 19:24:42 <waltermixxx> currently building one on the agnastrum Narcissus site as well :) so I have a couple sd cards working now...
Jun 08 19:25:00 <waltermixxx> then the fun begins.... turning L.E.D.'s on and off via web page...
Jun 08 19:25:01 <waltermixxx> :)
Jun 08 19:26:17 <djlewis> cool, I have a little app for my rabbit rcm4k / rcm3k that does that :)
Jun 08 19:26:34 <djlewis> easier as there is no os :)
Jun 08 19:26:39 <djlewis> or fs to some
Jun 08 19:27:04 <mdp> ds2, we can probably add one in the fpga cape though…empire strikes back
Jun 08 19:27:11 <waltermixxx> i suspect i will need to use perl, i was hoping to mess around with Cloud9
Jun 08 19:27:20 <waltermixxx> sorry not pearl, I meant python
Jun 08 19:27:38 <waltermixxx> i did an opkg upgrade cloud9,
Jun 08 19:27:48 <waltermixxx> and now it's running version 6.0.r0
Jun 08 19:27:58 <waltermixxx> no built in examples...
Jun 08 19:29:46 <djlewis> sakoman_: hi, and your site seems extra slow today.
Jun 08 19:31:01 <waltermixxx> hoping to get my trainer xM board in soon so I can start messing about :)
Jun 08 19:31:09 <sakoman_> djlewis: you are correct.  someone seems to be hammering on the site right now.  I'll see if I can boot them
Jun 08 19:34:12 <aholler> someone should build a lol-cape for the led-freaks
Jun 08 19:48:18 <djlewis> I had to have a Mtn Dew chaser after that Coke
Jun 08 19:50:14 <mranostay> aholler: that is a weekend eagle project at worse :)
Jun 08 19:52:39 <aholler> mranostay: build one for the launchpad too, no need for a beagle ;)
Jun 08 19:55:29 <mranostay> i have other projects atm :)
Jun 08 19:56:27 <djlewis> sakoman_: now its gone
Jun 08 20:01:48 <riskable> BTW:  I got my Logitech UVC video webcam working on the Beaglebone...  Works great
Jun 08 20:02:07 <mdp> heh
Jun 08 20:03:55 <mranostay> can't wait till #beagle is in the news because of someone using a webcam for evil purposes
Jun 08 20:04:13 <mru> they have non-evil purposes?
Jun 08 20:04:35 <mranostay> mru: don't you live in London?
Jun 08 20:04:41 <mru> no
Jun 08 20:06:21 <riskable> Here's a screenshot I just took using mplayer on the Beaglebone:  http://imgur.com/OWGHe
Jun 08 20:06:41 <riskable> For reference, here's the command I used:  mplayer -vf screenshot tv:// -tv driver=v4l2:width=640:height=480:device=/dev/video0:fps=2:outfmt=mjpg # Press 's' to take a screenshot
Jun 08 20:07:04 <sakoman_> djlewis: should be back now
Jun 08 20:07:05 <riskable> Now I'm wondering how much power this webcam takes
Jun 08 20:08:39 <djlewis> sakoman_: much better now. Was it a bad guy?
Jun 08 20:09:16 <sakoman_> djlewis: probably a bad bot
Jun 08 20:25:20 <ipersite> hi all
Jun 08 20:29:57 <ipersite> nobody?
Jun 08 20:31:57 <ipersite> what about the adxl345 on the beaglebone? it doesn't work.
Jun 08 20:32:44 <ipersite> it's connected, i2cdetect detects it... but i have IRQ problems when loading driver
Jun 08 20:34:28 <riskable> Getting a strange error running bitbake:  ERROR: ExpansionError during parsing /storage/beaglebone/oe-build-core/sources/openembedded-core/meta/recipes-kernel/linux/linux-yocto_3.2.bb: Failure expanding variable SRCPV, expression was ${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError: Fetcher failure for URL: 'git://git.yoctoproject.org/linux-yocto-3.2;protocol=git;bareclone=1;branch=standard/default/base,
Jun 08 20:34:28 <riskable> meta;name=machine,meta'. The command git ls-remote git://git.yoctoproject.org/linux-yocto-3.2 ee78519365bdb25287703bbc31c06b193263c654l gave empty output unexpectedly
Jun 08 20:35:02 <riskable> Sure enough, "git ls-remote git://git.yoctoproject.org/linux-yocto-3.2 ee78519365bdb25287703bbc31c06b193263c654l" *does* return an empty result...  But why does the entirety of bitbake crap out when that happens?
Jun 08 20:43:00 <ipersite> riskable: because bitbake needs something from that repo
Jun 08 20:43:09 <riskable> ipersite: How do I fix this?
Jun 08 20:43:31 <ipersite> riskable: did you tried to do a git pull in your setup-scripts directory?
Jun 08 20:43:44 <ipersite> maybe oebb.sh is old version
Jun 08 20:43:46 <riskable> ipersite: Yep, Already up-to-date
Jun 08 20:44:14 <ipersite> riskable: I don't know... Personally I would do a complete clean up
Jun 08 20:44:30 <riskable> I think there's a problem with the git repo on the other end...  But that's out of my control.  I want to know how I can get bitbake to just skip that recipe without having to remove the recipe
Jun 08 20:44:37 <ipersite> remember, oebb creates also a directory in your home
Jun 08 20:44:41 <ipersite> (.oe)
Jun 08 20:45:19 <riskable> Forget it, I just moved the recipe in question to a temporary location while the Yocto project fixes their repo
Jun 08 20:45:45 <ipersite> riskable: does it work?
Jun 08 20:46:20 <riskable> Yep
Jun 08 20:46:28 <riskable> 'bitbake -s' works now (which was all I was trying to do)
Jun 08 20:48:15 <ipersite> riskable: fine... are you expert in i2c? i have a problem with an accelerometer
Jun 08 20:48:26 <riskable> ipersite: Hah, I know very little about i2c
Jun 08 20:48:48 <ipersite> riskable: ok no problem :)
Jun 08 20:56:39 <djlewis> ipersite: what specificallly is the prob?
Jun 08 21:03:03 <ipersite> djlewis: adxl345, when i initialize it dmesg writes about IRQ problem
Jun 08 21:03:16 <ipersite> it's an accelerometer
Jun 08 21:05:01 <djlewis> Oh, I was thinking it might be specific to reading the data or recognizing the device.
Jun 08 21:05:25 <djlewis> Sounds kernel related
Jun 08 21:05:31 <djlewis> + driver
Jun 08 21:06:11 <djlewis> lots have it working on beagleboards
Jun 08 21:06:16 <Sh0rtWave> Which driver should I use for the 5M camera board?
Jun 08 21:08:01 <ds2> the appropriate one of course!
Jun 08 21:08:49 <djlewis> wise man or wise arse ;)
Jun 08 21:09:21 <Sh0rtWave> Well sure
Jun 08 21:09:47 <Sh0rtWave> I'm presuming tho, since the board is slightly different, that there's some extra stuff I have to do to get this particular one up and running, no?
Jun 08 21:10:01 <Sh0rtWave> Anyone know if the kernel module is available via ipkg?
Jun 08 21:10:15 <ds2> build from source and get exactly what you want
Jun 08 21:11:34 <Sh0rtWave> of course you'll say that.
Jun 08 21:14:33 <ds2> why should you not build kernels from source?
Jun 08 21:14:37 <ds2> it is next to trivial
Jun 08 21:21:28 <ipersite> sorry, i was afk
Jun 08 21:22:24 <ipersite> djlewis: what i need to do?
Jun 08 21:22:36 <ipersite> (if you know)
Jun 08 21:36:09 <djlewis> most kernels come with i2c support as it is required for certain features
Jun 08 21:36:53 <djlewis> ipersite: do we know what you are working with? board, fs etc?
Jun 08 21:37:45 <ipersite> i wrote it before... but nobody answered! anyway, beaglebone, angstrom dist...
Jun 08 21:38:36 <djlewis> ipersite: if you dont have anthing connected to your beaglebone and you use the i2c tools does it work?
Jun 08 21:38:51 <djlewis> anything as in the adxl345
Jun 08 21:39:04 <ipersite> djlewis: what do you mean? other sensors works well with the 92c
Jun 08 21:39:08 <ipersite> *i2c
Jun 08 21:39:08 <ds2> why is TI working so hard to take every bit of usefulness out of their website? why why why?!?
Jun 08 21:39:55 <djlewis> ipersite: if other sensors are working well then there should be no reason for a irq error with the 345
Jun 08 21:40:18 <ipersite> djlewis: that's what i thought too!
Jun 08 21:40:45 <ipersite> but when i "echo adxl345 0x1d > new_device"
Jun 08 21:40:55 <djlewis> so perhaps your adxl345 is damaged and the driver in the kernel can not properly deal with what the adxl is handing it.
Jun 08 21:41:19 <ds2> are you sure the adxl345 isn't wedging the bus?
Jun 08 21:41:28 <ds2> or that your pull ups are not AFU?
Jun 08 21:41:30 <djlewis> ooh wedgies, hate them
Jun 08 21:42:05 <ipersite> ds2: what do you mean? sorry
Jun 08 21:42:16 <djlewis> ipersite: have you put a scope on the lines to verify whats happening?
Jun 08 21:42:29 <ds2> what do you mean what do I mean?
Jun 08 21:42:29 <ipersite> djlewis: no.
Jun 08 21:42:35 <ds2> I meant exactly what I said
Jun 08 21:42:40 <ds2> is the adxl345 wedging the bus
Jun 08 21:43:34 <ds2> if the i2c block is complaining, checking to see if the bus is wedge is a good first step
Jun 08 21:43:37 <ipersite> ds2: i'll check
Jun 08 21:43:47 <ipersite> immediately
Jun 08 21:44:21 <ipersite> in order to check it, is it correct to try reading other sensor on the same bus?
Jun 08 21:46:05 <ipersite> ds2: the bus doesn't seem to be wedged
Jun 08 21:46:14 <ds2> okay
Jun 08 21:46:20 <ds2> what pull ups do you have on there?
Jun 08 21:46:56 <ipersite> (double checking this...)
Jun 08 21:48:41 <ipersite> ds2: pin muxing is set to have pull ups on, nothing else
Jun 08 21:50:41 <ds2> ipersite: the internal pull ups are sometimes too weak. try it with a hard pull up
Jun 08 21:50:51 <ds2> like maybe 4K7 or so
Jun 08 21:51:14 <ipersite> ds2: and should i disable the internal one or should i keep them on?
Jun 08 21:51:36 <djlewis> ds2: good call, my beagleboard internals were not enough
Jun 08 21:51:40 <ds2> turning it off is best but you can leave it
Jun 08 21:51:48 <djlewis> got random action from i2c device.
Jun 08 21:52:22 <ds2> Rint || Rext ~= for Rext << Rint
Jun 08 21:52:35 <ipersite> ds2: do you have one adxl345?
Jun 08 21:52:55 <ipersite> because the driver is the same for both adxl345 and adxl346
Jun 08 21:53:07 <ds2> ipersite: not that particular chip at the moment... but I do deal with a lot of different sensor chips
Jun 08 21:53:40 <ipersite> if i try to initialize it with the name "adxl345" dmesg reports "i2c i2c-3: new_device: Instantiated device adxl345 at 0x1d"
Jun 08 21:54:02 <ipersite> but the driver doesn't get loaded
Jun 08 21:54:19 <ds2> a name is just a name
Jun 08 21:54:30 <ds2> you can call it whatever you want as long as all parties agree
Jun 08 21:55:07 <ipersite> yes but if i try with adxl34x (the driver source code calls them adxl34x) i got irq error
Jun 08 21:55:20 <ds2> is the IRQ being used by something else?
Jun 08 21:55:50 <ipersite> how can i check if is it?
Jun 08 21:56:06 <ipersite> i mean, other sensors work well with the bus.
Jun 08 21:56:08 <ds2> are you passing a valid IRQ in your platform data?
Jun 08 21:56:08 <ds2> is there too much air in the mind hand interface?
Jun 08 21:56:49 <ds2> use the organic inspection sensor along with appropriate applications of dexterity?
Jun 08 21:57:49 <ipersite> ds2: i didn't get what you said.
Jun 08 21:59:24 <ipersite> with other i2c peripherals is easy: you install the kernel module (or compile it yourself) insmod it, and it works as soon as you add the device.
Jun 08 22:00:21 <ipersite> for example the common bmp085 pressure/temp sensor, you insmod the bmp085 module, you do an echo ... > new_device and it works!
Jun 08 22:00:34 <ds2> read how to define a platform driver.
Jun 08 22:00:45 <ds2> finding out where to read it is left as an exercise for the student.
Jun 08 22:01:52 <ipersite> bah
Jun 08 22:02:35 <mranostay> mythos: your name makes me think of beer
Jun 08 22:03:06 <mythos> hmm... mranostay, is that good or bad?
Jun 08 22:03:23 <djlewis> ipersite: if beaglebone u-boot supports i2c then you can test it there as well.
Jun 08 22:04:02 <ipersite> djlewis: thank you. can you please tell me how?
Jun 08 22:04:28 <djlewis> ya gotta study and learn young skywalker :)
Jun 08 22:05:29 <mranostay> mythos: http://en.wikipedia.org/wiki/Mythos_Brewery
Jun 08 22:05:30 <djlewis> hint: if you get into the u-boot prompt then you can type help
Jun 08 22:06:17 <ipersite> ok fine. that's what i needed to know.
Jun 08 22:06:22 <mythos> mranostay, that doesn't answer the question? ;)
Jun 08 22:06:26 <ipersite> i'll test it now.
Jun 08 22:07:37 <mranostay> i'm a avid beer lover :)
Jun 08 22:08:28 <mythos> you are flattering me ;)
Jun 08 22:14:14 <ipersite> djlewis: ok i can probe bus 0
Jun 08 22:14:31 <ipersite> but this isn't correct. i want to probe bus 2.
Jun 08 22:14:51 <ipersite> and if i try to probe other buses it says
Jun 08 22:14:51 <djlewis> logical numbers 0 1 2
Jun 08 22:15:03 <ipersite> Valid chip addresses: 00 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F 50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70 71 72 73 74 75 76 77 78 79 7A 7B 7C 7D 7E 7F
Jun 08 22:15:34 <djlewis> you have to set each bus then probe it
Jun 08 22:15:57 <ipersite> so i2c dev 1 ... then i2c probe
Jun 08 22:16:05 <ipersite> and this is the result
Jun 08 22:16:09 <djlewis> iirc, right
Jun 08 22:17:24 <djlewis> ipersite: are you looking at http://elinux.org/BeagleBoard_Trainer_Nunchuk
Jun 08 22:17:35 <djlewis> toward the end?
Jun 08 22:17:48 <ipersite> djlewis: i'll take a look
Jun 08 22:18:13 <djlewis> step 5
Jun 08 22:19:26 <ipersite> djlewis: yes. if i try to probe other buses than the number 0 i got the error i wrote before
Jun 08 22:19:28 <djlewis> ipersite: unless they changed u-boot for beaglebone then i expect it would be the same results
Jun 08 22:19:58 <djlewis> I have not used i2c on the bone yet.
Jun 08 22:20:29 <ipersite> U-Boot# i2c dev 0
Jun 08 22:20:31 <ipersite> Setting bus to 0
Jun 08 22:20:33 <ipersite> U-Boot# i2c probe
Jun 08 22:20:35 <ipersite> Valid chip addresses: 24 50
Jun 08 22:20:37 <ipersite> U-Boot# i2c dev 1
Jun 08 22:20:39 <ipersite> Setting bus to 1
Jun 08 22:20:41 <ipersite> U-Boot# i2c probe
Jun 08 22:20:43 <ipersite> Valid chip addresses: 00 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F 50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70 71 72 73 74 75 76 77 78 79 7A 7B 7C 7D 7E 7F
Jun 08 22:20:45 <ipersite> sorry for the long message.
Jun 08 22:20:51 <djlewis> ipersite: the idea was that if it works at this level then it is software above this level.
Jun 08 22:21:15 <djlewis> well, its software and ahrdware here too but different as u-boot does not stay resident
Jun 08 22:21:39 <djlewis> you are not getting the i2c-1,2 enabled
Jun 08 22:22:01 <ipersite> but they're enabled later in the kernel maybe
Jun 08 22:22:18 <ipersite> because they work.
Jun 08 22:22:23 <djlewis> u-boot should enable them unless someone got lazy coding u-boot for the bone
Jun 08 22:23:32 <djlewis> in previous boards i2c-2 was used for add on boards. not needed in the bone. so they must have left this fine tool out.
Jun 08 22:23:41 <djlewis> ds2?
Jun 08 22:23:57 <djlewis> ds2: ?
Jun 08 22:24:51 <djlewis> ipersite: sorry for the wild goose chase. You are back to debugging in the fs.
Jun 08 22:25:42 <djlewis> and time for me to head ome... :)
Jun 08 22:25:47 <djlewis> +h
Jun 08 22:26:20 <ipersite> the real problem is... adxl345 isn't working yet. thank you for helping me out
Jun 08 22:26:41 <djlewis> may the force be with you :)
Jun 08 22:28:07 <ipersite> djlewis: thanks :)
Jun 08 22:28:36 <djlewis> ipersite: follow the leads ds2 left you with
Jun 09 00:00:07 <riskable> When making a .bb file is there some variable where it is customary to point to the official home of the package?
Jun 09 00:02:14 <mranostay> *ahem* #yocto
Jun 09 00:07:08 <ds2> Yuck Doh
Jun 09 00:08:05 <ds2> place that under the sink to protect kids ;)
Jun 09 01:17:28 <riskable> Anyone know which ipk contains stdio.h (basic development files)?
Jun 09 01:17:54 <xxiao> native sdk?
Jun 09 01:19:10 <riskable> What's the name of that ipk though?
Jun 09 01:19:30 <xxiao> don't know, never used that
Jun 09 01:20:03 <riskable> I need to know what I need to bitbake, actually
Jun 09 01:20:26 <riskable> pyzmq is looking for stdio.h when it runs setup.py and I can't figure out the other dependencies with out it
Jun 09 01:20:29 <xxiao> for stdio.h i guess you want to compile something on the target?
Jun 09 01:21:12 <riskable> Yeah
Jun 09 01:21:23 <riskable> Well, I probably need glibc-dev or something like that
Jun 09 01:21:40 <xxiao> you need build native sdk i think
Jun 09 01:28:52 <riskable> I figured it out:  The setup.py had a bad default include_dir
Jun 09 01:33:52 <Borillion> anyone wanted to know for their info, CONFIG_EXPERT doesn't exist in kernel lower than 2.6.37 kernel for rowboat.
Jun 09 01:34:19 <xxiao> rowboat, is it android
Jun 09 01:35:18 <Borillion> yes
Jun 09 01:35:48 <Borillion> had a big problem with it the last couple days, its good to know its not in there
Jun 09 01:35:56 <xxiao> i think the EXPERT thing in the past it's called experimental?
Jun 09 01:37:09 <ds2> isn't it equiv to CONFIG_MORON=n?
Jun 09 01:38:34 <xxiao> ah...it's the old CONFIG_EMBEDDED, odd
Jun 09 01:38:36 <Borillion> I was told its config_embedded
Jun 09 01:38:43 <Borillion> yea its weird
Jun 09 01:40:01 <Borillion> can I use any android kernel thats greater than 2.6.37 thats for the omap3 to get the feature? Or is it harder than that.
Jun 09 01:40:28 <xxiao> why , for old kernel just use CONFIG_EMBEDDED
Jun 09 01:40:40 <xxiao> this is a rename, not a new feature per se
Jun 09 01:41:00 <Borillion> Well I have to modify the patch don't I?
Jun 09 01:41:16 <Borillion> its looking for expert to be enabled
Jun 09 01:41:36 <Borillion> http://code.google.com/p/android-x86/issues/attachmentText?id=670&aid=6700000000&name=0001-Faytech-Automotive-Touchscreen&token=zQgZfGL_dzonzJmnufMPqwSxCIE%3A1339054619872
Jun 09 01:43:18 <xxiao> this is a small patch, i will just manually port it
Jun 09 01:45:44 <Borillion> can I just delete "if EXPERT" to fix it?
Jun 09 01:47:08 <Borillion> xxiao, LOL I have never ported
Jun 09 01:48:41 <xxiao> :) no you can't
Jun 09 01:48:51 <xxiao> it's not hard, but a little more involved than that
Jun 09 01:49:46 <xxiao> basically you want to use this patch on top of rowboat's 2.6.37 kernel?
Jun 09 01:50:15 <Borillion> yea
Jun 09 01:51:38 <xxiao> i'm syncing my rowboat repo, it may take a while, haven't done that for 2 months
Jun 09 01:51:45 <xxiao> after that i can port it
Jun 09 01:51:57 <xxiao> what board is this for
Jun 09 01:53:02 <Borillion> the beagle xm
Jun 09 01:54:12 <Borillion> is it all kernels that have this issue or just specific to android <= 2.6.37
Jun 09 02:03:50 <xxiao> Borillion: i think you're about right
Jun 09 02:03:57 <xxiao> EXPERT is added after 2.6.37 time frame
Jun 09 02:10:32 <riskable> Man, I got zeromq to compile and install in no time yet pyzmq is giving me hell
Jun 09 02:36:12 <xxiao> Borillion: just finish checking out rowboat, which manifest are you using?
Jun 09 02:41:42 <xxiao> Borillion: ...r u there
Jun 09 02:51:26 <KeatonT> Lots of work to be done.
**** ENDING LOGGING AT Sat Jun 09 02:59:59 2012