|
[15:19] <poningru> anyone around? |
|
[15:19] <poningru> I had a quick question |
|
[15:19] <poningru> I wanted to package up a module |
|
[15:19] <poningru> but the module is included in lrm by default |
|
[15:20] <poningru> the only difference is I want to update the module as it includes a driver sorely needed for a particular community |
|
[15:20] <poningru> aspire one community needs the latest madwifi |
|
[15:20] <poningru> so what should I do? package up the atheros seperately? |
|
[15:20] <tseliot> poningru: you can use DKMS for the package |
|
[15:20] <poningru> or update lrm? |
|
[15:21] <poningru> oh hmm |
|
[15:21] <poningru> looking into it more |
|
[15:22] <tseliot> poningru: with DKMS there would be no conflict with the version in the lrm |
|
[15:22] <poningru> ah awesome |
|
[15:22] <poningru> that is exactly what I am looking for |
|
[15:23] <tseliot> and you would only have to keep the linux-headers installed (and the compiler) so that the kernel module is rebuilt every time the kernel is updated |
|
[15:23] <poningru> any official ubuntu packaging guides for dkms? |
|
[15:23] <poningru> that is exactly what I was looking for |
|
[15:24] * tseliot looks for an easy example |
|
[15:26] <tseliot> maybe the dvb driver is easy enough: https://launchpad.net/~pitti/+archive |
|
[15:26] <tseliot> and of course: sudo apt-get install dkms |
|
[15:26] <tseliot> man dkms |
|
[15:27] <poningru> ah hmm |
|
[15:27] <poningru> danke |
|
[15:32] <poningru> hmm quick question |
|
[15:33] <poningru> tseliot, does the dkms require it to be installed in the to be installed computer? |
|
[15:33] <poningru> oh nvm |
|
[15:34] <poningru> this seems a little wrong |
|
[15:34] <poningru> too easy |
|
[15:59] <AlmightyCthulhu> latest email from Foxconn, more motherboard models affected, BIOS patch is top priority |
|
[15:59] <AlmightyCthulhu> so far we're up to Foxconn, ASUS, MSI, and Intel |
|
[15:59] <AlmightyCthulhu> especially G31, G33, G35, and P33 and P35 based boards |
|
[15:59] <AlmightyCthulhu> all have AMI BIOS |
|
=== ivoks_ is now known as ivoks |
|
[16:05] <stgraber> BenC: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/246222 <-- Any idea why dsdt-in-initrd doesn't work ? |
|
[16:07] <BenC> stgraber: because the patch wasn't there until -4, IIRC |
|
[16:08] <BenC> stgraber: wait, just got down to the end of the bug report... |
|
[16:08] <BenC> stgraber: I'll check on it later today |
|
[16:09] <stgraber> cool, thanks |
|
[19:29] <poningru> question any reason why madwifi drivers are in /lib/kernel_vers/madwifi instead of /lib/kernel_vers/kernel/drivers/net/wireless ? |
|
[19:29] <poningru> rather what was the reasoning behind that? |
|
[19:44] <tormod> rtg, hi I think the patch for bug #245026 is now ready for you. |
|
[19:46] <tormod> rtg, and thanks for committing that Hauppauge WinTV thing for Hardy! |
|
[19:47] <mkrufky> what Hauppauge WinTV thing?!? |
|
[19:47] <mkrufky> tormod: ^ |
|
[19:48] <tormod> mkrufky: support for the cheapo Nova-T CE / SE cards, bug #238164 |
|
[19:49] <mkrufky> ah, ok... thats already in 2.6.26, i believe, so no worries |
|
[19:50] <mkrufky> oh! actually... i heard complaints about that one not being supported in some other distros (asus eee) |
|
[19:51] <mkrufky> tormod: sorry for being nosey -- i work for Hauppauge now, and i just wanted to make sure it wasnt a patch missing from upstream ... thanks :-) |
|
[19:51] <tormod> mkrufky: interesting :) it's in 2.6.26 since March I think |
|
[19:52] <mkrufky> January |
|
[19:53] <tormod> mkrufky: and if I had knew the needed patch was so small, I would have pushed for it earlier... |
|
[19:53] <tormod> s/had // |
|
[19:54] <mkrufky> :-) no worries... if i realized it was missing from 2.6.24 i would have pushed it to stable |
|
[19:54] <mkrufky> but now its too late |
|
[19:54] <mkrufky> no problem |
|
[19:56] <tormod> mkrufky: since you for them, I must say the card works very nicely. and it's cheap. |
|
[19:56] <tormod> *you work for them |
|
[19:56] <mkrufky> ya |
|
[19:56] <mkrufky> i wasnt involved in that one... but i appreciate the positive feedback :-D |
|
[19:57] <tormod> mkrufky: I guess you are into v4l-dvb ? |
|
[19:58] <mkrufky> yup |
|
[19:58] <mkrufky> thats where Hauppauge found me :-D |
|
[19:58] <tormod> do you know why the card/driver doesn't work in Norway? they use another encoding there h264(?) and I wonder if just a little patch is needed? |
|
[20:01] <mkrufky> brb |
|
[20:02] <tormod> mkrufky: http://linuxtv.org/pipermail/linux-dvb/2007-October/020851.html |
|
[20:03] <mkrufky> tormod: that is not related to the product / driver |
|
[20:03] <mkrufky> tormod: if the user has an app that can decode h264, then said user will not have a problem with the stick |
|
[20:03] <tormod> it's in v4l general? |
|
[20:03] <mkrufky> this has nothing to do with v4l |
|
[20:04] <mkrufky> DVB is a glorified network adapter |
|
[20:04] <mkrufky> a DVB device receives a transport stream and provides it to userspace |
|
[20:04] <tormod> only the viewer? I tried "scan" but it would not list it. |
|
[20:04] <mkrufky> userspace decodes that stream and plays it |
|
[20:05] <tormod> I tried me-tv. Is it in me-tv or gstreamer or ?? |
|
[20:09] <tormod> what is there between v4l and "scan"? |
|
[20:16] <mkrufky> me-tv uses xinelib |
|
[20:17] <mkrufky> v4l is video4linux, a api and kernel subsystem that deals with analog video, and has absolutely nothing to do with digital television |
|
[20:17] <mkrufky> (me-tv uses xinelib, *not* gstreamer) |
|
[20:22] <poningru> tormod, try dumping the stream and then try out various decoding stuff using mplayer or vlc |
|
=== thegodfather is now known as fabbione |
|
[20:31] <poningru> EGret1029W{}|A5867NOomV |
|
[20:35] <tormod> mkrufky: I guess I meant v4l-dvb and not v4l... |
|
[20:37] <tormod> poningru: can not, I am not in Norway... |
|
[20:38] <mkrufky> tormod: im sorry... are you asking me something? |
|
[20:40] <tormod> mkrufky: my question is, what has to be fixed? xinelib? |
|
[20:41] <mkrufky> tormod: what is the problem? |
|
[20:41] <mkrufky> h264? |
|
[20:41] <mkrufky> tormod: try it in mplayer, it might work there |
|
[20:41] <mkrufky> oh... h264 sucks in linux |
|
[20:41] <mkrufky> you need an extremely powerful system if you want a chance of smooth playback |
|
[20:42] <mkrufky> ...or a graphics chipset that has hardware decoding support available in linux |
|
[20:42] <mkrufky> h264 hardware decoding support |
|
[20:42] <mkrufky> ... when you find that graphics chipset, please let me know -- i'll buy one for myself |
|
[20:43] <tormod> sounds like it's getting a lot more expensive than just buying that dvb-t dongle :) |
|
[20:44] <mkrufky> if you record them on your PC, you can play them back on a PS3 |
|
[20:44] <mkrufky> not much else i can say |
|
[20:44] <mkrufky> i live in ATSC-land |
|
[20:47] <tormod> is h264 so more resource-hungry, or it just that the linux support is not worked on? |
|
[20:49] <poningru> tormod, both |
|
[20:50] <poningru> search for drm/dri implementations under X |
|
[20:50] <mkrufky> nah, there is linux support available |
|
[20:50] <poningru> mkrufky, there is? |
|
[20:50] <mkrufky> i dont think the distros have taken the latest ffmpeg stuff yet |
|
[20:50] <poningru> hardware support? |
|
[20:50] <mkrufky> hardware, nah |
|
[20:51] <mkrufky> i know Nvidia has h264 decode support in the 8600 and later models |
|
[20:51] <mkrufky> but no support in the drivers, afaik |
|
[20:51] <poningru> iirc intel also has it but no support in the drivers |
|
[20:51] <poningru> 965 and up |
|
[20:51] <poningru> but what I cant wait for is dirac support in hardware |
|
[20:51] <poningru> that is going to be awesome |
|
[20:53] <tormod> dvb-t works nice with my old laptop here in Switzerland (mp4 I guess), I just feel sorry for those in Norway (and other h264 places) |
|
=== rikai_ is now known as rikai |
|
[20:55] <poningru> meh less bandwidth usage |
|
[21:41] <DB42> https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/114312 | more specificly: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/114312/comments/47 <-- can anybody help ? |
|
|