[08:31] moin [08:32] moin [08:37] Hi. Anybody from the kernel team already awake? [08:37] 8-) [10:52] 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] (well from what i can tell it supports scan_capa) [12:35] 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] 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] Good morning ppl [12:58] BenC == Ben Collins? [12:59] yes [12:59] Great. Hi. Can you please have a look at bug #201197 I filed a few days ago? [12:59] 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] MiHu: reading... [13:22] MiHu: Ok, sounds reasonable, I'll look into getting it reverted === \sh_away is now known as \sh [13:27] 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] MiHu: since you seem to know a lot about this, can you add proper suggestions to the bug report? [13:28] I'd be guessing [13:28] 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] 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] where can I find instructions for building a lum package for a custom kernel? [15:12] 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] 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] 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] MiHu: great, thanks for testing...just include the correct config option for us to change [15:26] BenC: I updated the description for bug 201197. Is there already a new release planned for the kernel package? [15:26] 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] MiHu: Not planned, but we'll have to see how things go after the beta [15:27] 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] BenC: I played around with launchpad, hopefully the bug is now assigned to you. === Traxer is now known as Traxer|on === Traxer|on is now known as Traxer === \sh is now known as \sh_away === asac_ is now known as asac [19:31] hmm ... any idea if rtg will be here today? === \sh_away is now known as \sh === \sh is now known as \sh_away === lamont` is now known as lamont [22:32] where could I find some instructions how to build a lum package for a modified kernel? === \sh_away is now known as \sh === \sh is now known as \sh_away