[09:26] <angs> I have some boards that runs debian and some of them runs ubuntu. How can I understand which one is ubuntu and which one is debian? uname -a shows "Linux omap 3.2.0-psp7 #1 Fri Apr 13 04:55:05 UTC 2012 armv7l armv7l armv7l GNU/Linux"
[09:27] <rbasak> angs: on Ubuntu, "lsb_release -a" will tell you. I don't know if there's a better way.
[09:27] <angs> thanks a lot, it shows it is ubuntu:)
[11:15] <djszapi> ogra_: hey
[11:16] <djszapi> ogra_: gpio library is not available for Ubuntu arm ? :o
[11:18] <djszapi> perhaps it is the sysfs that is advertised for usage nowadays.
[13:13] <janimo> lilstevie, do you know if there are git trees of tf101 kernels with better history and changes rationale than what ASUS' tarballs provide?
[13:13] <lilstevie> janimo, yes/no
[13:13] <janimo> lilstevie, please expand on the yes branch :)
[13:14]  * janimo figures this is an interactive adventure
[13:14] <lilstevie> janimo, we can match to where they most likely branched from nvidias tree
[13:14] <lilstevie> with their history
[13:14] <lilstevie> but asus themselves strip *ALL* history before releasing it
[13:15] <janimo> lilstevie, that is what I was going to check, seeing only it is a 2.6.39.4
[13:15] <janimo> but compared to upstream pristine linux-stable 2.6.39.4 there
[13:15] <janimo> is a 15Mb patch :)
[13:15] <lilstevie> yeah, well matches with nvidias android tree
[13:15] <lilstevie> look at androids 2.6.39.4
[13:15] <lilstevie> it is a pain though
[13:15] <lilstevie> cause there are a few tags
[13:16] <lilstevie> RaYmAn has a script which diffs each tag against the asus release and suggests the closest match
[13:17] <lilstevie> we have done it to the tf201, tf101 is next on the list to be moved over to nvtegra
[14:17] <janimo> lilstevie, by moved over to nvtegra and 'we' what do you mean? Kernels used by the mod community?
[14:44] <lilstevie> androidroot team, me bumble-bee RaYmAn kmdm and IEF
[14:44] <lilstevie> janimo, ^^
[14:47] <janimo> lilstevie, ok
[16:34] <xase_> I cant believe theres no tutorials for running ubuntu on nookcolor besides  that silly chroot nonsense.
[16:39] <prpplague> hehe
[17:20] <GrueMaster> xase_: I was going to work on that for Oneiric, but was swamped with the arm server bringup.  Sadly, I have since moved on to a differnt job (and subsequentially lost time/interest).  Sorry.
[17:51] <xase_> GrueMaster: no problem do you have an archive of your work available?
[17:53] <GrueMaster> No.  I didn't get too far into it.  I barely spent a week on it, mainly going through the Nook source and seeing what I needed to implement.
[17:56] <xase_> damn
[19:17] <janimo> marvin24, are you working more on nvec until it gets out of staging?
[19:21] <marvin24_DT> janimo: yep
[19:22] <janimo> marvin24, do you have the docs from nvidia?
[19:22] <marvin24_DT> yes
[19:22] <janimo> the README in the tree suggests there are no docs at all
[19:22] <marvin24_DT> oh, that deserves a patch ;-)
[19:23] <marvin24_DT> in fact, I "appeared" some month ago
[19:23] <janimo> ok, just making sure you're not missing out :) I just discovered they're public last week, and downloaded them today
[19:23] <marvin24_DT> together with the tegra2/3 documentation
[19:23] <janimo> yes, Nov 11 from what I saw
[19:23] <marvin24_DT> janimo: public?
[19:23] <janimo> ah tegra3 as well? I thought that's still WIP
[19:23] <marvin24_DT> you need to register first ...
[19:24] <janimo> well, public with annoyance, but not private/NDA etc :)
[19:24] <marvin24_DT> mmh, I think there is a NDA at least, but I didn't read it to the end
[19:25] <janimo> marvin24, so this means the EC doc that was floating around of the chip used in the ac100 is not necessary, as you only need the tegra2 side/protocol
[19:25] <janimo> ah did not read either :)
[19:26] <marvin24_DT> mmh, I don't know of any EC doc floating around ... wait
[19:27] <marvin24_DT> ah, found it
[19:31] <marvin24_DT> of course, for this has no NDA ;-)
[19:31] <marvin24_DT> normally, you would have to register here http://developer.nvidia.com/tegra-2-technical-reference-manual
[19:42] <janimo> yes, I registered and downloaded this and the TRM today
[19:42] <janimo> there was an EC doc for an embedded keyboard controller in the ac100 last year
[19:42] <janimo> which I was told was the only doc that helped the nvec initial development
[19:42] <marvin24_DT> maybe that was the original source
[19:43] <marvin24_DT> it had some documentation inside
[19:46] <marvin24_DT> janimo: can you try to get linux-backports-modules-cw-3.3-precise-generic building on ARM ?
[19:46] <janimo> is that a package?
[19:46] <marvin24_DT> eh, no, the binary
[19:46] <marvin24_DT> wait ...
[19:46] <janimo> found it
[19:47] <janimo> but it's for the 3.2.0 precise kernel
[19:47] <marvin24_DT> linux-meta is the source :-(
[19:47] <marvin24_DT> should be buildable on any kernel
[19:47] <janimo> not even amd64 is enabled
[19:48] <marvin24_DT> I have it here on my amd64 ...
[19:48] <marvin24_DT> https://launchpad.net/ubuntu/precise/amd64/linux-backports-modules-cw-3.3-precise-generic
[19:48] <janimo> ok, so Architecture: is misleading
[19:49] <janimo> linux-backports-modules-3.2.0 the package
[19:49] <janimo> marvin24, which drivers are needed on arm?
[19:50] <marvin24_DT> I don't know, but paz00 needs rt2xx
[19:50] <marvin24_DT> I think they can also be useful for panda whatever
[19:52] <marvin24_DT> the package contains all wifi drivers
[19:54] <marvin24_DT> btw, I still can only get a 3.1 kernel booting with "console=ttyS0,115200n8 quiet" enabled
[19:54] <marvin24_DT> this ensures nothing it printed to the console on boot
[19:55] <janimo> so not yet ready for uploading I guess? Any chance of newer kernels being better?
[19:55] <janimo> how much of what's working now is not yet ported to 3.5?
[20:13] <marvin24_DT> everything gpu and power save related is missing
[20:13] <marvin24_DT> (which is too important to be skipped)
[20:13] <janimo> marvin24, are the changes in 3.5 too big so that code need significant rewrite?
[20:14] <janimo> I see nvidia devs steadily sending patches upstream
[20:14] <marvin24_DT> yeah, still unportable I think
[20:14] <marvin24_DT> there are lots of nv engineers already working on it
[20:14] <marvin24_DT> but it takes time
[20:15] <marvin24_DT> somehow nv decided to rewrite everything at least three times
[20:15] <marvin24_DT> this is the price you have to pay to get a product quickly to market
[20:16] <marvin24_DT> you just cannot do it in a sane way
[20:16] <marvin24_DT> and mainlining is only low priority compared to that
[20:17] <marvin24_DT> I don't want to know how many developers worked on porting win8 to tegra3
[20:18] <marvin24_DT> and even less I want to see that code
[20:18] <janimo> :)
[20:19] <janimo> in that case they may not rewrite at all as there's no mainlining required ever, and win8 will be around for many years
[20:19] <janimo> maybe it's only the FOSS model that gives grief to developers. Or at least this type of grief
[20:21] <marvin24_DT> I would be interested in some kind of statistics how much developer month it takes to port some arch to linux and windows
[20:21] <marvin24_DT> and how much time it consumes to maintain it
[20:21] <marvin24_DT> during product lifetime
[23:31] <lilstevie> marvin24, tbh because of UEFI, it would be more the UEFI code that you would want to see less :p