**** BEGIN LOGGING AT Fri Jun 22 02:59:59 2012 Jun 22 03:12:58 lilstevie, infinity, from what I understand it is running a sort of customized ubuntu 10.10 already.. but hopefully when they post the kernel the board support isn't too hard to forward port and get newer kernel and 12.04 running on it Jun 22 03:21:18 robclark: Hang a USB drive off the thing, and it would be a perfect devel kit to recommend to people. Jun 22 03:21:25 robclark: that's cool Jun 22 03:21:30 yup Jun 22 03:25:21 robclark, do you know if it's a 4430 or 4460? hard to argue with that price for something that has a monitor, etc. Jun 22 03:25:41 I think it is 4430 Jun 22 03:27:16 support for realtek USB wifi? Jun 22 03:28:41 http://h18000.www1.hp.com/products/quickspecs/14358_na/14358_na.HTML#Technical Specifications Jun 22 03:29:18 robclark, excellent, thanks! Jun 22 03:36:30 I kinda want one Jun 22 03:42:39 I also noticed that it has flash Jun 22 06:54:35 Tinti, I am trying to do a 12.04 image for gumstix (armel), and got errors - Failed to create pty - disabling logging for job Jun 22 06:55:34 cvanvliet: Does your kernel have support for devpts? Jun 22 06:57:24 I only compiled my first kernel a few days ago, and am not great with kernel foo yet, wil check it Jun 22 06:59:43 (what I did do was enable initramfs, and move init to / and it helped, but ended up in init being /bin/sh?) Jun 22 07:00:10 bbs, thanks infinity Jun 22 07:07:38 quick check -> yes, unix98 and bsd are both enabled Jun 22 07:13:18 Okay, but it sounds like you're doing some odd things with your initramfs... Jun 22 07:13:26 Are you creating it with update-initramfs? Jun 22 07:13:46 I mean, talk of moving init around and whatnot sounds a bit unconventional. :P Jun 22 07:13:59 yes Jun 22 07:14:37 infinity, I am mainly trying to learn, don’t take anything I say as being correct Jun 22 07:14:42 Anyhow, I probably shouldn't get into this tonight, I need to sleep and be up early. Jun 22 07:14:48 thanks Jun 22 07:15:00 But, yeah. If you think you need to move init around, you're almost certainly doing something wrong elsewhere. ;) Jun 22 07:15:19 I may have just seen something :/, let me try Jun 22 07:15:27 thanks! Jun 22 13:32:43 ogra_: we are going to stay with this kernel for omap4, sorry Jun 22 13:32:53 ogra_: tilt-tracking is heavily based on linaro kernels Jun 22 13:33:09 ogra_: and a rebase gave me all kinds of clashes Jun 22 13:33:35 ogra_: after alpha2 is out, i'll start building a 3.5 kernel for omap4 (as the email on the ubuntu kernel ml stated) Jun 22 13:36:03 damned Jun 22 13:36:05 but ok Jun 22 13:36:23 i guess then we cant really make A2 Jun 22 13:37:02 (with the display issues and the switch to full live images we wont have a way to install) Jun 22 13:37:33 ogra_: it works for some monitors actually Jun 22 13:37:44 i have tried three so far Jun 22 13:37:48 none of them works Jun 22 13:38:03 i dont' know what to tell Jun 22 13:38:10 i've two here and they work Jun 22 13:38:24 n othing to tell, ndec already said they completely reworked the graphics driver Jun 22 13:38:48 we just need that code dump .... Jun 22 13:39:17 but we don't have it for 3.5 Jun 22 13:39:25 * ndec checks ubuntu kernel list... Jun 22 13:39:40 oh, i thought you said it was 3.5 Jun 22 13:39:49 nope Jun 22 13:39:52 still 3.4 for them Jun 22 13:39:59 my prob is that omap doesnt boot either Jun 22 13:40:07 and it's actually 3.4 + a lot of stuff from linaro + ... Jun 22 13:40:08 and ac100 doesnt build yet Jun 22 13:40:19 we have 'frozen' tilt-3.4 just today. so tilt-tracking will start tracking 3.5 any day now. Jun 22 13:40:19 a disaster! :) Jun 22 13:40:21 so we wont have any arm images for A2 Jun 22 13:40:30 wait wait Jun 22 13:40:35 what's wrong with omap? Jun 22 13:40:45 however we (TI) will not spent a lot of energy on 3.5... Jun 22 13:40:58 so i am not sure which features will work in 3.5 Jun 22 13:40:59 ppisati, given that the QA team only has 5 weeks left to get their automated testing working, it is a desaster, there are no images yet for them to write scripts for Jun 22 13:41:00 yet Jun 22 13:41:31 ndec: i know i know, we are going to use 3.5 upstream after alpha2 + cherry picks useful stuff from tilt Jun 22 13:41:43 it's likely that the TILT 3.5 won't get many more than what's in mainline already Jun 22 13:42:01 so ppisati what's the problem exactly? Jun 22 13:42:03 ogra_: what's wrong with omap? Jun 22 13:42:14 oopses all over the place Jun 22 13:42:24 we didnt release it for A1 if you remember Jun 22 13:42:32 ogra_: i've been testing it till an hour ago Jun 22 13:42:33 3.4? Jun 22 13:42:40 ndec: 3.5 Jun 22 13:42:43 ah... Jun 22 13:42:52 ndec, oopses -> omap3 ... Jun 22 13:42:56 not omap4 Jun 22 13:43:02 tilt-3.4 should be in quite a good shape on OMAP4 and 5. Jun 22 13:43:11 hum. omap3? Jun 22 13:43:30 omap4 3.5 simply freaks out with the wlan device (demsg gets massively spammed) and doesnt detect any monitor here for me Jun 22 13:43:50 err 3.4 that is ... Jun 22 13:44:23 ogra_: me and ming were tracking down an mmc/fs issue in omap for 3.5 Jun 22 13:44:31 ah Jun 22 13:44:31 ogra_: but apart from that, kernel works here Jun 22 13:44:35 we use wlan with 3.4-tilt with *precise* these days. and it seems to be working. Jun 22 13:44:52 it seems it's an sd card problem with a late commit Jun 22 13:44:52 ppisati, well, it didnt for A1 thats why it was decided to be dropped Jun 22 13:45:22 ogra_: video wasn't working iirc Jun 22 13:45:27 ogra_: anyway, let me check Jun 22 13:45:51 and with the switch to full live images the XM install (with only 512M) wont be any fun anymore ... apart from fully relying on video Jun 22 13:46:33 infinity, around ? Jun 22 14:12:53 ogra_: i still believe we should enable serial console output by default Jun 22 14:16:51 that wont help anymore Jun 22 14:17:14 why? Jun 22 14:17:23 we are just in the process to switch to full live images, serial wont gain you anything there Jun 22 14:18:00 and how do we debug problems during installation? Jun 22 14:18:04 (upstart doesnt enable serial by default so you wont have a login, quiet and splash are set as default so you wont get much kernel output) Jun 22 14:18:24 oh, for debugging you just dump an uEnv.txt in place Jun 22 14:18:37 with the cmdline you want Jun 22 14:19:31 ogra_: so, i;m trying the daily image installation Jun 22 14:19:38 ogra_: omap3 on a beagle xm Jun 22 14:19:41 but that wont get you anywhere with a live image Jun 22 14:19:52 since the installer doesnt run on serial Jun 22 14:20:02 ogra_: i modifided boot.scr to have srial output Jun 22 14:20:11 and it's X failing Jun 22 14:20:21 right, you can just use uEnv.txt nowadays Jun 22 14:20:29 no need for fiddling with mkimage etc Jun 22 14:20:50 lucky you, for me it didnt boot (with A1 at least) Jun 22 14:21:01 daily from today Jun 22 14:21:09 so maybe we can fix it Jun 22 14:21:19 yeah, but there werent any omap related changes, were there ? Jun 22 14:21:21 eutehr something screwed in the kernel (omapfb&c) Jun 22 14:21:32 well, we passed from 3.4 to 3.5 Jun 22 14:21:42 so, everything could have happened Jun 22 14:22:00 ah, well, i'll try an omap image on monday, currently i'm focused to get omap4 live working Jun 22 14:22:01 ok, let's do that Jun 22 14:22:22 btw, can you get a new sd card and try an old P release on that panda? Jun 22 14:22:32 why a new SD card ? Jun 22 14:22:32 i wonder if video output is ok Jun 22 14:22:43 or rewrite it, whatever Jun 22 14:22:51 i mean, don't dump your installation Jun 22 14:22:54 i teasted all püanda images during precise development Jun 22 14:22:58 well, all milestones Jun 22 14:23:09 including the final reelase Jun 22 14:23:16 there were no issues at all Jun 22 14:23:36 (and you asked me to test the precise kernel when my A1 image didnt work if you remember) Jun 22 14:24:08 downgrading to the precise kernel fixes everything here Jun 22 14:25:35 ah, when was last time you had a working video kon that? Jun 22 14:25:38 because Jun 22 14:25:41 http://www.kernelhub.org/?msg=30802&p=2 Jun 22 14:25:50 there was a window of time Jun 22 14:26:02 where you could destroy your video output Jun 22 14:37:35 reboot Jun 22 14:51:25 what are the differences between ubuntu and linaro ( particularly omap3 , SGX) Jun 22 14:53:01 linaro takes snapshots of the ubuntu archive and rolls monthly images from them Jun 22 14:53:34 on top of that they include their imporvements that will soon land in the ubuntu archive ... Jun 22 14:53:55 they dont support their images though ... no security fixes updates etc Jun 22 14:55:11 so you get an image with outdated (or the same) SW from the last ubuntu release but with added linaro sweetness on top (toolchain fixes, other kernels, bootloaders etc) Jun 22 14:57:13 ok, that clears a lot up Jun 22 14:57:28 hello ogra_ did you wrote rootstock tool? Jun 22 14:57:49 Tinti, yes, but its dead since over a year now Jun 22 14:58:07 was Tinti the gumstix guy earlier? Jun 22 14:58:29 I saw, I want to start developing in linaro do you have any advices or tools that I should use? Jun 22 14:59:00 ask in #linaro ? :) Jun 22 14:59:04 cvanvliet, no I am Tinti for a long time :) Jun 22 14:59:17 I think I jumped to conclusion Jun 22 14:59:26 sorry long night :/ Jun 22 15:00:05 in fact I am there but I am not getting much things ... in fact I would like to get recommendations from you. probably you have switched from rootstock to something else right? Jun 22 15:01:00 nope Jun 22 15:01:26 rootstock was never actually used anywhere in ubuntu, it was just a script combining a lot of hacks Jun 22 15:01:56 to roll a rootfs you can use live-build ... and i think there are a ton of linaro tools to create images Jun 22 15:02:26 so best ask in linaro (we dont use these tools either in ubuntu, #linaro is a better place to ask about this) Jun 22 15:02:35 yes there are, I was thinking in use it Jun 22 15:02:59 are they any tutorials to get 12.04 armel up an running? Jun 22 15:03:48 well, there are installation howtos for the official images Jun 22 15:03:50 yeah thanks. I need to compile an environment for iMX51 Jun 22 15:04:07 I would like to do it from scratch in fact Jun 22 15:04:16 ogra_: Around now... Jun 22 15:04:22 ogra, I have tried most of these (they all seem beagle based)? Jun 22 15:04:48 infinity, so i will switch the crontab to roll live images for omap, omap4 and mx5 today Jun 22 15:04:59 infinity, what do we do about preinstalled server ? Jun 22 15:05:22 ogra_: We leave it as-is for now. Jun 22 15:05:22 cvanvliet, I really would like to have this Jun 22 15:05:23 i dont want to introduce alternate again Jun 22 15:05:27 ah, cool Jun 22 15:05:35 ogra_: If x86 server switches to live, we'll follow suit. Jun 22 15:05:49 cvanvliet, right, they are either beagle, panda or freescale mx5 based Jun 22 15:05:52 netboot, server image (armhf), build up form ubuntu core, qemu-debootstrap Jun 22 15:05:53 ogra_: Most sane server users install from d-i netboot anyway, regardless of the platform. Jun 22 15:06:05 ogra I have a gumstix Jun 22 15:06:05 infinity, they dont switch to live, they just use a squashfs in d-i Jun 22 15:06:12 the tutorials seems to be old in fact no? Jun 22 15:06:18 at least on wiki Jun 22 15:06:29 right, server on omap or omap4 is mostly intresting as minimal dev image Jun 22 15:06:36 ogra_: That's a "live-style" install. Jun 22 15:06:44 well, its still d-i Jun 22 15:06:48 ogra_: As in, no more installing packages. Jun 22 15:06:49 :) Jun 22 15:06:52 right Jun 22 15:06:55 ogra_: ubiquity is d-i. Jun 22 15:07:06 pfft, yeah Jun 22 15:07:12 I see this as "text ubiquity". :P Jun 22 15:07:28 k ... so i wont touch server ... thats good Jun 22 15:07:40 wrt install speed live is pretty horrid btw Jun 22 15:07:59 especially the partitioner takes like 5min after you clicked anything Jun 22 15:08:16 my test install took about 90min until it failed in the bootloader install Jun 22 15:08:21 That seems odd. Jun 22 15:08:28 The 5m partitioner thing, I mean. Jun 22 15:08:36 I expect the copy to be slow, not much else. Jun 22 15:08:40 thoguh i'm trying out the slowest HW combo i can atm Jun 22 15:08:51 Oh, installing to a USB stick? Jun 22 15:08:53 ogra, the live installs ar armhf? I assume Jun 22 15:09:00 i.e. installing to an SD in a cardreader as target Jun 22 15:09:09 cvanvliet, everything is armhf Jun 22 15:09:15 we dropped armel last release Jun 22 15:09:16 yep Jun 22 15:09:37 armel is dropped after precise ? Jun 22 15:09:47 while the archive is still there it is currently largely unmaintained and we dont roll any images for that arch Jun 22 15:09:56 cvanvliet: We didn't ship armel images for precise either. Jun 22 15:10:05 cvanvliet: Just netboot images (which we still ship). Jun 22 15:10:07 there is a core though Jun 22 15:10:11 and its likely it will be completely dropped before final release Jun 22 15:10:30 infinity, it wont find my ethernet Jun 22 15:11:25 file a bug and ask for the NIC driver module to be included in the installer Jun 22 15:11:34 (file it against linux and debian-installer) Jun 22 15:12:48 We might not have the driver at all, if this is an SoC we don't support. Jun 22 15:13:01 gumstix ? Jun 22 15:13:06 should all be in mainline Jun 22 15:13:07 Or a device. Jun 22 15:13:15 ok Jun 22 15:13:46 the base is a Tobi board Jun 22 15:14:20 never heard of that Jun 22 15:16:01 I have to reconsider somethings now (re support of armel) Jun 22 15:16:47 wish they would just release the drivers for armhf Jun 22 15:17:06 they will at some point, all distros are switching Jun 22 15:20:01 I feel that way to, but, I am trying to find the best tools for use (this is for my business) Jun 22 15:21:41 ppisati, hmm, https://lists.ubuntu.com/archives/ubuntu-release/2012-June/001440.html only talks about a 3.4 tilt kernel Jun 22 15:22:02 cvanvliet: Just keep pestering people in #beagle until an sgx drop appears, and let me know? ;) Jun 22 15:22:21 infinity, you will know within seconds Jun 22 15:22:46 I may also try Imagination (the powervr guys) Jun 22 15:22:55 We have PVR on armhf. Jun 22 15:23:06 Err, for omap4, that is. Jun 22 15:23:10 just not for the chip in the beagle Jun 22 15:23:12 YOu could just switch SoCs. :) Jun 22 15:23:12 they are in the UK, and may have a symapthetic ear for a UK startup :p Jun 22 15:23:18 sorta Jun 22 15:23:46 that was my thinking above in my reconsider Jun 22 15:23:58 I suspect they won't do much for you. Their licensees are the ones who are responsible for code drops. Jun 22 15:24:08 (In this case, TI) Jun 22 15:24:30 ok Jun 22 15:24:37 ogra_: it's a 3.4 + all linaro stuff Jun 22 15:24:55 ah, k Jun 22 15:25:20 ndec: AFAYK, FB_OMAP + DSS is enough to get decent video support for omap3, right? Jun 22 15:25:33 ndec: and what about DRM_OMAP? Jun 22 15:25:45 well, i think robclark tested DRM_OMAP on beagle... Jun 22 15:25:46 ndec: DRM_OMAP and FB_OMAP can't live together Jun 22 15:25:58 if that works, that's what we should be using i think... Jun 22 15:26:02 ppisati, and very very likely three tons of commandline options you need to set to even see a single pixel :) Jun 22 15:26:12 I may be wrong but omap4 is not industrial grade Jun 22 15:26:18 if not five tons Jun 22 15:26:25 (metric tons) Jun 22 15:26:32 cvanvliet: Define "industrial grade". Jun 22 15:26:35 the problem is that, FB_OMAP i get /dev/fb, right? Jun 22 15:26:50 while with DRM_OMAP do i need an external video driver? like pvr or what? Jun 22 15:26:54 well, fb0 Jun 22 15:27:08 but yeh, that should be the difference Jun 22 15:27:20 infinity, that was the answer I got form our supplier, only yesterday, I have to follow that up Jun 22 15:27:22 (for details ask koen in #beagle ;) ) Jun 22 15:27:42 w/ omapdrm you will get a /dev/fb0 as well.. and xf86-video-omap will work without pvr (but without accel) Jun 22 15:28:05 cvanvliet: I mean, what do you mean by "industrial grade". Are you building life-and-death-critical systems, telco backbones...? Jun 22 15:28:08 robclark: so, which one is better/the right one? DRM or FB_OMAP? Jun 22 15:28:25 robclark, on omap3 ? Jun 22 15:28:26 cvanvliet: Or is it just about wanting "reliable parts"? In which case, omap4 seems to be good enough for Amazon and HP (and many others). Jun 22 15:28:49 ogra_: He claims all the way back to omap2, though not tested. ;) Jun 22 15:28:58 heh Jun 22 15:29:43 ogra_, it should work on omap3.. admittedly it gets tested more on omap4, but I'll fix bugs if there are any on omap3 Jun 22 15:30:39 infinity, some of the o3 based parts (and other various parts) are avail in industrial package for harsh environments Jun 22 15:30:58 robclark: Ahh, kay. Jun 22 15:31:11 robclark: Again, I'm curious if that's actually what cvanvliet needs. Jun 22 15:31:12 infinity, yeah our supplier is generally in that area, and we may be at a later point, but not right now. Jun 22 15:31:41 but, they already haev a product, very similar to what we need Jun 22 15:32:00 so we don’t have the engineering costs Jun 22 15:32:12 and we can tweak it a little Jun 22 15:32:34 to suite our stuff, it is based on omap3 (igep boards) Jun 22 15:33:47 infinity, it is more which is the easiest (and cheapest ) way for a self backed start up :) Jun 22 15:34:34 cvanvliet: Absolutely. Build-your-own hardware isn't a sane way to startup, unless your business model is, in fact, designing hardware. Jun 22 15:34:34 but our stuff is not life or death, that is for sure Jun 22 15:35:53 so that is why I want 12.04, armel, SGX in omap3 Jun 22 15:36:15 we do a lot of 3d display Jun 22 15:37:24 cvanvliet: Check. Well, we'd all prefer if we could make that be armhf (but until we see an sgx driver, meh), but there's certainly no one stopping you from using 12.04 armel. It's not "officially supported", but it's not going away for 5y either. Jun 22 15:38:18 i just need to get it going ;) Jun 22 15:38:52 infinity, we make things like hawk-eye for sports Jun 22 15:39:20 cvanvliet: Sounds fun. Jun 22 15:39:40 accelerometers, forceplates, camera etc Jun 22 15:39:53 starting in golf industry Jun 22 15:40:30 Sounds like an industry where price-point isn't dead critical, and omap4 might be viable. Jun 22 15:40:36 yes Jun 22 15:40:38 (And I can't think insane durability is important either) Jun 22 15:41:12 Not that I'm recommending you start from scratch. :P Jun 22 15:41:20 Depends on if you are hitting the device with a driver. Jun 22 15:41:28 we have enough to do as it is Jun 22 15:41:30 Starting from scratch every 6 months leads to Duke Nukem Forever disease. Jun 22 15:41:52 Most electronics don't take well to being clubbed. Jun 22 15:41:53 * ogra_ prefers hiting devices with wrenches Jun 22 15:42:16 GrueMaster, Xbee plus arduino can fly 30 metres ;) Jun 22 15:42:36 when gaffa tape breaks on a golf club :p Jun 22 15:42:50 Heh Jun 22 15:42:52 drivers look so new-rich ... wrenches are more "male" :) Jun 22 15:43:05 uhm Jun 22 15:43:13 is it normal for my board to use fbdev? Jun 22 15:43:20 yes Jun 22 15:43:25 well Jun 22 15:43:32 on all arm boards Jun 22 15:43:36 X says i'm having a 1280x720 display Jun 22 15:43:43 but to me it looks like 640x480 Jun 22 15:43:47 (until we are installing SGX or whatever) Jun 22 15:43:56 thats omap3 ? Jun 22 15:43:59 yes Jun 22 15:44:09 well, as i said, three tons of cdmline options Jun 22 15:44:33 i'm using FB_OMAP here Jun 22 15:44:44 with Jun 22 15:44:46 vram=12M omapfb.mode=dvi:1280x720MR-16@60 Jun 22 15:44:51 isn'it enough? Jun 22 15:44:57 and what do we use for our installer? Jun 22 15:45:06 nothing Jun 22 15:45:16 so how does it work? Jun 22 15:45:24 we always asked the kernel team to set a proper default :P Jun 22 15:45:43 uh? Jun 22 15:46:03 and with the merge of omap in mainline that default should have been carried over Jun 22 15:46:20 it likely wasnt though and we need to set a cmdline option again to get a proper mode Jun 22 15:46:43 i remember in the first images we had omapfb.mode=dvi:1280x720MR-16@60 Jun 22 15:46:56 but i'm not even sure the option is still called like that Jun 22 15:47:12 it is, just not for omapdrm/kms.. Jun 22 15:47:47 Note that the above setting is for wide screen. Looked like crap on my 19" standard LCD monitors. Jun 22 15:47:50 well, he built with FB_OMAP Jun 22 15:48:00 yeap, so it should work. ;) Jun 22 15:48:01 not DSS Jun 22 15:48:09 I used 1280x1024. Jun 22 15:48:16 so, in P we were using FB_OMAP Jun 22 15:48:24 so, either we passed something in the cmdline Jun 22 15:48:35 or i don't know Jun 22 15:49:25 * ppisati trying with a kernel with FB_OMAP Jun 22 15:49:26 once it's up, can you access /proc/cmdline... Jun 22 15:49:44 rcn-ee: talking about the installer Jun 22 15:50:33 the older d-i? or the live-cd thing.. Jun 22 15:50:51 ogra@nusakan:~/branches/debian-cd$ grep omapfb tools/boot/quantal/post-boot-armhf+omap Jun 22 15:50:51 v_opts="vram=12M omapfb.mode=dvi:1280x720MR-16@60" Jun 22 15:50:54 the one that we use with the preinstalled-omap image Jun 22 15:51:02 ppisati, you are right, we do set it on omap3 Jun 22 15:51:08 ok, cool Jun 22 15:51:18 probably needs some adjustments Jun 22 15:51:57 Too bad it can't do autodetect. Jun 22 15:52:18 i was promised autodetection for ages Jun 22 15:52:35 it was set to that, since the default u-boot value was so small.. http://git.denx.de/?p=u-boot.git;a=blob;f=include/configs/omap3_beagle.h;hb=HEAD#l229 Jun 22 15:52:42 a bitz longe than i was promised unity 3d on arm (which only twook 2 years) Jun 22 15:52:57 actually autodetection works pretty good with v3.3/3.4 (omapdrm/kms) on the beagle. ;) Jun 22 15:53:24 "pretty good" ? Jun 22 15:53:34 like every tenth time ? on every second board ? Jun 22 15:53:40 or is it already reliable Jun 22 15:53:45 rcn-ee: so, what's the difference between drm and fb_omap? Jun 22 15:53:50 works on my 4-5 monitors.. (but until recently it wasn't stable enough to push to all users) Jun 22 15:54:21 both use omapdss internally. ;) Jun 22 15:55:02 ppisati, you better ask robclark, he wrote alot of the omapdrm/kms stuff.. i just enable/tweak it... Jun 22 15:56:02 robclark: ^ Jun 22 15:56:35 omapfb is using old fbdev driver infrastructure/interface.. omapdrm is using drm/kms.. Jun 22 15:56:48 short version, w/ omapdrm you can get xrandr Jun 22 15:57:13 (and dri2, hotplug detection, etc) Jun 22 15:57:19 well, if its stable i'm all for switching Jun 22 15:57:56 robclark: any drawback? Jun 22 15:58:11 btw, just compiled in fb_omap, X is up, but i don't have any output Jun 22 15:59:38 well.. omapdrm is newer... sometimes exposes some issues in omapdss, relies on monitors to have sane EDID (although more recently there is some drm bootargs added to allow reading EDID from firmware file to deal with broken monitors) Jun 22 16:03:28 omapfb omapfb: no driver for display: dvi Jun 22 16:03:30 uhm Jun 22 16:03:55 ppisati, this is 3.4 or 3.5? Jun 22 16:04:03 3.5 Jun 22 16:04:39 ah, haven't figured that one out yet, it was broken in rc3 last tried, sorry.. Jun 22 16:05:17 rcn-ee: are you saying fb_omap is broken somehow? Jun 22 16:06:36 with 3.5-rc3, it oppes'ed on my beagle_xm, and the display didn't come up, didn't dig into to much as i'm mostly on 3.4.x at the moment.. but the stuff for rc4 probally fixed that.. Jun 22 16:43:20 this time fb seems to be ok Jun 22 16:43:25 fbcvt: 1280x720@60: CVT Name - .921M9-R Jun 22 16:43:34 but i still get an ugly 640x480 Jun 22 16:43:47 any idea how to debug this? Jun 22 16:55:29 ppisati: What does xdpyinfo thing the resolution is? And does your monitor display the incoming signal info? Jun 22 17:18:19 ogra_: edid autodetection should work on omap3 just fine Jun 22 17:18:29 it was supported by upstream since 3.2 I believe Jun 22 17:20:28 if you're using omapfb with panel-dvi you should also get edid detection Jun 22 17:21:05 rsalveti: panel-dvi? Jun 22 17:21:30 CONFIG_PANEL_DVI Jun 22 17:21:40 drivers/video/omap2/displays/panel-dvi.c Jun 22 17:21:58 this is based on an implementation I had for quite a while ago Jun 22 17:22:10 rsalveti: it seems they killed it in 3.5 Jun 22 17:22:32 ls -la drivers/video/omap2/displays/*dvi* | wc -l Jun 22 17:22:33 0 Jun 22 17:22:43 could be, let me check Jun 22 17:23:01 omapdrm should probably be replacing most of the stuff Jun 22 17:23:18 trying that right now Jun 22 17:25:07 PANEL_TFP410? Jun 22 17:26:36 ok, it was renamed Jun 22 17:33:42 ppisati: yup Jun 22 17:34:49 rsalveti: so i assume i need to change cmdline too Jun 22 17:35:09 rsalveti: from omapfb.mode=dvi:1280x720MR-16@60 to omapfb.mode=tfp410:... Jun 22 17:36:41 btw, enabling DRM_OMAP didn't give me any /dev/fb*, what's wrong? Jun 22 17:36:43 robclark: ^ Jun 22 17:38:36 ppisati, if using omapdrm, then omapfb.mode won't do anything.. but you also shouldn't need it.. Jun 22 17:38:53 but possibly the kernel is not registering the platform device? Jun 22 17:39:00 ppisati: you don't need any cmdline for this panel as well Jun 22 17:39:19 wait Jun 22 17:39:36 * robclark wonders what kernel we are talking about? Jun 22 17:39:57 robclark: didn't you say that with DRM_OMAP we would get a /dev/fb, right? Jun 22 17:40:19 robclark: foerget about the omapfb stuff, i'm testing DRM and FB_OMAP in parallel Jun 22 17:40:25 3.5rc3 Jun 22 17:40:35 yes, you will.. but only if the driver is loaded (which it won't be if the device is not registered) Jun 22 17:40:44 if pure upstream kernel, there is one patch you need Jun 22 17:40:55 robclark: it's pure upstream Jun 22 17:41:02 k, hang on Jun 22 17:41:48 rsalveti: on the other hand, with FB_OMAP we always passed omapfb.etcetc Jun 22 17:42:03 ppisati: but it's not needed with this panel, afaik Jun 22 17:42:12 rsalveti: uhm ok Jun 22 17:42:14 ppisati, http://permalink.gmane.org/gmane.linux.ports.arm.omap/77544 Jun 22 17:43:18 robclark: ack, i'll try Jun 22 18:55:15 robclark: added your patch on top of 3.5rc3, got /dev/fb0 but still no output Jun 22 18:55:41 anywa, i'm off for the day Jun 22 18:56:14 ppisati, I guess next step, turning on omapdss.debug=1 and possibly drm.debug=7 in bootargs and then start havign look at the log Jun 22 19:24:18 hello people.... Jun 22 19:25:10 anyone here work at ARM? :P **** ENDING LOGGING AT Sat Jun 23 02:59:58 2012