/srv/irclogs.ubuntu.com/2009/07/14/#ubuntu-kernel.txt

=== bjf is now known as bjf-afk
billybigriganyone know why i can't build the nvidia module?00:20
billybigrigbillybigrigger@cabo:~$ sudo dkms build -m nvidia -v 185.18.14 -k 2.6.31-rc2-billybigrigger-07.1300:22
billybigrigError! Bad return status for module build on kernel: 2.6.31-rc2-billybigrigger-07.13 (x86_64)00:22
billybigrig*** Unable to determine the target kernel version. *** make: *** [select_makefile] Error 100:32
billybigrigno body can answer?00:51
jjohansensmb: I have tested Jaunty on my machine now with suspend and hibernate kernel builds, no thermal problems.  But under 11.1 it goes into thermal shutdown10:33
apwjjohansen, heh thanks for the testing there10:40
smbjjohansen, that sounds good, yet unexpected. but thanks for testing :)10:40
Keybukapw: err, you didn't include the inotify patches I sent in the most recent kernel upload ?12:16
apwKeybuk, hrm, tim actually put that upload together12:17
apwok tim said "i'll apply if they don't make it into -rc3" ... 12:18
apwdid you check if they made it in via mainline ...12:18
Keybukthey aren't in mainline yet12:18
Keybukwhich is why I forwarded them12:18
apwhrm12:19
apwKeybuk, i'll look at them now12:20
apwKeybuk, is there a bug for these regressions?12:31
Keybukapw: a bug?12:32
Keybuknot in LP, I went directly to the upstream ;)12:32
apwyeah a lp bug number?  if so i'll include it12:32
KeybukI can open a bug if you like12:32
apwno need, just would use it if there12:32
apwKeybuk, you need a test kernel for these?12:33
Keybukapw: no, just a release12:33
Keybukalready tested Eric's patches for him12:33
apwok thanks12:33
apwi think i am out of the country12:34
apwin dublin.  need to confirm when i get back exactly12:35
Keybuk?12:35
apwgah wrong channel12:35
apwKeybuk, ok they are applied so they deffo make the next upload12:50
apwwill talk to tim about getting that to be soon12:50
Keybukapw: could we do an upload especially please12:50
Keybukwithout these patches, inotify is basically useless12:51
apwi am sure we can, just want to touch with him to see if there is anything else urgent12:52
apwwill start preparing it12:52
tseliotamitk: do you deal with input devices in the kernel?13:26
UnderSampledhello13:31
UnderSampledI get WARNING at /build/builddd/linux-2.6.28/kernal/smo.c:333 smo_function_mask+0x1d4/0x1e0()13:31
UnderSampledWhenever I boot into 9.04, whether that mean into a live cd, the 'check disk for errors', or after upgrading 8.10 to 9.04 after a fresh install13:33
UnderSampledoh, and the capslock and scrolllock keys blink at a constant rate13:34
UnderSampledAny Ideas?13:34
amitktseliot: not specifically13:44
tseliotamitk: I have a doubt on passing EVIOCGID to ioctl() and on using id[ID_VENDOR], id[ID_PRODUCT], id[ID_VERSION] to check the model of a touchpad13:46
tseliotamitk: would it make sense to check id[ID_VERSION] to identify a specific model when id[ID_VENDOR] and id[ID_PRODUCT] are the same for all Synaptics touchpads?13:47
tseliotnote: I called ioctl(fd, EVIOCGID, id)13:48
tseliotI would like to use it to add quirks to the synaptics driver13:50
rtg_apw, by the way, there are 2 Karmic commits with an identical log message; 6325628641e58310d93acd8f0261a76752e38544 and 14b5433606289dbc5b6fd70ced11462f80e95003. How did the first one get there? It doesn't exist in Linus tree.13:52
=== bjf-afk is now known as bjf
apwrtg_, i see the first one as a stable commit which we applied, and the second is a real upstream commit13:54
apwi see that one in my linus tree too13:55
apwi would guess it may have gotten reverted 13:55
* apw checks13:55
rtg_apw, carried forward from Jaunty? It should have disappeared13:55
apwyes, unless someone reverted the original upstreaming ... will check13:55
amitktseliot: I don't see drivers/input/mouse/synaptics.c having any ioctls13:55
apwrtg, no by extreme bad luck it applied twice13:56
apw        if (scan->channel_count == 0) {13:56
apw                IWL_DEBUG_SCAN(priv, "channel count %d\n", scan->channel_count);13:56
apw                goto done;13:56
apw        }13:56
apw        if (scan->channel_count == 0) {13:56
apw                IWL_DEBUG_SCAN("channel count %d\n", scan->channel_count);13:56
apw                goto done;13:56
apw        }13:56
apwlooks benign13:56
apwwe can drop that one on the next rebase13:56
* apw reverts it in our tree13:57
rtg_apw, it causes an error when IWL_DEBUGFS is defined.13:57
tseliotamitk: I meant the Synaptics X driver. ID_VENDOR, ID_PRODUCT and ID_VERSION are defined in input.h though.13:57
apwrtg_, yeah it looks like the number of params to IWL_DEBUG_SCAN has changed and its left behind13:57
apwjust revert it13:57
rtg_apw, why not just rebase and drop the commit altogether? It'll avoid future conflicts13:58
apwwell i guess i should13:58
apwyep, can do, after this upload?13:58
rtg_might aswell do it now13:58
apwok13:58
UnderSampledCould someone please help me trouble shoot>14:05
amitktseliot: you'll have to try it. But it seems like the model id is stored in the synaptics driver's private data structure14:08
tseliotamitk: ok, thanks14:09
amitktseliot: http://lxr.linux.no/linux+v2.6.30/drivers/input/mouse/synaptics.c#L65214:09
amitkand http://lxr.linux.no/linux+v2.6.30/drivers/input/mouse/synaptics.c#L16714:10
tseliotamitk: it says "Encode touchpad model so that it can be used to set input device->id.version and be visible to userspace"14:11
mjg59tseliot: What quirks do you want to add? Note that several cases where we'd like to add quirks (the Dell mini, for example) don't have any destinctive information in the vendor or ID fields14:13
tseliotmjg59: I know how to prevent the cursor from jumping on the Dell Mini 10v: http://bugs.freedesktop.org/show_bug.cgi?id=2161414:14
ubot3Freedesktop bug 21614 in Input/synaptics "Touchpad cursor jumps when two fingers are used" [Normal,New] 14:14
tseliotmjg59: and since that code doesn't solve the problem on all touchpads I wanted to add a quirk for the Dell14:15
tseliotand checking ID_VENDOR, ID_PRODUCT and ID_VERSION should be enough14:15
mjg59tseliot: It's not14:16
mjg59tseliot: You get identical values to the Eee14:16
mjg59Sorry, not the Eee. Some Aspire Ones.14:16
tseliotmjg59: you get identical ID_VENDOR and ID_PRODUCT because they are Synaptics but do you also get the same ID_VERSION?14:17
mjg59Yes14:18
tseliotoh14:18
tseliotmjg59: so are you saying that quirks are not possible?14:18
mjg59No, I'm just saying that you're concentrating on the wrong aspect of it14:19
tseliotok14:19
tseliotany suggestions?14:19
mjg59The ones that people are having problems with all appear to be Synaptics (as opposed to ALPS or Elantech) without two-finger detection14:19
mjg59So you could possibly just key it off that?14:20
tseliotmjg59: maybe. I need to check what my other Synaptics touchpads report.14:21
smbmjg59, While you are around, might I abuse your time with another quirk question? In that case acpi_video...14:22
smbI looked at a bug report where people had regressions with backlight control. From the acpi dump and the dmesg it looks clear that the problem is that the only acpi video device with _BCL defines a _ADR with a pci device id that does not exist. So with kernels before the check people got working backlight control (though it sounds strange) but with it they don't. 14:25
mjg59What hardware is this?14:27
smbmjg59, Are you aware of similar cases and how would be the chances for dmi quirks in that area? 14:27
smbAcer 6920G14:27
mjg59Does acer-wmi work?14:27
smbno14:27
mjg59Unfortunate14:27
mjg59Got the bug number?14:27
smbPretty much. Yep, a sec14:28
smbhttps://bugs.launchpad.net/bugs/33338614:28
ubot3Malone bug 333386 in linux "Cannot change brightness with 2.6.27-11+ kernel" [Medium,Confirmed] 14:28
=== bjf is now known as bjf-afk
smbmjg59, I would have tried with an external DSDT file but iasl explodes more or less when trying to recompile14:30
mjg59Oh, ugh. It's one of those bugs where unrelated issues have appeared.14:30
smbmjg59, Yeah, its sometimes hard to keep "my backlight does not work" outside14:32
mjg59smb: I think the user's doing something wrong when trying to use acer-wmi14:32
smbmjg59, But in the end I concentrated on the Acer and saw that _ADR for GFX0 is 0002000 while the video device seems to be 01.014:32
mjg59I can't see any way he can get permission denied if he's actually running as root, which makes me think he's doing sudo echo foo >brightness14:33
mjg59Which won't work14:33
mjg59Oh, I see, he did finally check that14:33
smbmjg59, It was part of my learning curve to find out what regressed as well. 14:33
mjg59Is he using the binary nvidia drivers?14:33
mjg59If so, brightness control gets more complicated14:33
=== bjf-afk is now known as bjf
mjg59Because they disable the SMI access that the legacy paths use14:34
mjg59The smartdimmer pins may be hooked up14:34
smbmjg59, I am not 100% sure. But as he says he has a working backlight when using the kernel just before we pulled the pci checking patch and there he had gfx0 I assume that case is good14:34
mjg59It may have worked by accident14:35
smbIt seems at least some sort of accident as the acpi information is so incorrect. I can give him a recent kernel without the check to compare. But the question is how to move on14:36
mjg59The machine will come in two forms - integrated Intel and discrete Nvidia14:37
mjg59The same DSDT is used on both14:37
smbThe next kernel update will get that laptop back into that state (unless nouveau is better at controlling the backlight without acpi support)14:37
mjg59The ACPI information appears to be for the Intel device, not the nvidia one14:37
mjg59novueau will drive the backlight if the smartdimmer pins are hooked up14:37
mjg59Assuming recent enough nouveau14:38
mjg59But he's using the binary nvidia drivers14:38
smbSomehow this accidental thing looks a bit like that T61(?) case 14:38
mjg59Yes14:39
mjg59The Radeon code on the T61 happens to work on the Intel hardware as well14:39
smbThe whole information obviously is for the wrong device but some way it works when being poked at14:39
mjg59But the correct approach is to use the opregion code in recent i91514:39
mjg59That's why the patch didn't get merged until the opregion stuff was added14:40
smbSo here is the other direction, the nvidia device seems to react on the intel defined device. The nvidia device in acpi does not define any backlight control, so the only reasonable way would be to have the nvidia driver doing something (if possible) or a bios update (guess unlikely).14:43
mjg59Correct14:43
mjg59Unless nvidia have a sideband brightness interface14:44
smbEven worse as that laptop seems to come up with extremely dimmed backlight. :/14:44
mjg59Which is possible, I haven't figured out what all of their ACPI methods do yet14:44
smbHm, a sideband brightness interface? Would that be visible in the acpi code? I am slowly digging my way into that area...14:46
mjg59Uh.14:46
mjg59I see a _BCL and _BQC in his DSDT for the nvidia device.14:47
mjg59Under PEGP14:47
mjg59And again under NVGA14:47
mjg59One of those ought to be bound14:48
smbmjg59, Arg, sorry. I believe the problem was _DOD _DOS14:48
mjg59Those shouldn't be required for brightness changing14:48
mjg59They're just the display switch hotkeys14:48
mjg59Let me look at the kernel14:48
mjg59Right, they're only under the Intel one14:49
smbGFX0 is the only one defining thoise. and acpi_video check for them to decide this is a video device14:49
mjg59Sigh.14:49
mjg59Ok, acpi_video needs fixing not to have that requirement14:49
smbo some other values which are not there14:49
mjg59But I can see why it would make that assumption14:49
smbI think it was three different set of methods. If any of those sets is there the check is good14:50
mjg59Yeah, and this doesn't have any of them14:50
smbBut _DOD, _DOS was the only set present for any device14:50
smbSo GFX0 (the intel) is the only candidate for acpi_video14:51
mjg59Yeah14:51
mjg59But the spec doesn't actually require that14:51
mjg59It should also check the children and see whether they have any backlight control methods14:52
smbSo basically backlight control gets somewhat independent of the video device itself (if that is formulated understandably)14:53
mjg59/kind/ of14:53
mjg59What's weird is that EVGA and NVGA both seem to have the same addresses14:53
mjg59Oh, wait, I think I see a minimal patch14:54
smbhasn't NVGA adr zero14:54
mjg59So does EVGA14:54
mjg59They're both children of PEGP14:54
smbOh, I see14:55
mjg59ANyway14:55
smbHm, yeah and _DOD is there for several devices, only _DOS is there once14:56
mjg59Does http://www.codon.org.uk/~mjg59/tmp/acpi_switch.diff fix it?14:56
smbI'll create a kernel with it and we will see14:57
smbI haven't got the hardware, so I need to put it into the bug report14:57
mjg59As long as that gets it recognised it looks like it'll work - the code is identical15:01
mjg59So I think I'll just submit that upstream anyway15:01
smbmjg59, Thanks for now. Somehow I missed that _DOD is present for all devices and might be used as an alternative.15:02
mjg59Ok15:02
mjg59Let me know if it works15:02
mjg59Note that it probably won't do anything for any T61 people15:02
smbmjg59, Sure. Yeah, probably this setup is different. But for the time being we can fix those with acpi_backlight=vendor and thinkpad-acpi backlight=115:03
mjg59T61 should work fine upstream15:03
mjg59You need the i915 opregion support code15:04
smbOh, likely yes. I was more referring to Jaunty which is missing that but has the check slipped in15:04
amitkNOTICE: Upcoming Ubuntu Kernel Team Meeting - Tuesday, 14th of July - 17:00 UTC i.e. Today, in about an hour in #ubuntu-meeting16:02
=== amitk changed the topic of #ubuntu-kernel to: "Home: https://wiki.ubuntu.com/KernelTeam/ || Karmic Kernel Version: 2.6.31 || Ubuntu Kernel Team Meeting - Tuesday, 14th of July - 17:00 UTC"
bjfamitk, that's in 2 hours right?16:06
amitkbjf: err, right.16:07
amitkNOTICE: Upcoming Ubuntu Kernel Team Meeting - Tuesday, 14th of July - 17:00 UTC i.e. Today, in about 2 hours in #ubuntu-meeting16:07
amitk:)16:07
UnderSampledcan someone help me with this?16:53
UnderSampledhttp://yfrog.com/5fdumpij16:53
tseliotmjg59: there must be a bug somewhere (in the kernel?) as the Synaptics driver (when testing BTN_TOOL_DOUBLETAP) reports that the touchpad of the Dell Mini 10v multi-finger detection but, as evtest shows, it's not true16:55
tseliots/multi-finger/has multi-finger/16:56
mjg59tseliot: Can you put dmesg somewhere?16:56
UnderSampledhello hggdh16:57
hggdhUnderSampled: hello16:57
tseliotmjg59: http://pastebin.ubuntu.com/218063/16:59
UnderSampledI just tried the alternate install disk, but it does the same17:01
mjg59tseliot: What kernel version are you looking at?17:01
tseliotmjg59: Jaunty's i.e. 2.6.28-11-generic17:02
mjg59Looks like it was fixed in .2917:03
UnderSampledhggdh, you said that it hasn't shown all of the information. It freazes sometime during boot, usually either before anything is displayed or with the warning somewhere on the page17:03
hggdhUnderSampled: have you looked at https://wiki.ubuntu.com/DebuggingKernelOops?17:03
UnderSampled no17:04
tseliotmjg59: ok, thanks, I'll try with .29 then17:04
hggdhUnderSampled: and, genrically, at https://wiki.ubuntu.com/DebuggingProcedures#Kernel17:04
UnderSampledhggdh: just above the warning, it shows "Kernel panic - not sycing: fatal exception in interupt"17:05
UnderSampledthen it says"---------------[   cut here   ]----------------"17:06
tseliotmjg59: do you happen to have a link to the exact commit?17:07
mjg59e42b6646a8298fe06a33a0f68dab661335f5db6e17:09
tseliotmjg59: thanks a lot. BTW the quirk works now with 2.6.2917:15
mjg59Cool17:15
rtg_Keybuk, linux 2.6.31-3.19 uploadedwith your fsnotify and inotify patches17:17
tseliotsmb: would it be possible to have that commit ^^ in Jaunty? The diff is very small: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blobdiff;f=drivers/input/mouse/synaptics.c;h=865fc69e9bc39e8ef81b213722e572c95917fb0e;hp=d349c4a5e3e84488a4e812e33e6e547aac4d97e7;hb=e42b6646a8298fe06a33a0f68dab661335f5db6e;hpb=cec87e38e92cdfe86678ca2a5c29c38d0512760117:17
Keybukrtg_: thanks17:19
smbtseliot, the patch itself looks sensible. I guess we need to get together a good reason for the impact to get a SRU17:20
rtg_cjwatson, I've narrowed down the Karmic sshd annoyance to a relatively simple scenario. The first time after boot sshd fails to fully release a connection when the client is shutting down. If you stop/start /etc/init.d/ssh then all works fine thereafter. I'll see about instrumenting the initial invocation to get some debug.17:37
cjwatsonodd - ok17:38
Sarvattthanks TheMuso, will finally be able to install from a powerpc alternate cd again without starting from intrepid and upgrading all the way -- [Config] Enable CONFIG_BLK_DEV_IDECD on powerpc17:40
amitk********* 15 min warning for meeting ******************17:46
=== Nicke_ is now known as Nicke
JFohi ogasawara 18:57
JFosorry I haven't been available for a bit18:57
JFoI'm still finishing up moving my household18:58
JFo:-/18:58
ogasawaraJFo: no worries18:58
JFoI saw your e-mail, but I have yet to act upon it18:58
JFowill do so this evening18:58
ogasawaraJFo: great, let me know if you have any questions18:58
JFoI certainly will, thanks so much for the feedback18:59
JFo<-trying to be a better bug triager :)18:59
Kanohi apw , you added aufs again? i really thought i had to do it again myself. what did change your mind?19:50
amitkKano: vfs mounts still has several bugs that won't get fixed in 2.6.3119:52
Kanofunny, i am patching aufs2 since ages now on my own...19:52
Kanofuse-unionfs was really slow as hell ;)20:00
Dinhhello manjo?20:17
manjoDinh, hello sir20:17
manjoDinh, did u get my mail with the location of the kernel ? 20:17
Dinhcool...i still can't build it...what was your build command?20:17
Dinhyes, can you also put the zimage file there as well?20:18
manjoDinh, k will do20:18
Dinhmanjo: brb20:19
manjoDinh, done20:19
manjoDinh, I did a cross compile using the compiler from codesourcery... make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-  you need to have the cross gcc in ur path20:22
manjoDinh, http://www.codesourcery.com/sgpp/lite/arm/portal/release85820:23
manjoDinh, brb bio break :)20:24
Dinhmanjo: i did that cross_compile settting...let me try the zimage with the system.map file and look at the log_buf20:29
manjoDinh, k20:29
Dinhmanjo: kernel panic in mxc_timer_init()20:35
Dinhlet me try rebuiding again20:35
manjoDinh, where in mxc_timer_init() ? 20:35
manjowe know that the kernel does not boot 20:36
manjoDinh, can you paste the panic message ? 20:36
Dinhmanjo: i have to do a memory dump...1 sec20:40
Dinhmanjo: Backtrace (mxc_timer_init+0x0/0x4c) from (mx51_babbage_timer_init+0x0/0x4) from (time_init+0x1c/0x24)20:43
manjoDinh, in one of my attempts to compile the kernel I got an error message ... include/linux/jiffies.h:257:31: error: division by zero in #if20:45
manjobut it went away later when I used the config options i pointed you to20:46
Dinhmanjo:  here's my cross_compile path   /opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi- 20:46
Dinhwhen do  a build:  >make ARCH=arm CROSS_COMPILE=${CROSS_COMPILE}20:47
DinhI get this error:  scripts/mod/modpost.c: In function `match': scripts/mod/modpost.c:699: parse error before `const' 20:47
manjodid u use the config options like I suggested ? 20:48
Dinhmanjo [yes]20:48
manjoDinh, that is strange.. compiles for me 20:49
manjowhich cross compiler are you using ? from codesourcery ? 20:50
Dinhmanjo[anyways..the crash is coming from mx51_babbage_timer_init() in /arch/arm/mach-mx51/mx51_babbage.c20:50
=== kancerman_ is now known as kancerman
Dinhmanjo [ the standard arm compile gcc compiler from Redhat]20:51
manjoDinh, so the crash must be in timer_clk = clk_get(NULL, clk_timer); in arch/arm/plat-mxc/time.c but i dont know why... 20:53
manjoDinh, my compiler is arm-none-linux-gnueabi-gcc-4.3.320:55
manjoDinh, can you try the compiler from http://www.codesourcery.com/sgpp/lite/arm/portal/release858 ? 20:56
manjojust get the tar package and untar it in ~/bin something like that .... 20:56
Dinhmanjo: yeah..let me work on that...i there's some changes in mxc_timer_init function in your tree that I'm not sure about, I'll email you what we have in ours...20:57
manjoDinh, ok sounds good 20:58
manjowhat is ur tree based on ? 20:58
manjokernel version ? 20:58
Dinhmanjo[2.6.28...but I'm not sure why you need these changes for a platform file][21:00
manjoDinh, note that the kernel you downloaded is 2.6.31 based21:09
manjoDinh, with patches from FS21:10
Dinhmanjo: yeah, i know...i'm not sure about the changes in low-level platform timer code21:11
manjoDinh, k21:11
Dinhwait...i sent you the wrong stuff...the crash is in mxc_timer_init...i sent you code for mxc_clocks_init21:12
Dinhmanjo: i think i know why the crash is happening...21:15
manjoDinh, u rock!21:15
Dinhif you look at /arch/arm/plat-mxc/time.c and the function mxc_timer_init(), I don't think timer_base is getting the correct memory address21:16
manjoDinh, I guessed that .... see my previous comment .. 21:17
manjoDinh, so do we know why address is bad ? 21:18
Dinhmanjo: how come there is a case for CONFIG_ARCH_MX5 ? only MX1, MX2 and MX3?21:19
Dinhi mean no case for MX5?21:20
manjohmm right 21:20
manjo } else21:20
manjo                BUG();21:20
manjoDinh, that is your code correcct ? :) 21:20
Dinhmanjo: no, i just sent you our code21:21
manjoDinh, ok looking .. 21:21
manjoDinh, do you want me to rebuild and re-upload .. ? 21:22
Dinhyeah sure..21:24
manjoDinh, rebuilding now 21:27
zetanuxihow offten does a kernel completly disappear from grub? =/21:28
manjoDinh, some pieces missing still ...int i =3D 0, j =3D 0, reg;21:28
Dinhmanjo: downloading the new tool chain now21:28
manjoerror: invalid suffix "D" on integer constant21:28
Dinhmanjo: i made a mistake...put back your original version of mxc_clocks_init(), you don't need to change that...21:29
manjoDinh, heh21:29
zetanuxiif a kernel option disappears from grub, do i need to do a clean install to restore it?21:30
manjoDinh, do we know why we dont have CONFIG_ARCH_MX5 in arch/arm/plat-mxc/time.c ? 21:32
Dinhmanjo: i have no idea21:33
manjou have that in ur tree ? 21:33
manjoDinh, in the .config CONFIG_ARCH_MX51=y21:34
manjoso in mxc_timer_init() we will aways hit BUG(); in the CONFIG_ARCH_MX51 case... so it needs a similar entry  in that file 21:35
manjo#ifdef CONFIG_ARCH_MX5121:35
manjo                timer_base = IO_ADDRESS(GPT1_BASE_ADDR);21:35
manjo                irq = MXC_INT_GPT;21:35
manjo#endif21:35
Dinhyep..in the past we used CONFIG_ARCH_MX1 , 2, 3...but we have changed to use more specific names...CONFIG_ARCH_MX5121:37
manjolet me add that bit and build you a kernel 21:38
Dinhand the TIMER_BASE define is defined in your board-mx51_babbage.h,   in our tree it was mxc_timer.h21:38
Dinhin /plat-mxc/include/mach/21:39
manjohardware.h 84 #define cpu_is_mx51()21:39
Dinhyeah, so add code to get the TIMER_BASE and it should be good to go21:41
manjobuilding now 21:41
manjoDinh, called seng ? 21:42
Dinhi haven't...i'll call hime now...i'm extracting the new build tools.21:43
manjoDinh, cool21:44
Dinhemail me his # again? the previous # didn't work21:44
manjok21:45
manjoDinh, you should get in ur sms21:46
Dinhgot it21:47
manjothat is my google voice sms service 21:49
manjoDinh, can you try with the new kernel I uploaded to my ppl page ? 21:51
manjoit better fscking boot :)21:52
Dinhmanjo: i wouldn't count on it...but we'll get past the timer crash...21:54
manjoDinh, yeah me too... I see CONFIG_ARCH is tons of places ... 21:55
Dinhmanjo: just tried the image in /try1 folder...still crashes21:59
manjoDinh, no21:59
manjonot in try121:59
manjothat is the old stuff21:59
Dinhoh ok...good21:59
Dinhin the main folder?22:00
manjoyes sir22:00
manjophewww22:00
Dinhmanjo: hmm...failure is still in mxc_timer_init22:05
Dinhlet me get my build going...22:05
manjosame place  ? 22:05
Dinhi think so22:06
manjok22:07
manjoDinh, ur mxc_timer_init() code looks a lot less simpler with no cases 22:11
Dinhmanjo: yes, because it gets the TIMER_BASE from the correct hw file...i'm not sure why you guys need those changes...22:14
manjok22:14
Dinhmanjo: ok, I'm finally building23:09
manjoDinh, cool ... 23:18
manjoDinh, you think you will be able to get the jtag home for tomorrow ? 23:18
manjomy board should show up tomorrow at home 23:18
Dinhyeah, i'll bring my whole setup home today...23:19
manjoheh cool! 23:19
manjocant wait to see that jtag ... 23:19
Dinhmanjo F*** still getting an error:  23:20
Dinhdrivers/hwmon/isl29003.c: In function 'isl29003_i2c_remove': 23:20
manjoDinh, how about this ... you bring the setup home ... I can swing by later this evening with some thing to drink 23:20
Dinhi'm going out to dinner..won't be back til 9 or so...23:21
Dinhyou can come by tomorrow morning23:21
manjook I need to go to the hospital 23:21
manjotomorrow we can hash this out .. 23:21
Dinhok, i'll send out a quick status...23:21
manjo9am sounds ok ?23:21
manjoDinh, I should be up around 7am buzz me on this channel when you are ready tomorrow 23:22
manjoDinh, did u cd debian/config and then cat config.common.ubuntu armel/config.common.armel armel/config.flavour.imx51 > ../../.config ?23:24
manjoif you do that you should not see that build failure 23:24
Dinhyeah, i did that...i get a different error when i do that...let me start over23:24
Dinhis cat config.common.ubuntu armel/config.common.armel armel/config.flavour.imx51 > ../../.config     1 whole command? or is it cat config.common.ubuntu armel/config.common.armel armel/config.flavour.imx51 > ../../.config, then cat config.common.ubuntu armel/config.common.armel armel/config.flavour.imx51 > ../../.config23:28
manjono one command23:28
manjoyou need to cat config.common.ubuntu armel/config.common.armel armel/config.flavour.imx51  into your .config23:29
Dinhah ok...got it...i was doing it as 2 commands earlier...i think its working now23:29
manjook23:29
Dinhsure..come by tomorrow at 9...irish coffee?23:33
manjoin the morning! 23:33
manjook by me :) 23:33
manjoI can bring some einstin bagel23:33
Dinhnah..i got tons of bagels...23:34
Dinhmanjo: sweet..it finished building23:41
manjoDinh, cool... 23:41
manjoDinh, does it have the fix that I put in earlier ? 23:42
Dinhnot yet..set me a patch for what you put in23:42
manjook23:42
manjoDinh, offing u a patch on irc 23:48
manjooffering 23:48
Dinhhow do i accept it?23:49
manjoDinh, I emailed it to you as attachment 23:50
manjonever mind the irc transfer23:50

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!