[02:25] <infinity> ogra_: Reviewed and accepted.
[02:25] <infinity> ogra_: A bit shocked that those drivers don't both ship in the same tarball (or even just as the same driver), but whatever.  nvidia never ceases to confuse.
[03:09] <lilstevie> infinity, heh that is nvidia for you, I'm not even quite sure what the difference between the T2 and T3 pack is yet
[07:38] <marvin24> lilstevie: the avp firmware is different, but that's also a different tarball ...
[07:44] <lilstevie> marvin24, yeah I know the avp firmware is, but that is cause the avp is different in general from what we have seen
[07:45] <lilstevie> marvin24, but the acceleration xorg driver and libs that you guys package up for the ac100 work just fine on the tf201
[08:22] <marvin24> lilstevie: the original tar gz (for up to abi 12) contains a lot more
[08:22] <marvin24> e.g. kernel, bootloader, ...
[08:22] <marvin24> abi13 driver was released as a single tegra_drv.so (which is identical for tegra2/3)
[08:45] <lilstevie> marvin24, oh yeah, bootloader and stuff could easily go in the same tarball though
[08:45] <lilstevie> given size is not big
[09:20] <marvin24> maybe customers may get confused if they see more than one kernel ;-)
[09:44] <lilstevie> maybe
[09:44] <lilstevie> although that would be a little troubling :p
[13:28] <wookey> infinity: my build is failing with ../sysdeps/unix/sysv/linux/init-first.c:102:1: sorry, unimplemented: function profiling
[13:28] <wookey> and indeed it is unimplemented. Where do I turn it off for the arm64 build?
[13:29] <wookey> (eglibc)
[13:33] <wookey> aha debian/sysdeps/arm64.mk looks plausible. --disable-profile
[14:29] <doko> ogra_, is the openscenegraph ftbfs on arm the gl/gles problem?
[14:29] <ogra_> dunno, i didnt even know it ftbfs
[14:29] <doko> asking because a whole lot of things b-d on it
[14:30] <ogra_> (/me is on a special forces project until UDS ... so i didnt follow the ftbfs list)
[15:15] <janimo> marvin24, what's the prospect of ac100 being all mainlined, any ETA?
[15:15] <janimo> any blockers still?
[15:15]  * janimo hopes it's there by 13.04 :)
[15:15] <marvin24> janimo: it is (all) mainlined for over a year now
[15:15] <marvin24> unfortunately, tegra2 support isn't ...
[15:16] <marvin24> I would also prefer to move to mainline for 13.04
[15:16] <marvin24> we already lost supend with 3.1, so it shouldn't matter if we lose some more stuff ;-)
[15:17] <janimo> marvin24, well I mean ac100 support as in working out of the box :)
[15:17] <janimo> and your insight on where the tegra2 upstreaming stands
[15:18]  * ogra_ doesnt think there is anything gfoing on wrt upstreaming the tegra2/3 bits
[15:19] <ogra_> especially in the light that they are mostly developed for android which uses snapshot kernels
[15:20] <ogra_> as long as android moves with that practice i doubt we'll see changes here
[15:20] <marvin24> janimo: it works out of the box if you add the drm driver
[15:21] <marvin24> ogra_: wrong, e.g. today lp2 support was added for tegra3
[15:21] <ogra_> ah, nice
[15:21] <marvin24> I think tegra2 has it already
[15:21] <janimo> what's lp2
[15:21] <ogra_> well, they still build their binary drivers against a special kernel tag usually
[15:21] <marvin24> but I haven't looked lately
[15:22] <ogra_> and i doubt that will change in the short term
[15:22] <ogra_> marvin24, janimo's dream is to use mainline for ac100 (and other tegras) in 13.04
[15:22] <marvin24> ogra_: tegra drm will likely come to staging in 3.8
[15:23] <ogra_> when is 3.8 due ?
[15:23] <marvin24> and "they" already made some changes to mainline to get their propietary driver working
[15:23] <janimo> 6 mo probably
[15:23] <ogra_> early 20013 ?
[15:23] <ogra_> oops
[15:23] <marvin24> no, we are not that slow
[15:23] <ogra_> didnt mean to exaggerate that much :)
[15:23] <marvin24> ;-)
[15:24] <marvin24> so we will endup in a situation where both drivers are supported
[15:24] <marvin24> the open one likely without any 3d or video accel
[15:24] <ogra_> thats fine
[15:24] <ogra_> and thats how i use the closed one atm :)
[15:24] <marvin24> I hope I didn't look too deep into the glass
[15:25] <ogra_> on my ac100 at least
[15:26] <lilstevie> yeah, O cam
[15:26] <lilstevie> er
[15:27] <lilstevie> I can't say I use the 3D and video accel on my prime either
[15:29] <ogra_> well, and what for :)
[15:29] <ogra_> there isnt really much thats built for GLES
[15:36] <lilstevie> ogra_, yeah, and I really don't watch videos on my prime anyway
[16:05] <ppisati> ogra_: by any chance, did you try Q on your beagle?
[16:05] <ogra_> nope
[16:05] <ppisati> ok
[16:06] <ppisati> anyway, problem found and fix too
[16:06] <ppisati> i'll send a pull req tonight
[16:06] <ppisati> (after gym)
[16:06] <ogra_> ppisati, you rock !
[16:06] <ogra_> will test with the fix then
[21:02] <sakoman_> was the CONFIG_HIMEM issue on Pandaboard ever resolved?
[21:03] <sakoman_> (i.e. random crashes when trying to do a kernel build if CONFIG_HIMEM was set)
[21:04] <ogra_> ogra@panda:~$ grep HIGHMEM /boot/config-3.5.0-211-omap4
[21:04] <ogra_> # CONFIG_DEBUG_HIGHMEM is not set
[21:04] <ogra_> CONFIG_HIGHMEM=y
[21:05] <ogra_> we have it enabled since a while, so yes
[21:05] <ogra_> at least in 12.04 and 12.10 it should be fine
[21:05] <sakoman_> do you recall what the issue root cause was?
[21:05] <ogra_> no, but there was a bug
[21:05] <sakoman_> I'm working on another OMAP4 based system and it too has random crashes if HIMEM is enabled :-(
[21:06] <sakoman_> running 3.6
[21:06] <ogra_> bug 633227
[21:06] <ubot2> Launchpad bug 633227 in linux-ti-omap4 "instabilities with highmem activated" [High,Fix released] https://launchpad.net/bugs/633227
[21:06] <ogra_> we use 3.5 in 12.10, seems pretty solid
[21:07] <ogra_> but we dont use mainline. mind you
[21:10] <sakoman_> hmmm . . . not really clear from that bug exactly what fixed the problem :-(
[21:17] <GrueMaster> What ever became of devicetree for arm?  I'm reading articles covering the 3.7 kernel, and they don't even seem the same.
[21:57] <rsalveti> sakoman_: I don't think we got to the point of finding exactly what was the patch that fixed the issue
[21:57] <rsalveti> I believe that at some point it just worked as expected
[21:58] <tinti> Hi, can someone give me a hint about how to debug linux kernel boot without JTAG? I was thinking in use early_printk and try to use usb debug
[23:58] <wookey> tinti: DEBUG_LL is useful in early linux boot
[23:58] <tinti> wookey: thanks :)
[23:58] <wookey> maybe that's what's called early_printk these days
[23:58] <wookey> it writes direct to serial port
[23:59] <wookey> or probably USB these days, as no-one has serial ports anymore