[08:31] <kraut> moin
[08:32] <alex_joni> moin
[08:37] <MiHu> Hi. Anybody from the kernel team already awake?
[08:37] <MiHu> 8-)
[10:52] <asac> hmm ... iwl3945 driver somehow claims to not support scan_capa. is that correct or did we miss a patch for that driver somewhere?
[10:52] <asac> (well from what i can tell it supports scan_capa)
[12:35] <MiHu>  A few days ago I reported bug #201197. On 2007-05-17, Ben Collins removed my driver called "MXB" from the list of modules to be build. I think there was a misunderstanding which of my drivers supports which kind of hardware. Is anybody willing to discuss this issue with me now?
[12:35] <ubotu> Launchpad bug 201197 in linux-ubuntu-modules-2.6.22 "Driver for "Multimedia eXtension Board" (MXB) missing" [Undecided,New] https://launchpad.net/bugs/201197
[12:57] <BenC> Good morning ppl
[12:58] <MiHu> BenC == Ben Collins?
[12:59] <BenC> yes
[12:59] <MiHu> Great. Hi. Can you please have a look at bug #201197 I filed a few days ago?
[12:59] <ubotu> Launchpad bug 201197 in linux-ubuntu-modules-2.6.22 "Driver for "Multimedia eXtension Board" (MXB) missing" [Undecided,New] https://launchpad.net/bugs/201197
[13:03] <BenC> MiHu: reading...
[13:22] <BenC> MiHu: Ok, sounds reasonable, I'll look into getting it reverted
[13:27] <MiHu> BenC, One problem is that some of the saa7146 devices don't have proper subsystem/subvendor ids. So I think they need to be blacklisted against autoloading first. Otherwise it can happen that one of the drivers (for example hexium_orion) captures somebody elses TV card, depending which modules gets loaded first. I think the only sane way is to let the user load the appropriate moduel manually.
[13:28] <BenC> MiHu: since you seem to know a lot about this, can you add proper suggestions to the bug report?
[13:28] <BenC> I'd be guessing
[13:28] <MiHu> BenC: No problem, since I'm the author of most of these drivers I should know. 8-) It's just that I did not receive any feedback so far, so I did not know if somebody was looking into this.
[13:29] <MiHu> benc: Is module blacklisting done via /etc/modprobe.d/blacklist? If so, do you know the people from the module-init-tools package?
[13:41] <alex_joni> where can I find instructions for building a lum package for a custom kernel?
[15:12] <MiHu> benc: I did some experiments. I installed the linux sources, enabled the MXB in the .config, build mxb.ko, copied it to the right place, depmod -a, then reboot. The card is recognised and everything works as expected. 
[15:12] <MiHu> BenC: I'll add this to the bug report. It would be great if that card would be supported with the next update again.
[15:13] <MiHu> BenC: Perhaps you can assign this bug report to yourself or somebody else. Do you need a patch for the .config? Please tell me if anything is missing.
[15:14] <BenC> MiHu: great, thanks for testing...just include the correct config option for us to change
[15:26] <MiHu> BenC: I updated the description for bug 201197. Is there already a new release planned for the kernel package?
[15:26] <ubotu> Launchpad bug 201197 in linux-ubuntu-modules-2.6.22 "Driver for "Multimedia eXtension Board" (MXB) missing" [Undecided,New] https://launchpad.net/bugs/201197
[15:26] <BenC> MiHu: Not planned, but we'll have to see how things go after the beta
[15:27] <MiHu> BenC: Ok. This is not critical, only a handful of users are using this card and they are all lazy updaters. Just like me...
[16:17] <MiHu> BenC: I played around with launchpad, hopefully the bug is now assigned to you.
[19:31] <asac> hmm ... any idea if rtg will be here today?
[22:32] <alex_joni> where could I find some instructions how to build a lum package for a modified kernel?