**** BEGIN LOGGING AT Fri Apr 13 02:59:59 2012 Apr 13 03:10:07 prpplague: is the firmware bugs as bad as some of the lists suggests? Apr 13 03:10:44 ds2: yea there have been a bunch of little "bugs" Apr 13 03:12:33 prpplague: but does it do the basic scope functions (by scope I mean analog scope) Apr 13 03:12:39 or is even that buggy? Apr 13 03:12:45 ds2: yea it does the basics Apr 13 03:12:56 ds2: if you just want to do some low speed stuff Apr 13 03:13:11 what are you calling low speed? Apr 13 03:13:29 1KHz? Apr 13 03:13:32 1MHz? Apr 13 03:16:11 it says what speed it goes up to Apr 13 03:16:24 it says what sample rate Apr 13 03:16:25 I've heard that for just a little more you can get a far better o-scope Apr 13 03:16:42 you mean the Rigol stuff? Apr 13 03:16:51 yea Apr 13 03:17:13 it is about 1.7x more but it does get you into a true 100MHz territory Apr 13 03:17:25 and you give up the signal generator and the 2 digital channels Apr 13 03:18:02 a signal generator is cheap Apr 13 03:18:51 it is still 30-40 Apr 13 03:19:20 do you know anyone who might have one you can play with? Apr 13 03:19:37 ds2: 500KHz operations are solid Apr 13 03:19:40 you could also try for an analog o-scope off ebay for around the same price which would get you a ton more speed Apr 13 03:20:06 isaacbw: this is to supplement a 100MHz analog scope Apr 13 03:20:13 oh Apr 13 03:20:15 the analog scope is a suitcase Apr 13 03:20:22 they are super hefty Apr 13 03:20:29 well, then the portability might be nice Apr 13 03:20:44 I've never actually used one, I've just heard people whining about them Apr 13 03:21:27 i did see some firmware complaints Apr 13 03:23:27 for $150 + shipping, it looks temping Apr 13 03:24:41 ds2: get a das_oszi instead, hehe Apr 13 03:24:47 ds2: i need some hacking help Apr 13 03:24:53 das_oszi? Apr 13 03:24:55 got a link? Apr 13 03:25:28 http://elinux.org/Das_Oszi Apr 13 03:27:07 http://www.ebay.com/itm/220906916160?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1439.l2649 Apr 13 03:27:33 ds2: even if you aren't going to hack, just doing the firmware upgrade drives it to 200MHz support Apr 13 03:28:52 looking for a nonebay source Apr 13 03:29:10 ds2: they are pretty available Apr 13 03:29:24 under which name? nothing much under protek so far Apr 13 03:30:08 ds2: for the US it is the Hantek Apr 13 03:30:11 ds2: DSO5062 Apr 13 03:30:15 ds2: or DSO5062B Apr 13 03:30:26 http://www.web-tronics.com/dso5062b.html Apr 13 03:31:53 are you saying any of those can do 200MHz? Apr 13 03:32:08 ds2: yea Apr 13 03:32:14 ds2: only difference is the firmware Apr 13 03:32:40 http://www.eevblog.com/forum/general-chat/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg21170/#msg21170 Apr 13 03:33:05 it looks pretty nice Apr 13 03:33:58 ds2: i have barebox and 3.3 mainline booting on it Apr 13 03:35:41 booting but do you have scope functionality? Apr 13 03:36:16 it does need to be able to do something besides an expensive doorstop :) Apr 13 03:36:31 ds2: booting, only three days of work on it so far, give me time Apr 13 03:36:44 also, do you know if anyone has Linux equivalent of the desktop sw? Apr 13 03:36:59 oh.. okay..thought you got lucky and userland just "worked" Apr 13 03:37:32 ds2: yea the sigrok folks have the protocol mapped out Apr 13 03:37:39 ds2: and there are range of utils and such Apr 13 03:38:42 hmmm Apr 13 03:38:52 sigrok.org Apr 13 03:39:49 that would make it useable as a signal collection platform Apr 13 03:40:13 yea Apr 13 03:41:17 probally will get that then Apr 13 03:42:19 prpplague: what kind of help do you need? Apr 13 03:42:52 ds2: general kernel stuff atm Apr 13 03:43:02 ds2: later we need to hack some fpga driver Apr 13 03:43:04 ah.. stuff I can actually help with :) Apr 13 03:44:05 I wonder how fast can the USB host go Apr 13 03:44:50 slap on one of those $20 USB RF front ends and get real Spec.An functionality Apr 13 05:42:15 just plugged in a 2GB hd, such a satisfying startup sound Apr 13 06:12:14 2gb? where did you find that? Apr 13 06:18:38 i once played diablo-2 on 2gb magnetic HD :) Apr 13 06:44:05 aholler, time to clean out the closet Apr 13 06:45:51 and many drives with exciting death noises Apr 13 06:46:05 <_av500_> and many drives to smash to pieces Apr 13 06:46:13 <_av500_> before throwing them away Apr 13 06:46:32 well, the one that makes the zoop noise can't exactly be zeroized Apr 13 06:46:47 <_av500_> hence the smash to pieces Apr 13 06:46:57 8 drives to smash Apr 13 06:47:14 <_av500_> I usually extract the magnets Apr 13 06:47:25 <_av500_> makes for unremovable fridge magnets :) Apr 13 06:47:37 dangerous to have around when you have a dog that likes to eat random things Apr 13 06:48:05 <_av500_> well, stick them up high onto something magnetic Apr 13 06:48:33 maybe I can use the magnets to zeroize the platters Apr 13 06:49:08 * Russ compares Tc (curie point) to his oven's max temp Apr 13 06:49:13 ever tried to smash a drive into pieces? Apr 13 06:49:35 <_av500_> aholler: well, a hammer to deform the platters is enough Apr 13 06:50:00 it's unbelievable hard to destroy them. Apr 13 06:51:14 hmm, maybe I need to start collecting scrap aluminium and rust Apr 13 06:51:35 <_av500_> isnt that what cars are for? Apr 13 06:52:00 I live in phoenix where cars don't collect rust Apr 13 06:53:10 <_av500_> ah Apr 13 06:53:46 <_av500_> anybody got a spare roboraptor remote? Apr 13 06:53:55 <_av500_> I just got donated one Apr 13 06:59:20 Russ: making thermite? Apr 13 06:59:34 would be a fun way to melt the platters Apr 13 07:34:23 geez, talk about a slow boat Apr 13 07:34:35 Shipped - Delivery Estimate: Monday May 7, 2012 - Wednesday May 23, 2012 Apr 13 07:37:53 you've never seen the delivery a n950 to israel has taken. That rested about 3 month beneath some bureaucrats desk ;) Apr 13 07:38:49 this is just a easycap usb capture dongle Apr 13 07:39:01 easycaps are nice Apr 13 07:40:00 I'm going to be hooking them up to my xM and am37x-evm Apr 13 07:40:55 suppose the shipping policy is listed, 'Continental US Street · Standard · (17 - 28 business days)' Apr 13 07:44:41 Russ: me and brother got one working nicely on beagleboard Apr 13 07:45:41 I'm actually going the opposite way Apr 13 07:45:57 for testing the video output Apr 13 07:46:00 ah right, using them as composite in? Apr 13 07:46:04 yeah that works well as well Apr 13 07:46:16 doesnt work so well for zx spectrum video output though :-( Apr 13 07:46:46 main reason I had easycap was to use beagle video out without having to walk across room to TV Apr 13 07:47:07 I'd think the zx spectrum would be pal Apr 13 07:56:39 its PALish which trips up the decoder chip Apr 13 07:57:06 works fine on btxxx PCI card I have, but easycap goes a bit mental with the timings being off Apr 13 08:39:28 hey guys, I don't know why, but GPIO is not working this morning... Apr 13 08:39:59 I do echo 183 > export, to use the pin 23 Apr 13 08:40:06 and set direction to out Apr 13 08:40:20 my GPIOs work only in the afternoon, it's a union thing... Apr 13 08:40:25 and the value is on 0 but I have 1.8v on this pin Apr 13 08:40:47 lol okay, for this reason. Shit, I have to wait 2 hours... Apr 13 08:40:54 =) Apr 13 08:41:05 yes, have an early lunch Apr 13 08:41:32 ^^ Apr 13 08:41:37 otherwise... Apr 13 08:42:15 any help? Apr 13 08:45:11 no :(? Apr 13 08:45:24 I have no idea what you changed Apr 13 08:46:26 mhh, is my method is good? Apr 13 08:46:58 I mean export, set direction, & set value? Apr 13 08:47:41 I guess so, it worked before, non? Apr 13 08:48:00 maybe it was luck ^^ Apr 13 08:48:02 its open collector with a pullup? Apr 13 08:48:17 I don't know Apr 13 08:48:27 I want to simply blinka Led Apr 13 08:48:48 so i followed tutorials on net Apr 13 08:49:19 but nothing work. But on a google group, I saw someone talking about a problem with the latest kernel builded with angstrom.. Apr 13 08:51:12 Pin 23 of expansion connector is GPIO_130 Apr 13 08:51:28 http://elinux.org/BeagleBoardPinMux Apr 13 08:51:34 noted 183 here Apr 13 08:51:53 old doc? Apr 13 08:52:03 MMC2_CLK/McSPI3_CLK/GPIO_130 Apr 13 08:52:08 according to schematic Apr 13 08:52:16 although Im on laptop so might have misread Apr 13 08:52:21 is it on reference manual? Apr 13 08:52:39 your theory sounds good. Apr 13 08:52:51 oh wait I have wrong pin Apr 13 08:53:01 I zoomed and alignment is a bit better Apr 13 08:53:43 its GPIO_183 Apr 13 08:53:52 but I think by default that is muxed as I2C2 Apr 13 08:53:54 ... Apr 13 08:54:00 ok Apr 13 08:54:11 so I can't use it as I/O pin? Apr 13 08:54:15 so expansion boards work Apr 13 08:54:27 you can change muxing in kernel, not sure if they ever did usespace or not Apr 13 08:54:56 I'm beginning with beagle, not sure that I'm able to do that :) Apr 13 08:55:10 you should be able, somewhere in /sys/debug Apr 13 08:55:19 is tehre a "safe pin" that work every time with gpio config? Apr 13 08:55:55 you can see the muxing in the debugfs Apr 13 08:58:05 I tend to use those MCBSP pins, not sure what they mux to by default though :_D Apr 13 08:58:17 nothing called debug in /sys Apr 13 08:58:31 ok Apr 13 08:58:33 will try Apr 13 08:58:37 mount -t debugfs none /sys/kernel/debug Apr 13 08:58:47 ls /sys/kernel/debug Apr 13 08:59:32 ok thanks, good to know Apr 13 09:09:47 which build is the best to develop on beagleboard? Cloud9 or the demo-image? Apr 13 09:11:30 'gpio-183 (sysfs ) out lo ' Apr 13 09:11:41 founded in /sys/kernel/debug/gpio Apr 13 09:18:39 beagleboard or beaglebone? Apr 13 09:18:46 board Apr 13 09:18:54 use what suits you best Apr 13 09:18:58 or build a custom one Apr 13 09:19:07 ok Apr 13 09:19:32 will take the demo Apr 13 09:22:48 * Russ creates an mmc card for his xM, turns to his xM to insert it, then realizes that its probably time to sleep Apr 13 09:22:50 XorA: it seems most people lack the reading stamina to find your kernel workflow docs on the angstrom site :( Apr 13 10:01:23 I've two files when I do a Narcissus build. What is the difference? Apr 13 10:03:42 what are the files? Apr 13 10:03:56 Angstrom-2012.04-narcissus-beagleboard-i686-louisbobv4-nano-image-sdk.tar.gz Apr 13 10:04:05 louisbobv4-nano-image-beagleboard.tar.gz Apr 13 10:04:11 I guess the second is the distrib Apr 13 10:04:14 but the first? Apr 13 10:04:25 its the "SDK" Apr 13 10:04:39 its what you need on the host PC to build stuff for the image Apr 13 10:04:55 so it has all the headers and libs needed Apr 13 10:05:18 but there is also tar tvf $file Apr 13 10:05:45 ok so I don't care of the first for the moment Apr 13 10:05:52 yep Apr 13 10:06:02 if you uncheck the "sdk", you wont even get it Apr 13 10:06:03 it's for developping, and compiling on a pc, right? Apr 13 10:06:07 o Apr 13 10:06:08 yes Apr 13 10:06:08 k Apr 13 10:06:47 ok, so it allows to compile binaries and the program is ready to use on the board Apr 13 10:27:32 It defintely doesn't work. In my kernel/debug/gpio file, I had this line: "gpio-168 (sysfs ) out lo" Apr 13 10:28:02 and I have high level on the pin 24 (1.8V) Apr 13 10:29:34 and it's muxed to gpio? Apr 13 10:34:21 How can I know? Apr 13 10:36:53 ? Apr 13 10:45:26 need help please Apr 13 11:07:55 koen: How to know please? Apr 13 11:14:59 as already said, debugfs, ls /sys/kernel/debug/ Apr 13 12:02:29 hi :) someone have manage the chulk board lcd woth beagleboard xM? Apr 13 12:37:18 root@beagleboard:/sys/kernel/debug# ls asoc clock hid omapdss sched_features usb bdi gpio mmc0 pm_debug tracing vram Apr 13 12:37:39 this is the output of my ls command on kernel/debug folder Apr 13 12:41:23 any idea? Apr 13 12:41:57 WAKE UP! Apr 13 12:44:08 sigh Apr 13 12:44:22 r-pi trolls incomming Apr 13 12:46:48 ? Apr 13 12:47:33 keep them talking until dawn Apr 13 12:47:56 thx Apr 13 12:48:21 irc is trully usefull Apr 13 12:50:21 i met my wife on irc! Apr 13 12:50:29 oO Apr 13 12:50:49 irc = meetic Apr 13 12:50:55 metric? Apr 13 12:51:12 www.meetic.fr/ Apr 13 12:51:18 zombie apocalypse guide does not cover how to deal with hoards of trolls :( Apr 13 12:51:23 * mru uses imperial irc Apr 13 12:51:42 mru, excellent, we need more right thinkers in our camp Apr 13 13:15:02 av500: what triggered the trolls? Apr 13 13:15:09 no idea Apr 13 13:15:12 maybe r-pi ships Apr 13 13:16:02 ah no Apr 13 13:16:10 14:27 < stuk_gen+> is there here somebody have try chalkeboard lcd on beagleboard? Apr 13 13:16:12 14:33 < piless+> stuk_gen: Try #beagle Apr 13 13:16:13 14:33 < stuk_gen+> piless: i just try but in that room all are spleeping Apr 13 13:16:18 zzzz Apr 13 13:17:41 true story Apr 13 13:37:21 av500: its true Apr 13 13:38:04 * XorA is asleep Apr 13 13:38:36 where i can find a documentation of what parameters can i add to uenv.txt files? Apr 13 13:38:56 What you want to do? Apr 13 13:39:37 i try run an lcd on beagleboard xM Apr 13 13:39:50 connected on hdmi port? Apr 13 13:39:58 no lcd port Apr 13 13:40:03 is a chalk board Apr 13 13:40:15 sorry, I mean DVI port Apr 13 13:40:23 no Apr 13 13:40:23 follow "chalk board" documentation Apr 13 13:40:24 lcd Apr 13 13:40:57 av500: yes the 3 rows of documentations that tell to set 1024x600 resolution. Apr 13 13:42:15 i try to use boot.src or uenv.txt but lcd not work correctly maybe i'm wrong parameter but i can't find the documentation of the parameter that i can write on the uenv.txt Apr 13 13:42:24 stuk_gen: did you try google? Apr 13 13:42:26 https://www.google.com/search?q=uenv.txt+lcd+resolution Apr 13 13:42:36 I get a ton of hits.... Apr 13 13:42:52 av500: wow Apr 13 13:42:58 wow? Apr 13 13:43:28 av500: its 2 hours that i try search and try...but whitout solutions Apr 13 13:43:38 I have no omap_mux file in /sys/kernel/debug when it is mounted. What's wrong? Apr 13 13:44:10 louisbob: it turns out that is not turned on in the beagleboard kernel, but is in the beaglebone kernel :( Apr 13 13:44:10 is it possible that the kernel module is not loaded? Apr 13 13:44:29 but iirc they should all be muxed to gpio already Apr 13 13:44:33 and this is not a documentation but a more 'try code and look if run'... i spent much time to try and run...maybe if i study how uenv.txt work i can find solution... Apr 13 13:44:42 I remember playing with the gpios a while ago Apr 13 13:46:38 Yes, it's a plate of noodles. So, the muxing is made by the bootloader then? I have big problems with GPIOs, and I think that the issue is in relationship with muxing. Apr 13 13:48:17 ah right Apr 13 13:48:22 I remember now Apr 13 13:48:23 https://github.com/koenkooi/linux/blob/linux-3.0.25-r118a/arch/arm/mach-omap2/board-omap3beagle.c#L979 Apr 13 13:48:29 that's for the trainer Apr 13 13:48:35 not sure what the default mux is Apr 13 13:49:15 I have to compile my distro with this modified? Apr 13 13:49:22 av500: for example i found put in uEnv.txt dvimode="1024x600MR-16@60 omapfb.vram=0:40M,1:24M,2:4M omapfb.vrfb=0 " but i need lcd do i have to try lcdmode="1024 ecc.." ? Apr 13 13:51:00 omap_mux_init_gpio(140, OMAP_PIN_OUTPUT); Apr 13 13:51:01 no Apr 13 13:51:08 dvi and lcd share the same pins Apr 13 13:51:14 its not exactly the most difficult bit of code to change the mux :-D Apr 13 13:51:31 ok Apr 13 13:51:32 XorA: it does not even involve I2C :) Apr 13 13:52:04 just stick that in the board file somewhere Apr 13 13:52:08 XoRa: but it's a C function, so I have to add the header gpio_keys.h to my program? Apr 13 13:52:19 no Apr 13 13:52:20 kernel Apr 13 13:53:27 av500: I mod the kernel, recompile it and put it on the sdcard, right? Or could be done on live on the board? Apr 13 13:54:51 i guess it can be changed with devmem as well :-D Apr 13 13:54:55 but that way is scary Apr 13 13:55:08 hot needle and a steady hand Apr 13 13:55:13 I'm already scared by the "kernel" Apr 13 13:55:18 boo Apr 13 13:55:47 kernel is like a professional dominatrix :-D Apr 13 13:56:06 don't like to stroke an unknown thing =D Apr 13 13:57:08 XorA: so I have to recompile the kernel myself finnaly? Apr 13 14:11:01 av500: dvi and lcd share pins? Apr 13 14:11:16 av500: so i can't use dvi port and lcd at the same time? Apr 13 14:12:00 sure you can Apr 13 14:12:13 just don't expect different output Apr 13 14:12:50 different...not Apr 13 14:13:54 louisbob: within a week you shall be addicted :-D Apr 13 14:15:46 stuk_gen: correct Apr 13 14:15:51 schematics are public Apr 13 14:15:54 no surprise there Apr 13 14:22:46 av500: so or i connect to lcd or connect dvi? Apr 13 14:23:33 av500: its strange i see only more strange row in a lcd ...there is someting wrong Apr 13 14:28:15 lo! Apr 13 14:29:27 ¡hi Apr 13 14:30:15 - mediocre Apr 13 14:35:04 i'm still struggling with loggin on a beagleboard XM with 2.6.32 Apr 13 14:35:41 i use select and open with 0_NONBLOCK, but calls to write some times take 15 secs Apr 13 14:35:56 blame your sd card Apr 13 14:38:21 av500, that could be it... read a bit about them, wouldn't solve it with a faster one, fast means "fat stuff goes fat", right? Apr 13 14:38:51 and looks like write delay go down to 15ms max (instead of 15 SEC) if i will wifi Apr 13 14:38:56 *kill wifi Apr 13 14:39:02 hmm Apr 13 14:39:11 could the wifi driver be stealing the kernel from me? Apr 13 14:39:59 ok i think i have problem with lcd...or the problem is the lcd or the beagleboard. If i connect hdmi-dvi i can correct see on monitor an boot logo and angstrom run. if i use only lcd raw i see only strange row Apr 13 14:40:36 well, either DVI works or LCD Apr 13 14:40:40 but not both at the same time Apr 13 14:41:07 not even if attached displays support same timings? Apr 13 14:41:41 mru: would he complain in that case? Apr 13 14:42:03 you never can tell Apr 13 14:46:39 av500: dvi works, lcd not Apr 13 14:47:03 but i need kernel configuration driver or anyother tools to run the lcd?!? Apr 13 14:47:23 you need the correct timing for that LCD Apr 13 15:02:45 av500: what this mean? Apr 13 15:03:02 av500: i have to set up something? Apr 13 15:03:58 easter monday has me all confused Apr 13 15:04:10 it's friday already, but it feels like a thursday Apr 13 15:05:05 stuk_gen: see chalk-elec instructions Apr 13 15:05:33 av500: its not talk about timing, its only says add an argoment to uEnv.txt Apr 13 15:05:47 yes, and did you try that? Apr 13 15:06:06 that argument is an alias for a specific timing Apr 13 15:06:21 av500: yes i try Apr 13 15:06:28 av500: without success Apr 13 15:07:32 I updated kernel to v3 as well as installing gpu drivers, now my X wont start because it cant find any devices, is there any config program im missing? Pandaboard ES, Ubuntu Apr 13 15:08:14 av500: i'm using this http://pastebin.com/dT2bUzvG on my uEnv.txt Apr 13 15:09:55 also, A) My tummy hurts from overeating B) My face has been trapped in an endless loop of itchiness, everytime i itch the chickenjuices rub off making it itch worse. WDID Apr 13 15:10:49 stuk_gen: and how did you get there from the instructions here: http://www.chalk-elec.com/?p=1478 ? Apr 13 15:11:07 Haikarainen: wrong channel Apr 13 15:12:07 av500: there istruction is for debian on pandaboard, i'm using angstrom Apr 13 15:12:40 av500: and if you read its says "dvimode1024x600MR-16@60" Apr 13 15:13:12 and? Apr 13 15:13:36 if you are unwilling to follow the instructions given by who sold you the LCD, what can I say? Apr 13 15:13:52 chalk-elec has a support forum, go there please Apr 13 15:13:53 and important is set dvimode=1024x600... and i've do this Apr 13 15:14:10 cat /proc/cmdline Apr 13 15:15:03 av500: forum? where? O_o Apr 13 15:15:31 plonk Apr 13 15:15:38 stuk_gen: funny, i have seen a single person who purchased one of those chalk-elec lvds boards get it working properly Apr 13 15:15:53 yo prp Apr 13 15:15:55 yo prpplague Apr 13 15:16:01 XorA: hey bud Apr 13 15:16:05 XorA: what's cookin? Apr 13 15:16:25 prpplague: ages ago I was asking you about I2C IO extenders, do you remember one which can be soldered my mere mortals? Apr 13 15:16:34 prpplague: good news for me ... Apr 13 15:16:38 blind ones? Apr 13 15:17:08 XorA: pcf8574 Apr 13 15:17:32 XorA: http://www.sparkfun.com/products/8130 Apr 13 15:17:37 XorA: easy to add Apr 13 15:17:50 XorA: i'm planning to do some i2c hands on stuff at ELC-E Apr 13 15:18:00 av500: chalk-elec haven't forum... Apr 13 15:18:05 prpplague: $11.95? you are killing the company! Apr 13 15:18:05 aholler: ahah, DIP, yeah thats for mortals :-D Apr 13 15:19:05 prpplague: sorry for late...is this omapfb.mode=dvi:omapfb.mode=lcd omapdss.def_disp=lcd omapfb.mode=1024x600MR-16@60 fixrt omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait Apr 13 15:19:20 cat /proc/cmdline Apr 13 15:19:47 stuk_gen: no clue on how chalk-elec expects you to do it, i only know how i would do it Apr 13 15:20:42 prpplague: ok, but you know what is the correct sintax to set a resolution for lcdmode and say to kernel to use default display lcd? Apr 13 15:21:22 stuk_gen: like i said, it all depends on what is compiled in the kernel, what drivers are setup and what panel information you have Apr 13 15:21:54 prpplague: ok..its a disaster xD thanks Apr 13 15:22:07 stuk_gen: indeed Apr 13 15:22:15 prpplague: ahah, there is a easy UK source of them as well Apr 13 15:22:27 XorA: for the breakout board? Apr 13 15:22:57 prpplague: yes Apr 13 15:23:02 XorA: ahh nice! Apr 13 15:23:12 prpplague: lot of sparkfun stuff makes its way here now Apr 13 15:23:19 prpplague: couple of years ago it was much harder Apr 13 15:23:21 stuk_gen: which lcd panel are you using? Apr 13 15:23:35 prpplague: chalk-elec Apr 13 15:23:38 the chalk-elec one Apr 13 15:24:27 XorA: you'll need a level shifter for the i2c signals Apr 13 15:24:31 hehe Apr 13 15:24:43 stuk_gen: chalk-elec does not make a lcd panel, they sell one Apr 13 15:24:56 stuk_gen: they also sell several different models Apr 13 15:25:13 stuk_gen: so, again, which lcd panel are you trying to use? Apr 13 15:25:27 prpplague: got some of them Apr 13 15:25:51 prpplague: this http://www.chalk-elec.com/?page_id=1280#ecwid:category=0&mode=product&product=7703686 Apr 13 15:25:54 prpplague: TI jobbies Apr 13 15:25:58 XorA: i generally prefer to use the TCA64xx series from TI as it does not require level shifters Apr 13 15:26:44 but leet soldering skillz Apr 13 15:26:54 stuk_gen: turn your LCD panel over and look at the manufacturer and model number Apr 13 15:27:02 av500: yea Apr 13 15:28:02 prpplague: is B101AW02 Apr 13 15:28:13 prpplague: AU Optronics Apr 13 15:29:00 stuk_gen: the easiest to get that working is to add support in the panel-generic-dpi.c file Apr 13 15:29:13 stuk_gen: i'll be posting procedures for doing that in the next week or so Apr 13 15:29:23 stuk_gen: you are using angstrom? Apr 13 15:29:33 prpplague: yes Apr 13 15:30:05 prpplague: but only one information panel-generic-dpi.c what it is? a file of kernel that i have to modify? Apr 13 15:30:37 prpplague: why would dvimode=1024x600MR-16@60 not work? Apr 13 15:31:10 try without MR Apr 13 15:31:28 so far he refused to try at all Apr 13 15:31:43 av500: he refuse to try? who? ME? Apr 13 15:32:08 you are in my /ignore, so I cant hear you any more Apr 13 15:32:15 perfect Apr 13 15:32:29 but you pasted this: http://pastebin.com/dT2bUzvG Apr 13 15:32:40 and it does not look like what was posted in the instructions.... Apr 13 15:32:51 because tha only people that is trying to help me is prpplague that says some information...not only search google red doc go to forum Apr 13 15:33:17 stuk_gen: as av500 said, you purchased it from chalk-elec, you should expect them to support it Apr 13 15:33:35 stuk_gen: the people in the channel are not here to help chalk-elec sell their product Apr 13 15:33:53 stuk_gen: maybe you should carefully read your cmdline Apr 13 15:33:54 prpplague: i just send email to support but i when i waiting i can try some solution Apr 13 15:34:11 and the paste and google how it should be Apr 13 15:34:14 aholler: now you are asking him to do things too Apr 13 15:34:30 google, look into forum, read Apr 13 15:34:31 at least he was able to cat /proc/cmdline Apr 13 15:34:35 prpplague: ok, but i here is a beagle, i'm using beagle so i only want instruct to connect lcd Apr 13 15:34:37 where? Apr 13 15:34:52 LMGTFY Apr 13 15:35:23 ah ok, I was not interested any more Apr 13 16:18:19 av500: learn something new everyday Apr 13 16:24:17 prpplague: wuz? Apr 13 16:25:11 av500: i didn't realize you could use the dvi mode args to config for a lcd panel Apr 13 16:25:26 av500: silly me i've been using the panel-generic-dpi.c with custom builds Apr 13 16:25:29 prpplague: well, to the dss its all the same no? Apr 13 16:25:37 same dss pins Apr 13 16:26:03 av500: yea, just been doing the hardcode support for testing i didn't even think of it that way, hehe Apr 13 16:27:53 av500: killed a giant brown recluse spider on the porch yesterday, no i gotta call the exterminator to make sure there aren't any more hiding out Apr 13 16:41:57 anyone tinker around with the pixel-qi display? Apr 13 17:45:56 <_av500_> no Apr 13 17:46:15 <_av500_> is there a full hd one? :) Apr 13 17:46:33 <_av500_> or retina even Apr 13 17:48:30 anyone know why sound sound works on my XM, but when i try to run an NES emulator it fails? I have tried mednafen and fceu Apr 13 17:49:45 the emulator runs too fast if i enable sound, but if select a non existent alsa device (hw:1 instead of hw:0) the emulator runs correctly Apr 13 17:50:18 this is probably not the best place to ask, but i thought I would throw it out there Apr 13 19:45:18 Hello, I'm currently using a Beagleboard-xM and MT9P031 image sensor. I have successfully taken pictures with yavta and media-ctl based on the patches and current images out there, I have also successfully manipulated the gain/exposure. However, for the project I'm doing, I need to do some calculations and I need to know how the exposure times entered in the yavta command translate to real time (i.e. ns? ms?) Does anyone have any Apr 13 20:00:28 <_av500_> i guess the source code is your best friend Apr 13 20:53:41 Hey everyone, I just went through the build instructions on angstrom distribution webpage. I am somewhat confused with the results. Where can I find the files I need to boot up my BB-xm? (uImage, u-boot.bin, MLO)? Apr 13 20:55:36 I have poking around the /build/tmp-angstrom_2010_x-eglibc/work/beagle.... directories Apr 13 20:56:39 I am trying to follow along with the elinux.org/ECE497 class instructions, but it looks like things have changed since they were last edited. Apr 13 21:07:40 jstearns74, temp/deploy..... Apr 13 21:10:54 I must be an idiot, I can't seem to locate temp/deploy... Apr 13 21:11:32 I am in the ~/OE/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/beagleboard-angstrom-linux-gnueabi/linux-3.0.25-r118/ directory... am I close? Apr 13 21:11:53 there is a temp directory there, but no deploy folder... Apr 13 21:12:10 however, there is a deploy-linux/ folder Apr 13 21:13:05 in the deploy-linux folder, there is a file 'uImage-beagleboard.bin'. I am assuming that is my u-boot.bin file? Apr 13 21:14:08 <_av500_> no Apr 13 21:14:12 <_av500_> its uimage, the kernel Apr 13 21:14:32 ah. Apr 13 21:16:07 there is also a directory /linux-3.0.25-r118a/image/boot where there is a file uImage-3.0.25. I thought that would be my uImage file. Apr 13 21:16:25 tmp-ang..../deploy :) Apr 13 21:16:31 you are to far down Apr 13 21:16:44 you are in the work directories Apr 13 21:17:44 OK - found it! Apr 13 21:18:28 * mranostay pokes _av500_ Apr 13 21:18:45 * _av500_ shrugs Apr 13 21:19:00 alight - sorry - still confused. The uImage-beagleboard.bin file is there. Where is everything else I need? Apr 13 21:32:21 is that all? Apr 13 21:32:29 what did you build? Apr 13 21:34:23 There are 2 files (modules-3.0.25-r118a-beagleboard.tgz) & (uImage-beagleboard.bin which points to uImage-3.0.25-r118a-beagleboard-2....bin) Apr 13 21:35:13 Should I have more? Apr 13 21:37:55 <_av500_> mranostay: you worked on sigmatel stuff? Apr 13 21:41:51 _av500_: long time ago Apr 13 21:42:03 <_av500_> the 56k dsp stuff? Apr 13 21:43:29 no just HDA stuff Apr 13 21:45:53 <_av500_> ah Apr 13 21:47:51 Hi, has anyone had any problems with ioctl, and webcams, and usb. I'm using a bb rev b7. Apr 13 21:48:39 <_av500_> with all 3 Apr 13 21:48:44 <_av500_> but not combined Apr 13 21:51:42 _av500_: why you ask exactly? Apr 13 21:51:51 <_av500_> stalking you Apr 13 21:53:51 niro: what kind of problems? Apr 13 21:53:53 jstearns74, no image files? Apr 13 21:54:44 when the program i'm using gets to the function ioctl(/dev/video0, VIDIO_STREAMON, &type) it fails Apr 13 21:55:06 <_av500_> its VIDIOC_STREAMON Apr 13 21:55:08 not that I can find, but again, I am not exactly sure what I'm looking for. Apr 13 21:55:13 does it work with the same camera on a pc? Apr 13 21:55:31 and uvcvideo reports to dmesg, failed to submit URB 0 Apr 13 21:55:34 -28 Apr 13 21:55:52 yes, I did all the development on the pc Apr 13 21:55:57 that's ENOSPC Apr 13 21:56:09 <_av500_> thats a known "bug" Apr 13 21:56:17 <_av500_> we hadthat here before, or on the ML Apr 13 21:57:03 <_av500_> linux/drivers/media/video/uvc/uvc_video.c:339: ret = -ENOSPC; Apr 13 22:01:02 <_av500_> but does not look like this is called from STREAMON Apr 13 22:01:28 <_av500_> so ENOSPC is rather from usb layer i'd say Apr 13 22:02:30 <_av500_> niro: any your are on uptodate software? Apr 13 22:03:36 yes, I'm running kernel 3.2.14-x7 Apr 13 22:04:18 or do you mean opkg update? Apr 13 22:04:24 <_av500_> no Apr 13 22:04:26 <_av500_> kernel Apr 13 22:04:35 <_av500_> musb is a pain Apr 13 22:05:10 I was running 2.6.32, and the webcam was working on resolutions then I decided to get the latest kernel, and now it fails with everything. Apr 13 22:06:10 <_av500_> never change a running system Apr 13 22:06:53 _av500_: explain that to the kernel guys :P Apr 13 22:07:10 niro, if you installed it via "install-me.sh" script, there should be a backup.. Apr 13 22:08:17 rcn-ee, there's nothing on any importance on the board, and I think it was the angstrom demo anyway, so should be easy enough to back track... Apr 13 22:09:04 my thinking is that, I want to actually fix this issue. Apr 13 22:09:28 I've spent several days reading the usb source. Apr 13 22:09:54 I am thinking, why did I book a flight on the redeye Apr 13 22:10:09 anyone seen a batter clip that fits on the beagleboard xm? Apr 13 22:10:30 <_av500_> just batter it with a large bat Apr 13 22:13:20 Btw, I have a usb-ethernet adapter running on the same usb hub as the webcam. Apr 13 22:13:30 So I know that usb is working to some degree. Apr 13 22:13:53 I have tried running the webcam without this as well. Apr 13 22:14:46 So, makes me think there is a problem with isochronous tranfers Apr 13 22:14:53 <_av500_> I guess its rather that some patches broke iso Apr 13 22:16:01 _av500_ do you know anything about touchscreen drivers? Apr 13 22:16:29 <_av500_> anything? well, something Apr 13 22:17:34 I doubt he has even seen a touch screen Apr 13 22:19:05 _av500_, the touchscreen Im using is 90 degrees out of phase, in the clockwise direction, moving from the top left corner the touch registers at being at the top right, moving to the right the touch moves down to the right lower corner, moving to the right lower corner, the spot moves to the lower right corner, etc Apr 13 22:19:30 is that something that can be fixed with say the *.idc file or am I going to have to dig into the sources? Apr 13 22:19:43 <_av500_> i have no idea what an idc file is Apr 13 22:20:12 _av500_ input device configuration file for android Apr 13 22:21:04 borillion, I think it's a bit of a generalised question possibly. Apr 13 22:21:16 I assume that I should be able to load linux drivers for it as module on android without much issue, but I haven't ever done that Apr 13 22:21:26 The orientation is set by the registers of the touch screen controller chip... Apr 13 22:21:34 depending on which chip you have Apr 13 22:21:41 <_av500_> http://source.android.com/tech/input/input-device-configuration-files.html Apr 13 22:21:51 niro: so they are out of spec then? Apr 13 22:22:23 _av500_ I reead that a thousand times lol, there is nothing about rotation of the axis's Apr 13 22:23:04 The wrong settings for the register are being sent, yes. But the correct settings may be in the idc Apr 13 22:23:13 But, I have no idea what the idc is.. Apr 13 22:23:20 <_av500_> http://source.android.com/tech/input/touch-devices.html Apr 13 22:23:42 <_av500_> ...The Orientation field describes the orientation of the touch and tool as an angular measurement. An orientation of 0 indicates that the major axis is oriented vertically, ... Apr 13 22:24:22 thats for a stylus or some other tool, nothing to do with the layout of the axis on the screen surface do you know what I mean? Apr 13 22:25:18 <_av500_> sorry no idea Apr 13 22:25:36 hehe its ok, Ill figure it out eventually LOL Apr 13 22:26:19 You mean that when the screen is portrait, the bottom is x, and the side is y. But when it's landscape, that is still the case? Apr 13 22:27:19 the actual sensor obviously reports the same signal for the same input whatever is being displayed on the screen Apr 13 22:27:34 yes but my screen is fixed for my purposes and has no tilt sensor, its always in landscape, maybe somehow its stuck in the portrait mode Apr 13 22:27:54 I meant the touch sensing thing Apr 13 22:28:10 when I touch the screen and move my finger from the center down, I see the spot that is shown for the inputs go left Apr 13 22:28:27 from the center to the outer edge instead of following my finger Apr 13 22:28:34 presumably something applies a transformation to the raw values before the applications get them Apr 13 22:28:42 go from center to top and it goes right LOL Apr 13 22:29:37 yep, from what I can figure out its not the idc file (input device config) but at more of a fundamental level the drivers for this chip Apr 13 22:29:42 its usb btw Apr 13 22:31:30 I did find this The eGalax OEM touch controller chips (0x0eef:0x0001 version 01xx) Apr 13 22:31:30 have their MSB / LSB packets reversed from the Documentation from Apr 13 22:31:30 EETI both in the 1.1 and 2.0 reference manuals Apr 13 22:32:38 soo, either a) I reverse the packets the second time to get them in the right way .... or b) modify the driver to get the thing to understand what the screen is feeding it Apr 13 22:33:23 leaning for b as it sounds more reasonable, but I have no clue what/where to change Apr 13 22:34:39 most lcds have a pin to change the rotation Apr 13 22:35:01 and hw-devs are often unable to read datasheets Apr 13 22:36:05 so there just might be some pullup wrong or similiar. Apr 13 22:36:26 SilicaGel: how's your flirt with the PRUSS going? Apr 13 22:37:51 hmm thanks aholler Apr 13 22:43:40 rcn apologies - my pc crashed... Apr 13 22:45:51 and i had left work.. now home. ;) Apr 13 22:46:42 i'd fire up cutecom, which has a pretty easy serial logging system.. it would be interesting to see what your board is doing on power up.. Apr 13 22:48:11 thanks - I will work on it and get back to you Apr 13 22:48:54 ill update the bb forum with the log Apr 13 22:49:00 thanks again **** ENDING LOGGING AT Sat Apr 14 02:59:58 2012