[06:29] <tritium> Hello.  If I have a request for the inclusion of firmware, shall I subscribe the ubuntu kernel team to the bug, or email the mailing list?
[06:33] <tritium> Specifically, I'm referring to bug 321076
[06:33] <ubot3> Malone bug 321076 in linux-firmware "Hauppauge WinTV-HVR-1800 Firmware not included" [Undecided,New] https://launchpad.net/bugs/321076
[06:51] <tritium> Mail to list bounced, so I've assigned the bug to the kernel team.  Thanks!
[13:20] <rtg> zul: how are  the xen bits coming for Jaunty?
[13:20] <zul> not good
[13:20] <zul> alot of changes that are still confusing me ill let you know
[13:21] <rtg> zul: np.
[13:24] <Kano> hi rtg , did you look at the webcam module
[13:25] <rtg> Kano: not yet, I'm just back home.
[17:47] <Kano> rtg: the patches in my mail need to be applied in the correct order
[17:47] <Kano> you need all 3
[17:47] <rtg> Kano: you need to follow the patch submission instructions.
[17:47] <Kano> those are links to gentoo only
[17:47] <Kano> do you want it as direct patch against ubuntu?
[17:48] <rtg> Kano: yes - I want you to do all the work :)
[17:48] <Kano> well should be no problem i already made a dkms package, then i should manage do do that too
[17:50] <Kano> i would do a patch for em8300 too,but the tested did not appear yet
[17:52] <Kano> but all you need to do was to apply 3 patches in a row...
[17:53] <Kano> could you fix snd-bt-sco?
[17:55] <Kano> all 3 patches apply without any error btw...
[18:08] <henrik-hw0> rtg: do you have a minute?
[18:08] <rtg> henrik-hw0: topic ?
[18:08] <henrik-hw0> rtg: ralink wifi drivers and your opinion.
[18:09] <rtg> I don't have enough experience with ralink to offer an opinion. I thuink there are some OEM drivers, but they are of poor  code quality IIRC
[18:10] <henrik-hw0> rtg: i see upstream has included rt2860 and rt2870 drivers in staging. i've packaged the manufacturer drivers for REVU but it may be smarter to just enable compilation of them in the ubuntu linux kernel package.
[18:11] <rtg> henrik-hw0: they've been enabled in the staging directory for Jaunty for the last several uploads.
[18:12] <henrik-hw0> i inspected the binary usb nic package, no binary drivers found...
[18:12] <rtg> but those are realtek, not ralink
[18:16] <henrik-hw0> rtg: in any case, do you think it makes sense to have packages for the rt28xx chipsets in Jaunty? if they are already in the kernel package?
[18:18] <rtg> henrik-hw0: I'm not I understand your question. The drivers in drivers/net/wireless/rt2x00 do not conflict with drivers/staging/rt28[67]0
[18:20] <henrik-hw0> rtg: the rt2x00 drivers do not support the RT2860 and RT2870 series chipsets.
[18:20] <rtg> henrik-hw0: those chipsets are supported by drivers/staging/rt28[67]0
[18:23] <henrik-hw0> rtg: yes, they are. i made 2 DEB packages with the RT2860 and RT2870 drivers and submitted them to REVU. that was before said drivers was included in staging. my question is: should i still bother with getting those packages into Jaunty before feature-feeze or should i ask that they be nuked?
[18:25] <rtg> henrik-hw0: I'd say nuke your packages since I assume the stuff upstream is getting some love. I'll resync staging before release, so we ought to have the latest rt28[67]0 driver sources.
[18:26] <henrik-hw0> rtg: thank you very much.
[18:26] <rtg> henrik-hw0: np, sorry abot the confusion
[18:48] <nikolam> hi is there a way to use ext4 on hardy as additional file system.
[18:48] <nikolam> I need it to read jaunty test install on other partition
[18:48] <rtg> nikolam: no support for ext4 in the Hardy kernel.
[18:49] <nikolam> rtg, but to compile additional module, won`t work?
[18:50] <rtg> nikolam: you can try it, but it was pretty new in 2.6.24
[18:51] <nikolam> interested only in reading
[19:22] <tjaalton> rtg: 14d200c5e5bd19219d930b is now in linus' tree
[19:24] <tjaalton> to fix bug 320813
[19:24] <ubot3> Malone bug 320813 in xserver-xorg-video-intel "[drm] compiz animations cause temporary freezes with vblank" [Unknown,Confirmed] https://launchpad.net/bugs/320813
[19:24] <rtg> tjaalton: I was reading that bug report. neither tester though it fixed the problem.
[19:25] <rtg> s/though/thought/
[19:27] <tjaalton> well I've tested it and worked for me
[19:27] <rtg> tjaalton: k
[19:29] <tjaalton> maybe they have g45 chips, which means they also need 9880b7a527ffbb52f65
[19:32] <Kano> rtg: http://kanotix.com/files/kernel/unused-patches/2.6.28-ubuntu-qc-usb-messenger.patch.bz2
[19:32] <Kano> happy with this patch?
[19:33] <rtg> Kano: I'm not the only one that has to be happy with it, so resend to the mailing list.
[19:55] <Kano> rtg: got mail?
[19:55] <Kano> btw. i updated that patch to incl. BOM file
[19:58] <rtg> Kano: what is the difference between qc-usb and qc-usb-messenger ?
[19:58] <Kano> you disabled qc-usb because it is inside the kernel, it is for other ids, qc-usb-messenger is of course a mod of the first one
[19:59] <Kano> look into the launchpad error
[20:01] <Kano> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/209901
[20:01] <ubot3> Malone bug 209901 in linux "webcam Logitech QuickCam Messenger  ID 046d:08f6 is not reconized" [Medium,Fix released] 
[20:03] <Kano> there was never a fix released btw ;)
[20:08] <debfx> rtg: could you please have a look at bug 312554 - an upstream change has been reverted in jaunty, so now it doesn't boot anymore on asus p5q mainboards
[20:08] <ubot3> Malone bug 312554 in linux "Regression: bug: int 14 cr2... booting 2.6.28 in jaunty fails on ASUS P5q and maybe others" [Undecided,Confirmed] https://launchpad.net/bugs/312554
[20:24] <Kano> rtg: qc-usb is not qc-usb-messenger!
[20:25] <Kano> qc-usb is now the quickcam inside the kernel
[20:26] <Kano> thats a driver just for 4 usb ids
[20:27] <Kano> http://home.mag.cx/messenger/
[20:27] <Kano> which id added the patch, exactly fixing that launchpad error
[20:27] <Kano> if you named it qc-usb before but disalbed it,it is not my fault
[20:28] <Kano> from the BOM file it must be a differnet driver anyway
[20:41] <Kano> maybe it would be possible to patch another driver
[20:41] <Kano> and add some extra ids
[20:48] <Kano> rtg: maybe disable one usb id as it is used by another driver
[20:49] <Kano> quickcam_messenger
[20:49] <Kano> or try to add some more ids to that one...