[00:18] <trv__> ok i've found it
[00:19] <trv__> ubuntu must be one of the few if not the only distribution that sets KALLSYMS_ALL=y
[00:19] <trv__> may ask why is this ?
[14:37] <_ruben> huh, wtf .. the -virtual kernel in intrepid shows up as -server? confusing
[15:20] <mkrufky> rtg: Im sorry i know my emails are long-winded :-P
[15:20] <mkrufky> rtg: any other info u need?
[15:20] <mkrufky> smb_tp: ...and im back now -- thanks for noticing ;-)
[15:20] <rtg> mkrufky: nope. smb_tp is gonna handle it.
[15:21] <mkrufky> cool... thanks
[15:21] <smb_tp> mkrufky, whenever there was a v4l question.
[15:21] <smb_tp> mkrufky, :)
[15:21] <mkrufky> ah... 
[15:21] <mkrufky> i started coming online later on in the day because i noticed i was getting less hauppauge work done :-P
[15:21] <smb_tp> mkrufky, I will go for the lum updates next. The info is quite sufficient
[15:22] <mkrufky> but you should feel free to email me if there ever is a question
[15:22] <mkrufky> ...and it doesnt have to be about hauppauge stuff -- i started off as a linuxtv.org guy before they found me :-)
[15:22] <smb_tp> mkrufky, Ah and since my day shifted rather to the other end...
[15:22] <mkrufky> hah  murphy's law
[15:22] <mkrufky> i will just try to have more of a presence again
[15:23] <smb_tp> mkrufky, NP, I just should remember I can mail you. :)
[15:23] <mkrufky> yes... its mkrufky at linuxtv dot org
[15:24] <smb_tp> mkrufky, Ok, cool
[15:25] <smb_tp> mkrufky, Just a slight warning, it can take a bit until the changes will show up. There is a bit of other stuff ahead
[15:25] <mkrufky> thats ok .... i'll be happy when i see them in the git tree
[15:25] <mkrufky> i dont mind if it takes a month or two before they get pushed out to users
[15:25] <mkrufky> since the new sticks aren't available for purchase yet, anyway
[15:26] <smb_tp> mkrufky, It should not take that long. So that's okay then
[15:27] <mkrufky> ok cool
[15:32] <_ruben> hmm .. most recent -virtual kernel image package also shows as -server .. strange
[15:34] <rtg> zul: another xen question: https://lists.ubuntu.com/archives/kernel-team/2008-November/003548.html
[15:34] <zul> rtg: yeah I saw it
[15:35] <zul> its on my list to answer 
[15:42] <rtg> smb_tp: do you have all 12 v4l patches in a git repo ? I think there are at least 4 SRUs in that patch set in order to effectively track regressions.
[15:43] <laga> mkrufky: looks like my mail didn't go through. if you update the file name of the firmware, won't ehtat break existing setups?
[15:43] <mkrufky> no laga, there are no existing setups because that hardware is not shipping
[15:43] <mkrufky> laga: the email went thru, but u sent it to me privately without cc to the list
[15:43] <smb_tp> rtg, currently they are only in a private branch, if you are referring to the uvcvideo patch set
[15:43] <laga> mkrufky: ah. :)
[15:43] <mkrufky> rtg: pardon me being nosy -- which v4l patches?  (im just curious)
[15:44] <laga> mkrufky: ah, right. some mailing lists do not set reply-to correctly.
[15:44] <mkrufky> correct
[15:44] <rtg> mkrufky: LP #290506
[15:44] <mkrufky> thanx
[15:44] <smb_tp> mkrufky, Its chenges to uvcvideo driver to work with intrepid and the v4l compat lib
[15:44] <mkrufky> ah, very cool... we spoke about that stuff at plumbers...  
[15:45] <mkrufky> laga: correction -- the hardware isnt shipping _yet_
[15:46] <mkrufky> should be soon
[15:46] <smb_tp> mkrufky, yes. In that case there seemed to be some glitches in uvcvideo which made it not work with cheese.
[15:46] <mkrufky> i've been making a point to get driver support into the kernel BEFORE the devices appear on store shelves
[16:41] <rtg> apw: you can push 'em straight in to the main repo. make sure the SOB trail includes mine and Ben's for the corresponding ACKs.
[16:42] <apw> i have added 'acked-by' as appropriate, is that sufficient
[16:43] <rtg> apw: yep
[16:43] <apw> cool thanks
[17:37] <Kano> hi rtg , somebody told me you have got a 2.6.28 repo, but it does not look like it would work
[17:38] <rtg> Kano: its not done yet. give it a week.
[17:38] <Kano> the jaunty one then?
[18:28] <rtg> apw: depmod sorts according to rules in /etc/depmod.d/ubuntu.conf.
[18:29] <rtg> if you install LBM, then LBM drivers come first in the search order.
[18:29] <rtg> there are problems if drivers of different names both claim the same PCI ID, but thats adifferent issue.
[18:31] <apw> yeah ok, makes sense.  so what criteria is there for inclusion in lbm?
[18:32] <rtg> apw: um, its kind of loose. does it solve someone's problem without wreaking havoc? Is it a widely used device? Is the mainstream version totally borked? and on and on...
[18:33] <rtg> I think r8169 likely qualifies
[18:33] <apw> ok so i think this probabally is a good fit then, the version of r8169 is 'beta' in .27 and should be 'close to done' in .28
[18:34] <apw> the reporter has pulled down the .28 version from somewhere and hand compiled it and seems to have had success with it
[18:34] <apw> ok ... so even if its a bust in the end learning how to put a module in here is worthwhile me thinks
[18:35] <rtg> apw: ok, so it can live in LBM for awhile. if it proves to be stable, then we could promote it to the kernel package in the ubuntu directory.
[18:35] <apw> sounds like a sane way forward
[18:41] <apw> rtg this thing is asking for the main kernel source at -10, is there some magic at play
[18:43] <rtg> what thing?
[18:43] <rtg> DKMS?
[18:43] <apw> oh .. heh ... when i tried to debuild lbm it asked for the -10 source tarballs
[18:43] <apw> but they don't exist as yet do they
[18:44] <rtg> apw: you'll need to build the -10 kernel, then install linux-headers* for your arch in the correct chroot.
[18:44] <apw> ok thanks ...
[20:27] <shay> anyone involved with Xen?
[20:28] <zul> shay: yep whats up?
[20:28] <shay> zul, any status of Xen support on Ubuntu 8.10 kernels?
[20:29] <zul> shay: yep domU only
[20:31] <shay> zul, I might be a little confused, but as far as it seems, or from what i can understand from the articles i've found, seems like Ubuntu is dropping support of Xen (and from what I understand, giving priority to support KVM instead) am I wrong?
[20:32] <zul> shay: xen is community suppored kvm is the prefered method
[20:33] <shay> zul, any links you can give me referring development status or how can I get started on helping to improve the situation?
[21:05] <fransman> do we have 2.6.28 or 2.6.29 in view for Jaunty?
[21:05] <rtg> .28 at the moment
[21:06] <fransman> cool
[21:06] <fransman> is there a git created ?
[21:06] <rtg> BenC is working on it.
[21:09] <fransman> BenC1: is that ubuntu-next.git ?
[21:10] <rtg> fransman: its gonna get rebased, so just wait a bit.
[21:11] <fransman> thanks for helping at the moment rtg:
[21:43] <mkrufky> laga: i just received your bounce
[21:43] <laga> my bounce?
[21:43] <mkrufky> Reason: Error: DNS server reported a server failure [101]
[21:44] <mkrufky> yes... you didnt get my response to your email, earlier
[21:44] <mkrufky> apparantly it bounced
[21:44] <mkrufky> dns problem on laga.ath.cx
[21:44] <mkrufky> thats a new one -- runnign a dns server on a dynamic domain :-P
[21:45] <mkrufky> of maybe dyndns just hiccup'd ... i dunno
[21:45] <laga> oh, damn.
[21:45] <laga> my dyndns expired again
[21:45] <mkrufky> ah
[21:45] <mkrufky> well that explains it :-P
[21:46] <laga> no, it hasnt
[21:46] <laga> but it was about to ;)
[21:46] <mkrufky> ah
[21:47] <laga> still weird
[21:47] <mkrufky> email is just not a great technology
[21:48] <mkrufky> ha!  my dyndns is about to expire, too
[21:48]  * mkrufky makes mental note to renew tonight