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