--- em8300-0.18.0.orig/debian/control +++ em8300-0.18.0/debian/control @@ -0,0 +1,62 @@ +Source: em8300 +Section: contrib/graphics +Priority: optional +Maintainer: Nicolas Boullis +Build-Depends: debhelper (>= 5), libgtk2.0-dev, bzip2, dpatch +Standards-Version: 3.8.3 + +Package: em8300 +Architecture: any +Depends: ${perl:Depends}, ${misc:Depends}, ucf (>= 0.28), wget +Description: Drivers for DXR3/Hollywood+ decoder cards + Drivers for MPEG decoder cards based on Sigma Designs' EM8300 chip + (such as the Creative Labs DXR3 or the Sigma Designs Hollywood+). + . + Currently the device drivers support decoding MPEG-1 and MPEG-2 streams + and generating video on the TV-out and VGA Overlay connectors. Audio can + be played through the analog or S/PDIF digital connectors. + . + This package contains programs to setup the card. + +Package: em8300-source +Architecture: all +Depends: ${misc:Depends} +Recommends: bzip2, linux-source | kernel-source | linux-headers | kernel-headers, kernel-package | module-assistant +Description: Kernel module for DXR3/Hollywood+ decoder cards (source) + Drivers for MPEG decoder cards based on Sigma Designs' EM8300 chip + (such as the Creative Labs DXR3 or the Sigma Designs Hollywood+). + . + Currently the device drivers support decoding MPEG-1 and MPEG-2 streams + and generating video on the TV-out and VGA Overlay connectors. Audio can + be played through the analog or S/PDIF digital connectors. + . + Source code of kernel modules needed to access the specified cards. + +Package: em8300-bin +Architecture: any +Depends: ${misc:Depends}, ${shlibs:Depends}, em8300 (>= ${binary:Version}) +Description: Tools to setup DXR3/Hollywood+ decoder cards + Utilities to configure MPEG decoder cards based on Sigma Designs' EM8300 + chip (such as the Creative Labs DXR3 or the Sigma Designs Hollywood+). + . + em8300-dhc can be used to adjust the brightness, contrast, saturation, + aspect ratio, TV output standard (PAL, NTSC, and PAL 60), turn on and + off sub-pictures (subtitles, etc.), and change between analog and + S/PDIF audio outputs. + . + autocal is used for doing initialization of overlay settings after Xine + or OMS (or some other player capable of handling em8300-based cards) has + been started. + . + dxr3view can be used to fine tune the size, shape, and appearance of + the overlay to a certain extent. + +Package: em8300-headers +Architecture: all +Depends: ${misc:Depends} +Section: contrib/devel +Description: Kernel headers to access DXR3/Hollywood+ decoder cards + This package provides header files needed to compile applications that + directly use the kernel module for MPEG decoder cards based on Sigma + Designs' EM8300 chip (such as the Creative Labs DXR3 or the Sigma + Designs Hollywood+). --- em8300-0.18.0.orig/debian/howto.txt +++ em8300-0.18.0/debian/howto.txt @@ -0,0 +1,617 @@ + [Dxr3 Logo] [DXR3 & Hollywood Plus Logo] +[images/oul.gif] Linux DXR3 and Hollywood+ Driver Project Howto [images/ + our.gif] + [images/ [images/ + iul.gif] iur.gif] + News DXR3 / Hollywood Plus HOWTO Table of Contents + About * Prerequisites + FAQ o Dxr3_or_Hollywood_Plus + Howto o Kernel_2.2_or_newer + Download o I2C_Driver + Links o rmquasar.vxd_(H+)_or_enc2dev.vxd_ + Developers (dxr3) + Project o Compiler_and_Related_Tools + Page * Getting_the_Source + o Download_Release + o Source_Via_CVS + * Compiling_the_Modules + o Makefile_settings + o If_you_have_a_2.2_kernel + o Compiling + * Create_Device_Files + o /dev/em8300* + * Loading_the_Kernel_Modules + o ldm_and_rmm + o Module_Parameters + * All_Things_Microcode + o Uncompressing + o Extracting + o Loading + * Playing_MPEG_Streams_and_DVDs + o Playing_MPEGs_via_/dev/em8300_mv- + *_and_/dev/em8300_ma-* + o Using_Xine_to_play_DVDs + o Using_MPlayer_to_play_DVDs + o Using_MPlayer_to_play_DivX/ + RealVideo_etc + o Using_OMS_to_play_DVDs + * Other_Useful_Programs + o DHC_by_Ze'ev_Maor + * Using_VGA_Overlay_Mode + o Setting_it_up + o dxr3view_and_autocal + * Identifying_your_Card + o Sigma_Designs_Hollywood_Plus + Variants + o Creative_Labs_Dxr3_Variants + * Getting_Help + o Mailing_List_-_Preferred_Method + o IRC_Channel + o Sourceforge_Fora + ============================================== + **** Prerequisites **** + As with any project there are some + prerequisites. Besides the obvious like, + needing a computer running a recent + version of Linux, you will, for now, + need some experience building packages + from scratch. You will also have to be + comfortable with a text editor. Yeah, + you know what that means. + * Dxr3 or Hollywood Plus + I hate to have to say it but before you + can start watching DVDs and MPEG streams + using this driver, you need to have + either a Creative Labs DXR3 or a Sigma + Designs Hollywood Plus hardware MPEG + decoder card. If you have any other + decoder card, this driver is of no help + to you. But if you have a fast enough + computer you can still watch MPEGs and + DVDs on your monitor with one of the + software viewers available. (Remember, + this wouldn't be here if someone didn't + ask . . . ) + * Kernel 2.2 or newer + This driver will only work with Linux + kernels version 2.2 and greater. If you + are running a 2.0 kernel, well then this + is the time to get brave and upgrade! + (And if you are running 1.2 or 1.3 on + modern hardware then you are either + criminally insane or a masochist, but + that is a different story). But then + there is the question, does a computer + old enough to be running a 2.0 kernel + actually have enough power to play a DVD + - even with a hardware decoder card? + Anyway, you'll need the source tree, and + you'll need to have run at least "make + config" and "make dep" in that tree. + * I2C Driver + If you are running a 2.2 kernel, you + need to install the I2C driver version + 2.4.5 or newer! You can get the I2C + driver for 2.2 kernels at the LM_Sensors + Homepage. If you have a 2.4 kernel, then + I2C comes with the kernel and you just + need to make sure that it is compiled + into the kernel or as a module. If you + fail to do this, then your card will + emit X-Rays from your TV and cook your + DNA! Just kidding. In either case, just + make sure that you have this I2C driver + installed. + * rmquasar.vxd (H+) or enc2dev.vxd (dxr3) + (as of driver 0.12.0 this is optional + and not recommended unless you have + serious problems with the supplied + microcode) + You need the appropriate VxD from the + Windows driver for your card. If you + have a Creative Labs Dxr3, then you will + have enc2dev.vxd and if you have a + Hollywood Plus, then you'll have + rmquasar.vxd. Easy enough. Now, you + should be able to find these bad boys in + you windows/system directory. If you + don't have a windows/system directory + because you don't have windows, then you + can still get these guys. You just need + to obtain the latest version of your + card's drivers from the appropriate web + site and unzip them. But wait, what the + hell is that?!?! They only give us + rmquasar.vx_ and enc2dev.vx_! Where is + the 'd'?!? They shorted us a 'd'! No, + actually, Microsoft, in their infinite + corporate wisdom, long ago instituted + the policy of compressing their driver + files for distribution, which strangely + enough are compressed again (as zips, + cabs, self extracting exes, etc.) which + just wastes cpu cycles. And, if you + haven't noticed, compressing a file + twice rarely yields any gain in + compression. Now, since we are missing a + 'd', note: a very special 'd', from our + driver file, we need to replace it. + Included with the em8300 driver + distribution in the scripts directory is + a perl program called msexpand.pl which, + when run like "msexpand.pl + rmquasar.vx_", will after some time make + a new copy of the file, this time with + the special 'd' replaced. Then you may + continue. + * Compiler and Related Tools + You will need Perl and a C compiler. If + you're building from a CVS checkout, + you'll need some GNU programs: automake + and autoconf. Those two also require GNU + m4. Also, bootstrapping a CVS checkout + requires the development files for GTK+ + 2.x (in particular, its m4 macros). If + you get errors later about missing + header files or libraries, you'll have + to install those as well. Chances are + that suitable versions are available in + your distribution; if not, get them off + the Internet. + **** Getting the Source **** + There are currently two ways to get the + source for this driver: by downloading a + 'stable' release or by downloading the + latest CVS. Depending on how old the + last release is, it may be best to try + out the CVS. + * Download a Release + If you decide to try one of the 'stable' + releases, please note that as of yet + none are really quite stable. They are + more akin to Mozilla's milestones in + that there are still many bugs to be + worked out. + * Source Via CVS + #include + Ok, yeah, you know CVS is often broken + and unstable. Well, yeah, but we still + need you guys to check out from CVS and + report those bugs. So please do. Also, + plugin updates for new releases of Xine + and OMS are often available only on CVS + for a long period of time, so you really + shouldn't be too shy about trying a CVS + checkout. It wont bite, I promise! Ok, + the two steps to checking out the CVS + are: + + $ cvs -d :pserver: + anonymous@cvs.dxr3.sourceforge.net:/ + cvsroot/dxr3 login + CVS password: [Just press enter] + $ cvs -d :pserver: + anonymous@cvs.dxr3.sourceforge.net:/ + cvsroot/dxr3 -z3 co em8300 + + And that's it! You should have an em8300 + directory under your current directory. + In there you'll find all the goodies + you'll need later on. + **** Compiling the Modules **** + Now we must compile the kernel modules + and get them configured and loaded. + * Makefile settings + Ok, chdir to em8300/modules and open up + the Makefile in your favorite editor. + Now change KERNEL_LOCATION to wherever + your current kernel source tree is, and + make sure that you've at least run "make + config ; make dep" in there. Now, change + -DEM8300_VIDEOMODE_DEFAULT= to + EM8300_VIDEOMODE_PAL, + EM8300_VIDEOMODE_PAL60, or + EM8300_VIDEOMODE_NTSC. If you live in + the Americas, choose NTSC. Elsewhere + (like Europe), you're probably PAL. If + you live in the former Soviet Union then + your standard is SECAM, which these + cards do not support. You can probably + get a PAL TV or use VGA_Overlay. Don't + worry about these defaults too much + because they can be set at run time + either by a dvd player with dxr3 support + or by the dhc utility. + * If you have a 2.2 kernel (As of driver + 0.11.0 this is no longer needed) + If you are using a 2.2 kernel, just copy + Makefile.2.2 to Makefile and follow the + instructions below. Make sure you have + the I2C module compiled and installed. + * Compiling + Just run "make". This will build the + four modules, adv717x.o, bt865.o, + em8300.o, and eeprom.o. To install the + modules, run "make install". + If you have any trouble compiling the + modules please send a detailed message + to the mailing list at dxr3- + devel@lists.sourceforge.net. Thanks. + **** Creating the Device Files **** + In Linux, and Unix in general, to + communicate with a device you need to + have a device file. Well, the Dxr3 and + H+ are no different. We currently use + four device files, which must be created + as root. If you are running devfs or + udev, these will be created + automatically and will use kernel + assigned major/minor numbers, no need to + read this section. + * Creating the /dev/em8300* devices + To create the four device files, you + must be root. As root, run the modules/ + devices.sh script or these commands: # + mknod /dev/em8300-0 c 121 0 # mknod / + dev/em8300_mv-0 c 121 1 # mknod /dev/ + em8300_ma-0 c 121 2 # mknod /dev/ + em8300_sp-0 c 121 3 Note: The device + numbers that we are using are currently + using are likely to change in the + future. Keep that in mind. + **** Loading the Kernel Modules **** + * ldm and rmm + In the em8300/modules directory there + live two shell scripts related to + loading and unloading the kernel + modules, ldm and rmm. ldm automates + loading of the driver modules, and rmm + automates unloading of the modules. In + order to pass module parameters to the + adv717x.o and em8300.o modules you must + edit the ldm script. Commented out + underneath the lines to load the adv717x + and em8300 modules you can see some + examples of the more commonly used + module parameters. So, for example, to + set the adv717x module option + "pixelport_16bit" to 0 and + "pixelport_other_pal" to 1 you would + have a line like the following: + + insmod adv717x.o pixelport_16bit=0 + pixelport_other_pal=1 + + Enter other module options similarly. + See the following table for a list of + module options and explanations of what + they do. If you don't want to use ldm + and rmm you can just issue the + appropriate modprobe/insmod/rmmod + commands by themselves and enter the + module parameters on the command line or + in /etc/modules.conf. Note, with ldm, + module options located in /etc/ + modules.conf will not be read, so if you + use ldm make sure to edit the module + options in there. + * Module Parameters + There are multiple parameters for each + of the modules that affect their + functionality. The choice of module + options will depend upon your particular + board. Also, module options for the + adv717x driver do not matter for cards + with a bt865 chip and vice versa. + Further, module options for the adv717x + and bt865 modules only matter for TV + output and have no effect on overlay. + See modules/README-modoptions for the + list of supported options, possible + values, and their descriptions as well + as commonly used configurations. + **** All Things Microcode **** + The em8300 RISC processor needs to be + programed before use. This program is + called a "microcode" and we will use the + one that has already been written for + us. + Note that version 0.12.0 and later of + the driver package comes with a + microcode, so just running em8300setup + should be enough, no need to extract + your own. + Additionally, versions 0.15.2 and later + have the capability to load the + microcode on demand, so even running + em8300setup is no longer needed for the + purpose of just loading it. You may want + to run it for other purposes, though. + If you use the drivers in packaged form + from your distribution, chances are that + the microcode is not included in the + package. If that is the case, read on. + A microcode that is known to work well + for many users is available separately + from http://dxr3.sourceforge.net/ + download/. If you decide to use it, you + can skip directly to the loading + section. + * Uncompressing + If you have downloaded a copy of the + Windows driver (preferably the Windows + 98 driver) from Sigma Designs or + Creative Labs or copied the driver from + the cdrom, then you will have to + uncompress the driver files. If you have + already installed the Windows driver and + have access to your windows/system + directory, then you can skip to the next + section. First use unzip to uncompress + and expand the driver archive. In that + archive you will find either + rmquasar.vx_ or enc2dev.vx_ depending if + you have the Sigma Designs or Creative + Labs drivers, respectively. Now we have + to uncompress this file. Use the + provided perl program "msexpand.pl" + located in em8300/scripts to uncompress + this file. For example: $ unzip + HP1_82W1.ZIP $ em8300/scripts/ + msexpand.pl rmquasar.vx_ + * Extracting + Now that we have the uncompressed + Windows 98 driver vxd, we need to + extract the microcode files. To do that + use the included perl program + microcode_extract.pl located in em8300/ + scripts. After running this program two + or three microcode files will be written + to the current directory, the number + depending on the driver you have. The + different microcode versions seem to be + for different revisions of the cards. + Currently, the only way to determine + which microcode is correct for your card + is to try them all and pick the one that + works the best. Do not be alarmed if + some of them do not work at all. + * Loading + At this point you should have the + extracted microcode files available. If + you're using version 0.15.2 or newer, + copy the microcode file to wherever your + system's hotplug configuration loads + firmware images from (often /lib/ + firmware), name it em8300.bin, and load + the modules; the microcode should be + automatically uploaded. If not, or if + using version 0.15.1 or earlier, you can + use the em8300setup tool to load it. Run + em8300setup -h and look at the -f option + and where it expects to find the + microcode from, and copy the microcode + there. The included perl program + microcode_upload.pl can also be used to + load the microcode into the em8300. For + example: $ em8300/scripts/ + microcode_upload.pl microcode0.bin You + should get a message like "Microcode + uploaded to /dev/em8300-0". If there are + no messages then it was unable to open / + dev/em8300-0 and you should verify that + the device file exists. If they do and + you have the right permissions (if + unsure just chmod a+w /dev/em8300*) it + usually means that you have the option + "PNP OS Installed" set to "enabled" in + your bios. This option exists in + virtually all x86 bioses since the + pentium. Disable this option, this means + the bios will set up all your plug and + play device prior to booting the + operating system. Windows has a bad + habit of randomizing pnp options on + booting making it impossible for linux + to save any settings as they will have + changed after booting into windows. + Disabling pnp os will fix this. + Note: This may cause vga passthrough to + stop functioning. We are working on + this. The solution at this time is to + just plug your monitor straight into the + video card or use the + "activate_loopback" em8300 module + option. You cannot watch MPEG streams on + the TV output connector with + activate_loopback set, however. + **** Playing MPEG Streams and DVDs **** + This section is all about playing MPEGs + and DVDs. If you are using VGA loopback, + first see the VGA_Overlay section then + come right back here. If you are playing + on a TV, then make sure you have all + your cables connected properly, and that + your TV is set to receive the composite + signal generated by the card. So, since + you are following this document from top + to bottom, you should be ready to go. + * Playing MPEGs via /dev/em8300_mv-* and / + dev/em8300_ma-* + Sending mpeg and pcm streams directly to + the card is a great way to test that the + thing is working properly without the + overhead of working with a full on DVD + player. In order to display a MPEG video + stream simply send it to "/dev/ + em8300_mv-0". In order to test the + analog audio capability of the card you + can use mpg123. For example: $ + extract_mpeg2 testvideostream.mpeg > / + dev/em8300_mv-0 $ mpg123 -a /dev/ + em8300_ma-0 somegoodtestmusic.mp3 Note, + you must send only MPEG video streams to + /dev/em8300_mv-*, and only PCM audio to + /dev/em8300_ma-*. An MPEG system file, + composed of both video and audio, will + cause garbage to be displayed on the + screen. You must first separate the + system into video and audio components, + and play each one separately. Also, / + dev/em8300-* is a control device, and + cannot be use to play mpeg systems. + * Using Xine to play DVDs + A dxr3 plugin is included with Xine + since Xine 0.5.0. Please see xine-lib/ + doc/README.dxr3 + * Using MPlayer to play DVDs + Invoke mplayer with the following + options: "-ao oss:/dev/em8300_ma-0 -vo + dxr3 -dvd " + * Using MPlayer to play DivX/RealVideo etc + To play any non MPEG1/2 content with + mplayer you have to specify an MPEG1 + filter, you do this by adding -vop lavc + or -vop fame and you are good to go. If + you are using gmplayer (GUI enabled + MPlayer) you can set the mpeg1 filter to + use in Preferences->Video->(dxr3)- + >Configure Driver. + * Using OMS to play DVDs + OMS was the original player for this + project but since then development seems + to have stopped. Thus, we currently + suggest you use Xine. This may change at + some future date. + **** Other Useful Programs **** + In this section we describe some useful + programs that have been contributed to + the project. + * DHC by Ze'ev Maor + DHC is a useful program written by Ze've + Maor. DHC's source lives in the em8300/ + dhc directory and it is built by default + during the build process if GTK+ 2.x's + development files are available. DHC can + be used to adjust the brightness, + contrast, saturation, aspect ration, TV + output standard (PAL, NTSC, and PAL 60), + turn on and off the subpicture + (subtitles, etc.), and change between + analog and spdif audio outputs. + **** Using VGA Overlay Mode **** + VGA Overlay can be used to view hardware + MPEG decoded streams on your computer + monitor. The main drawback of the Dxr3/ + H+ design is that using this feature + results in added noise and reduced + visual quality on the monitor from the + video card. So, you may notice that your + text that used to appear crisp is now + fuzzy with the decoder card inserted. + Sorry, there is nothing we can do about + this. If it bothers you too much, use a + TV instead. + * Setting it up + First, you must make sure that the + overlay cable is correctly installed. + Follow the instructions that came with + your card. Second, you may need to + enable the "activate_loopback" module + option for the em8300 module. See the + Module Parameters section above for + details. Unload and reload the modules + for the change to take effect, if + needed. Then you must load the + microcode. See the section All_Things + Microcode for help loading the + microcode. Now you should be ready to + continue to the next section. Note: + Overlay support is considered + experimental at this time and will + probably not work. + * dxr3view and autocal + Again, run "bootstrap" in the em8300 + directory, then run configure, make, and + make install. First, run autocal. This + will make the screen flash for a second. + This has to be done every time the + microcode is reloaded, which means that + you must load Xine or OMS before running + autocal. Yeah, I know its silly. Should + be fixed in the future. Then you have to + run dxr3view. This will bring up a + rectangular window with the overlay + window on top. It should look akin to + the windows overlay. Now, you should be + able to press play in Xine or OMS and + watch your MPEG. The control window in + dxr3view can be used to fine tune the + size, shape, and appearance of the + overlay to a certain extent. Also, if + you press 't' while the mouse is over + the dxr3view window, a menu with several + options, including fullscreen, will + appear. + **** Identifying your Card **** + Sometimes it is helpful to know some + details about your particular board, + especially if you need help getting the + driver to work. You can use the + following table to help figure out what + card you have and if there are any + special notes about it. + * Sigma Designs Hollywood Plus Variants + ______________________________________ + |Board|EM8300 |Video |Notes | + |ID___|Version|Chip___|________________| + |??? |Rev 2 |ADV7170|Requires | + |_____|_______|_______|pixelport_16=0__| + | | | |Requires | + |??? |Rev 2 |ADV7175|pixelport_16=1, | + | | | |dicom_control=1,| + |_____|_______|_______|dicom_fix=1_____| + * Creative Labs Dxr3 Variants + _________________________________ + |Board ID|EM8300 |Video Chip|Notes| + |________|Version|__________|_____| + **** Getting Help **** + Eventually, every one of us needs a + little help, especially with this + hardware ;). There are currently three + ways to get help: IRC, the mailing list, + and the Sourceforge Fora. Note, the best + way to get help is the Mailing list, and + the least favorable is the SourceForge + Fora. This may change in the future, but + currently not many developers visit the + SourceForge Fora. + * Mailing List - Preferred Method + By far the best way to get help is to + send a message to the mailing list. This + is because all the developers are + subscribed and read their email + throughout the day. The list is dxr3- + devel@lists.sourceforge.net and you can + subscribe or unsubscribe at The + SourceForge_Project_Mail_Page. + * IRC Channel + We have an IRC channel! Its #dxr3 on + irc.openprojects.net. Come join us and + ask questions about the driver or just + chat with the developers and other + users. + * Sourceforge Fora + As nice as they are, we don't use them. + But you really can't tell that by the + number of people who have posted to + them. Do us all a favor, and just stay + away from them for now. Perhaps one day + we may be popular enough to need them, + but right now, just say "no". +[SourceForge_Logo] [images/ [images/ + ill.gif] ilr.gif] +[images/ [images/ +oll.gif] olr.gif] + dxr3-devel_mailing_list + Last modified: Thu Apr 13 21:50:11 EEST 2006 --- em8300-0.18.0.orig/debian/em8300.prerm +++ em8300-0.18.0/debian/em8300.prerm @@ -0,0 +1,17 @@ +#!/bin/sh -e + +case "$1" in + remove) + rm -f /usr/share/doc/em8300/examples/auto + ;; + + upgrade|remove-in-favour|deconfigure-in-favour) + ;; + + failed-upgrade) + ;; +esac + +#DEBHELPER# + +exit 0 --- em8300-0.18.0.orig/debian/watch +++ em8300-0.18.0/debian/watch @@ -0,0 +1,2 @@ +version=3 +http://sf.net/dxr3/ em8300-nofirmware-(.*)\.tar\.gz debian uupdate --- em8300-0.18.0.orig/debian/em8300.postrm +++ em8300-0.18.0/debian/em8300.postrm @@ -0,0 +1,42 @@ +#! /bin/sh -e + +#DEBHELPER# + +case "$1" in + purge) + # remove modutils and modprobe.d things + rm -f /etc/modutils/em8300 + rm -f /etc/modprobe.d/em8300 + + if [ -x /usr/bin/ucf ]; then + /usr/bin/ucf --purge /etc/modutils/em8300 + /usr/bin/ucf --purge /etc/modprobe.d/em8300 + fi + + # remove microcode + if [ -e /lib/firmware/em8300.bin ]; then + rm -f /lib/firmware/em8300.bin + fi + + # remove autogenerated file -> actually already done in the prerm + # but save is save + rm -f /usr/share/doc/em8300/examples/auto + + # update devfsd config - cause em8300 thingies have been removed + # HAAAARGGGG where is the error ????? this update thing doesn't work + # without -n + if [ -x /usr/sbin/update-devfsd ]; then + /usr/sbin/update-devfsd -n + fi + ;; + + remove|upgrade|failed-upgrade|disappear|abort-install|abort-upgrade) + ;; + + *) + echo "postrm called with unknown argument \`$1'" >&2 + exit 0 + ;; +esac + +exit 0 --- em8300-0.18.0.orig/debian/em8300.templates +++ em8300-0.18.0/debian/em8300.templates @@ -0,0 +1,129 @@ +Template: em8300/microcode/download +Type: boolean +Default: true +_Description: Download microcode image from the Web? + The upstream developers have tried several microcode images and + selected the one that works best on various cards. Therefore, this + microcode image is probably better than the ones you can get from + your Windows drivers. The upstream developers have made it available + for download on their website. + . + However, because of some legal issues, this microcode image cannot be + distributed by Debian. If you do not want to download it, you can + still extract the appropriate microcode image(s) from the Windows + .vxd file, using em8300mc_ex. + . + Warning: If /lib/firmware/em8300.bin already exists on your system, it + will be overwritten by the downloaded file. + +Template: em8300/microcode/download_failed +Type: error +_Description: Failed to download microcode image + The microcode image was not downloaded from the upstream authors' web + site. You probably won't be able to use your MPEG decoder card until + you download a microcode image. + . + To retry, run "dpkg-reconfigure em8300" as root, or download it from + http://dxr3.sourceforge.net/download/em8300.uc + and save it as "/lib/firmware/em8300.bin". + +Template: em8300/microcode/file +Type: select +_Choices: None${files} +Default: None +_Description: Primary microcode: + This will copy a microcode image previously installed in + /usr/share/em8300/ to /lib/firmware/em8300.bin and use it. + +Template: em8300/microcode/delete_olddir +Type: boolean +Default: false +_Description: Delete old firmware directory? + Multiple microcode images seem to be installed + in /usr/share/em8000/. Support for multiple microcode images has + been removed from this version, so if you wish to continue using + multiple microcode images, you will have to keep these files and + handle the situation manually. You will be responsible for removing + these files once you have finished with them. + . + Most people need only a single microcode image. If you want to use + only one microcode image, or if you do not know why you have multiple + microcode images installed, then you can accept and the extra files + will be deleted. + +Template: em8300/chipset +Type: select +Choices: adv717x, bt865 +_Description: Chip used on MPEG decoder card: + Creative DXR3 cards have a bt865 on board, while Hollywood Plus cards + use an adv717x. + +Template: em8300/bt865/options +Type: string +_Description: Options for bt865 module: + Options can be passed to the bt865 kernel module when it is loaded + to control how it works. + . + Options include: + output_mode=comp+svideo|rgb + Multiple options should be separated by spaces. + +Template: em8300/adv717x/options +Type: string +_Description: Options for adv717x module: + Options can be passed to the adv717x kernel module when it is loaded + to control how it works. + . + Options include: + output_mode=comp+svideo|svideo|comp|comp+psvideo|psvideo|composvideo|yuv|rgb|rgbs + pixelport_16bit=0|1 + pixelport_other_pal=0|1 + pixeldata_adjust_ntsc=0|1|2|3 + pixeldata_adjust_pal=0|1|2|3 + Multiple options should be separated by spaces. + . + Some sets of options have been reported to remove color + problems. Check the package documentation for details. + . + Unfortunately, there is currently no way to find the right parameters + for your card, so you'll have to find them yourself by trial and error. + +Template: em8300/options +Type: string +_Description: Options for em8300 module: + Options can be passed to the em8300 kernel module when it is loaded + to control how it works. + . + Options include: + activate_loopback=0|1 + audio_driver=alsa|oss|osslike|none + alsa_index=-1|0|1|2|3|... + dsp_num=-1|0|1|2|3|... + bt865_ucode_timeout=0|1 + dicom_control=0|1 + dicom_fix=0|1 + dicom_other_pal=0|1 + use_bt865=0|1 + Multiple options should be separated by spaces. + . + Some sets of options have been reported to remove color + problems. Check the package documentation for details. + . + Unfortunately, there is currently no way to find the right parameters + for your card, so you'll have to find them yourself by trial and error. + +Template: em8300/no_device_creation +Type: note +Default: true +_Description: No creation of device files + Special device files must exist to enable access to your MPEG decoder + card. + . + You seem to be using a static /dev. Special device files can't be + created automatically because no major number has been allocated to + the em8300 officially yet. + . + Hence, you'll have to choose a major number to use (121 is used by + default, but it's officially allocated to "LOCAL/EXPERIMENTAL USE") + and create the corresponding device files yourself. Please read + /usr/share/doc/em8300/README.Debian for more info. --- em8300-0.18.0.orig/debian/em8300.files +++ em8300-0.18.0/debian/em8300.files @@ -0,0 +1,4 @@ +usr/share/em8300/*.pl +usr/share/em8300/*.pm +usr/bin/em8300setup +usr/share/alsa/cards/EM8300.conf --- em8300-0.18.0.orig/debian/em8300-bin.files +++ em8300-0.18.0/debian/em8300-bin.files @@ -0,0 +1,3 @@ +/usr/bin/em8300-dhc +/usr/bin/autocal +/usr/bin/dxr3view --- em8300-0.18.0.orig/debian/compat +++ em8300-0.18.0/debian/compat @@ -0,0 +1 @@ +5 --- em8300-0.18.0.orig/debian/em8300-source.modulecontrol +++ em8300-0.18.0/debian/em8300-source.modulecontrol @@ -0,0 +1,10 @@ +Package: em8300-modules-${kvers} +Architecture: any +Depends: em8300, ${kstem}-image-${kvers} +Recommends: em8300 (>= 0.16.0-1) +Suggests: em8300-bin +Description: dxr3 & Hollywood Plus dvd decoder cards software + Hardware drivers for the Ceative Labs Dxr3 or the Sigma Designs Hollywood + Plus DVD decoder card. + . + This package contains the compiled kernel modules for linux ${kvers}. --- em8300-0.18.0.orig/debian/em8300.dirs +++ em8300-0.18.0/debian/em8300.dirs @@ -0,0 +1,4 @@ +/etc/devfs/conf.d +/etc/modprobe.d +/etc/modutils +/lib/firmware --- em8300-0.18.0.orig/debian/em8300-bin.menu +++ em8300-0.18.0/debian/em8300-bin.menu @@ -0,0 +1,4 @@ +?package(em8300-bin):needs="X11" section="Applications/Graphics"\ + title="em8300-dhc" command="/usr/bin/em8300-dhc" +?package(em8300-bin):needs="X11" section="Applications/Graphics"\ + title="dxr3view" command="/usr/bin/dxr3view" --- em8300-0.18.0.orig/debian/em8300-source.README.Debian +++ em8300-0.18.0/debian/em8300-source.README.Debian @@ -0,0 +1,61 @@ + Building the em8300 kernel modules + + +First of all, if you want to change the default video standard from +PAL to PAL60 or NTSC, or the audio mode from ANALOG to PCM or AC3, +edit the system-wide /etc/em8300-source or your own ~/.em8300-source +configuration file. + +If you are using i2c modules not from the kernel (such as from the +i2c-source package), you must set the I2C_LOCATION variable in the +Makefile for the em8300 module. + +There are two ways to build the em8300 kernel module: make-kpkg and +module-assistant. Both ways require either kernel headers (from a linux-headers +package corresponding to the image you wish to run the em8300 module on), or +kernel sources (from a linux-source package, or elsewhere). module-assistant +is easier to use if you only have headers. + +module-assistant +~~~~~~~~~~~~~~~~ +You will need to have installed fakeroot and module-assistant (from packages of +the same names). To build the module using module-assistant, run: + + $ m-a a-b em8300 + +This will compile the em8300 module for the currently running kernel. (If you +want to build for a different kernel, investigate the --kvers-list option of +module-assistant. See its manpage.) + +A new debian package will have been generated in /usr/src. As root, install this +package: + + # dpkg -i /usr/src/em8300-modules-2.6.15-1-amd64-k8_0.15.3-1+2.6.17-2_amd64.deb + +(The actual package name and version will vary with your kernel.) + +For more information, read the manpage for module-assistant. + + +make-kpkg +~~~~~~~~~ +You will need fakeroot and make-kpkg (from package kernel-package). It might be +possible compile em8300 modules with make-kpkg using linux-headers and not the +full source, but that would require extra flags that will not be discussed +here. + +After building your kernel, run in the kernel source directory: + + $ make-kpkg --rootcmd fakeroot --added-modules em8300 modules_image + +This will generate a new debian package in the parent directory. As +root, install this package: + + # dpkg -i em8300-modules-2.6.15-1-amd64-k8_0.15.3-1+2.6.17-2_amd64.deb + +(The actual package name and version will vary with your kernel.) + +For more information, read the manpage for make-kpkg. + + + -- Nicolas Boullis , Fri Oct 24 01:49:14 2003 --- em8300-0.18.0.orig/debian/rules +++ em8300-0.18.0/debian/rules @@ -0,0 +1,183 @@ +#!/usr/bin/make -f + +# Include dpatch stuff. +include /usr/share/dpatch/dpatch.make + +package := em8300 +CFLAGS := -Wall -g +INSTALL_PROGRAM := install -m755 +INSTALL_DATA := install -m644 + +ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS))) +CFLAGS += -O0 +else +CFLAGS += -O2 +endif + +DEB_HOST_GNU_TYPE := $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE) +DEB_BUILD_GNU_TYPE := $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) +DEB_HOST_ARCH := $(shell dpkg-architecture -qDEB_HOST_ARCH) + +# Uncomment this to turn on verbose mode. +#export DH_VERBOSE=1 + +KERNEL_DEPENDS=n + +configure: configure-stamp +configure-stamp: patch-stamp + dh_testdir +# sh bootstrap + CFLAGS="$(CFLAGS)" ./configure --build=$(DEB_BUILD_GNU_TYPE) \ + --host=$(DEB_HOST_GNU_TYPE) --prefix=/usr \ + --mandir=\$${prefix}/share/man \ + --infodir=\$${prefix}/share/info --with-pic \ + --with-alsa-dir=/usr/share/alsa + diff include/config.h debian/config.h.good + touch configure-stamp + +build: build-stamp +build-stamp: configure-stamp + dh_testdir + $(MAKE) + touch build-stamp + +clean: unpatch + dh_testdir + dh_testroot + rm -f configure-stamp build-stamp install-stamp + rm -f modules.tar.gz + [ ! -f Makefile ] || $(MAKE) distclean + dh_clean + +documentation: + perl debian/scripts/dh_docbook + -if [ ! -d debian/sourceforge.html ]; then \ + install -d debian/dxr3.sourceforge.net ; \ + cd debian/dxr3.sourceforge.net ; \ + for f in faq.html howto.html; do \ + wget -N --timeout=10 dxr3.sourceforge.net/$$f; \ + done; \ + cd ../..; \ + cp -a debian/dxr3.sourceforge.net debian/sourceforge.html; \ + fi + html2text -nobs -o debian/faq.txt debian/sourceforge.html/faq.html + html2text -nobs -o debian/howto.txt debian/sourceforge.html/howto.html + +install: install-stamp +install-stamp: build-stamp + dh_testdir + dh_testroot + dh_clean -k + dh_installdirs + $(MAKE) INSTALL_PROGRAM="$(INSTALL_PROGRAM)" \ + install DESTDIR="$(CURDIR)/debian/tmp" + +# install devfsd files + install -o root -g audio -m 644 debian/local/devfs.conf \ + debian/em8300/etc/devfs/conf.d/em8300 + + mv debian/tmp/usr/bin/dhc debian/tmp/usr/bin/em8300-dhc + + dh_movefiles + + ls debian/em8300/usr/share/em8300/*.pm | xargs chmod a-x + +# rename files for proper naming (and to avoid clashes, etc) + + mv debian/em8300/usr/share/em8300/microcode_extract.pl \ + debian/em8300/usr/bin/em8300-mc_ex + rm debian/em8300/usr/share/em8300/*.pl \ + debian/em8300/usr/share/em8300/em8300.pm + + rmdir debian/em8300/usr/share/em8300 + + touch install-stamp + +MODULES_DEST=debian/$(package)-source/usr/src/modules/$(package) +srcpkg := $(package)-source + +install-source: + dh_testdir + dh_testroot + +# install -d $(MODULES_DEST)/debian + perl debian/scripts/dh_modulecontrol + cd modules && \ + find . | grep -v '\(CVS\|ldm\|rmm\)' | \ + cpio -admpv "$(CURDIR)/$(MODULES_DEST)" + cp include/linux/em8300.h $(MODULES_DEST)/ + cp debian/changelog $(MODULES_DEST)/debian/ + cp debian/copyright $(MODULES_DEST)/debian/ + echo 4 > $(MODULES_DEST)/debian/compat + cp debian/modules-tools.d/rules $(MODULES_DEST)/debian/ + chmod u+x $(MODULES_DEST)/debian/rules +# clean the source tree +# $(MAKE) -C $(MODULES_DEST) INSTALL_MODULES=1 \ +# -f debian/rules clean-modules +# change owner & permissions + chown -R root.root debian/$(srcpkg) + find debian/$(srcpkg) -type d | xargs chmod 755 + -find debian/$(srcpkg) -type f -perm -100 | xargs chmod 755 + -find debian/$(srcpkg) -type f -not -perm -100 | xargs chmod 644 +# build tar.bz2 + cd debian/$(srcpkg)/usr/src && \ + tar cf $(package).tar modules && \ + rm -r modules/$(package) + bzip2 -9 debian/$(srcpkg)/usr/src/$(package).tar + chmod 644 debian/$(srcpkg)/usr/src/$(package).tar.bz2 + install -o root -g root -m 755 -d debian/$(srcpkg)/etc + install -o root -g root -m 644 debian/local/em8300-source \ + debian/$(srcpkg)/etc/em8300-source + +# Build architecture-independent files here. +binary-indep: install-stamp install-source + dh_testdir -i + dh_testroot -i + dh_installdebconf -i + dh_installdocs -i + dh_installexamples -i + dh_installmenu -i + dh_installinit -i + dh_installcron -i + dh_installman -i + dh_installinfo -i + dh_installchangelogs ChangeLog -i + dh_strip -i + dh_link -i + dh_compress -i + dh_fixperms -i + dh_makeshlibs -i + dh_installdeb -i + dh_perl -i + dh_shlibdeps -i + dh_gencontrol -i + dh_md5sums -i + dh_builddeb -i + +# Build architecture-dependent files here. +binary-arch: install-stamp + dh_testdir -a + dh_testroot -a + dh_installdebconf -a + dh_installdocs -a + dh_installexamples -a + dh_installmenu -a + dh_installinit -a + dh_installcron -a + dh_installman -a + dh_installinfo -a + dh_installchangelogs ChangeLog -a + dh_strip -a + dh_link -a + dh_compress -a + dh_fixperms -a + dh_makeshlibs -a + dh_installdeb -a + dh_perl -a + dh_shlibdeps -a + dh_gencontrol -a + dh_md5sums -a + dh_builddeb -a + +binary: binary-indep binary-arch +.PHONY: build clean binary-indep binary-arch binary install configure --- em8300-0.18.0.orig/debian/copyright +++ em8300-0.18.0/debian/copyright @@ -0,0 +1,57 @@ +This package was debianized by Michael Moerz + +It was checked out from cvs.dxr3.sourceforge.net using following commands: + cvs -d :pserver:anonymous@cvs.dxr3.sourceforge.net:/cvsroot/dxr3 login + CVS password: [Just press enter] + cvs -d :pserver:anonymous@cvs.dxr3.sourceforge.net:/cvsroot/dxr3 -z3 co em8300 + +original reverse engineering, project + + Henrik Johansson + Ze'ev Maor + +maintaining, updating oms plugin, xine patch, autoconfiging + + Rick Haines + +kernel 2.4 makefile stuff + + Anton Altaparmakov + +Contributions + + Ralph Zimmermann + bt865 initialization + + Edward Salley + dxr3view patches + + Jeffrey H. Ingber + rev1 overlay patches + + Andrew Meredith + rpm packaging and module build-on-boot + + Paul Laufer + new web site, msexpand.pl, various patches + + Chris Horler + James Farwell + additional reverse engineering + +Copyright: + + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 2 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License with + the Debian GNU/Linux distribution in file /usr/share/common-licenses/GPL + if not, write to the Free Software Foundation, Inc., 51 Franklin St, + Fifth Floor, Boston, MA 02110-1301 USA --- em8300-0.18.0.orig/debian/config.h.good +++ em8300-0.18.0/debian/config.h.good @@ -0,0 +1,83 @@ +/* include/config.h. Generated from config.h.in by configure. */ +/* include/config.h.in. Generated from configure.ac by autoheader. */ + +/* Define the default path for the firmware. */ +#define FIRMWARE_DIR "/lib/firmware" + +/* Define to 1 if you have the header file. */ +#define HAVE_FCNTL_H 1 + +/* Defined if you have GTK */ +#define HAVE_GTK 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_INTTYPES_H 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_MEMORY_H 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_STDINT_H 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_STDLIB_H 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_STRINGS_H 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_STRING_H 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_SYS_IOCTL_H 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_SYS_STAT_H 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_SYS_TYPES_H 1 + +/* Define to 1 if you have the header file. */ +#define HAVE_UNISTD_H 1 + +/* Name of package */ +#define PACKAGE "em8300" + +/* Define to the address where bug reports for this package should be sent. */ +#define PACKAGE_BUGREPORT "" + +/* Define to the full name of this package. */ +#define PACKAGE_NAME "EM8300" + +/* Define to the full name and version of this package. */ +#define PACKAGE_STRING "EM8300 0.18.0" + +/* Define to the one symbol short name of this package. */ +#define PACKAGE_TARNAME "em8300" + +/* Define to the version of this package. */ +#define PACKAGE_VERSION "0.18.0" + +/* Define to 1 if you have the ANSI C header files. */ +#define STDC_HEADERS 1 + +/* Define to 1 if you can safely include both and . */ +#define TIME_WITH_SYS_TIME 1 + +/* Version number of package */ +#define VERSION "0.18.0" + +/* Define to empty if `const' does not conform to ANSI C. */ +/* #undef const */ + +/* Define to `__inline__' or `__inline' if that's what the C compiler + calls it, or to nothing if 'inline' is not supported under any name. */ +#ifndef __cplusplus +/* #undef inline */ +#endif + +/* Define to `long int' if does not define. */ +/* #undef off_t */ + +/* Define to `unsigned int' if does not define. */ +/* #undef size_t */ --- em8300-0.18.0.orig/debian/em8300.postinst +++ em8300-0.18.0/debian/em8300.postinst @@ -0,0 +1,105 @@ +#!/bin/sh -e + +case "$1" in +configure) + . /usr/share/debconf/confmodule + + db_get em8300/microcode/download + if [ "$RET" = "false" ] && [ -d /usr/share/em8300 ] && [ -n "`find /usr/share/em8300 -type f`" ]; then + db_get em8300/microcode/file + file="$RET" + + if [ "$file" != "None" ]; then + cp --remove-destination "/usr/share/em8300/$file" /lib/firmware/em8300.bin + fi + + db_set em8300/microcode/file None + fi + + if [ -d /usr/share/em8300 ]; then + db_get em8300/microcode/delete_olddir + if [ "$RET" = "true" ]; then + rm -rf /usr/share/em8300 + fi + fi + + # Download microcode + db_get em8300/microcode/download + if [ "$RET" = "true" ]; then + if wget -O /lib/firmware/em8300.bin 'http://dxr3.sourceforge.net/download/em8300.uc' > /dev/null 2>&1; then + db_set em8300/microcode/download false + else + # Failed to download microcode + db_input low em8300/microcode/download_failed || true + db_go + fi + fi + + # Generate /etc/modutils/em8300 + newfile=`tempfile` + chmod a+r "$newfile" + echo "alias /dev/em8300* em8300" > "$newfile" + echo "alias char-major-121 em8300" >> "$newfile" + db_get em8300/options + [ -n "$RET" ] && echo "options em8300 $RET" >> "$newfile" + db_get em8300/chipset + echo "below em8300 $RET" >> "$newfile" + if [ "$RET" = "adv717x" ]; then + db_get em8300/adv717x/options + [ -n "$RET" ] && echo "options adv717x $RET" >> "$newfile" + else + db_get em8300/bt865/options + [ -n "$RET" ] && echo "options bt865 $RET" >> "$newfile" + fi + echo "post-install em8300 /usr/bin/em8300setup -f /lib/firmware/em8300.bin" >> "$newfile" + /usr/bin/ucf --debconf-ok --three-way "$newfile" /etc/modutils/em8300 + rm "$newfile" + + # Generate /etc/modprobe.d/em8300 + newfile=`tempfile` + chmod a+r "$newfile" + echo "alias /dev/em8300* em8300" > "$newfile" + echo "alias char-major-121 em8300" >> "$newfile" + db_get em8300/options + [ -n "$RET" ] && echo "options em8300 $RET" >> "$newfile" + db_get em8300/chipset + chipset="$RET" + if [ "$RET" = "adv717x" ]; then + db_get em8300/adv717x/options + [ -n "$RET" ] && echo "options adv717x $RET" >> "$newfile" + else + db_get em8300/bt865/options + [ -n "$RET" ] && echo "options bt865 $RET" >> "$newfile" + fi + echo "install em8300 /sbin/modprobe $chipset && /sbin/modprobe --ignore-install em8300" >> "$newfile" + /usr/bin/ucf --debconf-ok --three-way "$newfile" /etc/modprobe.d/em8300 + rm "$newfile" + + [ -x /sbin/update-modules ] && /sbin/update-modules > /dev/null + + if [ -c /dev/.devfsd ]; then + # devfs active + if [ -x /usr/sbin/update-devfsd ]; then + # if devfs is installed (remove that -n when it's working again) + /usr/sbin/update-devfsd -n + fi + fi + + if [ -n "$2" -a "$2" != "" ] && dpkg --compare-versions "$2" lt "0.16.0-1"; then + db_unregister em8300/make_devices + fi + +;; + +abort-upgrade|abort-remove|abort-deconfigure) +;; + +*) + echo "postinst called with unknown argument \`$1'" >&2 + exit 0 +;; +esac + +#DEBHELPER# + +exit 0 --- em8300-0.18.0.orig/debian/em8300-bin.links +++ em8300-0.18.0/debian/em8300-bin.links @@ -0,0 +1 @@ +usr/share/man/man1/autocal.1 usr/share/man/man1/dxr3view.1 --- em8300-0.18.0.orig/debian/em8300.manpages +++ em8300-0.18.0/debian/em8300.manpages @@ -0,0 +1,2 @@ +debian/local/em8300-mc_ex.1 +debian/tmp/usr/share/man/man1/em8300setup.1 --- em8300-0.18.0.orig/debian/faq.txt +++ em8300-0.18.0/debian/faq.txt @@ -0,0 +1,735 @@ + [Dxr3 Logo] [DXR3 & Hollywood Plus + Logo] +[images/oul.gif] Linux DXR3 and Hollywood+ Driver Project FAQ [images/ + our.gif] + [images/ [images/ + iul.gif] iur.gif] + News Table of Contents + About * I'm_unable_to + FAQ change_the_audio + Howto volume_in_my_mixer, + Download what_gives? + Links * I_get_unresolved + Developers symbols_when + Project_Page running_"make + install"_or_loading + modules,_what's + wrong? + * My_kernel_source_is + not_in_/usr/src/ + linux,_how_can_I + get_the_darned + thing_to_compile? + * Microcode_upload_to + /dev/em8300- + 1_failed._What_does + that_mean? + * Does_this_actually + work_for_anyone? + Where_can_I_find + their_results? + * Can_I_play_stuff + like_DivX/RealVideo + as_well? + * Will_the_driver + ever_become_part_of + the_official + kernel? + * When_I_cat_a_.mpg + file_to_/dev/ + em8300_mv-*_a_bunch + of_garbage_appears + on_the_screen. + Whats_wrong? + * Only_two_microcode + files_are_extracted + from_my_driver + file._What_gives? + * How_can_I + uncompress + rmquasar.vx__or + enc2dev.vx_? + * I_left_a_message_in + the_Sourceforge + project_site_forums + and_nobody_has + answered! + * The_video_is_all + green!_How_can_I + fix_it? + * The_tv_output_looks + like_a_scrambled + cable-channel, + what's_wrong? + * The_video_is_only + on_one_half_of_my + screen!_What's + wrong? + * I_can_only_play_low + bit_rate_mpeg + videos,_higher_bit + rate_streams_lock + up_the_card._What + could_be_the + problem? + * When_I_load_the + microcode,_my + monitor_starts + making_funny + noises! + * When_I_load_the + microcode,_my + monitor_screen_goes + blank! + * What_is_libdxr3? + * Can_I_help_with_the + project? + ========================= + + Answers + Question: + I'm unable to + change the audio + volume in my mixer, + what gives? + Answer: + The em8300 does not + contain an audio + mixer, so this + feature cannot be + implemented. You + could write a + software mixer but + we have decided + that something like + that does not + belong in a kernel + module. + + Alternatively you + can output your + audio through a + native OSS or Alsa + device, and then + just use your + regular mixer + controls. Think of + the the em8300 + audio out as what + it really is, a + line out. Which is + perfect for hooking + up to stereo + equipment. + Question: + I get unresolved + symbols when + running "make + install" or loading + modules, what's + wrong? + Answer: + First thing's + first. The kernel + source you are + compiling against + must match your + running kernel. + i.e. if you're + running say RedHat- + 2.4.18-14 you must + point the Makefile + for the kernel + modules at the + correct source tree + for your "running + kernel". You can + verify that your + running kernel and + sources match by + typing "uname -a" + and looking at the + Makefile in the + root directory of + the kernel source. + e.g. output from + uname + + root@barney# uname + -a + Linux barney + 2.4.18-14custom #1 + Wed Sep 4 13:35:50 + EDT 2002 i686 i686 + i386 GNU/Linux + + Excerpt from + Makefile in /usr/ + src/linux-2.4 + + VERSION = 2 + PATCHLEVEL = 4 + SUBLEVEL = 18 + EXTRAVERSION = - + 14custom + See these match so + it should be safe + to compile kernel + modules against + this tree. You + really need to + compile your own + kernel tree, and + boot it. This + establishes that a) + the kernel source + you have runs, b) + creates all the + dependency files + and links that + em8300 uses to + compile itself + correctly. Think of + it as a pre- + requisite to + getting em8300 + running. + Before compiling a + "vendor" kernel it + is recommended you + type: make mrproper + this will clean up + any lingering files + from previous + compilations. If + you have your own + .config file you + will need to back + it up before doing + this otherwise it + is gone forever and + you have to set it + up again. + Vendor kernels are + typically set up + correctly for + em8300, i.e. they + have I2C, I2C-bit- + banging and OSS + Sound support + enabled. You can + usually short cut + the whole process + and get the default + configuration by + typing make + oldconfig. If you + download a + "Marcelo/Linus" + kernel you will + need to configure + both these options + in using something + like make + menuconfig + For more in-depth + discussion on how + to compile a linux + kernel check out + the Kernel_HOW-TO. + Question: + My kernel source is + not in /usr/src/ + linux, how can I + get the darned + thing to compile? + Answer: + Edit the + KERNEL_LOCATION + line in the + Makefile. This must + be the source + directory for the + kernel you are + currently running, + not the version + that shipped with + your distribution + (which you should + keep in /usr/src/ + linux for other + reasons). Also, you + must have run make + config and make dep + in the kernel tree + before compiling + the driver kernel + modules. + Question: + Microcode upload to + /dev/em8300- + 1 failed. What does + that mean? + Answer: + This error message + is normal. /dev/ + em8300-1, /dev/ + em8300-2, and /dev/ + em8300-3 are used + for multi card + support only. If + you don't have more + than one dxr3 don't + worry about it. + Question: + Does this actually + work for anyone? + Where can I find + their results? + Answer: + Yes. Unfortunately + Patryk Laurent's + dxr3_users_database + domain appears to + be down. We'll + update this link if + things change. + Question: + Can I use my DXR3/ + H+ to watch movies + other than DVDs or + MPEG1/2? Is this + accelerated? + Answer: + Yes, you will be + able to play DivX + and other supported + video formats on + your card as well. + Though this has to + happen through an + MPEG1 filter which + means it needs lots + of CPU power, you + should have at + least a 400MHz CPU + or preferably + faster. + + The em8300 cannot + decode anything + other than MPEG1/ + 2 in hardware so + this will never + happen in an + accelerated form. + If that is what you + want, look for + another card. What + it can and will do + is to handle + postprocessing for + you, so the output + will look alot + nicer than it would + do if you play it + on your monitor + without any + postprocessing + enabled. And, this + is a real cheap way + of getting a tv-out + for watching + movies. + For further + information + regardning this + please refer to the + DXR3 howto or + MPlayer manual. + Question: + Will the driver + ever become part of + the official Linux + kernel or will I + have to download + and compile this + thing separately + for the rest of my + life? + Answer: + Development of a + new driver in the + official Linux + kernel tree is + difficult because + Linus doesn't like + to apply lots of + little patches; he + would rather apply + fewer larger + patches to revise + an already working + driver. So, once we + get this thing + stable and working + with the known + revisions of the + cards, we may seek + to include the + kernel portion of + this driver in the + official kernel + source tree. + Question: + When I cat a .mpg + file to /dev/ + em8300_mv-* a bunch + of garbage appears + on the screen. + Whats wrong? + Answer: + Only mpeg video can + be sent to /dev/ + em8300_mv-*. If an + mpeg system file, + which is both mpeg + video and audio, is + sent to the device, + garbage like that + will show up on the + screen. First + separate the mpeg + system into + separate video and + audio files, then + send those to the + appropriate device. + See the Howto. + Question: + Only two microcode + files are extracted + from my driver + file. What gives? + Answer: + Some revisions of + the driver (seems + like those shipped + with boards with a + bt865) only came + with two microcode + files. Just use one + of these two and + the card should + work correctly. You + can also download + the latest version + of the driver from + either Creative + Labs or Sigma + Designs and use the + microcode shipped + with those drivers + instead. + + Update: (12/06/ + 2002) This question + is somewhat + obsolete now as the + latest driver, 0.13 + at this time, comes + with a microcode + file. + Question: + How can I + uncompress + rmquasar.vx_ or + enc2dev.vx_? + Answer: + A utility written + by Paul Laufer + called msexpand.pl + is included in the + em8300/scripts + directory that will + uncompress + microsoft + compressed files. + Just run it without + any arguments to + get the usage + information. See + the Howto. + + Update: (12/06/ + 2002) See the + previous question + as to why you don't + need to do this + anymore. + Question: + I left a message in + the Sourceforge + project site forums + and nobody has + answered! + Answer: + In general, use the + mailing list. + Unfortunately, at + this point the + Sourceforge project + forums are not + visited very often + by developers. See + the Howto + Question: + The video is all + green! How can I + fix it? + Answer: + Check to make sure + you are passing the + correct module + options to the + em8300.o and + adv717x.o kernel + modules. See the + Howto for further + information about + these options. In + the future + detection of these + settings should be + automated. + Question: + The tv output looks + like a scrambled + cable-channel, + what's wrong? + Answer: + There are a couple + of possibilities. + Firstly check that + you've configured + your Dxr3 for the + correct TV + standard. PAL in + Europe and parts of + South America, NTSC + in the US and Japan + and SECAM in France + or Russia. SECAM is + not supported. + Secondly, if you + are using an SVHS/ + S-Video to + Composite converter + cable, make sure + the SVHS connector + has 7 pins and not + 4. Most video cards + are delivered with + 4-pin SVHS- + >Composite + converters because + they use only 2 + outputs for video + (Luminance and + Chrominance). But + the DXR3/H+ is a + very high quality + card that uses 3 + outputs (Luminance, + and 2 Chrominance + outputs) which also + requires that you + use a converter + cable that + recognizes this. If + you can't find one, + the solution is to + buy an SVHS cable + and a scart contact + which accepts an + SVHS input. + If your TV has SVHS + inputs you can also + modify a regular + SVHS cable by + removing the + plastic leg on one + end of the cable. + Only do this if you + know what you are + doing as it is not + reversable and + basically removes + the key allowing + you to try plugging + it in upside down. + However it works + quite well and lets + you use a high + quality cable + rather than the + cheap one the DXR3 + comes with. + Question: + The video is only + on one half of my + screen! What's + wrong? + Answer: + Check to make sure + you are passing the + correct module + options to the + em8300.o and + adv717x.o kernel + modules. See the + Howto for further + information about + these options.In + the future + detection of these + settings should be + automated. + Question: + I can only play low + bit rate mpeg + videos, higher bit + rate streams lock + up the card. What + could be the + problem? + Answer: + Try using microcode + from a newer driver + version or one of + the other microcode + files that were + extracted from your + rmquasar.vxd or + enc2dev.vxd. Some + microcode files + seem only to work + with some versions + of the card. + + Update: (12/05/ + 2002) Try + downloading the + latest version of + the driver. It + includes a + universal microcode + as part of the + source. + Question: + When I load the + microcode, my + monitor starts + making funny + noises! + Answer: + Remove the + passthrough cable + and connect your + monitor to the + video card + directly. VGA + overlay and + passthrough are not + working on some + revisions of the + card. More reverse + engineering is much + needed. If you own + one of these cards + you currently have + to watch your DVDs + using the TV out + connector. + Question: + When I load the + microcode, my + monitor screen goes + blank! + Answer: + Some cards disable + the passthrough + when the microcode + is uploaded. Use + the + 'activate_loopback' + module parameter to + fix this. However, + you may not be able + to use the tv out + connector with + activate_loopback. + If you want to use + tvout you'll need + to disconnect the + passthrough cable + for now. See the + Howto. + Question + What is libdxr3? + Answer + libdxr3 was a + library that served + as an interface + between client + programs like Xine + and OMS and the + kernel modules. The + original idea was + to provide a + reusable library + and avoid code + duplication in + client programs, + but the library was + never quite + finished and its + use never really + took off, so it was + removed from the + em8300 distribution + as of version + 0.15.1 after being + unmaintained and + unused for a few + years. In case + someone's + interested in + finishing and + maintaining it, the + code can still be + resurrected from + CVS. + Question: + Can I help with the + project? + Answer: + Of course! We need + people to help + write better + documentation, + reverse engineer + the windows driver, + implement new + features in the + Linux driver, and + better integrate + the driver into the + DVD player + software. + [SourceForge_Logo] [images/ [images/ + ill.gif] ilr.gif] +[images/ [images/ +oll.gif] olr.gif] + dxr3-devel_mailing_list + Last modified: Sun Nov 6 11:01:15 EET 2005 --- em8300-0.18.0.orig/debian/em8300-headers.files +++ em8300-0.18.0/debian/em8300-headers.files @@ -0,0 +1 @@ +usr/include/linux/em8300.h --- em8300-0.18.0.orig/debian/em8300.examples +++ em8300-0.18.0/debian/em8300.examples @@ -0,0 +1,3 @@ +debian/local/examples/adv717x +debian/local/examples/both +debian/local/examples/bt865 --- em8300-0.18.0.orig/debian/em8300.config +++ em8300-0.18.0/debian/em8300.config @@ -0,0 +1,99 @@ +#!/bin/sh -e + +. /usr/share/debconf/confmodule + +db_version 2.0 + +db_capb backup + +STATE=1 + +while [ $STATE -gt 0 ] && [ $STATE -le 6 ]; do + case $STATE in + 1) + db_input high em8300/microcode/download || true + ;; + + 2) + db_get em8300/microcode/download + if [ "$RET" = "false" ] && [ -d /usr/share/em8300 ] && [ -n "`find /usr/share/em8300 -type f`" ]; then + files=`find /usr/share/em8300 -type f -printf ", %P"` + db_subst em8300/microcode/file files ${files} + db_input high em8300/microcode/file || true + fi + ;; + + 3) + if [ -d /usr/share/em8300 ]; then + prio=high + if [ -z "`find /usr/share/em8300 -type f`" ]; then + db_fget em8300/microcode/delete_olddir seen + if [ "$RET" = "false" ]; then + prio=medium + db_set em8300/microcode/delete_olddir true + fi + else + db_get em8300/microcode/download + if [ "$RET" = "false" ]; then + db_get em8300/microcode/file + if [ "$RET" = "`find /usr/share/em8300 -type f -printf %f`" ]; then + db_fget em8300/microcode/delete_olddir seen + if [ "$RET" = "false" ]; then + prio=medium + db_set em8300/microcode/delete_olddir true + fi + fi + fi + fi + db_input $prio em8300/microcode/delete_olddir || true + fi + ;; + + 4) + db_input high em8300/chipset || true + ;; + + 5) + db_beginblock + db_input medium em8300/options || true + db_get em8300/chipset + if [ "$RET" = "adv717x" ]; then + db_input medium em8300/adv717x/options || true + else + db_input medium em8300/bt865/options || true + fi + db_endblock + ;; + + 6) + if [ -c /dev/.devfsd ]; then + # devfs active + : + elif [ -d /dev/.udevdb ] || [ -d /dev/.udev ]; then + # udeb active + : + else + # static /dev + if [ ! -c /dev/em8300 ] && [ ! -c /dev/em8300-0 ]; then + db_input medium em8300/no_device_creation || true + fi + fi + ;; + esac + + if db_go; then + STATE=`expr $STATE + 1` + else + RETURN_CODE=$? + case $RETURN_CODE in + "30") + if [ $STATE -gt 1 ]; then + STATE=`expr $STATE - 1` + fi + ;; + *) + exit $RETURN_CODE + ;; + esac + fi +done --- em8300-0.18.0.orig/debian/em8300.docs +++ em8300-0.18.0/debian/em8300.docs @@ -0,0 +1,2 @@ +debian/howto.txt +debian/faq.txt --- em8300-0.18.0.orig/debian/em8300-bin.manpages +++ em8300-0.18.0/debian/em8300-bin.manpages @@ -0,0 +1,2 @@ +debian/local/em8300-dhc.1 +debian/local/autocal.1 --- em8300-0.18.0.orig/debian/em8300.README.Debian +++ em8300-0.18.0/debian/em8300.README.Debian @@ -0,0 +1,62 @@ + Special device files and major number + +No major number has yet been officially allocated for em8300. + +If you use a dynamic /dev system, like the old devfs or the new udev, +you need not worry about the major number in use, and can (and probably +should) use automatic assignment of major number. This is done by +loading the em8300 module with the "major=0" option. + +If you use a static /dev, you need to know the major number in use to +generate the required special device files. Although it is officially +reserved for "LOCAL/EXPERIMENTAL USE", the major number 121 is +currently used by default, but you can choose any other one with the +major option of the em8300 module. + +Once you know the major number you will use, generate the appropriate +device files with the following shell script (replace the 121 value as +appropriate): + #!/bin/sh + MAJOR=121 + for i in `seq 0 3`; do + mknod -m 0660 /dev/em8300-${i} c ${MAJOR} `expr 4 \* ${i}` + mknod -m 0660 /dev/em8300_mv-${i} c ${MAJOR} `expr 4 \* ${i} + 1` + mknod -m 0660 /dev/em8300_ma-${i} c ${MAJOR} `expr 4 \* ${i} + 2` + mknod -m 0660 /dev/em8300_sp-${i} c ${MAJOR} `expr 4 \* ${i} + 3` + chgrp video /dev/em8300-${i} /dev/em8300_mv-${i} /dev/em8300_ma-${i} /dev/em8300_sp-${i} + done + ln -s em8300-0 /dev/em8300 + ln -s em8300_mv-0 /dev/em8300_mv + ln -s em8300_ma-0 /dev/em8300_ma + ln -s em8300_sp-0 /dev/em8300_sp + + -- Nicolas Boullis , Tue, 19 Dec 2006 10:46:26 +0100 + + 2.6 kernel systems without automatic firmware loading + +Em8300 by default on 2.6 series kernels relies on automatic firmware loading +to load the firmware into the em8300 chip. The default debian kernels ship with +this enabled, so if that's what you're using you should be fine. + +If you are not using a kernel with automatic firmware loading you will need to +modify the line in /etc/modprobe.d/em8300 which says "install em8300 +/sbin/modprobe $chipset && /sbin/modprobe --ignore-install em8300" to read: + +install em8300 /sbin/modprobe $chipset && /sbin/modprobe --ignore-install em8300 && for i in \`seq 5\`; do [ -e /dev/em8300-0 ] && break; sleep 1; done && /usr/bin/em8300setup -f /lib/firmware/em8300.bin + +This will ensure that the firmware is loaded when the module is loaded. + + -- Brendon Higgins , Wed Apr 12 17:48:58 2006 + + Support for multiple firmwares + +Previous versions of the em8300 package supported more than one microcode image +by keeping them in the /usr/share/em8300 folder. As microcode images should be +stored in the common /lib/firmware folder, the em8300 package no longer supports +handling of multiple firmware images. + +If you wish, you can continue to use more than one microcode image as done +previously, however it then becomes your responsibility to remove these image +files should you wish to purge the em8300 package from your system. + + -- Brendon Higgins , Sat Dec 2 17:01:23 EST 2006 --- em8300-0.18.0.orig/debian/changelog +++ em8300-0.18.0/debian/changelog @@ -0,0 +1,524 @@ +em8300 (0.18.0-0prodeia1) unstable; urgency=low + + * New upstream release + * debian/config.h.good: Adapted + * debian/patches/00list: Commented all patches, as they are pre- + upstream patches + * debian/control: Updated standards-version to 3.8.3 + * debian/control: Added as dependency to binary package em8300-bin + for to fullfill debhelpers dependencies + * debian/control: Added as dependency to binary package em8300-source + for to fullfill debhelpers dependencies + * debian/control: Added as dependency to binary package em8300- + headers for to fullfill debhelpers dependencies + * debian/compat: Updated to 5 + * debian/control: Updated build-depend for debhelper to >=5 + * debian/control: Removed duplicate Section entries + + -- Roman Müllenschläder Sat, 06 Feb 2010 11:18:01 +0100 + +em8300 (0.16.4-4) unstable; urgency=low + + * Fix compatibility with linux 2.6.26 by using the relevant mercurial + changesets from upstream mercurial repository. + Thanks to Daniel Baumann for reporting the problem. + (Closes: #493715) + * Update Swedish debconf templates translation. Thanks Martin Bagge. + (Closes: #488178) + + -- Nicolas Boullis Thu, 07 Aug 2008 01:29:10 +0200 + +em8300 (0.16.4-3) unstable; urgency=low + + * Fix compatibility with linux 2.6.25 by using the relevant mercurial + changeset from upstream mercurial repository. + Note that the problem is solved in the released 0.17.0 version of the + driver, but this new version introduces some significant changes that + requires some significant changes in the packaging. + Thanks to Daniel Baumann for reporting the problem. + (Closes: #481463) + + -- Nicolas Boullis Sun, 18 May 2008 00:01:24 +0200 + +em8300 (0.16.4-2) unstable; urgency=low + + * Improve the modules' build system for inclusion in + linux-modules-contrib-2.6 (Closes: #464457) + + -- Nicolas Boullis Thu, 7 Feb 2008 01:43:04 +0100 + +em8300 (0.16.4-1) unstable; urgency=low + + * New upstream release + + [ Nicolas Boullis ] + * Protect all calls to db_input with " || true"; one was missing and was + causing the em8300 package to be uninstallable with a static + /dev. (Closes: #452985) + * Ensure that /etc/modprobe.d exists before creating a configuration + file there. + * Also ensure that /etc/modutils exists before creating a configuration + file there. This configuration file should certainly go away, but I + currently have problems using ucfq to determine whether the file was + changed (so I can safely remove it). + * Bump Standards-Version to 3.7.3 (no changes needed). + + -- Nicolas Boullis Wed, 6 Feb 2008 01:09:20 +0100 + +em8300 (0.16.3-1) unstable; urgency=low + + * New upstream release. + + [ Nicolas Boullis ] + * Use ${binary:Version} instead of the deprecated ${Source-Version}, as + suggested by lintian. + * Don't ignore failures of "make distclean", as suggested by lintian. + * Use debian/compat instead of setting DH_COMPAT=4 in debian/rules, as + suggested by lintian. + * Do the same with the em8300.tar.bz2 module source tarball. + * Use $(CURDIR) in debian/rules, instead of $(PWD) (defined as + $(shell pwd) ), as suggested by lintian. + * Move the menu entries of em8300-dhc and dxr3view from the Apps section + to the Applications section, as suggested by lintian. + * Add Spanish debconf templates translation. Thanks to Enrique Matías + Sánchez (Quique) (Closes: #419216) + * Add Portugese debconf templates translation. Thanks to Américo + Monteiro (Closes: #437386) + + -- Nicolas Boullis Tue, 16 Oct 2007 22:51:59 +0200 + +em8300 (0.16.2-1) UNRELEASED; urgency=low + + * New upstream release + + Fixes fails to build with 2.6.20 (Closes: #424176) + + -- Brendon Higgins Sat, 14 Jul 2007 19:18:48 +1000 + +em8300 (0.16.0-2) unstable; urgency=low + + * Update French debconf templates translation. Thanks to Christian + Perrier. (Closes: #404459) + * Update Czech debconf templates translation. Thanks to Martin Šín. + * Add Russian debconf templates translation. Thanks to Yuri + Kozlov. (Closes: #405362) + * Add Norwegian Bokmål debconf templates translation. Thanks to Bjørn + Steensrud. + * Add Vietnamese debconf templates translation. Thanks to Clytie + Siddall. + * Add German debconf templates translation. Thanks to Matthias + Julius. (Closes: #405635) + * Fix a typo in a debconf template (module option misspelt). Thanks to + Antoine Pardigon for reporting. (Closes: #405816) + * Also fix and unfuzzy the translations. (Translators, please feel free + to check I haven't done something stupid.) + + -- Nicolas Boullis Sat, 6 Jan 2007 19:35:06 +0100 + +em8300 (0.16.0-1) unstable; urgency=medium + + * New upstream release + + Fixes fails to build with 2.6.14 (Closes: #342377) + + [ Brendon Higgins ] + * Add extra guesswork for kstem, fixes problem when using module-assistant. + (Closes: #373646) + * Remove mention of em8300-i2c-2.8.0.patch in em8300-source.README.Debian, + that patch has been obsolete and non-existant for ages. + * Mention the use of module-assistant in same. (Closes: #373646) + * Add headers and module-assistant as alternative recommendations for + em8300-source. + * Make kernel dependency in em8300-modules unversioned. + * Have em8300-source recommend bzip2 (it's kinda useless if you can't extract + it). + * Added Swedish debconf templates translation. Thanks Daniel Nylander. + (Closes: #331031) + * Change microcode download failure notification template type to error + (Closes: #388891) + * Make debconf templates compliant with the guidelines. + * Let dh_installmodules handle depmod in postinst. (Closes: #381776) + * Don't try to generate device nodes when udev or devfs is running. + * Move em8300 firmware to /lib/firmware. (Closes: #341313) + * Remove support for multiple firmwares (most users won't need it, not worth + the effort). + * Remove support for 2.6 kernels that are missing automatic firmware loading. + + Add mention in README of how to fix it for such kernels. + * Modify debian/watch to support new "nofirmware" upstream release series. + + Drop the dfsg label since upstream supplies us with a dfsg version. + * debian/em8300.postinst, debian/em8300.config, debian/control: Remove logic + to handle upgrade path from oldstable packages, not necessary. + * Update the 10_modules_em8300_header patch for modules/em8300_alsa.c. + * Remove backspace-underlining in readme.txt, faq.txt that made these files + almost unreadable in text editors. + * Update FSF address in copyright file. + * Bump debhelper compatibility to V4 (no changes needed). + * Bump Standards-Version to 3.7.2 (no changes needed). + + [ Nicolas Boullis ] + * Install /usr/share/alsa/cards/EM8300.conf for ALSA support. + * No more (policy-violating) creation of special device files; add a + debconf note instead if they need to be created on a static /dev. + * Unregister the old em8300/make_devices template. + * Reorganize em8300.config and em8300.postinst. + * Do not ship an empty and now useless /usr/share/em8300 in em8300. + * Remove the map files generated by depmod from the built module + package. + * The module package now recommends em8300 >= 0.16.0-1 because of the + ALSA configuration file. + * Have em8300's debconf templates reviewed and improved by + debian-l10n-english, thanks to MJ Ray. + * Have em8300's README.Debian file reviewed and improved by + debian-l10n-english, thanks to Dominic Hargreaves. + + -- Nicolas Boullis Tue, 19 Dec 2006 10:46:07 +0100 + +em8300 (0.15.1.dfsg-1) unstable; urgency=low + + * New upstream release. + * Make the built module depend on the real kernel package, according to + KPKG_STEM, to support the kernel->linux transition, thanks to + Erik Schanze. (Closes: #328641) + + -- Nicolas Boullis Mon, 19 Sep 2005 00:34:25 +0200 + +em8300 (0.15.0.dfsg-2) unstable; urgency=low + + * Add Czech debconf translation, thanks to Martin Šín. (Closes: #319579) + * Add debian/watch file for easier tracking of upstream releases. + * Bump Standards-Version (no change needed). + * Compare include/config.h with a known good one, and fail if they differ. + + -- Nicolas Boullis Wed, 3 Aug 2005 01:46:52 +0200 + +em8300 (0.15.0.dfsg-1) unstable; urgency=low + + * New upstream release. + * Add .dfsg to the upstream version number to make it clear that the + non-free microcode was removed. + * Back to unstable. + + -- Nicolas Boullis Fri, 10 Jun 2005 00:24:48 +0200 + +em8300 (0.14.99+0.15.0.rc4-1) experimental; urgency=low + + * New upstream prerelease. + * Update em8300's postinst such that /etc/modprobe.d/em8300 waits for + udev to create the device special files before it runs em8300setup. + * Update em8300-source such that modules built for 2.6 kernels recommend + this new em8300 for improved udev support. + * Don't forget to remove /etc/modprobe.d/em8300 on purge in + em8300.postrm. + + -- Nicolas Boullis Thu, 26 May 2005 01:27:17 +0200 + +em8300 (0.14.99+0.15.0.rc1-2) experimental; urgency=low + + * The "I should check my packages even before uploads to experimental" + release. + * Update (really: fix) the em8300-source package. + - Include the em8300.h file in the source tarball for the module. + - Nuke the dependency on em8300-header. + - Built modules for 2.6 kernels recommend new em8300 (for + /etc/modprobe.d/em8300). + * Also generate /etc/modprobe.d/em8300 in em8300's postinst. + + -- Nicolas Boullis Sun, 3 Apr 2005 01:37:13 +0200 + +em8300 (0.14.99+0.15.0.rc1-1) experimental; urgency=low + + * New upstream prerelease. + - Add support for 2.6 series kernel. + - Add support for 2.9 series external i2c modules for 2.4 series + kernels. (Closes: #292067). + - Merge my 01_modules_i2c_headers, 01_modules_Makefile and + 30_modules_nodebug patches and my em8300setup.1 manpage. + * Kill the merged patches and update the other ones. + * Kill the local em8300setup.1 manpage. + + -- Nicolas Boullis Fri, 25 Mar 2005 01:49:08 +0100 + +em8300 (0.14.0-2) unstable; urgency=low + + * The "let's hope i2c will now be fine" release. + * When building modules, if $(I2C_LOCATION) is set, ensure that the i2c + headers from $(I2C_LOCATION) are prioritized over those from the + kernel source, thanks to Janne Kujanpää for pointing the problem. + + -- Nicolas Boullis Fri, 12 Mar 2004 20:17:54 +0100 + +em8300 (0.14.0-1) unstable; urgency=low + + * The "back to unstable" release. + * New upstream release: + - the sparc64 patch was merged in. + - semaphores are used rather than spinlocks for locking. + * Use ucf's new --debconf-ok option; thanks to Josselin Mouette for + pointing this. + * Add quotes around strings in em8300-bin's menu file. + + -- Nicolas Boullis Tue, 2 Mar 2004 01:38:16 +0100 + +em8300 (0.13.0+cvs20040210-1) experimental; urgency=low + + * New CVS snapshot: + - em8300-modules now builds on powerpc, thanks to Paavo Hartikainen + for his help. + - the patch for xine was updated and merged. + * Apply a patch for sparc64 support. + * Use the --build and --host options of configure. + + -- Nicolas Boullis Tue, 10 Feb 2004 22:40:24 +0100 + +em8300 (0.13.0+cvs20031218-1) experimental; urgency=low + + * New CVS snapshot: + - em8300-source is now compatible with both old and new i2c. + - em8300-modules now builds on alpha, thanks to Paavo Hartikainen for + reporting and for his help. (Closes: #219047) + * Apply the Michael Roitzsch to work with xine. + + -- Nicolas Boullis Thu, 18 Dec 2003 01:36:27 +0100 + +em8300 (0.13.0+cvs20031016-3) experimental; urgency=low + + * Fix broken quoting in em8300.config. A single quote was supposed to + match a double quote... Thanks to Gaetan Angely for noticing the + problem. (Closes: #217649) + * Check /dev/.devfsd rather than /usr/sbin/update-devfsd to know if the + system is using devfs. + * Remove the "These modules currently lack devfs support." comment from + em8300-source's long description. + + -- Nicolas Boullis Mon, 3 Nov 2003 02:08:58 +0100 + +em8300 (0.13.0+cvs20031016-2) experimental; urgency=low + + * The "I just switched to devfs" release. + * em8300.postinst: update /etc/modutils/em8300 to load em8300 when + /dev/em8300 is accessed. + * Clean up the /etc/devfs/conf.d/em8300 conffile. + * Remove empty directory /etc/devfs/devices.d from package em8300. + + -- Nicolas Boullis Tue, 28 Oct 2003 02:20:11 +0100 + +em8300 (0.13.0+cvs20031016-1) experimental; urgency=low + + * CVS snapshot + - em8300-source now includes a patch for compatibility with i2c + 2.8.0. (Closes: #215834) + * Remove the 20_em8300setup patch as the problem was fixed upstream. + * Update debconf templates to deal with the new options for the adv717x + module. + * Modify the em8300.config script to update the current adv717x options + "on the fly". + * Because of these new options, the built em8300-module package now + recommends a recent version of em8300. + * Add comments about i2c modules in the README.Debian file of package + em8300-source. + + -- Nicolas Boullis Fri, 24 Oct 2003 01:59:51 +0200 + +em8300 (0.13.0-6) unstable; urgency=low + + * Move the microcodes from /usr/lib/em8300 to /usr/share/em8300. + * Change the default microcode file in em8300setup to + /usr/share/em8300/em8300.uc. (Closes: #216174) + * Move em8300-mc_ex to /usr/bin/ and change the corresponding manpage to + section 1 accordingly. + * Remove the unused em8300-mc_up and em8300-mc_info, and the + corresponding manpages. + * Remove useless perl scripts from /usr/share/em8300 (in package + em8300). + * Capitalize first letter in short descriptions of debconf + templates. This is against Branden's advice, but most debconf + templates are capitalized, and I'd rather see things being consistent + in Sarge. + * Rewrite debconf templates to better english, thanks to Andre + Lehovich. + * Add french translation of debconf templates, thanks to Christian + Perrier for the initial translation. + + -- Nicolas Boullis Wed, 22 Oct 2003 02:23:22 +0200 + +em8300 (0.13.0-5) unstable; urgency=low + + * Ensure the em8300/microcode/download_failed note is actually + displayed/sent each time the download fails by setting the seen flag + to false beforehand. + * Remove -g from the module build options as that leads to a huge module + with gcc-3.2 or gcc-3.3. + * Add conflicts in em8300-headers against versions of dvb-dev that add a + /usr/include/linux/em8300.h file as well. (Closes: #211313) + * Remove include/linux/em8300.h from source tarball in em8300-source and + depend on em8300-headers instead as it is more convenient for people + who need to change the major number used by the driver. + * Nuke all libdxr3 packages as, according to upstream, it was not kept + up to date, and nothing uses it. + * Write a new README.Debian file for the package em8300, that explains + how to change the major number used by the em8300 driver. + * Write a manpage for em8300setup. (Closes: #192799) + * Rewrite debconf templates to better english, thanks to Aaron M. Ucko, + Ben Foley, Christian Perrier, and Branden Robinson. + + -- Nicolas Boullis Fri, 10 Oct 2003 00:54:13 +0200 + +em8300 (0.13.0-4) unstable; urgency=low + + * The "back to unstable" release. + * Apply some changes that were suggested by Joey Hess. (Thanks again, Joey.) + - Merge the em8300/microcode/download and em8300/chipset debconf + templates into a block. + - Trust dh_installdebconf to find the correct versionned dependency on + debconf. + - No need to call db_purge "by hand" in postrm script: + dh_installdebconf already does this. + * Add quotes around filenames generated by tempfile, as it may contain + spaces if $TMPDIR does. + * Since 0.13.0-2, maintainer script do not try to force anything into + modules options. (Closes: #192757) + + -- Nicolas Boullis Sat, 20 Sep 2003 00:38:00 +0200 + +em8300 (0.13.0-3) experimental; urgency=low + + * The "thank you Joey" release. + * Download microcode from upstream web site rather that CVS, and update + debconf template accordingly. Thanks to David Holm for putting this + microcode there. + * Add wget to em8300's depends. Thanks to Joey Hess for noticing this. + * Rewrite some debconf templates thanks to Joey Hess. + * Add some fallback if download fails. (Asked by Joey Hess.) + * Removed the unused README files from previous maintainer and write a + new one. + * Rewrite config script to support backing up. (Asked by Joey Hess.) + + -- Nicolas Boullis Sun, 14 Sep 2003 01:45:39 +0200 + +em8300 (0.13.0-2) experimental; urgency=low + + * Split em8300-headers out of libdxr3-dev. + * Revert the main/contrib split until everything is properly sorted + out. + * Clean up debian/ dir in source package. + * Removed the init.d script and rely on kmod to load the modules when + needed. (Closes: #192757) + * Completely rewrite maintainer scripts: + - Do not try to extract microcodes from widows drivers. (Closes: #165090) + - Ask to download a working microcode for upstream CVS instead. + - Merge /etc/modutils/adv717x into /etc/modutils/em8300. + - Use ucf to maintain /etc/modutils/em8300. + - Ask for permission to generate special device files. + - Switch to po-debconf. + * Bump Standards-Version to 3.6.1. + + -- Nicolas Boullis Sun, 31 Aug 2003 19:19:35 +0200 + +em8300 (0.13.0-1) unstable; urgency=low + + * Hijack. (Closes: #190269) + * Also delete microcode*.bin from /usr/lib/em8300 while purging em8300: + those files were misgenerated instead of {adv,bt}_mcode*.bin because + of a bug in em8300-mc_ex. (Closes: #180225) + * Acknowledge my own NMU + close bugs I forgot to close. (Closes: + #164885, #165401, #165458, #165470, #166997, #167779, #169511, + #169546, #171343) + + * debian/control: + - Rewrote the short descriptions and adapted the long ones. + (Closes: #165076) + - Rename libdxr30 to libdxr3-0 (as it is libdxr3 version 0) and + libdxr30-dev to libdxr3-dev. + - Add transition packages. + - Move em8300-source, libdxr3-0, libdxr3-dev and the source package from + contrib to main. + - Move libdxr3-0 to section libs and libdxr3-dev to libdevel. + + * em8300-source: + - append the debian revision number of the kernel to the version of + the generated modules package. + - the built module is useless without the corresponding kernel, so + depend on it instead of only recommending it. + - there's no need for the built module to depend on perl; remove the + dependency. + - the module should hopefuly be buildable on any architecture. (Well, + only linux-based architectures in fact...) + - change the shipped Makefile from to configure the default audio mode + and videomode from /etc/em8300-source (or ~/.em8300-source) and + actually ship a default configuration file. (Closes: #165947) + - remove a misplaced Build-Depend from the Package section of the + debian/control file inside the source tarball. + + -- Nicolas Boullis Sun, 11 May 2003 18:10:40 +0200 + +em8300 (0.13.0-0.1) unstable; urgency=low + + * NMU. (No answer from maintainer for one week + upload to DELAYED/7-day) + * New upstream release. (Closes: #169511) + * Remove depedency for em8300-sources on libdxr3-dev . (Closes: #166997) + * Remove a few useless files in the debian/ directory in the source + package (config, dirs, doc, examples, manpages, postinst, postrm, + prerm, templates). + * Remove buggy watch file. + * Remove em8300.conffiles : since debhelper V3, dh_installdeb already + flags /etc/devfs/conf.d/em8300 as a conffile. + * Remove em8300-doc.substvars . + * Add a patch for microcode_extract (em8300-mc_ex) to really handle its + NAMEBASE option. + * Add a pacth for the new em8300setup not to fail if there are less than + 4 em8300-based cards. + * Add missing Build-Depends: bzip2 . (Closes: #164885) + * Make em8300-source Architecture: all instead of i386. + (Closes: #169546) + * Make em8300, em8300-bin Architecture: any instead of i386. + * libdxr3 only Recommends: em8300 ; do not Depend: em8300 . + * Added missing final EOL in several files in debian/ + (local/devfs.devices, local/examples/both, local/makedev, + modules-tools.d/README.debian, modules-tools.d/postinst, + debian/modules-tools.d/README.debian.in and packages.d/em8300.in). + * Apply patch by Frederic Bothamy for installem8300.pl (Thanks + Frederic!) (Closes: #165401, #165458) + * Adapt installem8300.pl to use the new em8300setup instead of the old + em8300-mc_up . + * Fix installem8300.pl to re-read /etc/modutils/{em8300,adv717x} + properly. + * Add missing '#!/bin/sh' in debian/local/makedev . + * Fix debian/modules-tools.d/rules to handle $ROOT_CMD properly. + * Add the new em8300setup program to the em8300 package. + * Give proper permissions to usr/share/em8300/installem8300.pl and + usr/lib/em8300/makedev . + * Fix debian/rules not to generate an extraneous + debian/sourceforge.html/dxr3.sourceforge.net , and remove this + extraneous directory. + * Fix debian/rules to build Architecture: all packages. + * Fix installem8300.pl to prevent /etc/em8300.cfg from growing. + * Fix /etc/init.d/em8300 to handle restart/force-reload. + (Closes: #167779) + * Use dpatch instead of dbs (as maintainer wanted to do when we last + discussed it, 3 months ago). + * Do not try to download documentation at build time (because + autobuilders and people building the package my lack internet + access). The documentation target shall be run before upload. + * Split package descriptions (.files, .config, .dirs, .docs, ... files). + * Removed buid-dependency on html2text and docbook-to-man . + * Fixed a few typos in the descriptions. + * Fix attributions of patches. + * Write description for patches. + + -- Nicolas Boullis Sat, 22 Feb 2003 00:51:54 +0100 + +em8300 (0.12.0-2) unstable; urgency=low + + * correcting section from main to contrib (where it actually belongs) + * corrected minor build bug that caused stop of build when no kernel + was installed at /usr/src/linux + + -- Michael Moerz Sun, 31 Mar 2002 19:34:58 +0200 + +em8300 (0.12.0-1) unstable; urgency=low + + * Initial Release with modified tar ball since the legal state of the + microcode that is found in upstreams sources is unknown from my + point of view. So I drop it to avoid any legal issues. + + -- Michael Moerz Tue, 26 Feb 2002 22:56:13 +0100 + + --- em8300-0.18.0.orig/debian/patches/95_version.dpatch +++ em8300-0.18.0/debian/patches/95_version.dpatch @@ -0,0 +1,28 @@ +#! /bin/sh /usr/share/dpatch/dpatch-run +## 95_version.dpatch by Nicolas Boullis +## +## All lines beginning with `## DP:' are a description of the patch. +## DP: Move the version definition inside the section of the Makefile +## DP: used when the kernel's build system is used directly. + +@DPATCH@ +diff -urNad em8300-0.16.4~/modules/Makefile em8300-0.16.4/modules/Makefile +--- em8300-0.16.4~/modules/Makefile 2008-02-07 01:39:04.000000000 +0100 ++++ em8300-0.16.4/modules/Makefile 2008-02-07 01:39:50.000000000 +0100 +@@ -29,7 +29,6 @@ + #export EM8300_I2C_LOCATION := /usr/src/modules/i2c + #export EM8300_I2C_FORCE_API := NEW + +-export EM8300_VERSION := "0.16.4" + export INSTALL_MOD_DIR=em8300 + + # Try to get defaults from configuration files +@@ -90,6 +89,8 @@ + + else + ++EM8300_VERSION := "0.16.4" ++ + BUILD_IOCTL32 := n + + ifeq ($(ARCH),sparc64) --- em8300-0.18.0.orig/debian/patches/00list +++ em8300-0.18.0/debian/patches/00list @@ -0,0 +1,6 @@ +#01_compat_2.6.25 +#02_compat_2.6.26 +#05_modules_Makefile +#10_modules_em8300_header +#90_modules_defaults_conffile +#95_version --- em8300-0.18.0.orig/debian/patches/90_modules_defaults_conffile.dpatch +++ em8300-0.18.0/debian/patches/90_modules_defaults_conffile.dpatch @@ -0,0 +1,70 @@ +#!/bin/sh -e +## 90_modules_defaults_conffile.dpatch by Nicolas Boullis +## +## All lines beginning with `## DP:' are a description of the patch. +## DP: Support setting the module's default videomode and audiomode in a +## DP: configuration file (~/.em8300-source or /etc/em8300-source). + + +if [ $# -ne 1 ]; then + echo >&2 "`basename $0`: script expects -patch|-unpatch as argument" + exit 1 +fi + +[ -f debian/patches/00patch-opts ] && . debian/patches/00patch-opts +patch_opts="${patch_opts:--f --no-backup-if-mismatch}" + +case "$1" in + -patch) patch $patch_opts -p1 < $0;; + -unpatch) patch $patch_opts -p1 -R < $0;; + *) + echo >&2 "`basename $0`: script expects -patch|-unpatch as argument" + exit 1;; +esac + +exit 0 + +@DPATCH@ +diff -urNad em8300-0.16.4~/modules/Makefile em8300-0.16.4/modules/Makefile +--- em8300-0.16.4~/modules/Makefile 2008-02-07 01:31:16.000000000 +0100 ++++ em8300-0.16.4/modules/Makefile 2008-02-07 01:36:45.000000000 +0100 +@@ -32,6 +32,28 @@ + export EM8300_VERSION := "0.16.4" + export INSTALL_MOD_DIR=em8300 + ++# Try to get defaults from configuration files ++ ++ifeq ($(EM8300_VIDEOMODE_DEFAULT),) ++export EM8300_VIDEOMODE_DEFAULT=$(shell test -r ~/.em8300-source && sed -ne 's/^[[:space:]]*EM8300_VIDEOMODE_DEFAULT[[:space:]]*=[[:space:]]*//p' < ~/.em8300-source) ++endif ++ifeq ($(EM8300_VIDEOMODE_DEFAULT),) ++export EM8300_VIDEOMODE_DEFAULT=$(shell test -r /etc/em8300-source && sed -ne 's/^[[:space:]]*EM8300_VIDEOMODE_DEFAULT[[:space:]]*=[[:space:]]*//p' < /etc/em8300-source) ++endif ++ifeq ($(EM8300_VIDEOMODE_DEFAULT),) ++export EM8300_VIDEOMODE_DEFAULT=EM8300_VIDEOMODE_PAL ++endif ++ ++ifeq ($(EM8300_AUDIOMODE_DEFAULT),) ++export EM8300_AUDIOMODE_DEFAULT=$(shell test -r ~/.em8300-source && sed -ne 's/^[[:space:]]*EM8300_AUDIOMODE_DEFAULT[[:space:]]*=[[:space:]]*//p' < ~/.em8300-source) ++endif ++ifeq ($(EM8300_AUDIOMODE_DEFAULT),) ++export EM8300_AUDIOMODE_DEFAULT=$(shell test -r /etc/em8300-source && sed -ne 's/^[[:space:]]*EM8300_AUDIOMODE_DEFAULT[[:space:]]*=[[:space:]]*//p' < /etc/em8300-source) ++endif ++ifeq ($(EM8300_AUDIOMODE_DEFAULT),) ++export EM8300_AUDIOMODE_DEFAULT=EM8300_AUDIOMODE_ANALOG ++endif ++ + build: + $(MAKE) -C $(KERNEL_LOCATION) SUBDIRS=$(CURDIR) modules + +@@ -78,8 +100,8 @@ + BUILD_IOCTL32 := $(CONFIG_IA32_EMULATION) + endif + +-EXTRA_CFLAGS := -DEM8300_VIDEOMODE_DEFAULT=EM8300_VIDEOMODE_PAL \ +- -DEM8300_AUDIOMODE_DEFAULT=EM8300_AUDIOMODE_ANALOG \ ++EXTRA_CFLAGS := -DEM8300_VIDEOMODE_DEFAULT=$(shell printf "%s" "$${EM8300_VIDEOMODE_DEFAULT:-EM8300_VIDEOMODE_PAL}") \ ++ -DEM8300_AUDIOMODE_DEFAULT=$(shell printf "%s" "$${EM8300_AUDIOMODE_DEFAULT:-EM8300_AUDIOMODE_ANALOG}") \ + -DEM8300_VERSION=\"$(EM8300_VERSION)\" \ + -DCONFIG_ADV717X_PIXELPORT16BIT -DCONFIG_ADV717X_PIXELPORTPAL \ + -DCONFIG_EM8300_DICOMPAL -DCONFIG_EM8300_DICOMFIX \ --- em8300-0.18.0.orig/debian/patches/02_compat_2.6.26.dpatch +++ em8300-0.18.0/debian/patches/02_compat_2.6.26.dpatch @@ -0,0 +1,162 @@ +#! /bin/sh /usr/share/dpatch/dpatch-run +## 02_compat_2.6.26.dpatch by Nicolas Boullis +## +## All lines beginning with `## DP:' are a description of the patch. +## DP: Fix compatibility with the 2.6.26 kernel. +## DP: Patches taken from upstream's mercurial repository (changesets +## DP: 1f6e519f4e6d and 8bfd80c74fa2) whose descriptions are: +## DP: As proc_root export has been removed (commit: +## DP: c74c120a21d87b0b6925ada5830d8cac21e852d9), we need to replace +## DP: proc_root with NULL to get this part of driver compiling again. +## DP: and: +## DP: Handle the removal of the class_device structure in linux 2.6.26. +## DP: +## DP: Thanks to Christian Gmeiner who noticed the proble, and proposed +## DP: a patch to solve the problem (in a different way). +## DP: +## DP: Small "regression": em8300_ma-#, em8300_mv-# and em8300_sp-# are +## DP: no longer subdevices of em8300-#. + + +@DPATCH@ +diff -urNad em8300-0.16.4~/include/linux/em8300.h em8300-0.16.4/include/linux/em8300.h +--- em8300-0.16.4~/include/linux/em8300.h 2008-01-03 00:17:29.000000000 +0100 ++++ em8300-0.16.4/include/linux/em8300.h 2008-08-07 00:56:48.000000000 +0200 +@@ -268,14 +268,6 @@ + ulong memsize; + + int playmode; +- +- /* Sysfs */ +-#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,5,46) +- struct class_device *classdev; +- struct class_device *classdev_mv; +- struct class_device *classdev_ma; +- struct class_device *classdev_sp; +-#endif + + #if defined(CONFIG_SND) || defined(CONFIG_SND_MODULE) + snd_card_t *alsa_card; +diff -urNad em8300-0.16.4~/modules/em8300_procfs.c em8300-0.16.4/modules/em8300_procfs.c +--- em8300-0.16.4~/modules/em8300_procfs.c 2007-03-07 00:04:32.000000000 +0100 ++++ em8300-0.16.4/modules/em8300_procfs.c 2008-08-07 00:56:43.000000000 +0200 +@@ -169,7 +169,7 @@ + static void em8300_procfs_unregister_driver(void) + { + if (em8300_proc) { +- remove_proc_entry(EM8300_PROCFS_DIR, &proc_root); ++ remove_proc_entry(EM8300_PROCFS_DIR, NULL); + } + } + +@@ -177,7 +177,7 @@ + { + em8300_proc = create_proc_entry(EM8300_PROCFS_DIR, + S_IFDIR | S_IRUGO | S_IXUGO, +- &proc_root); ++ NULL); + if (em8300_proc) { + em8300_proc->owner = THIS_MODULE; + } else { +diff -urNad em8300-0.16.4~/modules/em8300_udev.c em8300-0.16.4/modules/em8300_udev.c +--- em8300-0.16.4~/modules/em8300_udev.c 2007-03-03 00:00:35.000000000 +0100 ++++ em8300-0.16.4/modules/em8300_udev.c 2008-08-07 00:56:48.000000000 +0200 +@@ -29,9 +29,21 @@ + #if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,13) + #define class class_simple + #define class_create class_simple_create +-#define class_device_create class_simple_device_add +-#define class_device_destroy(cls, dev) class_simple_device_remove(dev) + #define class_destroy class_simple_destroy ++#define device_create(cls, parent, devt, fmt, args...) \ ++ class_simple_device_add(cls, devt, parent, fmt, ## args) ++#define device_destroy(cls, devt) \ ++ class_simple_device_remove(devt) ++#elif LINUX_VERSION_CODE < KERNEL_VERSION(2,6,15) ++#define device_create(cls, parent, devt, fmt, args...) \ ++ class_device_create(cls, devt, parent, fmt, ## args) ++#define device_destroy(cls, devt) \ ++ class_device_destroy(cls, devt) ++#elif LINUX_VERSION_CODE < KERNEL_VERSION(2,6,18) ++#define device_create(cls, parent, devt, fmt, args...) \ ++ class_device_create(cls, NULM, devt, parent, fmt, ## args) ++#define device_destroy(cls, devt) \ ++ class_device_destroy(cls, devt) + #endif + + #include "em8300_params.h" +@@ -45,58 +57,38 @@ + + static void em8300_udev_register_card(struct em8300_s *em) + { +- em->classdev = class_device_create(em8300_class, +-#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,15) +- NULL, +-#endif +- MKDEV(major, em->card_nr * 4 + 0), +- &em->dev->dev, +- "%s-%d", +- EM8300_LOGNAME, em->card_nr); ++ device_create(em8300_class, &em->dev->dev, ++ MKDEV(major, em->card_nr * 4 + 0), ++ "%s-%d", EM8300_LOGNAME, em->card_nr); + } + + static void em8300_udev_enable_card(struct em8300_s *em) + { +- em->classdev_mv = class_device_create(em8300_class, +-#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,15) +- em->classdev, +-#endif +- MKDEV(major, em->card_nr * 4 + 1), +- &em->dev->dev, +- "%s_mv-%d", +- EM8300_LOGNAME, em->card_nr); ++ device_create(em8300_class, &em->dev->dev, ++ MKDEV(major, em->card_nr * 4 + 1), ++ "%s_mv-%d", EM8300_LOGNAME, em->card_nr); + if ((audio_driver_nr[em->card_nr] == AUDIO_DRIVER_OSSLIKE) + || (audio_driver_nr[em->card_nr] == AUDIO_DRIVER_OSS)) +- em->classdev_ma = class_device_create(em8300_class, +-#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,15) +- em->classdev, +-#endif +- MKDEV(major, em->card_nr * 4 + 2), +- &em->dev->dev, +- "%s_ma-%d", +- EM8300_LOGNAME, em->card_nr); +- em->classdev_sp = class_device_create(em8300_class, +-#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,15) +- em->classdev, +-#endif +- MKDEV(major, em->card_nr * 4 + 3), +- &em->dev->dev, +- "%s_sp-%d", +- EM8300_LOGNAME, em->card_nr); ++ device_create(em8300_class, &em->dev->dev, ++ MKDEV(major, em->card_nr * 4 + 2), ++ "%s_ma-%d", EM8300_LOGNAME, em->card_nr); ++ device_create(em8300_class, &em->dev->dev, ++ MKDEV(major, em->card_nr * 4 + 3), ++ "%s_sp-%d", EM8300_LOGNAME, em->card_nr); + } + + static void em8300_udev_disable_card(struct em8300_s *em) + { +- class_device_destroy(em8300_class, MKDEV(major, em->card_nr * 4 + 1)); ++ device_destroy(em8300_class, MKDEV(major, em->card_nr * 4 + 1)); + if ((audio_driver_nr[em->card_nr] == AUDIO_DRIVER_OSSLIKE) + || (audio_driver_nr[em->card_nr] == AUDIO_DRIVER_OSS)) +- class_device_destroy(em8300_class, MKDEV(major, em->card_nr * 4 + 2)); +- class_device_destroy(em8300_class, MKDEV(major, em->card_nr * 4 + 3)); ++ device_destroy(em8300_class, MKDEV(major, em->card_nr * 4 + 2)); ++ device_destroy(em8300_class, MKDEV(major, em->card_nr * 4 + 3)); + } + + static void em8300_udev_unregister_card(struct em8300_s *em) + { +- class_device_destroy(em8300_class, MKDEV(major, em->card_nr * 4 + 0)); ++ device_destroy(em8300_class, MKDEV(major, em->card_nr * 4 + 0)); + } + + static void em8300_udev_unregister_driver(void) --- em8300-0.18.0.orig/debian/patches/10_modules_em8300_header.dpatch +++ em8300-0.18.0/debian/patches/10_modules_em8300_header.dpatch @@ -0,0 +1,223 @@ +#! /bin/sh /usr/share/dpatch/dpatch-run +## 10_modules_em8300_header.dpatch by Nicolas Boullis +## +## All lines beginning with `## DP:' are a description of the patch. +## DP: #include the local copy of em8300.h . + +@DPATCH@ +diff -urNad em8300-0.16.2~/modules/adv717x.c em8300-0.16.2/modules/adv717x.c +--- em8300-0.16.2~/modules/adv717x.c 2007-07-14 21:45:48.000000000 +1000 ++++ em8300-0.16.2/modules/adv717x.c 2007-07-14 21:45:54.000000000 +1000 +@@ -47,7 +47,7 @@ + + #include "em8300_compat24.h" + #include "em8300_reg.h" +-#include ++#include "em8300.h" + + #include "adv717x.h" + #include "encoder.h" +diff -urNad em8300-0.16.2~/modules/em8300_alsa.c em8300-0.16.2/modules/em8300_alsa.c +--- em8300-0.16.2~/modules/em8300_alsa.c 2007-07-14 21:45:48.000000000 +1000 ++++ em8300-0.16.2/modules/em8300_alsa.c 2007-07-14 21:45:54.000000000 +1000 +@@ -26,7 +26,7 @@ + #include + #include + #include +-#include ++#include "em8300.h" + #include + #include + #include +diff -urNad em8300-0.16.2~/modules/em8300_audio.c em8300-0.16.2/modules/em8300_audio.c +--- em8300-0.16.2~/modules/em8300_audio.c 2007-07-14 21:45:48.000000000 +1000 ++++ em8300-0.16.2/modules/em8300_audio.c 2007-07-14 21:45:54.000000000 +1000 +@@ -19,7 +19,7 @@ + #include + + #include "em8300_reg.h" +-#include ++#include "em8300.h" + #include "em8300_fifo.h" + + #ifndef AFMT_AC3 +diff -urNad em8300-0.16.2~/modules/em8300_dicom.c em8300-0.16.2/modules/em8300_dicom.c +--- em8300-0.16.2~/modules/em8300_dicom.c 2007-07-14 21:45:48.000000000 +1000 ++++ em8300-0.16.2/modules/em8300_dicom.c 2007-07-14 21:45:54.000000000 +1000 +@@ -18,7 +18,7 @@ + #include + + #include "em8300_reg.h" +-#include ++#include "em8300.h" + + #include "em8300_params.h" + +diff -urNad em8300-0.16.2~/modules/em8300_eeprom.c em8300-0.16.2/modules/em8300_eeprom.c +--- em8300-0.16.2~/modules/em8300_eeprom.c 2007-03-25 10:41:32.000000000 +1000 ++++ em8300-0.16.2/modules/em8300_eeprom.c 2007-07-14 21:51:02.000000000 +1000 +@@ -19,7 +19,7 @@ + */ + + #include "em8300_eeprom.h" +-#include ++#include "em8300.h" + #include + #include + #include +diff -urNad em8300-0.16.2~/modules/em8300_fifo.c em8300-0.16.2/modules/em8300_fifo.c +--- em8300-0.16.2~/modules/em8300_fifo.c 2007-07-14 21:45:48.000000000 +1000 ++++ em8300-0.16.2/modules/em8300_fifo.c 2007-07-14 21:45:54.000000000 +1000 +@@ -46,7 +46,7 @@ + #include + + #include "em8300_reg.h" +-#include ++#include "em8300.h" + #include "em8300_fifo.h" + + #include "em8300_compat24.h" +diff -urNad em8300-0.16.2~/modules/em8300_i2c.c em8300-0.16.2/modules/em8300_i2c.c +--- em8300-0.16.2~/modules/em8300_i2c.c 2007-07-14 21:45:48.000000000 +1000 ++++ em8300-0.16.2/modules/em8300_i2c.c 2007-07-14 21:45:54.000000000 +1000 +@@ -19,7 +19,7 @@ + + #include "em8300_compat24.h" + #include "em8300_reg.h" +-#include ++#include "em8300.h" + + #include "adv717x.h" + #include "bt865.h" +diff -urNad em8300-0.16.2~/modules/em8300_ioctl.c em8300-0.16.2/modules/em8300_ioctl.c +--- em8300-0.16.2~/modules/em8300_ioctl.c 2007-07-14 21:45:48.000000000 +1000 ++++ em8300-0.16.2/modules/em8300_ioctl.c 2007-07-14 21:45:54.000000000 +1000 +@@ -22,7 +22,7 @@ + #include + + #include "em8300_reg.h" +-#include ++#include "em8300.h" + #include "em8300_fifo.h" + + #include "encoder.h" +diff -urNad em8300-0.16.2~/modules/em8300_ioctl32.c em8300-0.16.2/modules/em8300_ioctl32.c +--- em8300-0.16.2~/modules/em8300_ioctl32.c 2007-07-14 21:45:48.000000000 +1000 ++++ em8300-0.16.2/modules/em8300_ioctl32.c 2007-07-14 21:45:54.000000000 +1000 +@@ -37,7 +37,7 @@ + #include + + #include "em8300_reg.h" +-#include ++#include "em8300.h" + #include "em8300_ioctl32.h" + + typedef struct { +diff -urNad em8300-0.16.2~/modules/em8300_main.c em8300-0.16.2/modules/em8300_main.c +--- em8300-0.16.2~/modules/em8300_main.c 2007-07-14 21:45:48.000000000 +1000 ++++ em8300-0.16.2/modules/em8300_main.c 2007-07-14 21:45:54.000000000 +1000 +@@ -54,7 +54,7 @@ + #include "encoder.h" + + #include "em8300_reg.h" +-#include ++#include "em8300.h" + #include "em8300_fifo.h" + #include "em8300_registration.h" + #include "em8300_params.h" +diff -urNad em8300-0.16.2~/modules/em8300_misc.c em8300-0.16.2/modules/em8300_misc.c +--- em8300-0.16.2~/modules/em8300_misc.c 2007-07-14 21:45:48.000000000 +1000 ++++ em8300-0.16.2/modules/em8300_misc.c 2007-07-14 21:45:54.000000000 +1000 +@@ -18,7 +18,7 @@ + #include + + #include "em8300_reg.h" +-#include ++#include "em8300.h" + + #include + +diff -urNad em8300-0.16.2~/modules/em8300_params.c em8300-0.16.2/modules/em8300_params.c +--- em8300-0.16.2~/modules/em8300_params.c 2007-03-09 09:48:00.000000000 +1000 ++++ em8300-0.16.2/modules/em8300_params.c 2007-07-14 21:46:38.000000000 +1000 +@@ -19,7 +19,7 @@ + */ + + #include "em8300_params.h" +-#include ++#include "em8300.h" + #include + #include + +diff -urNad em8300-0.16.2~/modules/em8300_registration.h em8300-0.16.2/modules/em8300_registration.h +--- em8300-0.16.2~/modules/em8300_registration.h 2007-07-14 21:45:48.000000000 +1000 ++++ em8300-0.16.2/modules/em8300_registration.h 2007-07-14 21:45:54.000000000 +1000 +@@ -27,7 +27,7 @@ + #include + #include + #include +-#include ++#include "em8300.h" + + struct em8300_registrar_s { + void (*register_driver)(void); +diff -urNad em8300-0.16.2~/modules/em8300_spu.c em8300-0.16.2/modules/em8300_spu.c +--- em8300-0.16.2~/modules/em8300_spu.c 2007-07-14 21:45:48.000000000 +1000 ++++ em8300-0.16.2/modules/em8300_spu.c 2007-07-14 21:45:54.000000000 +1000 +@@ -22,7 +22,7 @@ + #include + + #include "em8300_reg.h" +-#include ++#include "em8300.h" + #include "em8300_fifo.h" + + #include "em8300_compat24.h" +diff -urNad em8300-0.16.2~/modules/em8300_ucode.c em8300-0.16.2/modules/em8300_ucode.c +--- em8300-0.16.2~/modules/em8300_ucode.c 2007-07-14 21:45:48.000000000 +1000 ++++ em8300-0.16.2/modules/em8300_ucode.c 2007-07-14 21:45:54.000000000 +1000 +@@ -18,7 +18,7 @@ + #include + + #include "em8300_reg.h" +-#include ++#include "em8300.h" + + #include + +diff -urNad em8300-0.16.2~/modules/em8300_video.c em8300-0.16.2/modules/em8300_video.c +--- em8300-0.16.2~/modules/em8300_video.c 2007-07-14 21:45:48.000000000 +1000 ++++ em8300-0.16.2/modules/em8300_video.c 2007-07-14 21:45:54.000000000 +1000 +@@ -22,7 +22,7 @@ + #include + + #include "em8300_reg.h" +-#include ++#include "em8300.h" + #include "em8300_fifo.h" + + #include +diff -urNad em8300-0.16.2~/modules/em9010.c em8300-0.16.2/modules/em9010.c +--- em8300-0.16.2~/modules/em9010.c 2007-07-14 21:45:48.000000000 +1000 ++++ em8300-0.16.2/modules/em9010.c 2007-07-14 21:45:54.000000000 +1000 +@@ -19,7 +19,7 @@ + #include + + #include "em8300_reg.h" +-#include ++#include "em8300.h" + + /* sub_2ac2d */ + static int testcable(struct em8300_s *em) +diff -urNad em8300-0.16.2~/modules/encoder.h em8300-0.16.2/modules/encoder.h +--- em8300-0.16.2~/modules/encoder.h 2007-07-14 21:45:48.000000000 +1000 ++++ em8300-0.16.2/modules/encoder.h 2007-07-14 21:45:54.000000000 +1000 +@@ -1,7 +1,7 @@ + #ifndef _ENCODER_H_ + #define _ENCODER_H_ + +-#include ++#include "em8300.h" + + #define ENCODER_MODE_NTSC 1 + #define ENCODER_MODE_NTSC60 2 --- em8300-0.18.0.orig/debian/patches/01_compat_2.6.25.dpatch +++ em8300-0.18.0/debian/patches/01_compat_2.6.25.dpatch @@ -0,0 +1,56 @@ +#! /bin/sh /usr/share/dpatch/dpatch-run +## 01_compat_2.6.25.dpatch by Nicolas Boullis +## +## All lines beginning with `## DP:' are a description of the patch. +## DP: Fix compatibility with the 2.6.25 kernel. +## DP: Patch taken from upstream's mercurial repository (changeset 09eafeb5970a) +## DP: whose description is: +## DP: Work around the removal of I2C_DRIVERID_EEPROM in linux 2.6.25-rc3. +## DP: Many thanks to Christian Gmeiner who noticed the removal (and proposed a +## DP: patch), and Jean Delvare who explained his changes to linux and helped +## DP: me solve the problem. + + +@DPATCH@ +diff -urNad em8300-0.16.4~/modules/em8300_i2c.c em8300-0.16.4/modules/em8300_i2c.c +--- em8300-0.16.4~/modules/em8300_i2c.c 2008-05-17 23:27:57.000000000 +0200 ++++ em8300-0.16.4/modules/em8300_i2c.c 2008-05-17 23:31:57.000000000 +0200 +@@ -177,10 +177,19 @@ + em->encoder = client; + EM8300_I2C_MAKE_LINK("encoder"); + break; ++#ifdef I2C_DRIVERID_EEPROM + case I2C_DRIVERID_EEPROM: + EM8300_I2C_MAKE_LINK("eeprom"); + break; ++#endif + default: ++#ifndef I2C_DRIVERID_EEPROM ++ if ((client->addr == 0x50) && ++ (strcmp(client->name, "eeprom") == 0)) { ++ EM8300_I2C_MAKE_LINK("eeprom"); ++ break; ++ } ++#endif + printk(KERN_ERR "em8300_i2c: unknown client id\n"); + return -ENODEV; + } +@@ -205,9 +214,18 @@ + #endif + #endif + break; ++#ifdef I2C_DRIVERID_EEPROM + case I2C_DRIVERID_EEPROM: + sysfs_remove_link(&em->dev->dev.kobj, "eeprom"); + break; ++#else ++ default: ++ if ((client->addr == 0x50) && ++ (strcmp(client->name, "eeprom") == 0)) { ++ sysfs_remove_link(&em->dev->dev.kobj, "eeprom"); ++ break; ++ } ++#endif + } + + return 0; --- em8300-0.18.0.orig/debian/patches/05_modules_Makefile.dpatch +++ em8300-0.18.0/debian/patches/05_modules_Makefile.dpatch @@ -0,0 +1,46 @@ +#!/bin/sh -e +## 05_modules_Makefile.dpatch by Nicolas Boullis +## +## All lines beginning with `## DP:' are a description of the patch. +## DP: When building modules, no need for ../include/ . + +if [ $# -lt 1 ]; then + echo >&2 "`basename $0`: script expects -patch|-unpatch as argument" + exit 1 +fi + +[ -f debian/patches/00patch-opts ] && . debian/patches/00patch-opts +patch_opts="${patch_opts:--f --no-backup-if-mismatch}" + +case "$1" in + -patch) patch $patch_opts -p1 < $0;; + -unpatch) patch $patch_opts -p1 -R < $0;; + *) + echo >&2 "`basename $0`: script expects -patch|-unpatch as argument" + exit 1;; +esac + +exit 0 + +@DPATCH@ +diff -urNad em8300-0.16.4~/modules/Makefile em8300-0.16.4/modules/Makefile +--- em8300-0.16.4~/modules/Makefile 2008-02-05 01:22:07.000000000 +0100 ++++ em8300-0.16.4/modules/Makefile 2008-02-05 01:23:23.000000000 +0100 +@@ -30,7 +30,6 @@ + #export EM8300_I2C_FORCE_API := NEW + + export EM8300_VERSION := "0.16.4" +-export EM8300_DIR := $(CURDIR)/.. + export INSTALL_MOD_DIR=em8300 + + build: +@@ -79,8 +78,7 @@ + BUILD_IOCTL32 := $(CONFIG_IA32_EMULATION) + endif + +-EXTRA_CFLAGS := -I$(EM8300_DIR)/include \ +- -DEM8300_VIDEOMODE_DEFAULT=EM8300_VIDEOMODE_PAL \ ++EXTRA_CFLAGS := -DEM8300_VIDEOMODE_DEFAULT=EM8300_VIDEOMODE_PAL \ + -DEM8300_AUDIOMODE_DEFAULT=EM8300_AUDIOMODE_ANALOG \ + -DEM8300_VERSION=\"$(EM8300_VERSION)\" \ + -DCONFIG_ADV717X_PIXELPORT16BIT -DCONFIG_ADV717X_PIXELPORTPAL \ --- em8300-0.18.0.orig/debian/modules-tools.d/README.debian.in +++ em8300-0.18.0/debian/modules-tools.d/README.debian.in @@ -0,0 +1,120 @@ + Debian Creative Labs Dxr3 / Sigma Designs Hollywood driver _version_ + README File + + +This is the Debian GNU/Linux prepackaged version of the _version_ drivers +package. + +By default, debian/rules will set the kernel-specific options from the +kernel source tree in /usr/src/linux. + +You need to have a complete linux source tree for your kernel, not just an +up-to-date kernel image, to compile the em8300 drivers. The em8300 modules +contain some references to kernel source files. While you may want to +build a new kernel to remove unnecessary drivers, installing em8300 does +not require you to do so. + +To recompile the em8300 Version _version_ kernel modules: + + The process of recompiling a kernel and the em8300 _version_ modules + has been greatly simplified by Debian's kernel-package package + (available in Debian's main distribution). This package contains + the make-kpkg utility, which is used to create the kernel related + Debian packages. It is highly recommended that you use this utility. + + If you are using make-kpkg: + + 0) Check whether `Recomends' packages of alsa-source are installed. + You need to install them if you use make-kpkg. + + 1) Unpack /usr/src/em8300-_version_.tar.bz2 into your working + directory. + !!WARMING!! + If you use same working directory where an old version of the source + is put, then you remove the old source before extracting this new + source. + + 2) Go to the the base of the kernel source tree (usually + the /usr/src/linux directory). If you are building a kernel that + is custom configured to your specifications, go ahead and + configure the kernel with `make config,' `make menuconfig,' or + `make xconfig.' + + 3) To build a new kernel-image package, execute: + make-kpkg --revision number kernel_image + as any root privilege. + This will generate a kernel-image- deb file in + the parent directory. Here number (the argument supplied after + the --revision flag) is a version number for your custom built + kernel. You may also do this on the fly by setting the + DEBIAN_REVISION environmental variable. It is important that you + choose the revision number in such a way that a generic kernel- + + image package will not override the custom package while using + dselect (or `dpkg -BOGiE'). I recommend a two-level scheme where + the major level starts with a letter. One such scheme is your + (short) host name followed by a dot (.) and a number. For + example, if your machine is named myhost, you would use + --revision myhost.1 in the command line. If you had to rebuild + your custom kernel, you would use --revision myhost.2 and so on. + See /usr/doc/kernel-package/README.gz for more information on + revision numbers. + + 3) To build the em8300 modules, execute: + make-kpkg --revision number modules_image + with setting MODULE_LOC environment variable: + /your_working_directory/modules/ + where number is the same revision number used to build the + kernel-image package in the previous step. This will generate a + alsa-modules- deb file in the parent directory. + + MODULE_LOC environment variable specifies a top directory + where kernel module sources you want to build are put. + For example, if you want to build em8300 _VERSION_ and the source + are put in ~/modules/em8300_VERSION_/, then you need to + set MODULE_LOC="~/modules". + + 4) Install the two newly created deb files (you can use `dpkg -i + file'). + + If you are not using make-kpkg: + + If your kernel is compiled with CONFIG_MODVERSIONS enabled, for kernel + symbol version checking, the configure script will check for the + existence of /usr/include/linux/modversions.h, the symbol version + database. This is created by running `make dep' (in addition to `make + config) in the kernel source tree. + + 1) Ensure that the kernel source tree is in the /usr/src/linux + directory and ensure that it is configured (execute `make config + dep' in the /usr/src/linux directory). + + 2) Go to the em8300_VERSION_ root directory. + + 3) Execute as root (or fakeroot) `debian/rules binary-modules'. This + will generate an em8300_VERSION_- deb file in the + parent directory. + + You must manually set KDREV environment variable, which specifies + the Debian kernel revision on which this em8300 modules package + depends. For example, if the Debian revision of the kernel package + is Custom.1, the proper command would be + debian/rules KDREV=Custom.1 binary-modules + + The em8300 package will have a recommendation of + kernel-image- (= Custom.1) + + Note: The location of the kernel source tree may be specified by + supplying the KSRC variable as a command line option. For example, if + the kernel source is located in /usr/local/src/kernel-2.0.0, the + proper command would be + debian/rules KSRC=/usr/local/src/kernel-2.0.0 binary-modules + + +This document is almost an exact copy of the documentation for the pcmcia +packages made by Brian Mays . +Dynamic options propagation and more descriptions for alsa + written by Masato Taruishi +So most of this is taken from the alsa-driver package + +Changes to em8300 have been made by Michael Moerz --- em8300-0.18.0.orig/debian/modules-tools.d/postinst +++ em8300-0.18.0/debian/modules-tools.d/postinst @@ -0,0 +1,5 @@ +#!/bin/sh -e + +# Let dh_installmodules handle depmodding now. + +#DEBHELPER# --- em8300-0.18.0.orig/debian/modules-tools.d/rules +++ em8300-0.18.0/debian/modules-tools.d/rules @@ -0,0 +1,207 @@ +#!/usr/bin/make -f +# +# taken from alsa-drivers +# changes were done by Michael Moerz +# and by Nicolas Boullis +# and by Brendon Higgins +# +############################# variable definitions ############################ + +export INTERNAL_DESTDIR=debian/tmp + +# unset ROOTCMD if already running as root +ifeq ($(shell id -u),0) +ROOT_CMD = +endif + +# set version to nothing +VERSION = + +# KSRC is the location of the kernel source. This is the default value, +# when make-kpkg is used it will supply to real value +ifndef KSRC +KSRC = /usr/src/linux +endif + +# KDREV is the package-revision, as given to make-kpkg by the user. +# Just put a simply default value in here which we use when we test +# the packagebuilding without make-kpkg +ifeq ($(strip $(KDREV)),) +KDREV = "1.00.Custom" +endif + +## Now to determine the kernel version, normally supplied by make-kpkg +ifeq ($(strip $(KVERS)),) +# Now we need to get the kernel-version somehow (we are not running +# under make-kpkg?) +ifeq ($(strip $(KSRC)),) +$(error Error. I do not know how to determine the kernel version) +else +kversion :=$(shell egrep '^VERSION +=' $(KSRC)/Makefile 2>/dev/null | \ + sed -e 's/[^0-9]*\([0-9]*\)/\1/') +kplevel :=$(shell egrep '^PATCHLEVEL +=' $(KSRC)/Makefile 2>/dev/null | \ + sed -e 's/[^0-9]*\([0-9]*\)/\1/') +ksublevel:=$(shell egrep '^SUBLEVEL +=' $(KSRC)/Makefile 2>/dev/null | \ + sed -e 's/[^0-9]*\([0-9]*\)/\1/') +EXTRA_VERSION:=$(shell egrep '^EXTRAVERSION +=' $(KSRC)/Makefile 2>/dev/null |\ + sed -e 's/EXTRAVERSION[\t ]*=[\t ]*\(.*\)/\1/') +kextra:=$(strip $(EXTRA_VERSION)) +HAVE_NEW_MODLIB:=$(shell egrep '\(INSTALL_MOD_PATH\)' \ + $(KSRC)/Makefile 2>/dev/null ) + +# If you want to have more than one kernel configuration per kernel +# version, set FLAVOUR in the top level kernel Makefile *before* +# invoking make-kpkg -- it will be appended to UTS_RELEASE in +# version.h (separated by a hyphen). This affects everything -- the +# names and versions of the image, source, headers, and doc packages, +# and where the modules are searched for in /lib/modules. + +ifdef FLAVOUR +# uhm - should check if we really have a Makefile capable of Flavours? +endif + +FLAVOUR:=$(shell grep ^FLAVOUR $(KSRC)/Makefile 2>/dev/null | \ + perl -ple 's/FLAVOUR[\s:=]+//g') + +ifneq ($(strip $(FLAVOUR)),) +INT_FLAV := -$(FLAVOUR) +FLAV_ARG := FLAVOUR=$(FLAVOUR) +else +INT_FLAV := +FLAV_ARG := +endif + +## This is the replacement for FLAVOUR +ifneq ($(strip $(APPEND_TO_VERSION)),) +iatv := $(strip $(APPEND_TO_VERSION)) +EXTRAV_ARG := EXTRAVERSION=${EXTRA_VERSION}${iatv} +else +iatv := +EXTRAV_ARG := +endif + +KVERS = $(kversion).$(kplevel).$(ksublevel)$(kextra)$(iatv)$(INT_FLAV) + +endif +else +kversion:=$(shell echo $(KVERS) | cut -d. -f1) +kplevel:=$(shell echo $(KVERS) | cut -d. -f2) +ksublevel:=$(shell echo $(KVERS) | cut -d. -f3 | sed -e 's/^\([0-9]*\)[^0-9].*$$/\1/') +endif + +non_epoch_version=$(shell echo $(KVERS) | perl -pe 's/^\d+://') +epoch=$(shell echo $(KVERS) | perl -ne 'm/^(\d+:)/ && print $$1') + +ifeq ($(KPKG_STEM),) + # better work out what KPKG_STEM should be + # idea flangrantly stolen from module-assistant + # Debian started using "linux" with 2.6.12 + ifneq ($(kversion),) + ifneq ($(kplevel),) + ifneq ($(ksublevel),) + KPKG_STEM:=$(shell if expr $(kversion) \* 10000 + $(kplevel) \* 100 + $(ksublevel) \>= 20612 > /dev/null; then echo "linux"; else echo "kernel"; fi) + endif + endif + endif +endif + +# We also need the package name and version +package = $(shell sed -ne '1s/^\(.*\) (.*).*/\1/p' debian/changelog) +version = $(shell sed -ne '1s/.*(\(.*\)).*/\1/p' debian/changelog) +packagename = $(package)-modules-$(KVERS)$(INT_SUBARCH) + +export DH_OPTIONS = -p$(packagename) + +topdir=$(shell pwd) + +# MODDIR is the place where the final .deb package should be made. This is the +# default value, when make-kpkg is used it will supply to real value +ifndef MODDIR +MODDIR = .. +endif + +ifndef MODULE_SOURCE +MODULE_SOURCE=modules +endif + +##################### module targets (to build source .deb) ################## + +DEB_MTOOLS=debian/modules-tools.d + +MODULES_SRC=debian/$(srcpkg)/usr/src/modules/$(package)-$(version) +MODULES_DEB_MTOOLS=$(MODULES_SRC)/$(DEB_MTOOLS) +MODULES_DEST=$(topdir)/debian/$(srcpkg)/usr/src/modules/$(package)-$(version) + +build-modules: + $(MAKE) $(MFLAGS) KERNEL_LOCATION=$(KSRC) + +binary-modules: clean-modules build-modules + dh_testdir + dh_testroot + +# generate substitutions + echo "kvers=$(KVERS)$(INT_SUBARCH)" >> debian/substvars + echo "kversdeb=$(KDREV)" >> debian/substvars + echo "kstem=$(KPKG_STEM)" >> debian/substvars + echo "debian/substvars" >>stamp-debian + + perl debian/scripts/dh_modulecontrol --module + + install -d debian/$(packagename) + dh_installdirs + + $(MAKE) $(MFLAGS) install KERNEL_LOCATION=$(KSRC) DESTDIR=$(topdir)/debian/$(packagename) + + # Remove the map files generated by depmod (run by make install) + find $(topdir)/debian/$(packagename)/lib/modules/$(KVERS) -maxdepth 1 -type f -exec rm {} \; + + dh_installdocs + dh_installmodules + dh_installchangelogs + dh_link + dh_strip + dh_compress + dh_fixperms + dh_installdeb +# dh_shlibdeps + dh_gencontrol -- -v$(version)+$(KDREV) -cdebian/$(packagename).control + dh_md5sums + dh_builddeb --destdir=$(MODDIR) + +clean-modules: + $(MAKE) $(MFLAGS) KERNEL_LOCATION=$(KSRC) clean + perl debian/scripts/dh_modulecontrol --module --clean + rm -rf $(topdir)/debian/$(packagename) + -if [ -f stamp-debian ]; then rm -f `cat stamp-debian`; fi + -rm -f stamp-debian + +######################## make-kpkg interface ########################### + +# The kdist_configure target is called by make-kpkg modules_config. It +# should configure the module so it is ready for compilation (mostly +# useful for calling configure) +.PHONY: kdist_config +kdist_config: + @echo Nothing to configure + +# the kdist_image target is called by make-kpkg modules_image. It is +# responsible for compiling the module and creating the package. It +# should also clean up after making the module. Please note we use a +# seperate binary-modules target to make testing the package building +# easier +.PHONY: kdist_image +kdist_image: + $(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules MODDIR=$(KSRC)/.. binary-modules + $(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules MODDIR=$(KSRC)/.. clean-modules + +# the kdist_clean target is called by make-kpkg modules_clean. It is +# responsible for cleaning up any changes that have been made by the +# other kdist_commands (except for the .deb files created). +.PHONY: kdist_clean +kdist_clean: + $(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules MODDIR=$(KSRC)/.. clean-modules + +# kdist missing? what's kdist at all? +#kdist: + + --- em8300-0.18.0.orig/debian/modules-tools.d/README.debian +++ em8300-0.18.0/debian/modules-tools.d/README.debian @@ -0,0 +1,120 @@ + Debian Creative Labs Dxr3 / Sigma Designs Hollywood driver 0.9.0-1 + README File + + +This is the Debian GNU/Linux prepackaged version of the 0.9.0-1 drivers +package. + +By default, debian/rules will set the kernel-specific options from the +kernel source tree in /usr/src/linux. + +You need to have a complete linux source tree for your kernel, not just an +up-to-date kernel image, to compile the em8300 drivers. The em8300 modules +contain some references to kernel source files. While you may want to +build a new kernel to remove unnecessary drivers, installing em8300 does +not require you to do so. + +To recompile the em8300 Version 0.9.0-1 kernel modules: + + The process of recompiling a kernel and the em8300 0.9.0-1 modules + has been greatly simplified by Debian's kernel-package package + (available in Debian's main distribution). This package contains + the make-kpkg utility, which is used to create the kernel related + Debian packages. It is highly recommended that you use this utility. + + If you are using make-kpkg: + + 0) Check whether `Recomends' packages of alsa-source are installed. + You need to install them if you use make-kpkg. + + 1) Unpack /usr/src/em8300-0.9.0-1.tar.bz2 into your working + directory. + !!WARMING!! + If you use same working directory where an old version of the source + is put, then you remove the old source before extracting this new + source. + + 2) Go to the the base of the kernel source tree (usually + the /usr/src/linux directory). If you are building a kernel that + is custom configured to your specifications, go ahead and + configure the kernel with `make config,' `make menuconfig,' or + `make xconfig.' + + 3) To build a new kernel-image package, execute: + make-kpkg --revision number kernel_image + as any root privilege. + This will generate a kernel-image- deb file in + the parent directory. Here number (the argument supplied after + the --revision flag) is a version number for your custom built + kernel. You may also do this on the fly by setting the + DEBIAN_REVISION environmental variable. It is important that you + choose the revision number in such a way that a generic kernel- + + image package will not override the custom package while using + dselect (or `dpkg -BOGiE'). I recommend a two-level scheme where + the major level starts with a letter. One such scheme is your + (short) host name followed by a dot (.) and a number. For + example, if your machine is named myhost, you would use + --revision myhost.1 in the command line. If you had to rebuild + your custom kernel, you would use --revision myhost.2 and so on. + See /usr/doc/kernel-package/README.gz for more information on + revision numbers. + + 3) To build the em8300 modules, execute: + make-kpkg --revision number modules_image + with setting MODULE_LOC environment variable: + /your_working_directory/modules/ + where number is the same revision number used to build the + kernel-image package in the previous step. This will generate a + alsa-modules- deb file in the parent directory. + + MODULE_LOC environment variable specifies a top directory + where kernel module sources you want to build are put. + For example, if you want to build em8300 and the source + are put in ~/modules/em8300/, then you need to + set MODULE_LOC="~/modules". + + 4) Install the two newly created deb files (you can use `dpkg -i + file'). + + If you are not using make-kpkg: + + If your kernel is compiled with CONFIG_MODVERSIONS enabled, for kernel + symbol version checking, the configure script will check for the + existence of /usr/include/linux/modversions.h, the symbol version + database. This is created by running `make dep' (in addition to `make + config) in the kernel source tree. + + 1) Ensure that the kernel source tree is in the /usr/src/linux + directory and ensure that it is configured (execute `make config + dep' in the /usr/src/linux directory). + + 2) Go to the em8300 root directory. + + 3) Execute as root (or fakeroot) `debian/rules binary-modules'. This + will generate an em8300- deb file in the + parent directory. + + You must manually set KDREV environment variable, which specifies + the Debian kernel revision on which this em8300 modules package + depends. For example, if the Debian revision of the kernel package + is Custom.1, the proper command would be + debian/rules KDREV=Custom.1 binary-modules + + The em8300 package will have a recommendation of + kernel-image- (= Custom.1) + + Note: The location of the kernel source tree may be specified by + supplying the KSRC variable as a command line option. For example, if + the kernel source is located in /usr/local/src/kernel-2.0.0, the + proper command would be + debian/rules KSRC=/usr/local/src/kernel-2.0.0 binary-modules + + +This document is almost an exact copy of the documentation for the pcmcia +packages made by Brian Mays . +Dynamic options propagation and more descriptions for alsa + written by Masato Taruishi +So most of this is taken from the alsa-driver package + +Changes to em8300 have been made by Michael Moerz --- em8300-0.18.0.orig/debian/dxr3.sourceforge.net/howto.html +++ em8300-0.18.0/debian/dxr3.sourceforge.net/howto.html @@ -0,0 +1,644 @@ + + +Linux DXR3 and Hollywood+ Driver + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Dxr3 Logo

DXR3 & Hollywood Plus Logo

+ +Linux DXR3 and Hollywood+ Driver Project Howto + +
   
  + + + + News
+ About
+ FAQ
+ Howto
+ Download
+ Links
+ Developers
+ Project Page
+ + + + 		  + + + +DXR3 / Hollywood Plus HOWTO Table of Contents + + +
+ +

Prerequisites

+
    +

    + As with any project there are some prerequisites. Besides the obvious like, needing a computer running a recent version of Linux, you will, for now, need some experience building packages from scratch. You will also have to be comfortable with a text editor. Yeah, you know what that means. +

    +
  • Dxr3 or Hollywood Plus +

    + I hate to have to say it but before you can start watching DVDs and MPEG streams + using this driver, you need to have either a Creative Labs DXR3 or a Sigma Designs + Hollywood Plus hardware MPEG decoder card. If you have any other decoder card, this + driver is of no help to you. But if you have a fast enough computer you can still + watch MPEGs and DVDs on your monitor with one of the software viewers available. + (Remember, this wouldn't be here if someone didn't ask . . . ) +

    +
  • Kernel 2.2 or newer +

    + This driver will only work with Linux kernels version 2.2 and greater. If you are + running a 2.0 kernel, well then this is the time to get brave and upgrade! (And if + you are running 1.2 or 1.3 on modern hardware then you are either criminally insane + or a masochist, but that is a different story). But then there is the question, + does a computer old enough to be running a 2.0 kernel actually have enough power to + play a DVD - even with a hardware decoder card? Anyway, you'll need the source tree, + and you'll need to have run at least "make config" and "make dep" in that tree. +

    +
  • I2C Driver +

    + If you are running a 2.2 kernel, you need to install the I2C driver version 2.4.5 or + newer! You can get the I2C driver for 2.2 kernels at the LM Sensors Homepage. If you have + a 2.4 kernel, then I2C comes with the kernel and you just need to make sure that it + is compiled into the kernel or as a module. If you fail to do this, then your card + will emit X-Rays from your TV and cook your DNA! Just kidding. In either case, just + make sure that you have this I2C driver installed. +

    +
  • rmquasar.vxd (H+) or enc2dev.vxd (dxr3) + (as of driver 0.12.0 this is optional and not recommended unless you + have serious problems with the supplied microcode) +

    + You need the appropriate VxD from the Windows driver for your card. If you have a + Creative Labs Dxr3, then you will have enc2dev.vxd and if you have a Hollywood Plus, + then you'll have rmquasar.vxd. Easy enough. Now, you should be able to find these + bad boys in you windows/system directory. If you don't have a windows/system + directory because you don't have windows, then you can still get these guys. You + just need to obtain the latest version of your card's drivers from the appropriate + web site and unzip them. But wait, what the hell is that?!?! They only give us + rmquasar.vx_ and enc2dev.vx_! Where is the 'd'?!? They shorted us a 'd'! No, + actually, Microsoft, in their infinite corporate wisdom, long ago instituted the + policy of compressing their driver files for distribution, which strangely enough + are compressed again (as zips, cabs, self extracting exes, etc.) which just wastes + cpu cycles. And, if you haven't noticed, compressing a file twice rarely yields any + gain in compression. Now, since we are missing a 'd', note: a very special 'd', from + our driver file, we need to replace it. Included with the em8300 driver distribution + in the scripts directory is a perl program called msexpand.pl which, when run like + "msexpand.pl rmquasar.vx_", will after some time make a new copy of the file, this + time with the special 'd' replaced. Then you may continue. +

    +
  • Compiler and Related Tools +

    + You will need Perl and a C compiler. If you're building from a + CVS checkout, you'll need some GNU programs: automake and + autoconf. Those two also require GNU m4. Also, bootstrapping + a CVS checkout requires the development files for GTK+ 2.x + (in particular, its m4 macros). If you get errors later about + missing header files or libraries, you'll have to install + those as well. Chances are that suitable versions are + available in your distribution; if not, get them off the + Internet. +

    +
+ +

Getting the Source

+
    +

    There are currently two ways to get the source for this driver: by downloading a + 'stable' release or by downloading the latest CVS. Depending on how old the last release + is, it may be best to try out the CVS. +

    +
  • Download a Release +

    + If you decide to try one of the 'stable' releases, please note that as of yet none + are really quite stable. They are more akin to Mozilla's milestones in that there are + still many bugs to be worked out. +

    +
  • Source Via CVS +

    + #include <stdcvswarning.h>
    + Ok, yeah, you know CVS is often broken and unstable. Well, yeah, but we still need + you guys to check out from CVS and report those bugs. So please do. Also, plugin + updates for new releases of Xine and OMS are often available only on CVS for a long + period of time, so you really shouldn't be too shy about trying a CVS checkout. It + wont bite, I promise! Ok, the two steps to checking out the CVS are: +

    +$ cvs -d :pserver:anonymous@cvs.dxr3.sourceforge.net:/cvsroot/dxr3 login
    +CVS password: [Just press enter]
    +$ cvs -d :pserver:anonymous@cvs.dxr3.sourceforge.net:/cvsroot/dxr3 -z3 co em8300
    +
    + And that's it! You should have an em8300 directory under your current directory. In + there you'll find all the goodies you'll need later on. +

    +
+ +

Compiling the Modules

+
    +

    + Now we must compile the kernel modules and get them configured and loaded. +

    +
  • Makefile settings +

    + Ok, chdir to em8300/modules and open up the Makefile in your favorite editor. Now + change KERNEL_LOCATION to wherever your current kernel source tree is, and make sure + that you've at least run "make config ; make dep" in there. Now, change + -DEM8300_VIDEOMODE_DEFAULT= to EM8300_VIDEOMODE_PAL, EM8300_VIDEOMODE_PAL60, or + EM8300_VIDEOMODE_NTSC. If you live in the Americas, choose NTSC. Elsewhere (like + Europe), you're probably PAL. If you live in the former Soviet Union then your + standard is SECAM, which these cards do not support. You can probably get a PAL TV + or use VGA Overlay. Don't worry about these defaults too + much because they can be set at run time either by a dvd player with dxr3 support + or by the dhc utility. +

    +
  • If you have a 2.2 kernel (As of driver 0.11.0 this is no longer needed) +

    + If you are using a 2.2 kernel, just copy Makefile.2.2 to Makefile and follow the + instructions below. Make sure you have the I2C module compiled and installed. +

    +
  • Compiling +

    + Just run "make". This will build the four modules, adv717x.o, bt865.o, em8300.o, + and eeprom.o. To install the modules, run "make install". +

    +

    + If you have any trouble compiling the modules please send a detailed message to + the mailing list at dxr3-devel@lists.sourceforge.net. + Thanks. +

+ +

Creating the Device Files

+
    +

    + In Linux, and Unix in general, to communicate with a device you need to have a device + file. Well, the Dxr3 and H+ are no different. We currently use four device files, which + must be created as root. If you are running devfs or udev, these will be created automatically + and will use kernel assigned major/minor numbers, no need to read this section. +

    +
  • Creating the /dev/em8300* devices +

    To create the four device files, you must be root. + As root, run the modules/devices.sh script or + these commands: +

    # mknod /dev/em8300-0 c 121 0 +# mknod /dev/em8300_mv-0 c 121 1 +# mknod /dev/em8300_ma-0 c 121 2 +# mknod /dev/em8300_sp-0 c 121 3 + Note: The device numbers that we are using are currently using are likely to change + in the future. Keep that in mind. +

    +
    • +
+ +

Loading the Kernel Modules

+
    +
  • ldm and rmm +

    + In the em8300/modules directory there live two shell scripts related to loading and + unloading the kernel modules, ldm and rmm. ldm + automates loading of the driver modules, and rmm automates unloading of the modules. In + order to pass module parameters to the adv717x.o and em8300.o modules you must edit the + ldm script. Commented out underneath the lines to load the adv717x and em8300 modules + you can see some examples of the more commonly used module parameters. So, for example, + to set the adv717x module option "pixelport_16bit" to 0 and "pixelport_other_pal" to 1 you would have a line like the + following: +

    +insmod adv717x.o pixelport_16bit=0 pixelport_other_pal=1
    +
    + Enter other module options similarly. See the following table for a list of module + options and explanations of what they do. If you don't want to use ldm and rmm you + can just issue the appropriate modprobe/insmod/rmmod commands by themselves and + enter the module parameters on the command line or in /etc/modules.conf. Note, with + ldm, module options located in /etc/modules.conf will not be read, so if you use ldm + make sure to edit the module options in there. +

    +
  • Module Parameters +

    + There are multiple parameters for each of the modules that + affect their functionality. The choice of module options will + depend upon your particular board. Also, module options for + the adv717x driver do not matter for cards with a bt865 chip + and vice versa. Further, module options for the adv717x and + bt865 modules only matter for TV output and have no effect on + overlay. See + modules/README-modoptions + for the list of supported options, possible values, and their + descriptions as well as commonly used configurations. +

    +
+

All Things Microcode

+
    +

    + The em8300 RISC processor needs to be programed before use. This program is called a + "microcode" and we will use the one that has already been written for us. +

    +

    + Note that version 0.12.0 and later of the driver package comes + with a microcode, so just running em8300setup should be enough, + no need to extract your own. +

    +

    + Additionally, versions 0.15.2 and later have the capability to + load the microcode on demand, so even running em8300setup is no + longer needed for the purpose of just loading it. You may want to + run it for other purposes, though. +

    +

    + If you use the drivers in packaged form from your distribution, + chances are that the microcode is not included in the package. + If that is the case, read on. +

    +

    + A microcode that is known to work well for many users is + available separately from + http://dxr3.sourceforge.net/download/. + If you decide to use it, you can skip directly to the + loading section. +

    +
  • Uncompressing +

    + If you have downloaded a copy of the Windows driver (preferably the Windows 98 + driver) from Sigma Designs or Creative Labs or copied the driver from the cdrom, + then you will have to uncompress the driver files. If you have already installed the + Windows driver and have access to your windows/system directory, then you can skip + to the next section. First use unzip to uncompress and expand the driver archive. In + that archive you will find either rmquasar.vx_ or enc2dev.vx_ depending if you have + the Sigma Designs or Creative Labs drivers, respectively. Now we have to uncompress + this file. Use the provided perl program "msexpand.pl" located in em8300/scripts to + uncompress this file. For example: +

    $ unzip HP1_82W1.ZIP +$ em8300/scripts/msexpand.pl rmquasar.vx_ +

    +
  • Extracting +

    + Now that we have the uncompressed Windows 98 driver vxd, we need to extract the + microcode files. To do that use the included perl program microcode_extract.pl + located in em8300/scripts. After running this program two or three microcode files + will be written to the current directory, the number depending on the driver you + have. The different microcode versions seem to be for different revisions of the + cards. Currently, the only way to determine which microcode is correct for your + card is to try them all and pick the one that works the best. Do not be alarmed if + some of them do not work at all. +

    +
  • Loading +

    + At this point you should have the extracted microcode files + available. If you're using version 0.15.2 or newer, copy the microcode file to + wherever your system's hotplug configuration loads firmware images from (often + /lib/firmware), name it em8300.bin, and load the + modules; the microcode should be automatically uploaded. If not, or if using + version 0.15.1 or earlier, you can use the em8300setup tool to load it. Run + em8300setup -h and look at the -f option and where + it expects to find the microcode from, and copy the microcode there. The + included perl program microcode_upload.pl can also be used to load the + microcode into the em8300. For example: +

    $ em8300/scripts/microcode_upload.pl microcode0.bin + You should get a message like "Microcode uploaded to /dev/em8300-0". If there are + no messages then it was unable to open /dev/em8300-0 and you should verify that + the device file exists. If they do and you have the right permissions (if unsure + just chmod a+w /dev/em8300*) it usually means that you have the option "PNP OS + Installed" set to "enabled" in your bios. This option exists in virtually all x86 + bioses since the pentium. Disable this option, this means the bios will set up all + your plug and play device prior to booting the operating system. Windows has a bad + habit of randomizing pnp options on booting making it impossible for linux to save + any settings as they will have changed after booting into windows. Disabling pnp os + will fix this. +

    +

    + Note: This may cause vga passthrough to stop functioning. We are working on this. + The solution at this time is to just plug your monitor straight into the video card + or use the "activate_loopback" em8300 module option. You cannot watch MPEG streams + on the TV output connector with activate_loopback set, however. +

    +
+ +

Playing MPEG Streams and DVDs

+
    +

    + This section is all about playing MPEGs and DVDs. If you are using VGA loopback, first + see the VGA Overlay section then come right back here. If you are + playing on a TV, then make sure you have all your cables connected properly, and that + your TV is set to receive the composite signal generated by the card. So, since you are + following this document from top to bottom, you should be ready to go. +

    +
  • Playing MPEGs via /dev/em8300_mv-* and /dev/em8300_ma-* +

    + Sending mpeg and pcm streams directly to the card is a great way to test that the + thing is working properly without the overhead of working with a full on DVD player. + In order to display a MPEG video stream simply send it to "/dev/em8300_mv-0". + In order to test the analog audio capability of the card you can use mpg123. For + example: +

    $ extract_mpeg2 testvideostream.mpeg > /dev/em8300_mv-0 +$ mpg123 -a /dev/em8300_ma-0 somegoodtestmusic.mp3 + Note, you must send only MPEG video streams to /dev/em8300_mv-*, and only PCM audio to + /dev/em8300_ma-*. An MPEG system file, composed of both + video and audio, will cause garbage to be displayed on the screen. You must first + separate the system into video and audio components, and play each one separately. + Also, /dev/em8300-* is a control device, and cannot be use to play mpeg systems. +

    +
  • Using Xine to play DVDs +

    + A dxr3 plugin is included with Xine since Xine 0.5.0. Please see xine-lib/doc/README.dxr3 +

    +
  • Using MPlayer to play DVDs +

    + Invoke mplayer with the following options: "-ao oss:/dev/em8300_ma-0 -vo dxr3 -dvd <chapternumber>" +

    +
  • Using MPlayer to play DivX/RealVideo etc +

    + To play any non MPEG1/2 content with mplayer you have to specify an MPEG1 filter, you do this by + adding -vop lavc or -vop fame and you are good to go. If you are using gmplayer + (GUI enabled MPlayer) you can set the mpeg1 filter to use in + Preferences->Video->(dxr3)->Configure Driver. +

    +
  • Using OMS to play DVDs +

    + OMS was the original player for this project but since then development seems to + have stopped. Thus, we currently suggest you use Xine. This may change at some + future date. +

    +
+ +

Other Useful Programs

+
    +

    + In this section we describe some useful programs that have been contributed to the + project. +

    +
  • DHC by Ze'ev Maor +

    + DHC is a useful program written by Ze've Maor. DHC's source lives in the em8300/dhc + directory and it is built by default during the build process + if GTK+ 2.x's development files are available. + DHC can be used to adjust the brightness, contrast, saturation, aspect + ration, TV output standard (PAL, NTSC, and PAL 60), turn on and off the subpicture + (subtitles, etc.), and change between analog and spdif audio outputs. +

    +
+ +

Using VGA Overlay Mode

+
    +

    + VGA Overlay can be used to view hardware MPEG decoded streams on your computer monitor. + The main drawback of the Dxr3/H+ design is that using this feature results in added + noise and reduced visual quality on the monitor from the video card. So, you may notice + that your text that used to appear crisp is now fuzzy with the decoder card inserted. + Sorry, there is nothing we can do about this. If it bothers you too much, use a TV + instead. +

    +
  • Setting it up +

    + First, you must make sure that the overlay cable is correctly installed. Follow the + instructions that came with your card. Second, you may need to enable the + "activate_loopback" module option for the em8300 module. See the Module Parameters section above for details. Unload and reload the + modules for the change to take effect, if needed. Then you must load the microcode. + See the section All Things Microcode for help loading the + microcode. Now you should be ready to continue to the next section. Note: Overlay + support is considered experimental at this time and will probably not work. +

    +
  • dxr3view and autocal +

    + Again, run "bootstrap" in the em8300 directory, then run + configure, make, and make install. First, run autocal. This will make the screen + flash for a second. This has to be done every time the microcode is reloaded, which + means that you must load Xine or OMS before running autocal. Yeah, I know its silly. + Should be fixed in the future. Then you have to run dxr3view. This will bring up a + rectangular window with the overlay window on top. It should look akin to the + windows overlay. Now, you should be able to press play in Xine or OMS and watch your + MPEG. The control window in dxr3view can be used to fine tune the size, shape, and + appearance of the overlay to a certain extent. Also, if you press 't' while the + mouse is over the dxr3view window, a menu with several options, including + fullscreen, will appear. +

    +
+ +

Identifying your Card

+ +
    +

    Sometimes it is helpful to know some details about your particular board, especially + if you need help getting the driver to work. You can use the following table to help + figure out what card you have and if there are any special notes about it. +

    +
  • Sigma Designs Hollywood Plus Variants +

    + + + + + + + + + + + + + + + + + + + +
    Board IDEM8300 VersionVideo ChipNotes
    ???Rev 2ADV7170Requires pixelport_16=0
    ???Rev 2ADV7175Requires pixelport_16=1, dicom_control=1, dicom_fix=1
    +

    +
  • Creative Labs Dxr3 Variants +

    + + + + + + + + + + + + + +
    Board IDEM8300 VersionVideo ChipNotes
    ct7235-vbq (9938 rev b) board:ct7260Rev 2Conexant bt865akrf 
    +

    +
+ + +

Getting Help

+
    +

    + Eventually, every one of us needs a little help, especially with this hardware ;). There + are currently three ways to get help: IRC, the mailing list, and the Sourceforge Fora. + Note, the best way to get help is the Mailing list, and the least favorable is the + SourceForge Fora. This may change in the future, but currently not many developers visit + the SourceForge Fora. +

    +
  • Mailing List - Preferred Method +

    + By far the best way to get help is to send a message to the mailing list. This is + because all the developers are subscribed and read their email throughout the day. + The list is dxr3-devel@lists.sourceforge.net + and you can subscribe or unsubscribe at The SourceForge Project Mail + Page. +

    +
  • IRC Channel +

    + We have an IRC channel! Its #dxr3 on irc.openprojects.net. Come join us and ask + questions about the driver or just chat with the developers and other users. +

    +
  • Sourceforge Fora +

    + As nice as they are, we don't use them. But you really can't tell that by the number + of people who have posted to them. Do us all a favor, and just stay away from them + for now. Perhaps one day we may be popular enough to need them, but right now, just + say "no". +

    +
+ + + + 		  
+ + SourceForge Logo +   
 
+ +
dxr3-devel mailing list
+ + +Last modified: Thu Apr 13 21:50:11 EEST 2006 + + + --- em8300-0.18.0.orig/debian/dxr3.sourceforge.net/faq.html +++ em8300-0.18.0/debian/dxr3.sourceforge.net/faq.html @@ -0,0 +1,374 @@ + + +Linux DXR3 and Hollywood+ Driver + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Dxr3 Logo

DXR3 & Hollywood Plus Logo

+ +Linux DXR3 and Hollywood+ Driver Project FAQ + +
   
  + + + + News
+ About
+ FAQ
+ Howto
+ Download
+ Links
+ Developers
+ Project Page
+ + + + 		  + + + +Table of Contents + + +
+ +
+Answers +
+ +
Question: +
I'm unable to change the audio volume in my mixer, what gives? +
Answer: +
The em8300 does not contain an audio mixer, so this feature cannot be implemented. You could write a software mixer but we have decided that something like that does not belong in a kernel module. +

+ +Alternatively you can output your audio through a native OSS or Alsa +device, and then just use your regular mixer controls. Think of the +the em8300 audio out as what it really is, a line out. Which is perfect +for hooking up to stereo equipment. + +

+ +
Question: +
I get unresolved symbols when running "make install" or loading modules, what's wrong? +
Answer: +
+First thing's first. The kernel source you are compiling against must match +your running kernel. i.e. if you're running say RedHat-2.4.18-14 you +must point the Makefile for the kernel modules at the correct source tree +for your "running kernel". You can verify that your running kernel and +sources match by typing "uname -a" and looking at the Makefile in the +root directory of the kernel source.

+ +e.g. output from uname

+ +root@barney# uname -a
+Linux barney 2.4.18-14custom #1 Wed Sep 4 13:35:50 EDT 2002 i686 i686 i386 GNU/Linux + +

+Excerpt from Makefile in /usr/src/linux-2.4 +

+ +VERSION = 2
+PATCHLEVEL = 4
+SUBLEVEL = 18
+EXTRAVERSION = -14custom
+ +

+See these match so it should be safe to compile kernel modules against +this tree. You really need to compile your own kernel tree, and boot it. +This establishes that a) the kernel source you have runs, b) creates +all the dependency files and links that em8300 uses to compile itself +correctly. Think of it as a pre-requisite to getting em8300 running. +

+Before compiling a "vendor" kernel it is recommended you type: +make mrproper this will clean up any lingering files +from previous compilations. If you have your own .config file you +will need to back it up before doing this otherwise it is gone +forever and you have to set it up again. +

+Vendor kernels are typically set up correctly for em8300, i.e. they +have I2C, I2C-bit-banging and OSS Sound support enabled. You can +usually short cut the whole process and get the default configuration by typing +make oldconfig. If you download a "Marcelo/Linus" kernel you will +need to configure both these options in using something like make +menuconfig + +

+For more in-depth discussion on how to compile a linux kernel check +out the +Kernel HOW-TO. +

+ +
Question: +
My kernel source is not in /usr/src/linux, how can I get the darned thing to compile? +
Answer: +
Edit the KERNEL_LOCATION line in the Makefile. This must be the source directory for the kernel +you are currently running, not the version that shipped with your distribution (which you should +keep in /usr/src/linux for other reasons). Also, you must have run make config and make dep in the +kernel tree before compiling the driver kernel modules. +

+ +
Question: +
Microcode upload to /dev/em8300-1 failed. What does that mean? +
Answer: +
This error message is normal. /dev/em8300-1, /dev/em8300-2, and /dev/em8300-3 are used for multi card support only. If you don't have more than one dxr3 don't worry about it. +

+ +
Question: +
Does this actually work for anyone? Where can I find their results? +
Answer: +
Yes. Unfortunately Patryk Laurent's dxr3 users database domain appears to be down. We'll update this link if things change. +

+ +
Question: +
+Can I use my DXR3/H+ to watch movies other than DVDs or MPEG1/2? Is this accelerated? +
Answer: +
+Yes, you will be able to play DivX and other supported video formats on your card as well. Though +this has to happen through an MPEG1 filter which means it needs lots of CPU power, you should have +at least a 400MHz CPU or preferably faster.

+The em8300 cannot decode anything other than MPEG1/2 in hardware so this will never happen in an +accelerated form. If that is what you want, look for another card. What it can and will do is to +handle postprocessing for you, so the output will look alot nicer than it would do if you play it +on your monitor without any postprocessing enabled. And, this is a real cheap way of getting a +tv-out for watching movies.
+For further information regardning this please refer to the DXR3 howto +or MPlayer manual. +

+ +
Question: +
+Will the driver ever become part of the official Linux kernel or will +I have to download and compile this thing separately for the rest of +my life? + +
Answer: +
+Development of a new driver in the official Linux kernel tree is +difficult because Linus doesn't like to apply lots of little patches; +he would rather apply fewer larger patches to revise an already working +driver. So, once we get this thing stable and working with the known +revisions of the cards, we may seek to include the kernel portion of +this driver in the official kernel source tree. + +

+ +
Question: +
When I cat a .mpg file to /dev/em8300_mv-* a bunch of garbage appears on the screen. Whats wrong? +
Answer: +
+Only mpeg video can be sent to /dev/em8300_mv-*. If an mpeg system file, +which is both mpeg video and audio, is sent to the device, garbage like +that will show up on the screen. First separate the mpeg system into +separate video and audio files, then send those to the appropriate device. +See the Howto. + +

+ +
Question: +
Only two microcode files are extracted from my driver file. What gives? +
Answer: +
+Some revisions of the driver (seems like those shipped with boards with +a bt865) only came with two microcode files. Just use one of these two +and the card should work correctly. You can also download the latest +version of the driver from either Creative Labs or Sigma Designs and +use the microcode shipped with those drivers instead. +

+Update: (12/06/2002) This question is somewhat obsolete +now as the latest driver, 0.13 at this time, comes with a microcode file. + +

+ +
Question: +
How can I uncompress rmquasar.vx_ or enc2dev.vx_? +
Answer: +
A utility written by Paul Laufer called msexpand.pl is included in the em8300/scripts directory +that will uncompress microsoft compressed files. Just run it without any arguments to get the usage +information. See the Howto. +

+Update: (12/06/2002) See the previous question as to why you don't need to do this anymore. + +

+ +
Question: +
I left a message in the Sourceforge project site forums and nobody has answered! +
Answer: +
In general, use the mailing list. Unfortunately, at this point the Sourceforge project forums +are not visited very often by developers. See the Howto +

+ +
Question: +
The video is all green! How can I fix it? +
Answer: +
Check to make sure you are passing the correct module options to the em8300.o and adv717x.o +kernel modules. See the Howto for further information about these options. In +the future detection of these settings should be automated. +

+ +
Question: +
The tv output looks like a scrambled cable-channel, what's wrong? +
Answer: +
+There are a couple of possibilities. Firstly check that you've configured your Dxr3 for the correct TV standard. PAL in Europe and parts of South America, NTSC in the US and Japan and SECAM in France or Russia. SECAM is not supported. +

+Secondly, if you are using an SVHS/S-Video to Composite converter cable, +make sure the SVHS connector has 7 pins and not 4. Most video cards +are delivered with 4-pin SVHS->Composite converters because they use +only 2 outputs for video (Luminance and Chrominance). But the DXR3/H+ +is a very high quality card that uses 3 outputs (Luminance, and 2 +Chrominance outputs) which also requires that you use a converter cable +that recognizes this. If you can't find one, the solution is to buy an +SVHS cable and a scart contact which accepts an SVHS input. + +

+If your TV has SVHS inputs you can also modify a regular SVHS cable by +removing the plastic leg on one end of the cable. Only do this if you +know what you are doing as it is not reversable and basically removes +the key allowing you to try plugging it in upside down. However it +works quite well and lets you use a high quality cable rather than the +cheap one the DXR3 comes with. + +

+ +
Question: +
The video is only on one half of my screen! What's wrong? +
Answer: +
Check to make sure you are passing the correct module options to the em8300.o and adv717x.o +kernel modules. See the Howto for further information about these options.In +the future detection of these settings should be automated. +

+ +
Question: +
I can only play low bit rate mpeg videos, higher bit rate streams lock up the card. What could +be the problem? +
Answer: +
+Try using microcode from a newer driver version or one of the +other microcode files that were extracted from your rmquasar.vxd or +enc2dev.vxd. Some microcode files seem only to work with some versions +of the card.

+ +Update: (12/05/2002) Try downloading the latest version +of the driver. It includes a universal microcode as part of the source. + +

+ +
Question: +
When I load the microcode, my monitor starts making funny noises! +
Answer: +
Remove the passthrough cable and connect your monitor to the video card directly. VGA overlay +and passthrough are not working on some revisions of the card. More reverse engineering is much +needed. If you own one of these cards you currently have to watch your DVDs using the TV out +connector. +

+ +
Question: +
When I load the microcode, my monitor screen goes blank! +
Answer: +
Some cards disable the passthrough when the microcode is uploaded. +Use the 'activate_loopback' module parameter to fix this. However, you may +not be able to use the tv out connector with activate_loopback. If you want to +use tvout you'll need to disconnect the passthrough cable for now. +See the Howto. +

+ + +
Question +
What is libdxr3? +
Answer +
libdxr3 was a library that served as an interface between client programs +like Xine and OMS and the kernel modules. The original idea was to provide a +reusable library and avoid code duplication in client programs, but the +library was never quite finished and its use never really took off, so it was +removed from the em8300 distribution as of version 0.15.1 after being +unmaintained and unused for a few years. In case someone's interested in +finishing and maintaining it, the code can still be resurrected from CVS. +

+ +
Question: +
Can I help with the project? +
Answer: +
Of course! We need people to help write better documentation, reverse engineer the windows +driver, implement new features in the Linux driver, and better integrate the driver into the DVD +player software. +

+ +
+ + + 		  
+ + SourceForge Logo +   
 
+ +
dxr3-devel mailing list
+ + +Last modified: Sun Nov 6 11:01:15 EET 2005 + + + --- em8300-0.18.0.orig/debian/po/de.po +++ em8300-0.18.0/debian/po/de.po @@ -0,0 +1,344 @@ +# translation of po-debconf template to German +# Copyright (C) 2007, Matthias Julius +# This file is distributed under the same license as the em8300 package. +# +# Matthias Julius , 2007. +msgid "" +msgstr "" +"Project-Id-Version: em8300 0.16.0-1\n" +"Report-Msgid-Bugs-To: nboullis@debian.org\n" +"POT-Creation-Date: 2007-01-06 19:00+0100\n" +"PO-Revision-Date: 2007-01-04 23:57-0500\n" +"Last-Translator: Matthias Julius \n" +"Language-Team: German \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "Download microcode image from the Web?" +msgstr "Microcode-Image aus dem Internet laden?" + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"The upstream developers have tried several microcode images and selected the " +"one that works best on various cards. Therefore, this microcode image is " +"probably better than the ones you can get from your Windows drivers. The " +"upstream developers have made it available for download on their website." +msgstr "" +"Die Entwickler dieses Programms haben verschiedene Microcode-Images getestet " +"und dasjenige ausgewählt, das am Besten mit verschiedenen Karten " +"funktioniert. Deshalb ist dieses Microcode-Image wahrscheinlich besser als " +"diejenigen, die Sie von Ihren Windows-Treibern bekommen können. Die " +"Entwickler haben es zum Herunterladen auf deren Website zur Verfügung " +"gestellt." + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"However, because of some legal issues, this microcode image cannot be " +"distributed by Debian. If you do not want to download it, you can still " +"extract the appropriate microcode image(s) from the Windows .vxd file, using " +"em8300mc_ex." +msgstr "" +"Aufgrund von rechtlichen Problemen kann dieses Microcode-Image jedoch von " +"Debian nicht verbreitet werden. Falls Sie es nicht herunterladen möchten, " +"können die entsprechenden Microcode-Images immer noch aus der Windows-.vxd-" +"Datei unter Verwendung von em8300mc_ex extrahieren." + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"Warning: If /lib/firmware/em8300.bin already exists on your system, it will " +"be overwritten by the downloaded file." +msgstr "" +"Warnung: Falls /lib/firmware/em8300.bin schon auf Ihrem System existiert, " +"wird es von der heruntergeladenen Datei überschrieben." + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "Failed to download microcode image" +msgstr "Herunterladen des Microcode-Images fehlgeschlagen" + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "" +"The microcode image was not downloaded from the upstream authors' web site. " +"You probably won't be able to use your MPEG decoder card until you download " +"a microcode image." +msgstr "" +"Das Microcode-Image wurde nicht von der Website der Programmautoren " +"heruntergeladen. Sie werden Ihre MPEG-Dekoder-Karte möglicherweise nicht " +"verwenden können, bis Sie ein Microcode-Image heruntergeladen haben." + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "" +"To retry, run \"dpkg-reconfigure em8300\" as root, or download it from\n" +" http://dxr3.sourceforge.net/download/em8300.uc\n" +"and save it as \"/lib/firmware/em8300.bin\"." +msgstr "" +"Um den Versuch zu wiederholen führen Sie »dpkg-reconfigure em8300« als root " +"aus oder laden Sie es von\n" +" http://dxr3.sourceforge.net/download/em8300.uc\n" +"herunter und speichern es als »/lib/firmware/em8300.bin«." + +#. Type: select +#. Choices +#: ../em8300.templates:3001 +msgid "None${files}" +msgstr "Keine ${files}" + +#. Type: select +#. Description +#: ../em8300.templates:3002 +msgid "Primary microcode:" +msgstr "Primärer Microcode:" + +#. Type: select +#. Description +#: ../em8300.templates:3002 +msgid "" +"This will copy a microcode image previously installed in /usr/share/em8300/ " +"to /lib/firmware/em8300.bin and use it." +msgstr "" +"Dies wird ein Microcode-Image, welches zuvor in /usr/share/em8300/ " +"installiert wurde, nach /lib/firmware/em8300.bin kopieren und verwenden." + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "Delete old firmware directory?" +msgstr "Das alte Firmware-Verzeichnis löschen?" + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "" +"Multiple microcode images seem to be installed in /usr/share/em8000/. " +"Support for multiple microcode images has been removed from this version, so " +"if you wish to continue using multiple microcode images, you will have to " +"keep these files and handle the situation manually. You will be responsible " +"for removing these files once you have finished with them." +msgstr "" +"Mehrere Microcode-Images scheinen in /usr/share/em8000/ installiert zu sein. " +"Die Unterstützung für mehrere Microcode-Images wurde aus dieser Version " +"entfernt. Falls Sie weiterhin mehrere Microcode-Images verwenden möchten, " +"müssen Sie diese Dateien behalten und die Situation manuell behandeln. Sie " +"sind dafür verantwortlich, diese Dateien zu entfernen sobald Sie mit ihnen " +"fertig sind." + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "" +"Most people need only a single microcode image. If you want to use only one " +"microcode image, or if you do not know why you have multiple microcode " +"images installed, then you can accept and the extra files will be deleted." +msgstr "" +"Die meisten Anwender benötigen nur ein einziges Microcode-Image. Falls Sie " +"nur eins verwenden möchten oder falls Sie nicht wissen, warum Sie mehrere " +"Microcode-Images installiert haben, können Sie hier akzeptieren, und die " +"zusätzlichen Dateien werden gelöscht." + +#. Type: select +#. Description +#: ../em8300.templates:5001 +msgid "Chip used on MPEG decoder card:" +msgstr "Der auf der MPEG-Dekoder-Karte verwendete Baustein:" + +#. Type: select +#. Description +#: ../em8300.templates:5001 +msgid "" +"Creative DXR3 cards have a bt865 on board, while Hollywood Plus cards use an " +"adv717x." +msgstr "" +"Creative-DXR3-Karten haben einen bt865 an Bord während Hollywood-Plus-Karten " +"einen adv717x verwenden." + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "Options for bt865 module:" +msgstr "Einstellungen für das bt865-Modul:" + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "" +"Options can be passed to the bt865 kernel module when it is loaded to " +"control how it works." +msgstr "" +"Die Optionen können an das bt865-Kernel-Modul übergeben werden, wenn es " +"geladen wird, um dessen Funktion zu steuern." + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "" +"Options include:\n" +" output_mode=comp+svideo|rgb\n" +"Multiple options should be separated by spaces." +msgstr "" +"Die Optionen beinhalten:\n" +" output_mode=comp+svideo|rgb\n" +"Mehrere Optionen sollten durch Leerzeichen getrennt werden." + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "Options for adv717x module:" +msgstr "Einstellungen für das adv717x-Modul:" + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "" +"Options can be passed to the adv717x kernel module when it is loaded to " +"control how it works." +msgstr "" +"Die Optionen können an das adv717x-Kernel-Modul übergeben werden, wenn es " +"geladen wird, um dessen Funktion zu steuern." + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "" +"Options include:\n" +" output_mode=comp+svideo|svideo|comp|comp+psvideo|psvideo|composvideo|yuv|" +"rgb|rgbs\n" +" pixelport_16bit=0|1\n" +" pixelport_other_pal=0|1\n" +" pixeldata_adjust_ntsc=0|1|2|3\n" +" pixeldata_adjust_pal=0|1|2|3\n" +"Multiple options should be separated by spaces." +msgstr "" +"Die Optionen beinhalten:\n" +" output_mode=comp+svideo|svideo|comp|comp+psvideo|psvideo|composvideo|yuv|" +"rgb|rgbs\n" +" pixelport_16bit=0|1\n" +" pixelport_other_pal=0|1\n" +" pixeldata_adjust_ntsc=0|1|2|3\n" +" pixeldata_adjust_pal=0|1|2|3\n" +"Mehrere Optionen sollten durch Leerzeichen getrennt werden." + +#. Type: string +#. Description +#. Type: string +#. Description +#: ../em8300.templates:7001 ../em8300.templates:8001 +msgid "" +"Some sets of options have been reported to remove color problems. Check the " +"package documentation for details." +msgstr "" +"Für manche Optionen wurde berichtet, dass sie Farbprobleme beseitigen. Lesen " +"Sie die Paketdokumentation für Einzelheiten." + +#. Type: string +#. Description +#. Type: string +#. Description +#: ../em8300.templates:7001 ../em8300.templates:8001 +msgid "" +"Unfortunately, there is currently no way to find the right parameters for " +"your card, so you'll have to find them yourself by trial and error." +msgstr "" +"Unglücklicherweise gibt es gegenwärtig keine Möglichkeit, die richtigen " +"Parameter für Ihre Karte zu bestimmen. Sie müssen sie selbst durch " +"ausprobieren herausfinden." + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "Options for em8300 module:" +msgstr "Einstellungen für das em8300-Modul:" + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "" +"Options can be passed to the em8300 kernel module when it is loaded to " +"control how it works." +msgstr "" +"Die Optionen können an das em8300-Kernel-Modul übergeben werden, wenn es " +"geladen wird, um dessen Funktion zu steuern." + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "" +"Options include:\n" +" activate_loopback=0|1\n" +" audio_driver=alsa|oss|osslike|none\n" +" alsa_index=-1|0|1|2|3|...\n" +" dsp_num=-1|0|1|2|3|...\n" +" bt865_ucode_timeout=0|1\n" +" dicom_control=0|1\n" +" dicom_fix=0|1\n" +" dicom_other_pal=0|1\n" +" use_bt865=0|1\n" +"Multiple options should be separated by spaces." +msgstr "" +"Die Optionen beinhalten:\n" +" activate_loopback=0|1\n" +" audio_driver=alsa|oss|osslike|none\n" +" alsa_index=-1|0|1|2|3|...\n" +" dsp_num=-1|0|1|2|3|...\n" +" bt865_ucode_timeout=0|1\n" +" dicom_control=0|1\n" +" dicom_fix=0|1\n" +" dicom_other_pal=0|1\n" +" use_bt865=0|1\n" +"Mehrere Optionen sollten durch Leerzeichen getrennt werden." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "No creation of device files" +msgstr "Keine Erzeugung von Gerätedateien" + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"Special device files must exist to enable access to your MPEG decoder card." +msgstr "" +"Spezielle Gerätedateien müssen existieren, um den Zugang zu Ihrer MPEG-" +"Decoder-Karte zu ermöglichen." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"You seem to be using a static /dev. Special device files can't be created " +"automatically because no major number has been allocated to the em8300 " +"officially yet." +msgstr "" +"Sie scheinen ein statisches /dev zu verwenden. Die speziellen Gerätedateien " +"können nicht automatisch angelegt werden, da an das em8300 noch keine Major-" +"Nummer offiziell vergeben wurde." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"Hence, you'll have to choose a major number to use (121 is used by default, " +"but it's officially allocated to \"LOCAL/EXPERIMENTAL USE\") and create the " +"corresponding device files yourself. Please read /usr/share/doc/em8300/" +"README.Debian for more info." +msgstr "" +"Deshalb müssen Sie eine Major-Nummer wählen (121 wird als Voreinstellung " +"verwendet, aber diese ist offiziell für »lokale/experimentelle Verwendung« " +"vorgesehen) und die entsprechende Gerätedatei selbst erzeugen. Bitte lesen " +"Sie /usr/share/doc/em8300/README.Debian für mehr Informationen." --- em8300-0.18.0.orig/debian/po/nb.po +++ em8300-0.18.0/debian/po/nb.po @@ -0,0 +1,335 @@ +# translation of em8300_nb.po to Norwegian BokmÃ¥l +# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER +# This file is distributed under the same license as the PACKAGE package. +# +# Bjørn Steensrud , 2007. +msgid "" +msgstr "" +"Project-Id-Version: em8300_nb\n" +"Report-Msgid-Bugs-To: nboullis@debian.org\n" +"POT-Creation-Date: 2007-01-06 19:00+0100\n" +"PO-Revision-Date: 2007-01-03 09:56+0100\n" +"Last-Translator: Bjørn Steensrud \n" +"Language-Team: Norwegian BokmÃ¥l \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.2\n" + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "Download microcode image from the Web?" +msgstr "Laste ned mikrokode-bildet fra nettet?" + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"The upstream developers have tried several microcode images and selected the " +"one that works best on various cards. Therefore, this microcode image is " +"probably better than the ones you can get from your Windows drivers. The " +"upstream developers have made it available for download on their website." +msgstr "" +"em8300-utviklerne har forsøkt flere mikrokode-bilder og valgt det som virker " +"best pÃ¥ diverse kort. Derfor er dette mikrokode-bildet sannsynligvis bedre " +"enn de du kan fÃ¥ fra dine Windows-drivere. Utviklerne har gjort det " +"tilgjengelig for nedlasting pÃ¥ nettsiden sin." + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"However, because of some legal issues, this microcode image cannot be " +"distributed by Debian. If you do not want to download it, you can still " +"extract the appropriate microcode image(s) from the Windows .vxd file, using " +"em8300mc_ex." +msgstr "" +"Imidlertid er det juridiske grunner til at Debian ikke kan distribuere dette " +"bildet. Hvis du ikke vil laste det ned kan du likevel trekke ut passende " +"mikrokode-bilde(r) fra Windows' .vxd-fil med em8300mc_ex." + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"Warning: If /lib/firmware/em8300.bin already exists on your system, it will " +"be overwritten by the downloaded file." +msgstr "" +"Advarsel: Hvis /lib/firmware/em8300.bin finnes fra før pÃ¥ systemet ditt, sÃ¥ " +"blir den overskrevet av den fila som lastes ned." + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "Failed to download microcode image" +msgstr "Klarte ikke laste ned mikrokode-bilde" + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "" +"The microcode image was not downloaded from the upstream authors' web site. " +"You probably won't be able to use your MPEG decoder card until you download " +"a microcode image." +msgstr "" +"Mikrokode-bildet ble ikke lastet ned fra forfatternes nettsted. Du vil " +"antakelig ikke kunne bruke MPEG dekoder-kortet før du laster ned et " +"mikrokode-bilde." + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "" +"To retry, run \"dpkg-reconfigure em8300\" as root, or download it from\n" +" http://dxr3.sourceforge.net/download/em8300.uc\n" +"and save it as \"/lib/firmware/em8300.bin\"." +msgstr "" +"Forsøk igjen ved Ã¥ kjøre «dpkg-reconfigure em8300» som root, eller last\n" +"ned fra http://dxr3.sourceforge.net/download/em8300.uc\n" +"og lagre som «/lib/firmware/em8300.bin»." + +#. Type: select +#. Choices +#: ../em8300.templates:3001 +msgid "None${files}" +msgstr "Ingen${files}" + +#. Type: select +#. Description +#: ../em8300.templates:3002 +msgid "Primary microcode:" +msgstr "Primær mikrokode:" + +#. Type: select +#. Description +#: ../em8300.templates:3002 +msgid "" +"This will copy a microcode image previously installed in /usr/share/em8300/ " +"to /lib/firmware/em8300.bin and use it." +msgstr "" +"Dette kopierer et mikrokode-bilde som er installert i /usr/share/em8300/ " +"til /lib/firmware/em8300.bin og bruker dette." + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "Delete old firmware directory?" +msgstr "Slette den gamle fastvare-mappa?" + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "" +"Multiple microcode images seem to be installed in /usr/share/em8000/. " +"Support for multiple microcode images has been removed from this version, so " +"if you wish to continue using multiple microcode images, you will have to " +"keep these files and handle the situation manually. You will be responsible " +"for removing these files once you have finished with them." +msgstr "" +"Det ser ut til at det er installert flere mikrokode-bilder i /usr/share/" +"em8000/. I denne versjonen er det ikke støtte for flere enn ett bilde, sÃ¥ " +"hvis du vil fortsette Ã¥ bruke flere mikrokode-bilder, mÃ¥ du beholde disse " +"filene og hÃ¥ndtere situasjonen manuelt. Du har ansvaret for Ã¥ fjerne disse " +"filene nÃ¥r du er ferdig med dem." + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "" +"Most people need only a single microcode image. If you want to use only one " +"microcode image, or if you do not know why you have multiple microcode " +"images installed, then you can accept and the extra files will be deleted." +msgstr "" +"De fleste trenger bare ett enkelt mikrokode-bilde. Hvis du vil bruke bare " +"ett bilde, eller hvis du ikke vet hvorfor du har flere mikrokode-bilder " +"installert, sÃ¥ kan du godta dette slik at de overskytende filene blir " +"slettet." + +#. Type: select +#. Description +#: ../em8300.templates:5001 +msgid "Chip used on MPEG decoder card:" +msgstr "Chip brukt pÃ¥ MPEG-dekoderkortet:" + +#. Type: select +#. Description +#: ../em8300.templates:5001 +msgid "" +"Creative DXR3 cards have a bt865 on board, while Hollywood Plus cards use an " +"adv717x." +msgstr "" +"Creative DXR3-kort har en bt865, mens Hollywood Plus-kort bruker en adv717x." + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "Options for bt865 module:" +msgstr "Oppsett for bt865-modulen:" + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "" +"Options can be passed to the bt865 kernel module when it is loaded to " +"control how it works." +msgstr "" +"Oppsettsdata kan sendes til kjernemodulen for bt865 nÃ¥r den lastes inn, for " +"Ã¥ styre virkemÃ¥ten." + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "" +"Options include:\n" +" output_mode=comp+svideo|rgb\n" +"Multiple options should be separated by spaces." +msgstr "" +"Valgmuligheter er bl.a.:\n" +" output_mode=comp+svideo|rgb\n" +"Flere valg oppgis med mellomrom." + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "Options for adv717x module:" +msgstr "Oppsett for adv717x-modulen:" + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "" +"Options can be passed to the adv717x kernel module when it is loaded to " +"control how it works." +msgstr "" +"Oppsettsdata kan sendes til kjernemodulen for adv717x nÃ¥r den lastes inn, " +"for Ã¥ styre virkemÃ¥ten." + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "" +"Options include:\n" +" output_mode=comp+svideo|svideo|comp|comp+psvideo|psvideo|composvideo|yuv|" +"rgb|rgbs\n" +" pixelport_16bit=0|1\n" +" pixelport_other_pal=0|1\n" +" pixeldata_adjust_ntsc=0|1|2|3\n" +" pixeldata_adjust_pal=0|1|2|3\n" +"Multiple options should be separated by spaces." +msgstr "" +"Valgmuligheter:\n" +" output_mode=comp+svideo|svideo|comp|comp+psvideo|psvideo|composvideo|yuv|" +"rgb|rgbs\n" +" pixelport_16bit=0|1\n" +" pixelport_other_pal=0|1\n" +" pixeldata_adjust_ntsc=0|1|2|3\n" +" pixeldata_adjust_pal=0|1|2|3\n" +"Flere valg mÃ¥ oppgis med mellomrom." + +#. Type: string +#. Description +#. Type: string +#. Description +#: ../em8300.templates:7001 ../em8300.templates:8001 +msgid "" +"Some sets of options have been reported to remove color problems. Check the " +"package documentation for details." +msgstr "" +"Det er meldt at noen oppsettskombinasjoner fjerner fargeproblemer. Se " +"etterdetaljer i dokumentasjonen for pakka." + +#. Type: string +#. Description +#. Type: string +#. Description +#: ../em8300.templates:7001 ../em8300.templates:8001 +msgid "" +"Unfortunately, there is currently no way to find the right parameters for " +"your card, so you'll have to find them yourself by trial and error." +msgstr "" +"Dessverre er det for tiden ingen mÃ¥te Ã¥ finne de riktige parameterne for " +"kortet ditt, sÃ¥ du mÃ¥ finne dem selv ved Ã¥ prøve og feile." + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "Options for em8300 module:" +msgstr "Oppsett for em8300-modulen:" + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "" +"Options can be passed to the em8300 kernel module when it is loaded to " +"control how it works." +msgstr "" +"Oppsettsdata kan sendes til kjernemodulen for em8300 nÃ¥r den lastes inn, for " +"Ã¥ styre virkemÃ¥ten." + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "" +"Options include:\n" +" activate_loopback=0|1\n" +" audio_driver=alsa|oss|osslike|none\n" +" alsa_index=-1|0|1|2|3|...\n" +" dsp_num=-1|0|1|2|3|...\n" +" bt865_ucode_timeout=0|1\n" +" dicom_control=0|1\n" +" dicom_fix=0|1\n" +" dicom_other_pal=0|1\n" +" use_bt865=0|1\n" +"Multiple options should be separated by spaces." +msgstr "" +"Valgmuligheter:\n" +" activate_loopback=0|1\n" +" audio_driver=alsa|oss|osslike|none\n" +" alsa_index=-1|0|1|2|3|...\n" +" dsp_num=-1|0|1|2|3|...\n" +" bt865_ucode_timeout=0|1\n" +" dicom_control=0|1\n" +" dicom_fix=0|1\n" +" dicom_other_pal=0|1\n" +" use_bt865=0|1\n" +"Flere valg mÃ¥ atskilles med mellomrom." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "No creation of device files" +msgstr "Enhetsfiler opprettes ikke" + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"Special device files must exist to enable access to your MPEG decoder card." +msgstr "For Ã¥ kunne bruke MPEG-dekoderkortet mÃ¥ spesielle enhetsfiler finnes." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"You seem to be using a static /dev. Special device files can't be created " +"automatically because no major number has been allocated to the em8300 " +"officially yet." +msgstr "" +"Det ser ut til at du bruker en statisk /dev-mappe. Spesielle enhetsfiler kan " +"ikke opprettes automatisk fordi det ikke er offisielt tilordnet et " +"hovednummer til em8300 ennÃ¥." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"Hence, you'll have to choose a major number to use (121 is used by default, " +"but it's officially allocated to \"LOCAL/EXPERIMENTAL USE\") and create the " +"corresponding device files yourself. Please read /usr/share/doc/em8300/" +"README.Debian for more info." +msgstr "" +"Derfor mÃ¥ du velge et hovednummer Ã¥ bruke (standard er 121, men det er " +"offisielt tilordnet «LOKALT/EKSPERIMENTELT BRUK») og opprette de tilsvarende " +"enhetsfilene selv. Les /usr/share/doc/em8300/README.Debian for Ã¥ finne ut " +"mer." --- em8300-0.18.0.orig/debian/po/es.po +++ em8300-0.18.0/debian/po/es.po @@ -0,0 +1,316 @@ +# Translation of em8300_0.16.0-2 to Spanish +# Copyright (C) 2007 THE PACKAGE'S COPYRIGHT HOLDER +# This file is distributed under the same license as the em8300 package. +# +# Traductores, si no conocen el formato PO, merece la pena leer la +# documentación de gettext, especialmente las secciones dedicadas a este +# formato, por ejemplo ejecutando: +# info -n '(gettext)PO Files' +# info -n '(gettext)Header Entry' +# +# Equipo de traducción al español, por favor lean antes de traducir +# los siguientes documentos: +# +# - El proyecto de traducción de Debian al español +# http://www.debian.org/intl/spanish/ +# especialmente las notas y normas de traducción en +# http://www.debian.org/intl/spanish/notas +# +# - La guía de traducción de po's de debconf: +# /usr/share/doc/po-debconf/README-trans +# o http://www.debian.org/intl/l10n/po-debconf/README-trans +# +# Si tiene dudas o consultas sobre esta traducción consulte con el último +# traductor (campo Last-Translator) y ponga en copia a la lista de +# traducción de Debian al español () +# +# Enrique Matias Sanchez (aka Quique) , 2007. +msgid "" +msgstr "" +"Project-Id-Version: em8300_0.16.0-2_es\n" +"Report-Msgid-Bugs-To: nboullis@debian.org\n" +"POT-Creation-Date: 2007-01-06 19:00+0100\n" +"PO-Revision-Date: 2007-03-19 18:59+0100\n" +"Last-Translator: Enrique Matias Sanchez (aka Quique) \n" +"Language-Team: Spanish \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "Download microcode image from the Web?" +msgstr "¿Hace falta descargar la imagen de microcódigo de la web?" + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"The upstream developers have tried several microcode images and selected the " +"one that works best on various cards. Therefore, this microcode image is " +"probably better than the ones you can get from your Windows drivers. The " +"upstream developers have made it available for download on their website." +msgstr "Los desarrolladores originales han probado varias imágenes de microcódigo y seleccionado la que mejor funciona con diferentes tarjetas. Por lo tanto, esta imagen de microcódigo probablemente sea mejor que la que pueda obtener de sus controladores de Windows. Esta imagen de microcódigo está disponible en el sitio web de los desarrolladores originales." + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"However, because of some legal issues, this microcode image cannot be " +"distributed by Debian. If you do not want to download it, you can still " +"extract the appropriate microcode image(s) from the Windows .vxd file, using " +"em8300mc_ex." +msgstr "Sin embargo, por motivos legales, Debian no puede distribuir esta imagen de microcódigo. Si no desea descargarla, siempre puede extraer la imagen (o imágenes) de microcódigo adecuada del fichero .vxd de Windows, utilizando la orden «em8300mc_ex»." + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"Warning: If /lib/firmware/em8300.bin already exists on your system, it will " +"be overwritten by the downloaded file." +msgstr "Advertencia: Si en su sistema hay ya un fichero «/lib/firmware/em8300.bin», se sobreescribirá por el fichero descargado." + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "Failed to download microcode image" +msgstr "Fallo al descargar la imagen de microcódigo" + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "" +"The microcode image was not downloaded from the upstream authors' web site. " +"You probably won't be able to use your MPEG decoder card until you download " +"a microcode image." +msgstr "La imagen de microcódigo no se ha descargado del sitio web de los autores originales. Probablemente no pueda utilizar su tarjeta decodificadora de MPEG hasta que descargue una imagen de microcódigo." + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "" +"To retry, run \"dpkg-reconfigure em8300\" as root, or download it from\n" +" http://dxr3.sourceforge.net/download/em8300.uc\n" +"and save it as \"/lib/firmware/em8300.bin\"." +msgstr "" +"Para volver a intentarlo, ejecute «dpkg-reconfigure em8300» como root, o descárguela de\n" +" http://dxr3.sourceforge.net/download/em8300.uc\n" +"y guárdela como «/lib/firmware/em8300.bin»." + +#. Type: select +#. Choices +#: ../em8300.templates:3001 +msgid "None${files}" +msgstr "Ningún ${files}" + +#. Type: select +#. Description +#: ../em8300.templates:3002 +msgid "Primary microcode:" +msgstr "Microcódigo principal:" + +#. Type: select +#. Description +#: ../em8300.templates:3002 +msgid "" +"This will copy a microcode image previously installed in /usr/share/em8300/ " +"to /lib/firmware/em8300.bin and use it." +msgstr "Se copiará la imagen de micrócodigo previamente instalada en «/usr/share/em8300/» a «/lib/firmware/em8300.bin», y se utilizará." + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "Delete old firmware directory?" +msgstr "¿Borrar el viejo directorio del firmware?" + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "" +"Multiple microcode images seem to be installed in /usr/share/em8000/. " +"Support for multiple microcode images has been removed from this version, so " +"if you wish to continue using multiple microcode images, you will have to " +"keep these files and handle the situation manually. You will be responsible " +"for removing these files once you have finished with them." +msgstr "Parece haber instaladas varias imágenes de microcódigo en «/usr/share/em8000/». En esta versión se ha eliminado el soporte a múltiples imágenes de microcódigo, por lo que si desea seguir utilizando varias imágenes de microcódigo, tendrá que mantener estos ficheros y gestionar la situación a mano. Una vez haya acabado con estos ficheros, deberá eliminarlos usted mismo." + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "" +"Most people need only a single microcode image. If you want to use only one " +"microcode image, or if you do not know why you have multiple microcode " +"images installed, then you can accept and the extra files will be deleted." +msgstr "La mayoría de la gente sólo necesita una imagen de microcódigo. Si desea usar una única imagen, o si no sabe porqué tiene instaladas varias imágenes de microcódigo, puede aceptar esta opción y se borrarán los ficheros extra." + +#. Type: select +#. Description +#: ../em8300.templates:5001 +msgid "Chip used on MPEG decoder card:" +msgstr "Chip usado en la tarjeta decodificadora de MPEG:" + +#. Type: select +#. Description +#: ../em8300.templates:5001 +msgid "" +"Creative DXR3 cards have a bt865 on board, while Hollywood Plus cards use an " +"adv717x." +msgstr "Las tarjetas Creative DXR3 tienen un chip bt865 en placa, mientras que las tarjetas Hollywood Plus usan un chip adv717x." + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "Options for bt865 module:" +msgstr "Opciones para el módulo bt865:" + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "" +"Options can be passed to the bt865 kernel module when it is loaded to " +"control how it works." +msgstr "Al cargar el módulo bt865 del núcleo, se le pueden pasar opciones para controlar su modo de funcionamiento." + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "" +"Options include:\n" +" output_mode=comp+svideo|rgb\n" +"Multiple options should be separated by spaces." +msgstr "" +"Estas opciones comprenden:\n" +" output_mode=comp+svideo|rgb\n" +"Si se pasan varias opciones, se deben separar entre sí mediante espacios." + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "Options for adv717x module:" +msgstr "Opciones para el módulo adv717x:" + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "" +"Options can be passed to the adv717x kernel module when it is loaded to " +"control how it works." +msgstr "Al cargar el módulo adv717x del núcleo, se le pueden pasar opciones para controlar su modo de funcionamiento." + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "" +"Options include:\n" +" output_mode=comp+svideo|svideo|comp|comp+psvideo|psvideo|composvideo|yuv|" +"rgb|rgbs\n" +" pixelport_16bit=0|1\n" +" pixelport_other_pal=0|1\n" +" pixeldata_adjust_ntsc=0|1|2|3\n" +" pixeldata_adjust_pal=0|1|2|3\n" +"Multiple options should be separated by spaces." +msgstr "" +"Estas opciones comprenden:\n" +" output_mode=comp+svideo|svideo|comp|comp+psvideo|psvideo|composvideo|yuv|" +"rgb|rgbs\n" +" pixelport_16bit=0|1\n" +" pixelport_other_pal=0|1\n" +" pixeldata_adjust_ntsc=0|1|2|3\n" +" pixeldata_adjust_pal=0|1|2|3\n" +"Si se pasan varias opciones, se deben separar entre sí mediante espacios." + +#. Type: string +#. Description +#. Type: string +#. Description +#: ../em8300.templates:7001 ../em8300.templates:8001 +msgid "" +"Some sets of options have been reported to remove color problems. Check the " +"package documentation for details." +msgstr "Se ha informado de que algunas combinaciones de opciones eliminan los problemas de color. Consulte la documentación del paquete para más detalles." + +#. Type: string +#. Description +#. Type: string +#. Description +#: ../em8300.templates:7001 ../em8300.templates:8001 +msgid "" +"Unfortunately, there is currently no way to find the right parameters for " +"your card, so you'll have to find them yourself by trial and error." +msgstr "Por desgracia, actualmente no hay manera de averiguar los parámetros adecuados para su tarjeta, así que tendrá que encontrarlos usted mismo mediante prueba y error." + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "Options for em8300 module:" +msgstr "Opciones para el módulo em8300:" + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "" +"Options can be passed to the em8300 kernel module when it is loaded to " +"control how it works." +msgstr "Al cargar el módulo em8300 del núcleo, se le pueden pasar opciones para controlar su modo de funcionamiento." + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "" +"Options include:\n" +" activate_loopback=0|1\n" +" audio_driver=alsa|oss|osslike|none\n" +" alsa_index=-1|0|1|2|3|...\n" +" dsp_num=-1|0|1|2|3|...\n" +" bt865_ucode_timeout=0|1\n" +" dicom_control=0|1\n" +" dicom_fix=0|1\n" +" dicom_other_pal=0|1\n" +" use_bt865=0|1\n" +"Multiple options should be separated by spaces." +msgstr "" +"Estas opciones incluyen:\n" +" activate_loopback=0|1\n" +" audio_driver=alsa|oss|osslike|none\n" +" alsa_index=-1|0|1|2|3|...\n" +" dsp_num=-1|0|1|2|3|...\n" +" bt865_ucode_timeout=0|1\n" +" dicom_control=0|1\n" +" dicom_fix=0|1\n" +" dicom_other_pal=0|1\n" +" use_bt865=0|1\n" +"Si se pasan varias opciones, se deben separar entre sí mediante espacios." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "No creation of device files" +msgstr "Sin creación de ficheros de dispositivos" + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "Special device files must exist to enable access to your MPEG decoder card." +msgstr "Los ficheros especiales de dispositivo son necesarios para acceder a su tarjeta decodificadora de MPEG." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"You seem to be using a static /dev. Special device files can't be created " +"automatically because no major number has been allocated to the em8300 " +"officially yet." +msgstr "Parece que está usando un /dev estático. No se puede crear automáticamente los ficheros especiales de dispositivo porque todavía no se ha asignado oficialmente ningún número mayor («major number») al em8300." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"Hence, you'll have to choose a major number to use (121 is used by default, " +"but it's officially allocated to \"LOCAL/EXPERIMENTAL USE\") and create the " +"corresponding device files yourself. Please read /usr/share/doc/em8300/" +"README.Debian for more info." +msgstr "Por lo tanto, tendrá que elegir un número mayor (por omisión se usa 121, pero oficialmente está asignado a «USO LOCAL/EXPERIMENTAL») y crear los ficheros de dispositivo correspondientes usted mismo. Consulte «/usr/share/doc/em8300/README.Debian» para más información." + --- em8300-0.18.0.orig/debian/po/ru.po +++ em8300-0.18.0/debian/po/ru.po @@ -0,0 +1,343 @@ +# translation of em8300_debconf_ru.po to Russian +# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER +# This file is distributed under the same license as the PACKAGE package. +# +# Yuri Kozlov , 2007. +msgid "" +msgstr "" +"Project-Id-Version: 0.16.0-1\n" +"Report-Msgid-Bugs-To: nboullis@debian.org\n" +"POT-Creation-Date: 2007-01-06 19:00+0100\n" +"PO-Revision-Date: 2007-01-03 00:48+0300\n" +"Last-Translator: Yuri Kozlov \n" +"Language-Team: Russian \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" +"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%" +"10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "Download microcode image from the Web?" +msgstr "Загрузить образ Ñ Ð¼Ð¸ÐºÑ€Ð¾ÐºÐ¾Ð´Ð¾Ð¼ из веб?" + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"The upstream developers have tried several microcode images and selected the " +"one that works best on various cards. Therefore, this microcode image is " +"probably better than the ones you can get from your Windows drivers. The " +"upstream developers have made it available for download on their website." +msgstr "" +"Разработчики программы иÑпытали неÑколько образов Ñ Ð¼Ð¸ÐºÑ€Ð¾ÐºÐ¾Ð´Ð¾Ð¼ и подобрали " +"Ð´Ð»Ñ ÐºÐ°Ð¶Ð´Ð¾Ð¹ карты лучший. ПоÑтому, предлагаемый образ Ñ Ð¼Ð¸ÐºÑ€Ð¾ÐºÐ¾Ð´Ð¾Ð¼, вероÑтно, " +"лучше чем тот, который вы получили из драйвера Windows. Разработчики " +"программы размеÑтили образ Ð´Ð»Ñ Ð·Ð°Ð³Ñ€ÑƒÐ·ÐºÐ¸ на Ñвоём веб-Ñайте." + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"However, because of some legal issues, this microcode image cannot be " +"distributed by Debian. If you do not want to download it, you can still " +"extract the appropriate microcode image(s) from the Windows .vxd file, using " +"em8300mc_ex." +msgstr "" +"Однако, из-за проблем Ñ Ð·Ð°ÐºÐ¾Ð½Ð¾Ð´Ð°Ñ‚ÐµÐ»ÑŒÑтвом, Ñтот образ Ñ Ð¼Ð¸ÐºÑ€Ð¾ÐºÐ¾Ð´Ð¾Ð¼ не может " +"раÑпроÑтранÑÑ‚ÑŒÑÑ Debian. ЕÑли вы не хотите Ñкачивать образ, то можете " +"выделить ÑоответÑтвующий образ(Ñ‹) Ñ Ð¼Ð¸ÐºÑ€Ð¾ÐºÐ¾Ð´Ð¾Ð¼ из Windows файла .vxd Ñ " +"помощью em8300mc_ex." + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"Warning: If /lib/firmware/em8300.bin already exists on your system, it will " +"be overwritten by the downloaded file." +msgstr "" +"Предупреждение: еÑли файл /lib/firmware/em8300.bin уже еÑÑ‚ÑŒ в ÑиÑтеме, то он " +"будет перезапиÑан загруженным файлом." + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "Failed to download microcode image" +msgstr "Ðе удалоÑÑŒ Ñкачать образ Ñ Ð¼Ð¸ÐºÑ€Ð¾ÐºÐ¾Ð´Ð¾Ð¼" + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "" +"The microcode image was not downloaded from the upstream authors' web site. " +"You probably won't be able to use your MPEG decoder card until you download " +"a microcode image." +msgstr "" +"Образ Ñ Ð¼Ð¸ÐºÑ€Ð¾ÐºÐ¾Ð´Ð¾Ð¼ не был загружен Ñ Ñайта разработчиков. ВероÑтно, вы не " +"Ñможете иÑпользовать карту MPEG декодера, пока не Ñкачаете образ Ñ " +"микрокодом." + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "" +"To retry, run \"dpkg-reconfigure em8300\" as root, or download it from\n" +" http://dxr3.sourceforge.net/download/em8300.uc\n" +"and save it as \"/lib/firmware/em8300.bin\"." +msgstr "" +"Чтобы повторить попытку, запуÑтите \"dpkg-reconfigure em8300\" Ñ Ð¿Ñ€Ð°Ð²Ð°Ð¼Ð¸ " +"ÑуперпользователÑ, или Ñкачайте\n" +" http://dxr3.sourceforge.net/download/em8300.uc\n" +"и Ñохраните в файле \"/lib/firmware/em8300.bin\"." + +#. Type: select +#. Choices +#: ../em8300.templates:3001 +msgid "None${files}" +msgstr "Ðет${files}" + +#. Type: select +#. Description +#: ../em8300.templates:3002 +msgid "Primary microcode:" +msgstr "ИÑпользуемый микрокод:" + +#. Type: select +#. Description +#: ../em8300.templates:3002 +msgid "" +"This will copy a microcode image previously installed in /usr/share/em8300/ " +"to /lib/firmware/em8300.bin and use it." +msgstr "" +"Ранее уÑтановленный образ Ñ Ð¼Ð¸ÐºÑ€Ð¾ÐºÐ¾Ð´Ð¾Ð¼ будет Ñкопирован из /usr/share/" +"em8300/ в /lib/firmware/em8300.bin и иÑпользован." + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "Delete old firmware directory?" +msgstr "Удалить Ñтарый каталог Ñ Ð¼Ð¸ÐºÑ€Ð¾ÐºÐ¾Ð´Ð¾Ð¼?" + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "" +"Multiple microcode images seem to be installed in /usr/share/em8000/. " +"Support for multiple microcode images has been removed from this version, so " +"if you wish to continue using multiple microcode images, you will have to " +"keep these files and handle the situation manually. You will be responsible " +"for removing these files once you have finished with them." +msgstr "" +"КажетÑÑ, что в каталог /usr/share/em8000/ уÑтановлено неÑколько образов Ñ " +"микрокодом. Поддержка неÑкольких образов Ñ Ð¼Ð¸ÐºÑ€Ð¾ÐºÐ¾Ð´Ð¾Ð¼ была удалена из Ñтой " +"верÑии, поÑтому, еÑли вы хотите продолжать иÑпользовать неÑколько образов Ñ " +"микрокодом, вам нужно оÑтавить Ñти файлы и разрешить Ñитуацию " +"ÑамоÑтоÑтельно. Ð’Ñ‹ Ñами должны удалить Ñти файлы, поÑле того как что-нибудь " +"Ñделаете Ñ Ð½Ð¸Ð¼Ð¸." + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "" +"Most people need only a single microcode image. If you want to use only one " +"microcode image, or if you do not know why you have multiple microcode " +"images installed, then you can accept and the extra files will be deleted." +msgstr "" +"БольшинÑтву людей доÑтаточно только одного образа Ñ Ð¼Ð¸ÐºÑ€Ð¾ÐºÐ¾Ð´Ð¾Ð¼. ЕÑли вы " +"хотите иÑпользовать только один образ Ñ Ð¼Ð¸ÐºÑ€Ð¾ÐºÐ¾Ð´Ð¾Ð¼, или еÑли не знаете " +"почему вдруг оказалоÑÑŒ уÑтановлено неÑколько образов, то ответьте " +"утвердительно и лишние файлы будут удалены." + +#. Type: select +#. Description +#: ../em8300.templates:5001 +msgid "Chip used on MPEG decoder card:" +msgstr "Чип, который иÑпользуетÑÑ Ð² вашей карте декодера MPEG:" + +#. Type: select +#. Description +#: ../em8300.templates:5001 +msgid "" +"Creative DXR3 cards have a bt865 on board, while Hollywood Plus cards use an " +"adv717x." +msgstr "" +"Карты Creative DXR3 Ñодержат на плате bt865, а в картах Hollywood Plus " +"иÑпользуетÑÑ adv717x." + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "Options for bt865 module:" +msgstr "Параметры Ð¼Ð¾Ð´ÑƒÐ»Ñ bt865:" + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "" +"Options can be passed to the bt865 kernel module when it is loaded to " +"control how it works." +msgstr "" +"Модулю Ñдра bt865 можно указать параметры Ð´Ð»Ñ ÑƒÐ¿Ñ€Ð°Ð²Ð»ÐµÐ½Ð¸Ñ ÐµÐ³Ð¾ работой, " +"которые будут переданы при загрузке." + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "" +"Options include:\n" +" output_mode=comp+svideo|rgb\n" +"Multiple options should be separated by spaces." +msgstr "" +"Параметры:\n" +" output_mode=comp+svideo|rgb\n" +"Можно указать неÑколько параметров через пробел." + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "Options for adv717x module:" +msgstr "Параметры Ð¼Ð¾Ð´ÑƒÐ»Ñ adv717x:" + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "" +"Options can be passed to the adv717x kernel module when it is loaded to " +"control how it works." +msgstr "" +"Модулю Ñдра adv717x можно указать параметры Ð´Ð»Ñ ÑƒÐ¿Ñ€Ð°Ð²Ð»ÐµÐ½Ð¸Ñ ÐµÐ³Ð¾ работой, " +"которые будут переданы при загрузке." + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "" +"Options include:\n" +" output_mode=comp+svideo|svideo|comp|comp+psvideo|psvideo|composvideo|yuv|" +"rgb|rgbs\n" +" pixelport_16bit=0|1\n" +" pixelport_other_pal=0|1\n" +" pixeldata_adjust_ntsc=0|1|2|3\n" +" pixeldata_adjust_pal=0|1|2|3\n" +"Multiple options should be separated by spaces." +msgstr "" +"Параметры:\n" +" output_mode=comp+svideo|svideo|comp|comp+psvideo|psvideo|composvideo|yuv|" +"rgb|rgbs\n" +" pixelport_16bit=0|1\n" +" pixelport_other_pal=0|1\n" +" pixeldata_adjust_ntsc=0|1|2|3\n" +" pixeldata_adjust_pal=0|1|2|3\n" +"Можно указать неÑколько параметров через пробел." + +#. Type: string +#. Description +#. Type: string +#. Description +#: ../em8300.templates:7001 ../em8300.templates:8001 +msgid "" +"Some sets of options have been reported to remove color problems. Check the " +"package documentation for details." +msgstr "" +"Ðам Ñообщили, что Ñ Ð¿Ð¾Ð¼Ð¾Ñ‰ÑŒÑŽ некоторых параметров можно уÑтранить проблему Ñ " +"цветом. Подробней об Ñтом читайте в документации к пакету." + +#. Type: string +#. Description +#. Type: string +#. Description +#: ../em8300.templates:7001 ../em8300.templates:8001 +msgid "" +"Unfortunately, there is currently no way to find the right parameters for " +"your card, so you'll have to find them yourself by trial and error." +msgstr "" +"К Ñожалению, в данный момент Ð½ÐµÐ»ÑŒÐ·Ñ Ð¿Ð¾Ð´Ð¾Ð±Ñ€Ð°Ñ‚ÑŒ нужные параметры Ð´Ð»Ñ Ð²Ð°ÑˆÐµÐ¹ " +"карты, поÑтому вам придётÑÑ Ñделать Ñто ÑамоÑтоÑтельно путём проб и ошибок." + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "Options for em8300 module:" +msgstr "Параметры Ð¼Ð¾Ð´ÑƒÐ»Ñ em8300:" + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "" +"Options can be passed to the em8300 kernel module when it is loaded to " +"control how it works." +msgstr "" +"Модулю Ñдра em8300 можно указать параметры Ð´Ð»Ñ ÑƒÐ¿Ñ€Ð°Ð²Ð»ÐµÐ½Ð¸Ñ ÐµÐ³Ð¾ работой, " +"которые будут переданы при загрузке." + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "" +"Options include:\n" +" activate_loopback=0|1\n" +" audio_driver=alsa|oss|osslike|none\n" +" alsa_index=-1|0|1|2|3|...\n" +" dsp_num=-1|0|1|2|3|...\n" +" bt865_ucode_timeout=0|1\n" +" dicom_control=0|1\n" +" dicom_fix=0|1\n" +" dicom_other_pal=0|1\n" +" use_bt865=0|1\n" +"Multiple options should be separated by spaces." +msgstr "" +"Параметры:\n" +" activate_loopback=0|1\n" +" audio_driver=alsa|oss|osslike|none\n" +" alsa_index=-1|0|1|2|3|...\n" +" dsp_num=-1|0|1|2|3|...\n" +" bt865_ucode_timeout=0|1\n" +" dicom_control=0|1\n" +" dicom_fix=0|1\n" +" dicom_other_pal=0|1\n" +" use_bt865=0|1\n" +"Можно указать неÑколько параметров через пробел." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "No creation of device files" +msgstr "Файлы уÑтройÑтва не Ñозданы" + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"Special device files must exist to enable access to your MPEG decoder card." +msgstr "" +"Ð”Ð»Ñ Ð´Ð¾Ñтупа к карте декодера MPEG должны ÑущеÑтвовать Ñпециальные файлы " +"уÑтройÑтва." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"You seem to be using a static /dev. Special device files can't be created " +"automatically because no major number has been allocated to the em8300 " +"officially yet." +msgstr "" +"КажетÑÑ, вы иÑпользуете ÑтатичеÑкий /dev. Специальные файлы уÑтройÑтва не " +"будут Ñозданы автоматичеÑки, так как пока Ð´Ð»Ñ em8300 официально не назначено " +"главного номера уÑтройÑтва." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"Hence, you'll have to choose a major number to use (121 is used by default, " +"but it's officially allocated to \"LOCAL/EXPERIMENTAL USE\") and create the " +"corresponding device files yourself. Please read /usr/share/doc/em8300/" +"README.Debian for more info." +msgstr "" +"Следовательно, вы должны ÑамоÑтоÑтельно выбрать главный номер (по умолчанию " +"иÑпользуетÑÑ 121, но официально он из диапазона \"ЛОКÐЛЬÐЫЙ/" +"ЭКСПЕРИМЕÐТÐЛЬÐОЕ ИСПОЛЬЗОВÐÐИЕ\") и Ñоздать ÑоответÑтвующие файлы " +"уÑтройÑтва. Подробней читайте в файле /usr/share/doc/em8300/README.Debian." --- em8300-0.18.0.orig/debian/po/fr.po +++ em8300-0.18.0/debian/po/fr.po @@ -0,0 +1,352 @@ +# translation of fr.po to French +# +# Translators, if you are not familiar with the PO format, gettext +# documentation is worth reading, especially sections dedicated to +# this format, e.g. by running: +# info -n '(gettext)PO Files' +# info -n '(gettext)Header Entry' +# +# Some information specific to po-debconf are available at +# /usr/share/doc/po-debconf/README-trans +# or http://www.debian.org/intl/l10n/po-debconf/README-trans +# +# Developers do not need to manually edit POT or PO files. +# +# Christian Perrier , 2006. +msgid "" +msgstr "" +"Project-Id-Version: fr\n" +"Report-Msgid-Bugs-To: nboullis@debian.org\n" +"POT-Creation-Date: 2007-01-06 19:00+0100\n" +"PO-Revision-Date: 2006-12-22 22:55+0100\n" +"Last-Translator: Christian Perrier \n" +"Language-Team: French \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=ISO-8859-15\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "Download microcode image from the Web?" +msgstr "Faut-il télécharger l'image du microcode sur Internet ?" + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"The upstream developers have tried several microcode images and selected the " +"one that works best on various cards. Therefore, this microcode image is " +"probably better than the ones you can get from your Windows drivers. The " +"upstream developers have made it available for download on their website." +msgstr "" +"Les développeurs amont ont essayé plusieurs images de microcode et choisi " +"celle qui fonctionne le mieux avec différentes cartes. En conséquence, cette " +"image de microcode fonctionne probablement mieux que celles que vous " +"obtiendriez à partir de vos pilotes Windows. Cette image de microcode est " +"disponible sur le site web des développeurs amont." + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"However, because of some legal issues, this microcode image cannot be " +"distributed by Debian. If you do not want to download it, you can still " +"extract the appropriate microcode image(s) from the Windows .vxd file, using " +"em8300mc_ex." +msgstr "" +"Cependant, pour des raisons légales, elle ne peut pas être distribuée par " +"Debian. Si vous ne souhaitez pas la télécharger, vous pouvez toujours " +"extraire celle(s) du fichier .vxd de Windows en utilisant la commande " +"« em8300-mc_ex »." + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"Warning: If /lib/firmware/em8300.bin already exists on your system, it will " +"be overwritten by the downloaded file." +msgstr "" +"Attention : si un fichier /lib/firmware/em8300.bin existe déjà sur le " +"système, il sera écrasé par le fichier téléchargé." + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "Failed to download microcode image" +msgstr "Échec du téléchargement de l'image du microcode" + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "" +"The microcode image was not downloaded from the upstream authors' web site. " +"You probably won't be able to use your MPEG decoder card until you download " +"a microcode image." +msgstr "" +"L'image du microcode n'a pas pu être téléchargée depuis le site des " +"développeurs amont. Vous ne pourrez probablement pas utiliser votre carte de " +"décompression MPEG tant qu'elle ne sera pas téléchargée." + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "" +"To retry, run \"dpkg-reconfigure em8300\" as root, or download it from\n" +" http://dxr3.sourceforge.net/download/em8300.uc\n" +"and save it as \"/lib/firmware/em8300.bin\"." +msgstr "" +"Pour réessayer cette opération, vous pouvez utiliser la commande « dpkg-" +"reconfigure em8300 » avec les privilèges du superutilisateur ou télécharger " +"vous-même l'image du microcode à l'adresse http://dxr3.sourceforge.net/" +"download/em8300.uc puis la placer sur votre système sous le nom /usr/share/" +"em8300/em8300.uc." + +#. Type: select +#. Choices +#: ../em8300.templates:3001 +msgid "None${files}" +msgstr "Aucun${files}" + +#. Type: select +#. Description +#: ../em8300.templates:3002 +msgid "Primary microcode:" +msgstr "Microcode principal :" + +#. Type: select +#. Description +#: ../em8300.templates:3002 +msgid "" +"This will copy a microcode image previously installed in /usr/share/em8300/ " +"to /lib/firmware/em8300.bin and use it." +msgstr "" +"L'image du microcode installée jusqu'ici dans /usr/share/em8300/ sera copiée " +"dans /lib/firmware/em8300.bin et sera utilisée." + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "Delete old firmware directory?" +msgstr "Faut-il supprimer l'ancien répertoire du microcode ?" + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "" +"Multiple microcode images seem to be installed in /usr/share/em8000/. " +"Support for multiple microcode images has been removed from this version, so " +"if you wish to continue using multiple microcode images, you will have to " +"keep these files and handle the situation manually. You will be responsible " +"for removing these files once you have finished with them." +msgstr "" +"Plusieurs images de microcode semblent être installées dans /usr/share/" +"em8000/. La gestion d'images de microcode multiples a été supprimée de cette " +"version. En conséquence, si vous voulez continuer à utiliser plusieurs " +"images de microcode, vous devrez les conserver et les gérer vous-même, y " +"compris les effacer quand vous n'en aurez plus besoin." + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "" +"Most people need only a single microcode image. If you want to use only one " +"microcode image, or if you do not know why you have multiple microcode " +"images installed, then you can accept and the extra files will be deleted." +msgstr "" +"Dans la plupart des cas, une seule image est nécessaire. Si vous êtes dans " +"ce cas et si vous ignorez pourquoi plusieurs images sont détectées, vous " +"pouvez choisir cette option et les fichiers supplémentaires seront effacés." + +#. Type: select +#. Description +#: ../em8300.templates:5001 +msgid "Chip used on MPEG decoder card:" +msgstr "Composant utilisé par votre carte de décompression MPEG :" + +#. Type: select +#. Description +#: ../em8300.templates:5001 +msgid "" +"Creative DXR3 cards have a bt865 on board, while Hollywood Plus cards use an " +"adv717x." +msgstr "" +"Les cartes DXR3 de Creative sont dotées d'un composant bt865 alors que les " +"cartes Hollywood Plus utilisent un adv717x." + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "Options for bt865 module:" +msgstr "Options pour le module bt865 :" + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "" +"Options can be passed to the bt865 kernel module when it is loaded to " +"control how it works." +msgstr "" +"Les options passées au module bt865 du noyau permettent de contrôler son " +"mode de fonctionnement." + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "" +"Options include:\n" +" output_mode=comp+svideo|rgb\n" +"Multiple options should be separated by spaces." +msgstr "" +"Ces options peuvent être :\n" +" output_mode=comp+svideo|rgb\n" +"Les différentes options doivent être séparées par des espaces." + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "Options for adv717x module:" +msgstr "Options pour le module adv717x :" + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "" +"Options can be passed to the adv717x kernel module when it is loaded to " +"control how it works." +msgstr "" +"Les options passées au module adv717x du noyau permettent de contrôler son " +"mode de fonctionnement." + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "" +"Options include:\n" +" output_mode=comp+svideo|svideo|comp|comp+psvideo|psvideo|composvideo|yuv|" +"rgb|rgbs\n" +" pixelport_16bit=0|1\n" +" pixelport_other_pal=0|1\n" +" pixeldata_adjust_ntsc=0|1|2|3\n" +" pixeldata_adjust_pal=0|1|2|3\n" +"Multiple options should be separated by spaces." +msgstr "" +"Ces options peuvent être :\n" +" - output_mode=comp+svideo|svideo|comp|comp+psvideo|psvideo|composvideo|yuv|" +"rgb|rgbs\n" +" - pixelport_16bit=0|1\n" +" - pixelport_other_pal=0|1\n" +" - pixeldata_adjust_ntsc=0|1|2|3\n" +" - pixeldata_adjust_pal=0|1|2|3\n" +"Les différentes options doivent être séparées par des espaces." + +#. Type: string +#. Description +#. Type: string +#. Description +#: ../em8300.templates:7001 ../em8300.templates:8001 +msgid "" +"Some sets of options have been reported to remove color problems. Check the " +"package documentation for details." +msgstr "" +"Certaines combinaisons sont connues pour supprimer les problèmes de couleur. " +"Veuillez consulter la documentation pour plus de détails." + +#. Type: string +#. Description +#. Type: string +#. Description +#: ../em8300.templates:7001 ../em8300.templates:8001 +msgid "" +"Unfortunately, there is currently no way to find the right parameters for " +"your card, so you'll have to find them yourself by trial and error." +msgstr "" +"Malheureusement, il n'existe actuellement pas de moyen pour trouver les " +"paramètres adaptés à votre carte. Vous devez donc les trouver par essais " +"successifs." + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "Options for em8300 module:" +msgstr "Options pour le module em8300 :" + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "" +"Options can be passed to the em8300 kernel module when it is loaded to " +"control how it works." +msgstr "" +"Les options passées au module em8300 du noyau permettent de contrôler son " +"mode de fonctionnement." + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "" +"Options include:\n" +" activate_loopback=0|1\n" +" audio_driver=alsa|oss|osslike|none\n" +" alsa_index=-1|0|1|2|3|...\n" +" dsp_num=-1|0|1|2|3|...\n" +" bt865_ucode_timeout=0|1\n" +" dicom_control=0|1\n" +" dicom_fix=0|1\n" +" dicom_other_pal=0|1\n" +" use_bt865=0|1\n" +"Multiple options should be separated by spaces." +msgstr "" +"Ces options peuvent être :\n" +" - activate_loopback=0|1\n" +" - audio_driver=alsa|oss|osslike|none\n" +" - alsa_index=-1|0|1|2|3|...\n" +" - dsp_num=-1|0|1|2|3|...\n" +" - bt865_ucode_timeout=0|1\n" +" - dicom_control=0|1\n" +" - dicom_fix=0|1\n" +" - dicom_other_pal=0|1\n" +" - use_bt865=0|1\n" +"Les différentes options doivent être séparées par des espaces." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "No creation of device files" +msgstr "Pas de création des fichiers de périphériques" + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"Special device files must exist to enable access to your MPEG decoder card." +msgstr "" +"Des fichiers spéciaux de périphériques sont nécessaires pour pouvoir accéder " +"à votre carte de décompression MPEG." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"You seem to be using a static /dev. Special device files can't be created " +"automatically because no major number has been allocated to the em8300 " +"officially yet." +msgstr "" +"Le répertoire /dev semble être géré statiquement. Les fichiers de " +"périphériques ne peuvent pas être créés automatiquement car aucun numéro " +"majeur (« major number ») n'a encore été attribué au pilote em8300." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"Hence, you'll have to choose a major number to use (121 is used by default, " +"but it's officially allocated to \"LOCAL/EXPERIMENTAL USE\") and create the " +"corresponding device files yourself. Please read /usr/share/doc/em8300/" +"README.Debian for more info." +msgstr "" +"En conséquence, vous devez choisir un numéro majeur (121 par défaut, " +"quoiqu'alloué officiellement pour utilisation locale ou expérimentale) et " +"créer vous-même le fichier de périphérique correspondant. Veuillez consulter " +"le fichier /usr/share/doc/em8300/README.Debian pour plus d'informations." --- em8300-0.18.0.orig/debian/po/pt.po +++ em8300-0.18.0/debian/po/pt.po @@ -0,0 +1,341 @@ +# translation of em8300 debconf to Portuguese +# Copyright (C) 2007 Américo Monteiro +# This file is distributed under the same license as the em8300 package. +# +# Américo Monteiro , 2007. +msgid "" +msgstr "" +"Project-Id-Version: em8300 0.16.0-2\n" +"Report-Msgid-Bugs-To: nboullis@debian.org\n" +"POT-Creation-Date: 2007-01-06 19:00+0100\n" +"PO-Revision-Date: 2007-08-11 18:21+0100\n" +"Last-Translator: Américo Monteiro \n" +"Language-Team: Portuguese \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "Download microcode image from the Web?" +msgstr "Transferir a imagem microcode da Web?" + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"The upstream developers have tried several microcode images and selected the " +"one that works best on various cards. Therefore, this microcode image is " +"probably better than the ones you can get from your Windows drivers. The " +"upstream developers have made it available for download on their website." +msgstr "" +"Os desenvolvedores têm testado várias imagens microcode e seleccionaram a " +"que funciona melhor em várias placas. Portanto, esta imagem microcode é " +"provavelmente melhor que aquelas que pode obter dos seus drivers do Windows. " +"Os desenvolvedores colocaram-na disponível para transferência a partir do " +"website deles." + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"However, because of some legal issues, this microcode image cannot be " +"distributed by Debian. If you do not want to download it, you can still " +"extract the appropriate microcode image(s) from the Windows .vxd file, using " +"em8300mc_ex." +msgstr "" +"No entanto, devido a questões legais, esta imagem microcode não pode ser " +"distribuida pela Debian. Se você não quiser transferi-la, você também pode " +"extrair a(s) imagem(ns) microcode apropriadas do ficheiro .vxd do Windows " +"usando o em8300mc_ex." + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"Warning: If /lib/firmware/em8300.bin already exists on your system, it will " +"be overwritten by the downloaded file." +msgstr "" +"Aviso: Se /lib/firmware/em8300.bin já existir no seu sistema, será " +"substituido pelo ficheiro transferido." + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "Failed to download microcode image" +msgstr "Falha ao transferir a imagem microcode" + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "" +"The microcode image was not downloaded from the upstream authors' web site. " +"You probably won't be able to use your MPEG decoder card until you download " +"a microcode image." +msgstr "" +"A imagem microcode não foi transferida do website do autor. Você " +"provavelmente não vai poder usar a sua placa descodificadora de MPEG até que " +"transfira a imagem microcode." + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "" +"To retry, run \"dpkg-reconfigure em8300\" as root, or download it from\n" +" http://dxr3.sourceforge.net/download/em8300.uc\n" +"and save it as \"/lib/firmware/em8300.bin\"." +msgstr "" +"Para tentar de novo, corra \"dpkg-reconfigure em8300\" como root, ou faça\n" +"você a transferência de http://dxr3.sourceforge.net/download/em8300.uc\n" +"e grave como \"/lib/firmware/em8300.bin\"." + +#. Type: select +#. Choices +#: ../em8300.templates:3001 +msgid "None${files}" +msgstr "None${files}" + +#. Type: select +#. Description +#: ../em8300.templates:3002 +msgid "Primary microcode:" +msgstr "Microcode primário:" + +#. Type: select +#. Description +#: ../em8300.templates:3002 +msgid "" +"This will copy a microcode image previously installed in /usr/share/em8300/ " +"to /lib/firmware/em8300.bin and use it." +msgstr "" +"Isto irá copiar a imagem microcode previamente instalada em " +"/usr/share/em8300/ para /lib/firmware/em8300.bin e irá usá-la." + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "Delete old firmware directory?" +msgstr "Apagar o antigo directório de firmware?" + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "" +"Multiple microcode images seem to be installed in /usr/share/em8000/. " +"Support for multiple microcode images has been removed from this version, so " +"if you wish to continue using multiple microcode images, you will have to " +"keep these files and handle the situation manually. You will be responsible " +"for removing these files once you have finished with them." +msgstr "" +"Parecem estar instaladas múltiplas imagens microcode em " +"/usr/share/em8000/. O suporte para múltiplas imagens microcode foi removido " +"nesta versão, por isso se deseja continuar a usar múltiplas imagens " +"microcode, você terá que manter estes ficheiros e controlar a situação " +"manualmente. Você será responsável por remover estes ficheiros assim que não " +"precisar mais deles." + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "" +"Most people need only a single microcode image. If you want to use only one " +"microcode image, or if you do not know why you have multiple microcode " +"images installed, then you can accept and the extra files will be deleted." +msgstr "" +"A maioria das pessoas apenas precisa dum uma imagem microcode. Se você apenas " +"quer usar uma imagem microcode, ou se não sabe porque tem múltiplas imagens " +"microcode instaladas, então pode aceitar aqui e os ficheiros extra serão " +"eliminados." + +#. Type: select +#. Description +#: ../em8300.templates:5001 +msgid "Chip used on MPEG decoder card:" +msgstr "Chip usado pela placa descodificadora de MPEG:" + +#. Type: select +#. Description +#: ../em8300.templates:5001 +msgid "" +"Creative DXR3 cards have a bt865 on board, while Hollywood Plus cards use an " +"adv717x." +msgstr "" +"As placas Creative DXR3 têm o chip bt865, enquanto as placas Hollywood Plus " +"usam o chip adv717x." + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "Options for bt865 module:" +msgstr "Opções para o módulo bt865:" + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "" +"Options can be passed to the bt865 kernel module when it is loaded to " +"control how it works." +msgstr "" +"Podem ser passadas opções ao módulo de kernel bt865 quando é carregado " +"para controlar como ele funciona." + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "" +"Options include:\n" +" output_mode=comp+svideo|rgb\n" +"Multiple options should be separated by spaces." +msgstr "" +"Opções incluem:\n" +" output_mode=comp+svideo|rgb\n" +"Múltiplas opções devem ser separadas por espaços." + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "Options for adv717x module:" +msgstr "Opções para o módulo adv717x:" + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "" +"Options can be passed to the adv717x kernel module when it is loaded to " +"control how it works." +msgstr "" +"Podem ser passadas opções ao módulo de kernel adv717x quando é carregado " +"para controlar como ele funciona." + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "" +"Options include:\n" +" output_mode=comp+svideo|svideo|comp|comp+psvideo|psvideo|composvideo|yuv|" +"rgb|rgbs\n" +" pixelport_16bit=0|1\n" +" pixelport_other_pal=0|1\n" +" pixeldata_adjust_ntsc=0|1|2|3\n" +" pixeldata_adjust_pal=0|1|2|3\n" +"Multiple options should be separated by spaces." +msgstr "" +"Opções incluem:\n" +" output_mode=comp+svideo|svideo|comp|comp+psvideo|psvideo|composvideo|yuv|" +"rgb|rgbs\n" +" pixelport_16bit=0|1\n" +" pixelport_other_pal=0|1\n" +" pixeldata_adjust_ntsc=0|1|2|3\n" +" pixeldata_adjust_pal=0|1|2|3\n" +"Múltiplas opções devem ser separadas por espaços." + +#. Type: string +#. Description +#. Type: string +#. Description +#: ../em8300.templates:7001 ../em8300.templates:8001 +msgid "" +"Some sets of options have been reported to remove color problems. Check the " +"package documentation for details." +msgstr "" +"Foram relatados alguns conjuntos de opções como solução para problemas com " +"cores. Verifique a documentação do pacote para mais detalhes." + +#. Type: string +#. Description +#. Type: string +#. Description +#: ../em8300.templates:7001 ../em8300.templates:8001 +msgid "" +"Unfortunately, there is currently no way to find the right parameters for " +"your card, so you'll have to find them yourself by trial and error." +msgstr "" +"Infelizmente, não há maneira de descobrir quais os parâmetros correctos " +"para a sua placa, então você terá que descobri-los por tentativas." + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "Options for em8300 module:" +msgstr "Opções para o módulo em8300:" + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "" +"Options can be passed to the em8300 kernel module when it is loaded to " +"control how it works." +msgstr "" +"Podem ser passadas opções ao módulo de kernel em8300 quando é carregado " +"para controlar como ele funciona." + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "" +"Options include:\n" +" activate_loopback=0|1\n" +" audio_driver=alsa|oss|osslike|none\n" +" alsa_index=-1|0|1|2|3|...\n" +" dsp_num=-1|0|1|2|3|...\n" +" bt865_ucode_timeout=0|1\n" +" dicom_control=0|1\n" +" dicom_fix=0|1\n" +" dicom_other_pal=0|1\n" +" use_bt865=0|1\n" +"Multiple options should be separated by spaces." +msgstr "" +"Opções incluem:\n" +" activate_loopback=0|1\n" +" audio_driver=alsa|oss|osslike|none\n" +" alsa_index=-1|0|1|2|3|...\n" +" dsp_num=-1|0|1|2|3|...\n" +" bt865_ucode_timeout=0|1\n" +" dicom_control=0|1\n" +" dicom_fix=0|1\n" +" dicom_other_pal=0|1\n" +" use_bt865=0|1\n" +"Múltiplas opções devem ser separadas por espaços. " + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "No creation of device files" +msgstr "Nenhuma criação de ficheiros de dispositivo." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "Special device files must exist to enable access to your MPEG decoder card." +msgstr "" +"Precisam existir ficheiros especiais de dispositivo para permitir acesso à " +"sua placa descodificadora de MPEG." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"You seem to be using a static /dev. Special device files can't be created " +"automatically because no major number has been allocated to the em8300 " +"officially yet." +msgstr "" +"Parece que você está a usar /dev estáticos. Ficheiros especiais de " +"dispositivo não podem ser criados automaticamente porque nenhum número " +"'major' foi ainda oficialmente alocado ao em8300." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"Hence, you'll have to choose a major number to use (121 is used by default, " +"but it's officially allocated to \"LOCAL/EXPERIMENTAL USE\") and create the " +"corresponding device files yourself. Please read /usr/share/doc/em8300/" +"README.Debian for more info." +msgstr "" +"Por isso, você tem que escolher um número 'major' para usar (121 é usado por " +"omissão, mas está oficialmente alocado a \"LOCAL/EXPERIMENTAL USE\") e criar " +"os ficheiros de dispositivo correspondentes você mesmo. Por favor leia " +"/usr/share/doc/em8300/README.Debian para mais informação." + --- em8300-0.18.0.orig/debian/po/templates.pot +++ em8300-0.18.0/debian/po/templates.pot @@ -0,0 +1,269 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER +# This file is distributed under the same license as the PACKAGE package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"Report-Msgid-Bugs-To: nboullis@debian.org\n" +"POT-Creation-Date: 2007-01-06 19:00+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=CHARSET\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "Download microcode image from the Web?" +msgstr "" + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"The upstream developers have tried several microcode images and selected the " +"one that works best on various cards. Therefore, this microcode image is " +"probably better than the ones you can get from your Windows drivers. The " +"upstream developers have made it available for download on their website." +msgstr "" + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"However, because of some legal issues, this microcode image cannot be " +"distributed by Debian. If you do not want to download it, you can still " +"extract the appropriate microcode image(s) from the Windows .vxd file, using " +"em8300mc_ex." +msgstr "" + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"Warning: If /lib/firmware/em8300.bin already exists on your system, it will " +"be overwritten by the downloaded file." +msgstr "" + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "Failed to download microcode image" +msgstr "" + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "" +"The microcode image was not downloaded from the upstream authors' web site. " +"You probably won't be able to use your MPEG decoder card until you download " +"a microcode image." +msgstr "" + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "" +"To retry, run \"dpkg-reconfigure em8300\" as root, or download it from\n" +" http://dxr3.sourceforge.net/download/em8300.uc\n" +"and save it as \"/lib/firmware/em8300.bin\"." +msgstr "" + +#. Type: select +#. Choices +#: ../em8300.templates:3001 +msgid "None${files}" +msgstr "" + +#. Type: select +#. Description +#: ../em8300.templates:3002 +msgid "Primary microcode:" +msgstr "" + +#. Type: select +#. Description +#: ../em8300.templates:3002 +msgid "" +"This will copy a microcode image previously installed in /usr/share/em8300/ " +"to /lib/firmware/em8300.bin and use it." +msgstr "" + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "Delete old firmware directory?" +msgstr "" + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "" +"Multiple microcode images seem to be installed in /usr/share/em8000/. " +"Support for multiple microcode images has been removed from this version, so " +"if you wish to continue using multiple microcode images, you will have to " +"keep these files and handle the situation manually. You will be responsible " +"for removing these files once you have finished with them." +msgstr "" + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "" +"Most people need only a single microcode image. If you want to use only one " +"microcode image, or if you do not know why you have multiple microcode " +"images installed, then you can accept and the extra files will be deleted." +msgstr "" + +#. Type: select +#. Description +#: ../em8300.templates:5001 +msgid "Chip used on MPEG decoder card:" +msgstr "" + +#. Type: select +#. Description +#: ../em8300.templates:5001 +msgid "" +"Creative DXR3 cards have a bt865 on board, while Hollywood Plus cards use an " +"adv717x." +msgstr "" + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "Options for bt865 module:" +msgstr "" + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "" +"Options can be passed to the bt865 kernel module when it is loaded to " +"control how it works." +msgstr "" + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "" +"Options include:\n" +" output_mode=comp+svideo|rgb\n" +"Multiple options should be separated by spaces." +msgstr "" + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "Options for adv717x module:" +msgstr "" + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "" +"Options can be passed to the adv717x kernel module when it is loaded to " +"control how it works." +msgstr "" + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "" +"Options include:\n" +" output_mode=comp+svideo|svideo|comp|comp+psvideo|psvideo|composvideo|yuv|" +"rgb|rgbs\n" +" pixelport_16bit=0|1\n" +" pixelport_other_pal=0|1\n" +" pixeldata_adjust_ntsc=0|1|2|3\n" +" pixeldata_adjust_pal=0|1|2|3\n" +"Multiple options should be separated by spaces." +msgstr "" + +#. Type: string +#. Description +#. Type: string +#. Description +#: ../em8300.templates:7001 ../em8300.templates:8001 +msgid "" +"Some sets of options have been reported to remove color problems. Check the " +"package documentation for details." +msgstr "" + +#. Type: string +#. Description +#. Type: string +#. Description +#: ../em8300.templates:7001 ../em8300.templates:8001 +msgid "" +"Unfortunately, there is currently no way to find the right parameters for " +"your card, so you'll have to find them yourself by trial and error." +msgstr "" + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "Options for em8300 module:" +msgstr "" + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "" +"Options can be passed to the em8300 kernel module when it is loaded to " +"control how it works." +msgstr "" + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "" +"Options include:\n" +" activate_loopback=0|1\n" +" audio_driver=alsa|oss|osslike|none\n" +" alsa_index=-1|0|1|2|3|...\n" +" dsp_num=-1|0|1|2|3|...\n" +" bt865_ucode_timeout=0|1\n" +" dicom_control=0|1\n" +" dicom_fix=0|1\n" +" dicom_other_pal=0|1\n" +" use_bt865=0|1\n" +"Multiple options should be separated by spaces." +msgstr "" + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "No creation of device files" +msgstr "" + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"Special device files must exist to enable access to your MPEG decoder card." +msgstr "" + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"You seem to be using a static /dev. Special device files can't be created " +"automatically because no major number has been allocated to the em8300 " +"officially yet." +msgstr "" + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"Hence, you'll have to choose a major number to use (121 is used by default, " +"but it's officially allocated to \"LOCAL/EXPERIMENTAL USE\") and create the " +"corresponding device files yourself. Please read /usr/share/doc/em8300/" +"README.Debian for more info." +msgstr "" --- em8300-0.18.0.orig/debian/po/cs.po +++ em8300-0.18.0/debian/po/cs.po @@ -0,0 +1,378 @@ +# +# Translators, if you are not familiar with the PO format, gettext +# documentation is worth reading, especially sections dedicated to +# this format, e.g. by running: +# info -n '(gettext)PO Files' +# info -n '(gettext)Header Entry' +# +# Some information specific to po-debconf are available at +# /usr/share/doc/po-debconf/README-trans +# or http://www.debian.org/intl/l10n/po-debconf/README-trans +# +# Developers do not need to manually edit POT or PO files. +# +msgid "" +msgstr "" +"Project-Id-Version: em8300 0.15.0.dfsg-1\n" +"Report-Msgid-Bugs-To: nboullis@debian.org\n" +"POT-Creation-Date: 2007-01-06 19:00+0100\n" +"PO-Revision-Date: 2007-01-02 21:39+0100\n" +"Last-Translator: Martin Sin \n" +"Language-Team: Czech \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "Download microcode image from the Web?" +msgstr "Stáhnout obraz mikrokódu z webu?" + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"The upstream developers have tried several microcode images and selected the " +"one that works best on various cards. Therefore, this microcode image is " +"probably better than the ones you can get from your Windows drivers. The " +"upstream developers have made it available for download on their website." +msgstr "" +"Vývojáři vyzkouÅ¡eli různé obrazy mikrokódu a vybrali ten, který nejlépe " +"pracuje s různými kartami. Proto je tento obraz mikrokódu pravdÄ›podobnÄ› " +"lepší než ty, které můžete získat z vaÅ¡ich ovladaÄů Windows. Vývojáři ho " +"zpřístupnili ke stažení na svých webových stránkách." + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"However, because of some legal issues, this microcode image cannot be " +"distributed by Debian. If you do not want to download it, you can still " +"extract the appropriate microcode image(s) from the Windows .vxd file, using " +"em8300mc_ex." +msgstr "" +"Bohužel, z důvodu nÄ›kterých právních důvodů, nemůže být tento obraz " +"distribuován spolu s Debianem. Pokud si ho nepÅ™ejete stáhnout, můžete stále " +"rozbalit odpovídající obraz(y) mikrokódu z Windowsového souboru .vxd, pomocí " +"em8300mc_ex." + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"Warning: If /lib/firmware/em8300.bin already exists on your system, it will " +"be overwritten by the downloaded file." +msgstr "" +"UpozornÄ›ní: pokud již ve vaÅ¡em systému existuje soubor /lib/firmware/em8300." +"bin, bude pÅ™epsán staženým souborem." + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "Failed to download microcode image" +msgstr "Stažení obrazu mikrokódu selhalo" + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "" +"The microcode image was not downloaded from the upstream authors' web site. " +"You probably won't be able to use your MPEG decoder card until you download " +"a microcode image." +msgstr "" +"Obraz mikrokódu nemohl být stažen z webových stránek autorů programu. Dokud " +"nebude tento obraz stažen, pravdÄ›podobnÄ› nebudete moci svoji kartu " +"dekódující MPEG použít." + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "" +"To retry, run \"dpkg-reconfigure em8300\" as root, or download it from\n" +" http://dxr3.sourceforge.net/download/em8300.uc\n" +"and save it as \"/lib/firmware/em8300.bin\"." +msgstr "" +"Pro nový pokus o stažení obrazu spusÅ¥te pod uživatelem root \"dpkg-" +"reconfigure em8300\", nebo ho stáhnÄ›te ruÄnÄ› z\n" +" http://dxr3.sourceforge.net/download/em8300.uc\n" +"a uložte do \"/lib/firmware/em8300.bin\"." + +#. Type: select +#. Choices +#: ../em8300.templates:3001 +msgid "None${files}" +msgstr "Žádný${files}" + +#. Type: select +#. Description +#: ../em8300.templates:3002 +msgid "Primary microcode:" +msgstr "Primární mikrokód:" + +#. Type: select +#. Description +#: ../em8300.templates:3002 +msgid "" +"This will copy a microcode image previously installed in /usr/share/em8300/ " +"to /lib/firmware/em8300.bin and use it." +msgstr "" +"Tímto zkopírujete obraz mikrokódu, který jste pÅ™edtím nainstalovali v /usr/" +"share/em8300/, do /lib/firmware/em8300.bin a můžete ho zaÄít používat." + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "Delete old firmware directory?" +msgstr "Smazat adresář se starým firmwarem?" + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "" +"Multiple microcode images seem to be installed in /usr/share/em8000/. " +"Support for multiple microcode images has been removed from this version, so " +"if you wish to continue using multiple microcode images, you will have to " +"keep these files and handle the situation manually. You will be responsible " +"for removing these files once you have finished with them." +msgstr "" +"Zdá se, že je nainstalováno více obrazů mikrokódu v /usr/share/em8000/. " +"Podpora více obrazů mikrokódu byla odstranÄ›na poÄínaje touto verzí, takže " +"pokud si pÅ™ejete používat více obrazů mikrokódu, musíte tyto soubory " +"ponechat a oÅ¡etÅ™it vzniklou situaci ruÄnÄ›. PÅ™i odstraňování tÄ›chto souborů " +"se chovejte zodpovÄ›dnÄ›." + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "" +"Most people need only a single microcode image. If you want to use only one " +"microcode image, or if you do not know why you have multiple microcode " +"images installed, then you can accept and the extra files will be deleted." +msgstr "" +"VÄ›tÅ¡ina lidí potÅ™ebuje pouze jeden obraz mikrokódu. Pokud chcete používat " +"pouze jeden obraz mikrokódu, nebo nevíte proÄ jich máte nainstalováno více, " +"pak můžete souhlasit a nadbyteÄné soubory budou odstranÄ›ny." + +#. Type: select +#. Description +#: ../em8300.templates:5001 +msgid "Chip used on MPEG decoder card:" +msgstr "ÄŒip používaný kartou dekodéru MPEG:" + +#. Type: select +#. Description +#: ../em8300.templates:5001 +msgid "" +"Creative DXR3 cards have a bt865 on board, while Hollywood Plus cards use an " +"adv717x." +msgstr "" +"Karty Creative DXR3 mají na desce bt865, zatímco karty Hollywood Plus " +"používají adv717x." + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "Options for bt865 module:" +msgstr "Volby modulu bt865:" + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "" +"Options can be passed to the bt865 kernel module when it is loaded to " +"control how it works." +msgstr "" +"Tyto volby mohou být pÅ™edány modulu jádra bt865 pÅ™i jeho zavedení a " +"zajiÅ¡Å¥ují jeho správnou funkÄnost." + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "" +"Options include:\n" +" output_mode=comp+svideo|rgb\n" +"Multiple options should be separated by spaces." +msgstr "" +"Možnosti obsahují:\n" +" output_mode=comp+svideo|rgb\n" +"Více voleb je potÅ™eba oddÄ›lit pomocí mezer." + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "Options for adv717x module:" +msgstr "Volby modulu adv717x:" + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "" +"Options can be passed to the adv717x kernel module when it is loaded to " +"control how it works." +msgstr "" +"Tyto volby mohou být pÅ™edány modulu jádra adv717x pÅ™i jeho zavedení a " +"zajiÅ¡Å¥ují jeho správnou funkÄnost." + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "" +"Options include:\n" +" output_mode=comp+svideo|svideo|comp|comp+psvideo|psvideo|composvideo|yuv|" +"rgb|rgbs\n" +" pixelport_16bit=0|1\n" +" pixelport_other_pal=0|1\n" +" pixeldata_adjust_ntsc=0|1|2|3\n" +" pixeldata_adjust_pal=0|1|2|3\n" +"Multiple options should be separated by spaces." +msgstr "" +"Možné volby jsou:\n" +" output_mode=comp+svideo|svideo|comp|comp+psvideo|psvideo|composvideo|yuv|" +"rgb|rgbs\n" +" pixelport_16bit=0|1\n" +" pixelport_other_pal=0|1\n" +" pixeldata_adjust_ntsc=0|1|2|3\n" +" pixeldata_adjust_pal=0|1|2|3\n" +"Více voleb oddÄ›lte pomocí mezer." + +#. Type: string +#. Description +#. Type: string +#. Description +#: ../em8300.templates:7001 ../em8300.templates:8001 +msgid "" +"Some sets of options have been reported to remove color problems. Check the " +"package documentation for details." +msgstr "" +"NÄ›které volby jsou známé tím, že odstraňují problémy s barvami. Pro více " +"informací se podívejte do dokumentace balíÄku." + +#. Type: string +#. Description +#. Type: string +#. Description +#: ../em8300.templates:7001 ../em8300.templates:8001 +msgid "" +"Unfortunately, there is currently no way to find the right parameters for " +"your card, so you'll have to find them yourself by trial and error." +msgstr "" +"Bohužel, v souÄasné dobÄ› není znám způsob, jak nalézt správné parametry pro " +"vaÅ¡i kartu, tak si je budete muset nalézt sami na základÄ› pokusu a omylu." + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "Options for em8300 module:" +msgstr "Volby modulu em8300:" + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "" +"Options can be passed to the em8300 kernel module when it is loaded to " +"control how it works." +msgstr "" +"Tyto volby mohou být pÅ™edány modulu jádra em8300 pÅ™i jeho zavedení a " +"zajiÅ¡Å¥ují jeho správnou funkÄnost." + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "" +"Options include:\n" +" activate_loopback=0|1\n" +" audio_driver=alsa|oss|osslike|none\n" +" alsa_index=-1|0|1|2|3|...\n" +" dsp_num=-1|0|1|2|3|...\n" +" bt865_ucode_timeout=0|1\n" +" dicom_control=0|1\n" +" dicom_fix=0|1\n" +" dicom_other_pal=0|1\n" +" use_bt865=0|1\n" +"Multiple options should be separated by spaces." +msgstr "" +"Možné volby jsou:\n" +" activate_loopback=0|1\n" +" audio_driver=alsa|oss|osslike|none\n" +" alsa_index=-1|0|1|2|3|...\n" +" dsp_num=-1|0|1|2|3|...\n" +" bt865_ucode_timeout=0|1\n" +" dicom_control=0|1\n" +" dicom_fix=0|1\n" +" dicom_other_pal=0|1\n" +" use_bt865=0|1\n" +"Více voleb oddÄ›lte pomocí mezer." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "No creation of device files" +msgstr "Bez vytvoÅ™ení souborů zařízení" + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"Special device files must exist to enable access to your MPEG decoder card." +msgstr "" +"Pro přístup ke kartÄ› dekodéru MPEG je nutná existence souborů zařízení." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"You seem to be using a static /dev. Special device files can't be created " +"automatically because no major number has been allocated to the em8300 " +"officially yet." +msgstr "" +"Zdá se, že používáte statické /dev. Není možné vytvoÅ™it speciální soubory " +"zařízení, protože em8300 nemá dosud pÅ™iÅ™azené žádné hlavní Äíslo." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"Hence, you'll have to choose a major number to use (121 is used by default, " +"but it's officially allocated to \"LOCAL/EXPERIMENTAL USE\") and create the " +"corresponding device files yourself. Please read /usr/share/doc/em8300/" +"README.Debian for more info." +msgstr "" +"Je potÅ™eba zvolit hlavní Äíslo (ve výchozím nastavení se používá 121, i když " +"se oficiálnÄ› používá pro \"MÃSTNÃ/EXPERIMENTÃLNà POUŽITÃ\") a vytvoÅ™it " +"odpovídající soubory zařízení. Pro více informací si prosím pÅ™eÄtÄ›te /usr/" +"share/doc/em8300/README.Debian." + +#~ msgid "Select desired microcode image" +#~ msgstr "Zvolte požadovaný obraz mikrokódu" + +#~ msgid "Create device files for MPEG decoder card" +#~ msgstr "VytvoÅ™it soubory zařízení pro kartu dekodéru MPEG" + +#~ msgid "" +#~ "Unfortunately, no major number has been officially allocated yet for the " +#~ "em8300. The major number 121 is currently used, but it's officially " +#~ "reserved for \"LOCAL/EXPERIMENTAL USE\"." +#~ msgstr "" +#~ "Bohužel, hlavní Äíslo nebylo pro em8300 jeÅ¡tÄ› oficiálnÄ› pÅ™iÅ™azeno. Hlavní " +#~ "Äíslo 121 je v souÄasné dobÄ› již použito, ale je zároveň oficiálnÄ› " +#~ "vyhrazeno pro \"MÃSTNÃ/EXPERIMENTÃLNà POUŽITÃ\"." + +#~ msgid "" +#~ "Thus, you may have already chosen to use this major number for another " +#~ "use. If you have, using the same major number for em8300 may cause " +#~ "problems or prevent access to the card. In most cases, however, unless " +#~ "you know for sure that you are already using it, it should be available." +#~ msgstr "" +#~ "Z tohoto důvodu, lze toto Äíslo používat jako hlavní Äíslo pro další " +#~ "použití. Použití stejného hlavního Äísla pro em8300 může způsobit " +#~ "problémy nebo zabránit přístupu ke kartÄ›. Ve vÄ›tÅ¡inÄ› případů by mÄ›lo být " +#~ "k dispozici (pokud si ovÅ¡em nejste jisti, že toto Äíslo již používáte pro " +#~ "jiné úÄely)." + +#~ msgid "" +#~ "If you need to use a different major number for em8300, please read /usr/" +#~ "share/doc/em8300/README.Debian for more info." +#~ msgstr "" +#~ "Pokud potÅ™ebujete použít pro em8300 jiné hlavní Äíslo, pak si prosím pro " +#~ "více informací pÅ™eÄtÄ›te /usr/share/doc/em8300/README.Debian." --- em8300-0.18.0.orig/debian/po/POTFILES.in +++ em8300-0.18.0/debian/po/POTFILES.in @@ -0,0 +1 @@ +[type: gettext/rfc822deb] em8300.templates --- em8300-0.18.0.orig/debian/po/sv.po +++ em8300-0.18.0/debian/po/sv.po @@ -0,0 +1,327 @@ +# translation of em8300_0.16.4-3_sv.po to swedish +# Translators, if you are not familiar with the PO format, gettext +# documentation is worth reading, especially sections dedicated to +# this format, e.g. by running: +# info -n '(gettext)PO Files' +# info -n '(gettext)Header Entry' +# Some information specific to po-debconf are available at +# /usr/share/doc/po-debconf/README-trans +# or http://www.debian.org/intl/l10n/po-debconf/README-trans +# Developers do not need to manually edit POT or PO files. +# +# Martin Bagge , 2008. +msgid "" +msgstr "" +"Project-Id-Version: em8300_0.16.4-3_sv\n" +"Report-Msgid-Bugs-To: nboullis@debian.org\n" +"POT-Creation-Date: 2007-01-06 19:00+0100\n" +"PO-Revision-Date: 2008-06-26 21:45+0200\n" +"Last-Translator: Martin Bagge \n" +"Language-Team: swedish \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=ISO-8859-1\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.4\n" + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "Download microcode image from the Web?" +msgstr "Laddar ner mikrokod från Internet" + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"The upstream developers have tried several microcode images and selected the " +"one that works best on various cards. Therefore, this microcode image is " +"probably better than the ones you can get from your Windows drivers. The " +"upstream developers have made it available for download on their website." +msgstr "" +"Utvecklarna har försökt med ett antal mikrokodavbilder och valt den som " +"fungerar bäst på olika kort. Därför är denna mikrokod antagligen bättre än " +"den du får från din Windows-drivrutin. Utvecklarna har gjort den tillgänglig " +"på sin websida." + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"However, because of some legal issues, this microcode image cannot be " +"distributed by Debian. If you do not want to download it, you can still " +"extract the appropriate microcode image(s) from the Windows .vxd file, using " +"em8300mc_ex." +msgstr "" +"På grund av legala skäl kan denna mikrokod inte distribueras av Debian. Om " +"du inte vill ladda ner det kan du packa upp den lämpliga mikrokoden från " +"Windows .vxd-fil med em8300mc_ex." + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"Warning: If /lib/firmware/em8300.bin already exists on your system, it will " +"be overwritten by the downloaded file." +msgstr "" +"Varning: om /usr/share/em8300/em8300.uc redan finns på ditt system kommer " +"den att bli överskriven av den nedladdade filen." + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "Failed to download microcode image" +msgstr "Misslyckades att ladda ner microcode-image" + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "" +"The microcode image was not downloaded from the upstream authors' web site. " +"You probably won't be able to use your MPEG decoder card until you download " +"a microcode image." +msgstr "" +"Mikrokoden kunde inte laddas ner från utvecklarens websida. Du kommer " +"antagligen inte att kunna använda ditt kort för MPEG-avkodning förräns mikrokoden " +"har blivit nedladdad." + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "" +"To retry, run \"dpkg-reconfigure em8300\" as root, or download it from\n" +" http://dxr3.sourceforge.net/download/em8300.uc\n" +"and save it as \"/lib/firmware/em8300.bin\"." +msgstr "" +"För att försöka igen, kör \"dpkg-reconfigure em8300\" som root eller ladda " +"ned den på egen hand från\n" +" http://dxr3.sourceforge.net/download/em8300.uc\n" +"och lägg den i \"/usr/share/em8300/em8300.uc\"." + +#. Type: select +#. Choices +#: ../em8300.templates:3001 +msgid "None${files}" +msgstr "Ingen${files}" + +#. Type: select +#. Description +#: ../em8300.templates:3002 +msgid "Primary microcode:" +msgstr "Primär mikrokod:" + +#. Type: select +#. Description +#: ../em8300.templates:3002 +msgid "" +"This will copy a microcode image previously installed in /usr/share/em8300/ " +"to /lib/firmware/em8300.bin and use it." +msgstr "Detta använder en kopia av mikrokoden från /usr/share/em8300/ på /lib/firmware/em8300.bin." + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "Delete old firmware directory?" +msgstr "Ta bort den gamla katalogen för mikrokoden?" + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "" +"Multiple microcode images seem to be installed in /usr/share/em8000/. " +"Support for multiple microcode images has been removed from this version, so " +"if you wish to continue using multiple microcode images, you will have to " +"keep these files and handle the situation manually. You will be responsible " +"for removing these files once you have finished with them." +msgstr "Det verkar som om du har flera olika versioner av mikrokoden installerad i /usr/share/em8000/. Stöd för flera mikrokoder har tagits bort i den här versionen, om du vill fortsätta använda flera versioner väljer du att behålla dessa filer och hanterar det hela manuellt. Du är ansvarig för att de tas bort när du använt dem klart." + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "" +"Most people need only a single microcode image. If you want to use only one " +"microcode image, or if you do not know why you have multiple microcode " +"images installed, then you can accept and the extra files will be deleted." +msgstr "De flesta användarna behöver bara en kopia av mikrokoden. Om du bara vill ha en version, eller inte vet varför du har flera installerade, så kan du lugnt välja att ta bort dem." + +#. Type: select +#. Description +#: ../em8300.templates:5001 +msgid "Chip used on MPEG decoder card:" +msgstr "Identifiera chip på kortet för MPEG-avkodning" + +#. Type: select +#. Description +#: ../em8300.templates:5001 +msgid "" +"Creative DXR3 cards have a bt865 on board, while Hollywood Plus cards use an " +"adv717x." +msgstr "" +"Creative DXR3-korten har en bt865 inbyggd medans Hollywood Plus-korten har " +"en adv717x." + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "Options for bt865 module:" +msgstr "Ange inställningar för bt865-modulen." + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "" +"Options can be passed to the bt865 kernel module when it is loaded to " +"control how it works." +msgstr "" +"Inställningar kan skickas till kärnmodulen för bt865 när den laddas för att " +"kontrollera hur den fungerar." + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "" +"Options include:\n" +" output_mode=comp+svideo|rgb\n" +"Multiple options should be separated by spaces." +msgstr "" +"Tillgängliga inställningar är:\n" +" output_mode=comp+svideo|rgb\n" +"Mutlipla val separeras med blanksteg." + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "Options for adv717x module:" +msgstr "Specificera inställningar för adv717x-modulen" + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "" +"Options can be passed to the adv717x kernel module when it is loaded to " +"control how it works." +msgstr "" +"Inställningar kan skicka till adv717x-kernelmodulen när den laddas för att " +"kontrollera hur den fungerar." + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "" +"Options include:\n" +" output_mode=comp+svideo|svideo|comp|comp+psvideo|psvideo|composvideo|yuv|" +"rgb|rgbs\n" +" pixelport_16bit=0|1\n" +" pixelport_other_pal=0|1\n" +" pixeldata_adjust_ntsc=0|1|2|3\n" +" pixeldata_adjust_pal=0|1|2|3\n" +"Multiple options should be separated by spaces." +msgstr "" +"Tillgängliga inställningar är:\n" +"output_mode=comp+svideo|svideo|comp|comp+psvideo|psvideo|composvideo|yuv|rgb|rgbs\n" +" pixelport_16bit=x\n" +" pixelport_other_pal=x\n" +" pixeldata_adjust_ntsc=y\n" +" pixeldata_adjust_pal=y\n" +"där x är 0 eller 1, och y är 0, 1, 2 eller 3. Multipla inställningar avskiljs med blanksteg." + +#. Type: string +#. Description +#. Type: string +#. Description +#: ../em8300.templates:7001 ../em8300.templates:8001 +msgid "" +"Some sets of options have been reported to remove color problems. Check the " +"package documentation for details." +msgstr "" +"Några inställningar har rapporterats att de tar bort problem med färger. " +"Kontrollera paketdokumentationen för mer detaljer." + +#. Type: string +#. Description +#. Type: string +#. Description +#: ../em8300.templates:7001 ../em8300.templates:8001 +msgid "" +"Unfortunately, there is currently no way to find the right parameters for " +"your card, so you'll have to find them yourself by trial and error." +msgstr "" +"Tyvärr så finns det inget enkelt sätt att ta fram de rätta parametrarna för " +"ditt kort så du måste hitta dom själv genom att prova dig fram." + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "Options for em8300 module:" +msgstr "Ange inställningar för em8300-module" + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "" +"Options can be passed to the em8300 kernel module when it is loaded to " +"control how it works." +msgstr "" +"Inställningar kan skicka till em8300-kernelmodulen när den laddas för att " +"kontrollera hur den fungerar." + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "" +"Options include:\n" +" activate_loopback=0|1\n" +" audio_driver=alsa|oss|osslike|none\n" +" alsa_index=-1|0|1|2|3|...\n" +" dsp_num=-1|0|1|2|3|...\n" +" bt865_ucode_timeout=0|1\n" +" dicom_control=0|1\n" +" dicom_fix=0|1\n" +" dicom_other_pal=0|1\n" +" use_bt865=0|1\n" +"Multiple options should be separated by spaces." +msgstr "" +"Tillgängliga inställningar är:\n" +" activate_loopback=x\n" +" audio_driver=alsa|oss|osslike|none\n" +" alsa_index=y\n" +" dsp_num=y\n" +" bt865_ucode_timeout=x\n" +" dicom_control=x\n" +" dicom_fix=x\n" +" dicom_other_pal=x\n" +" use_bt865=x\n" +"där x är 0 eller 1 och y är -1, 0, 1, 2 eller 3 Multipla inställningar ska avskiljas med blanksteg." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "No creation of device files" +msgstr "Skapa inte enhetsfiler" + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "Special device files must exist to enable access to your MPEG decoder card." +msgstr "" +"En specialenhetsfil måste finnas för att ge tillgång till ditt MPEG-" +"dekoderkort." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"You seem to be using a static /dev. Special device files can't be created " +"automatically because no major number has been allocated to the em8300 " +"officially yet." +msgstr "Det verkar som om du har en statisk /dev. Specialenhetsfiler kan inte skapas automatiskt då inget huvudnummer har avsatts för em8300 än." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"Hence, you'll have to choose a major number to use (121 is used by default, " +"but it's officially allocated to \"LOCAL/EXPERIMENTAL USE\") and create the " +"corresponding device files yourself. Please read /usr/share/doc/em8300/" +"README.Debian for more info." +msgstr "Däför måste du välja ett huvudnummer manuellt. (121 är standardvädet, det är avsett för \"LOKALT/EXPERIMENTELLT ANVÄNDADE\") och skapa de nödvändiga enhetsfilerna själv. Läs /usr/share/doc/em8300/README.Debian för ytterligare information." + --- em8300-0.18.0.orig/debian/po/vi.po +++ em8300-0.18.0/debian/po/vi.po @@ -0,0 +1,357 @@ +# Vietnamese translation for em8300. +# Copyright © 2006 Free Software Foundation, Inc. +# Clytie Siddall , 2006. +# +msgid "" +msgstr "" +"Project-Id-Version: em8300\n" +"Report-Msgid-Bugs-To: nboullis@debian.org\n" +"POT-Creation-Date: 2007-01-06 19:00+0100\n" +"PO-Revision-Date: 2007-01-04 16:38+1030\n" +"Last-Translator: Clytie Siddall \n" +"Language-Team: Vietnamese \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=1; plural=0;\n" +"X-Generator: LocFactoryEditor 1.6fc1\n" + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "Download microcode image from the Web?" +msgstr "Tải ảnh mã vi xuống Mạng không?" + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"The upstream developers have tried several microcode images and selected the " +"one that works best on various cards. Therefore, this microcode image is " +"probably better than the ones you can get from your Windows drivers. The " +"upstream developers have made it available for download on their website." +msgstr "" +"Những nhà phát triển của dá»± án gốc đã thá»­ ra vài ảnh mã vi (microcode) thì " +"chá»n Ä‘iá»u hoạt Ä‘á»™ng hữu hiệu nhất trên các thẻ khác nhau. Do đó ảnh mã vi " +"này rất có thể chạy tốt hÆ¡n những Ä‘iá»u thuá»™c vá» trình Ä‘iá»u khiển Windows. " +"Những nhà phát triển của dá»± án gốc đã làm cho nó sẵn sàng cho bạn tải xuống " +"nÆ¡i Mạng của há»." + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"However, because of some legal issues, this microcode image cannot be " +"distributed by Debian. If you do not want to download it, you can still " +"extract the appropriate microcode image(s) from the Windows .vxd file, using " +"em8300mc_ex." +msgstr "" +"Tuy nhiên, do má»™t số vấn Ä‘á» hợp pháp, Debian không thể phát hành ảnh mã vi " +"này. Nếu bạn không muốn tải xuống nó, vẫn còn có khả năng rút những ảnh mã " +"vi thích hợp từ tập tin .vxd Windows, dùng « em8300mc_ex »." + +#. Type: boolean +#. Description +#: ../em8300.templates:1001 +msgid "" +"Warning: If /lib/firmware/em8300.bin already exists on your system, it will " +"be overwritten by the downloaded file." +msgstr "" +"Cảnh báo : nếu tập tin « /lib/firmware/em8300.bin » đã nằm trên hệ thống của " +"bạn, nó sẽ bị ghi đè bằng tập tin đã tải xuống." + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "Failed to download microcode image" +msgstr "Lá»—i tải xuống ảnh mã vi" + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "" +"The microcode image was not downloaded from the upstream authors' web site. " +"You probably won't be able to use your MPEG decoder card until you download " +"a microcode image." +msgstr "" +"Ảnh mã vi không được tải xuống nÆ¡i Mạng của dá»± án gốc. Rất có thể là bạn " +"không thể sá»­ dụng thẻ giải mã MPEG khi chÆ°a tải xuống ảnh mã vi." + +#. Type: error +#. Description +#: ../em8300.templates:2001 +msgid "" +"To retry, run \"dpkg-reconfigure em8300\" as root, or download it from\n" +" http://dxr3.sourceforge.net/download/em8300.uc\n" +"and save it as \"/lib/firmware/em8300.bin\"." +msgstr "" +"Äể thá»­ lại, hãy chạy lệnh cấu hình lại « dpkg-reconfigure em8300 » nhÆ° ngÆ°á»i " +"chủ, hoặc tải nó xuống địa chỉ:\n" +" http://dxr3.sourceforge.net/download/em8300.uc\n" +"rồi lÆ°u dạng « /lib/firmware/em8300.bin »." + +#. Type: select +#. Choices +#: ../em8300.templates:3001 +msgid "None${files}" +msgstr "Không có${files}" + +#. Type: select +#. Description +#: ../em8300.templates:3002 +msgid "Primary microcode:" +msgstr "Mã vi chính:" + +#. Type: select +#. Description +#: ../em8300.templates:3002 +msgid "" +"This will copy a microcode image previously installed in /usr/share/em8300/ " +"to /lib/firmware/em8300.bin and use it." +msgstr "" +"Việc này sẽ sao chép má»™t ảnh mã vi đã được cài đặt vào « /usr/share/em8300/ " +"» sang « /lib/firmware/em8300.bin » và sá»­ dụng nó." + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "Delete old firmware directory?" +msgstr "Xoá thÆ° mục phần vững cÅ© không?" + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "" +"Multiple microcode images seem to be installed in /usr/share/em8000/. " +"Support for multiple microcode images has been removed from this version, so " +"if you wish to continue using multiple microcode images, you will have to " +"keep these files and handle the situation manually. You will be responsible " +"for removing these files once you have finished with them." +msgstr "" +"Có vẻ là nhiá»u ảnh mã vi đã được cài đặt vào « /usr/share/em8000/ ». Phiên " +"bản này không còn há»— trợ lại khả năng quản lý nhiá»u ảnh mã vi thì nếu bạn " +"muốn tiếp tục sá»­ dụng nhiá»u ảnh mã vi, bạn cần phải giữ các tập tin này và " +"tá»± quản lý trÆ°á»ng hợp. Bạn cÅ©ng chịu trách nhiệm vá» việc gỡ bá» các tập tin " +"này má»™t khi dùng xong." + +#. Type: boolean +#. Description +#: ../em8300.templates:4001 +msgid "" +"Most people need only a single microcode image. If you want to use only one " +"microcode image, or if you do not know why you have multiple microcode " +"images installed, then you can accept and the extra files will be deleted." +msgstr "" +"Phần lá»›n ngÆ°á»i chỉ cần má»™t ảnh mã vi riêng lẻ. Muốn sá»­ dụng chỉ má»™t ảnh mã " +"vi, hoặc không biết tại sao có nhiá»u ảnh mã vi được cài đặt thì bạn có thể " +"chấp nhận ở đây và các tập tin thêm sẽ được xoá." + +#. Type: select +#. Description +#: ../em8300.templates:5001 +msgid "Chip used on MPEG decoder card:" +msgstr "Phiến tinh thể dùng trên thẻ giải mã MPEG:" + +#. Type: select +#. Description +#: ../em8300.templates:5001 +msgid "" +"Creative DXR3 cards have a bt865 on board, while Hollywood Plus cards use an " +"adv717x." +msgstr "" +"Thẻ Creative DXR3 có phiến tinh thể kiểu bt865, còn thẻ Hollywood Plus có " +"Ä‘iá»u adv717x." + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "Options for bt865 module:" +msgstr "Tùy chá»n cho mô-Ä‘un bt865:" + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "" +"Options can be passed to the bt865 kernel module when it is loaded to " +"control how it works." +msgstr "" +"CÅ©ng có khả năng gá»­i tùy chá»n cho mô-Ä‘un hạt nhân bt865 trong khi nạp, để " +"Ä‘iá»u khiển thao tác của nó. " + +#. Type: string +#. Description +#: ../em8300.templates:6001 +msgid "" +"Options include:\n" +" output_mode=comp+svideo|rgb\n" +"Multiple options should be separated by spaces." +msgstr "" +"Các tùy chá»n gồm có :\n" +" output_mode=comp+svideo|rgb\n" +"[output mode\t\tchế Ä‘á»™ xuất\n" +"comp\t\t\t(viết tắt) máy tính\n" +"svideo\t\t\tsảnh Ä‘á»™ng\n" +"rgb\t\t\t\t(viết tắt) màu Ä‘á», lục, xanh]\n" +"Nên định giá»›i nhiá»u tùy chá»n bằng dấu cách." + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "Options for adv717x module:" +msgstr "Tùy chá»n cho mô-Ä‘un adv717x:" + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "" +"Options can be passed to the adv717x kernel module when it is loaded to " +"control how it works." +msgstr "" +"CÅ©ng có khả năng gá»­i tùy chá»n cho mô-Ä‘un hạt nhân adv717x trong khi nạp, để " +"Ä‘iá»u khiển thao tác của nó. " + +#. Type: string +#. Description +#: ../em8300.templates:7001 +msgid "" +"Options include:\n" +" output_mode=comp+svideo|svideo|comp|comp+psvideo|psvideo|composvideo|yuv|" +"rgb|rgbs\n" +" pixelport_16bit=0|1\n" +" pixelport_other_pal=0|1\n" +" pixeldata_adjust_ntsc=0|1|2|3\n" +" pixeldata_adjust_pal=0|1|2|3\n" +"Multiple options should be separated by spaces." +msgstr "" +"Các tùy chá»n gồm có :\n" +" output_mode=comp+svideo|svideo|comp|comp+psvideo|psvideo|composvideo|yuv|" +"rgb|rgbs\n" +" pixelport_16bit=0|1\n" +" pixelport_other_pal=0|1\n" +" pixeldata_adjust_ntsc=0|1|2|3\n" +" pixeldata_adjust_pal=0|1|2|3\n" +"[output mode\t\tchế Ä‘á»™ xuất\n" +"comp\t\t\t(viết tắt) máy tính\n" +"svideo\t\t\tsảnh Ä‘á»™ng\n" +"rgb\t\t\t\t(viết tắt) màu Ä‘á», lục, xanh\n" +"pixel\t\t\tÄ‘iểm ảnh\n" +"port\t\t\t\tcổng\n" +"adjust\t\t\tÄ‘iá»u chỉnhother\t\t\tkhác]\n" +"Nên định giá»›i nhiá»u tùy chá»n bằng dấu cách." + +#. Type: string +#. Description +#. Type: string +#. Description +#: ../em8300.templates:7001 ../em8300.templates:8001 +msgid "" +"Some sets of options have been reported to remove color problems. Check the " +"package documentation for details." +msgstr "" +"NgÆ°á»i dùng đã thông bão má»™t số tập tùy chá»n riêng gây ra vấn Ä‘á» màu sắc. Hãy " +"kiểm tra tài liệu hÆ°á»›ng dẫn có sẵn trong gói, để tìm chi tiết." + +#. Type: string +#. Description +#. Type: string +#. Description +#: ../em8300.templates:7001 ../em8300.templates:8001 +msgid "" +"Unfortunately, there is currently no way to find the right parameters for " +"your card, so you'll have to find them yourself by trial and error." +msgstr "" +"Tiếc là hiện thá»i không thể tìm những tham số thích hợp vá»›i thẻ của bạn, vậy " +"bạn cần phải tá»± tìm bằng cách mò mẫm." + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "Options for em8300 module:" +msgstr "Tùy chá»n cho mô-Ä‘un em8300:" + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "" +"Options can be passed to the em8300 kernel module when it is loaded to " +"control how it works." +msgstr "" +"CÅ©ng có khả năng gá»­i tùy chá»n cho mô-Ä‘un hạt nhân em8300 trong khi nạp, để " +"Ä‘iá»u khiển thao tác của nó. " + +#. Type: string +#. Description +#: ../em8300.templates:8001 +msgid "" +"Options include:\n" +" activate_loopback=0|1\n" +" audio_driver=alsa|oss|osslike|none\n" +" alsa_index=-1|0|1|2|3|...\n" +" dsp_num=-1|0|1|2|3|...\n" +" bt865_ucode_timeout=0|1\n" +" dicom_control=0|1\n" +" dicom_fix=0|1\n" +" dicom_other_pal=0|1\n" +" use_bt865=0|1\n" +"Multiple options should be separated by spaces." +msgstr "" +"Các tùy chá»n gồm có :\n" +" activate_loopback=0|1\n" +" audio_driver=alsa|oss|osslike|none\n" +" alsa_index=-1|0|1|2|3|...\n" +" dsp_num=-1|0|1|2|3|...\n" +" bt865_ucode_timeout=0|1\n" +" dicom_control=0|1\n" +" dicom_fix=0|1\n" +" dicom_other_pal=0|1\n" +" use_bt865=0|1\n" +"[activate \t\tkích hoạt\n" +"loopback\t\tvòng lặp\n" +"audio\t\tâm thanh\n" +"device\t\tthiết bị\n" +"index\t\tchỉ mục\n" +"timeout\t\tthá»i hạn\n" +"control\t\tÄ‘iá»u khiểnfix\t\t\tsá»­a chữa\n" +"other\t\tkhác\n" +"use\t\t\tdùng]\n" +"Nên định giá»›i nhiá»u tùy chá»n bằng dấu cách." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "No creation of device files" +msgstr "Không tạo tập tin thiết bị" + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"Special device files must exist to enable access to your MPEG decoder card." +msgstr "" +"Cần có má»™t số tập tin thiết bị đặc biệt để hiệu lá»±c truy cấp thẻ giải mã " +"MPEG." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"You seem to be using a static /dev. Special device files can't be created " +"automatically because no major number has been allocated to the em8300 " +"officially yet." +msgstr "" +"Có vẻ là bạn sá»­ dụng má»™t « /dev » tÄ©nh. Không thể tá»± Ä‘á»™ng tạo các tập tin " +"thiết bị đặc biệt vì chÆ°a gán chính thức số chính nào cho em8300." + +#. Type: note +#. Description +#: ../em8300.templates:9001 +msgid "" +"Hence, you'll have to choose a major number to use (121 is used by default, " +"but it's officially allocated to \"LOCAL/EXPERIMENTAL USE\") and create the " +"corresponding device files yourself. Please read /usr/share/doc/em8300/" +"README.Debian for more info." +msgstr "" +"Vì thế, bạn cần phải chá»n má»™t số chính cần dùng (121 là mặc định, nhÆ°ng nó " +"được gán chính thức cho « LOCAL/EXPERIMENTAL USE » {chỉ dùng cục bá»™/thá»­ " +"nghiệm}) và tá»± tạo những tập tin thiết bị tÆ°Æ¡ng ứng. Hãy Ä‘á»c tài liệu Äá»c Äi " +"« /usr/share/doc/em8300/README.Debian » để tìm thêm thông tin." --- em8300-0.18.0.orig/debian/sourceforge.html/howto.html +++ em8300-0.18.0/debian/sourceforge.html/howto.html @@ -0,0 +1,644 @@ + + +Linux DXR3 and Hollywood+ Driver + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Dxr3 Logo

DXR3 & Hollywood Plus Logo

+ +Linux DXR3 and Hollywood+ Driver Project Howto + +
   
  + + + + News
+ About
+ FAQ
+ Howto
+ Download
+ Links
+ Developers
+ Project Page
+ + + + 		  + + + +DXR3 / Hollywood Plus HOWTO Table of Contents + + +
+ +

Prerequisites

+
    +

    + As with any project there are some prerequisites. Besides the obvious like, needing a computer running a recent version of Linux, you will, for now, need some experience building packages from scratch. You will also have to be comfortable with a text editor. Yeah, you know what that means. +

    +
  • Dxr3 or Hollywood Plus +

    + I hate to have to say it but before you can start watching DVDs and MPEG streams + using this driver, you need to have either a Creative Labs DXR3 or a Sigma Designs + Hollywood Plus hardware MPEG decoder card. If you have any other decoder card, this + driver is of no help to you. But if you have a fast enough computer you can still + watch MPEGs and DVDs on your monitor with one of the software viewers available. + (Remember, this wouldn't be here if someone didn't ask . . . ) +

    +
  • Kernel 2.2 or newer +

    + This driver will only work with Linux kernels version 2.2 and greater. If you are + running a 2.0 kernel, well then this is the time to get brave and upgrade! (And if + you are running 1.2 or 1.3 on modern hardware then you are either criminally insane + or a masochist, but that is a different story). But then there is the question, + does a computer old enough to be running a 2.0 kernel actually have enough power to + play a DVD - even with a hardware decoder card? Anyway, you'll need the source tree, + and you'll need to have run at least "make config" and "make dep" in that tree. +

    +
  • I2C Driver +

    + If you are running a 2.2 kernel, you need to install the I2C driver version 2.4.5 or + newer! You can get the I2C driver for 2.2 kernels at the LM Sensors Homepage. If you have + a 2.4 kernel, then I2C comes with the kernel and you just need to make sure that it + is compiled into the kernel or as a module. If you fail to do this, then your card + will emit X-Rays from your TV and cook your DNA! Just kidding. In either case, just + make sure that you have this I2C driver installed. +

    +
  • rmquasar.vxd (H+) or enc2dev.vxd (dxr3) + (as of driver 0.12.0 this is optional and not recommended unless you + have serious problems with the supplied microcode) +

    + You need the appropriate VxD from the Windows driver for your card. If you have a + Creative Labs Dxr3, then you will have enc2dev.vxd and if you have a Hollywood Plus, + then you'll have rmquasar.vxd. Easy enough. Now, you should be able to find these + bad boys in you windows/system directory. If you don't have a windows/system + directory because you don't have windows, then you can still get these guys. You + just need to obtain the latest version of your card's drivers from the appropriate + web site and unzip them. But wait, what the hell is that?!?! They only give us + rmquasar.vx_ and enc2dev.vx_! Where is the 'd'?!? They shorted us a 'd'! No, + actually, Microsoft, in their infinite corporate wisdom, long ago instituted the + policy of compressing their driver files for distribution, which strangely enough + are compressed again (as zips, cabs, self extracting exes, etc.) which just wastes + cpu cycles. And, if you haven't noticed, compressing a file twice rarely yields any + gain in compression. Now, since we are missing a 'd', note: a very special 'd', from + our driver file, we need to replace it. Included with the em8300 driver distribution + in the scripts directory is a perl program called msexpand.pl which, when run like + "msexpand.pl rmquasar.vx_", will after some time make a new copy of the file, this + time with the special 'd' replaced. Then you may continue. +

    +
  • Compiler and Related Tools +

    + You will need Perl and a C compiler. If you're building from a + CVS checkout, you'll need some GNU programs: automake and + autoconf. Those two also require GNU m4. Also, bootstrapping + a CVS checkout requires the development files for GTK+ 2.x + (in particular, its m4 macros). If you get errors later about + missing header files or libraries, you'll have to install + those as well. Chances are that suitable versions are + available in your distribution; if not, get them off the + Internet. +

    +
+ +

Getting the Source

+
    +

    There are currently two ways to get the source for this driver: by downloading a + 'stable' release or by downloading the latest CVS. Depending on how old the last release + is, it may be best to try out the CVS. +

    +
  • Download a Release +

    + If you decide to try one of the 'stable' releases, please note that as of yet none + are really quite stable. They are more akin to Mozilla's milestones in that there are + still many bugs to be worked out. +

    +
  • Source Via CVS +

    + #include <stdcvswarning.h>
    + Ok, yeah, you know CVS is often broken and unstable. Well, yeah, but we still need + you guys to check out from CVS and report those bugs. So please do. Also, plugin + updates for new releases of Xine and OMS are often available only on CVS for a long + period of time, so you really shouldn't be too shy about trying a CVS checkout. It + wont bite, I promise! Ok, the two steps to checking out the CVS are: +

    +$ cvs -d :pserver:anonymous@cvs.dxr3.sourceforge.net:/cvsroot/dxr3 login
    +CVS password: [Just press enter]
    +$ cvs -d :pserver:anonymous@cvs.dxr3.sourceforge.net:/cvsroot/dxr3 -z3 co em8300
    +
    + And that's it! You should have an em8300 directory under your current directory. In + there you'll find all the goodies you'll need later on. +

    +
+ +

Compiling the Modules

+
    +

    + Now we must compile the kernel modules and get them configured and loaded. +

    +
  • Makefile settings +

    + Ok, chdir to em8300/modules and open up the Makefile in your favorite editor. Now + change KERNEL_LOCATION to wherever your current kernel source tree is, and make sure + that you've at least run "make config ; make dep" in there. Now, change + -DEM8300_VIDEOMODE_DEFAULT= to EM8300_VIDEOMODE_PAL, EM8300_VIDEOMODE_PAL60, or + EM8300_VIDEOMODE_NTSC. If you live in the Americas, choose NTSC. Elsewhere (like + Europe), you're probably PAL. If you live in the former Soviet Union then your + standard is SECAM, which these cards do not support. You can probably get a PAL TV + or use VGA Overlay. Don't worry about these defaults too + much because they can be set at run time either by a dvd player with dxr3 support + or by the dhc utility. +

    +
  • If you have a 2.2 kernel (As of driver 0.11.0 this is no longer needed) +

    + If you are using a 2.2 kernel, just copy Makefile.2.2 to Makefile and follow the + instructions below. Make sure you have the I2C module compiled and installed. +

    +
  • Compiling +

    + Just run "make". This will build the four modules, adv717x.o, bt865.o, em8300.o, + and eeprom.o. To install the modules, run "make install". +

    +

    + If you have any trouble compiling the modules please send a detailed message to + the mailing list at dxr3-devel@lists.sourceforge.net. + Thanks. +

+ +

Creating the Device Files

+
    +

    + In Linux, and Unix in general, to communicate with a device you need to have a device + file. Well, the Dxr3 and H+ are no different. We currently use four device files, which + must be created as root. If you are running devfs or udev, these will be created automatically + and will use kernel assigned major/minor numbers, no need to read this section. +

    +
  • Creating the /dev/em8300* devices +

    To create the four device files, you must be root. + As root, run the modules/devices.sh script or + these commands: +

    # mknod /dev/em8300-0 c 121 0 +# mknod /dev/em8300_mv-0 c 121 1 +# mknod /dev/em8300_ma-0 c 121 2 +# mknod /dev/em8300_sp-0 c 121 3 + Note: The device numbers that we are using are currently using are likely to change + in the future. Keep that in mind. +

    +
    • +
+ +

Loading the Kernel Modules

+
    +
  • ldm and rmm +

    + In the em8300/modules directory there live two shell scripts related to loading and + unloading the kernel modules, ldm and rmm. ldm + automates loading of the driver modules, and rmm automates unloading of the modules. In + order to pass module parameters to the adv717x.o and em8300.o modules you must edit the + ldm script. Commented out underneath the lines to load the adv717x and em8300 modules + you can see some examples of the more commonly used module parameters. So, for example, + to set the adv717x module option "pixelport_16bit" to 0 and "pixelport_other_pal" to 1 you would have a line like the + following: +

    +insmod adv717x.o pixelport_16bit=0 pixelport_other_pal=1
    +
    + Enter other module options similarly. See the following table for a list of module + options and explanations of what they do. If you don't want to use ldm and rmm you + can just issue the appropriate modprobe/insmod/rmmod commands by themselves and + enter the module parameters on the command line or in /etc/modules.conf. Note, with + ldm, module options located in /etc/modules.conf will not be read, so if you use ldm + make sure to edit the module options in there. +

    +
  • Module Parameters +

    + There are multiple parameters for each of the modules that + affect their functionality. The choice of module options will + depend upon your particular board. Also, module options for + the adv717x driver do not matter for cards with a bt865 chip + and vice versa. Further, module options for the adv717x and + bt865 modules only matter for TV output and have no effect on + overlay. See + modules/README-modoptions + for the list of supported options, possible values, and their + descriptions as well as commonly used configurations. +

    +
+

All Things Microcode

+
    +

    + The em8300 RISC processor needs to be programed before use. This program is called a + "microcode" and we will use the one that has already been written for us. +

    +

    + Note that version 0.12.0 and later of the driver package comes + with a microcode, so just running em8300setup should be enough, + no need to extract your own. +

    +

    + Additionally, versions 0.15.2 and later have the capability to + load the microcode on demand, so even running em8300setup is no + longer needed for the purpose of just loading it. You may want to + run it for other purposes, though. +

    +

    + If you use the drivers in packaged form from your distribution, + chances are that the microcode is not included in the package. + If that is the case, read on. +

    +

    + A microcode that is known to work well for many users is + available separately from + http://dxr3.sourceforge.net/download/. + If you decide to use it, you can skip directly to the + loading section. +

    +
  • Uncompressing +

    + If you have downloaded a copy of the Windows driver (preferably the Windows 98 + driver) from Sigma Designs or Creative Labs or copied the driver from the cdrom, + then you will have to uncompress the driver files. If you have already installed the + Windows driver and have access to your windows/system directory, then you can skip + to the next section. First use unzip to uncompress and expand the driver archive. In + that archive you will find either rmquasar.vx_ or enc2dev.vx_ depending if you have + the Sigma Designs or Creative Labs drivers, respectively. Now we have to uncompress + this file. Use the provided perl program "msexpand.pl" located in em8300/scripts to + uncompress this file. For example: +

    $ unzip HP1_82W1.ZIP +$ em8300/scripts/msexpand.pl rmquasar.vx_ +

    +
  • Extracting +

    + Now that we have the uncompressed Windows 98 driver vxd, we need to extract the + microcode files. To do that use the included perl program microcode_extract.pl + located in em8300/scripts. After running this program two or three microcode files + will be written to the current directory, the number depending on the driver you + have. The different microcode versions seem to be for different revisions of the + cards. Currently, the only way to determine which microcode is correct for your + card is to try them all and pick the one that works the best. Do not be alarmed if + some of them do not work at all. +

    +
  • Loading +

    + At this point you should have the extracted microcode files + available. If you're using version 0.15.2 or newer, copy the microcode file to + wherever your system's hotplug configuration loads firmware images from (often + /lib/firmware), name it em8300.bin, and load the + modules; the microcode should be automatically uploaded. If not, or if using + version 0.15.1 or earlier, you can use the em8300setup tool to load it. Run + em8300setup -h and look at the -f option and where + it expects to find the microcode from, and copy the microcode there. The + included perl program microcode_upload.pl can also be used to load the + microcode into the em8300. For example: +

    $ em8300/scripts/microcode_upload.pl microcode0.bin + You should get a message like "Microcode uploaded to /dev/em8300-0". If there are + no messages then it was unable to open /dev/em8300-0 and you should verify that + the device file exists. If they do and you have the right permissions (if unsure + just chmod a+w /dev/em8300*) it usually means that you have the option "PNP OS + Installed" set to "enabled" in your bios. This option exists in virtually all x86 + bioses since the pentium. Disable this option, this means the bios will set up all + your plug and play device prior to booting the operating system. Windows has a bad + habit of randomizing pnp options on booting making it impossible for linux to save + any settings as they will have changed after booting into windows. Disabling pnp os + will fix this. +

    +

    + Note: This may cause vga passthrough to stop functioning. We are working on this. + The solution at this time is to just plug your monitor straight into the video card + or use the "activate_loopback" em8300 module option. You cannot watch MPEG streams + on the TV output connector with activate_loopback set, however. +

    +
+ +

Playing MPEG Streams and DVDs

+
    +

    + This section is all about playing MPEGs and DVDs. If you are using VGA loopback, first + see the VGA Overlay section then come right back here. If you are + playing on a TV, then make sure you have all your cables connected properly, and that + your TV is set to receive the composite signal generated by the card. So, since you are + following this document from top to bottom, you should be ready to go. +

    +
  • Playing MPEGs via /dev/em8300_mv-* and /dev/em8300_ma-* +

    + Sending mpeg and pcm streams directly to the card is a great way to test that the + thing is working properly without the overhead of working with a full on DVD player. + In order to display a MPEG video stream simply send it to "/dev/em8300_mv-0". + In order to test the analog audio capability of the card you can use mpg123. For + example: +

    $ extract_mpeg2 testvideostream.mpeg > /dev/em8300_mv-0 +$ mpg123 -a /dev/em8300_ma-0 somegoodtestmusic.mp3 + Note, you must send only MPEG video streams to /dev/em8300_mv-*, and only PCM audio to + /dev/em8300_ma-*. An MPEG system file, composed of both + video and audio, will cause garbage to be displayed on the screen. You must first + separate the system into video and audio components, and play each one separately. + Also, /dev/em8300-* is a control device, and cannot be use to play mpeg systems. +

    +
  • Using Xine to play DVDs +

    + A dxr3 plugin is included with Xine since Xine 0.5.0. Please see xine-lib/doc/README.dxr3 +

    +
  • Using MPlayer to play DVDs +

    + Invoke mplayer with the following options: "-ao oss:/dev/em8300_ma-0 -vo dxr3 -dvd <chapternumber>" +

    +
  • Using MPlayer to play DivX/RealVideo etc +

    + To play any non MPEG1/2 content with mplayer you have to specify an MPEG1 filter, you do this by + adding -vop lavc or -vop fame and you are good to go. If you are using gmplayer + (GUI enabled MPlayer) you can set the mpeg1 filter to use in + Preferences->Video->(dxr3)->Configure Driver. +

    +
  • Using OMS to play DVDs +

    + OMS was the original player for this project but since then development seems to + have stopped. Thus, we currently suggest you use Xine. This may change at some + future date. +

    +
+ +

Other Useful Programs

+
    +

    + In this section we describe some useful programs that have been contributed to the + project. +

    +
  • DHC by Ze'ev Maor +

    + DHC is a useful program written by Ze've Maor. DHC's source lives in the em8300/dhc + directory and it is built by default during the build process + if GTK+ 2.x's development files are available. + DHC can be used to adjust the brightness, contrast, saturation, aspect + ration, TV output standard (PAL, NTSC, and PAL 60), turn on and off the subpicture + (subtitles, etc.), and change between analog and spdif audio outputs. +

    +
+ +

Using VGA Overlay Mode

+
    +

    + VGA Overlay can be used to view hardware MPEG decoded streams on your computer monitor. + The main drawback of the Dxr3/H+ design is that using this feature results in added + noise and reduced visual quality on the monitor from the video card. So, you may notice + that your text that used to appear crisp is now fuzzy with the decoder card inserted. + Sorry, there is nothing we can do about this. If it bothers you too much, use a TV + instead. +

    +
  • Setting it up +

    + First, you must make sure that the overlay cable is correctly installed. Follow the + instructions that came with your card. Second, you may need to enable the + "activate_loopback" module option for the em8300 module. See the Module Parameters section above for details. Unload and reload the + modules for the change to take effect, if needed. Then you must load the microcode. + See the section All Things Microcode for help loading the + microcode. Now you should be ready to continue to the next section. Note: Overlay + support is considered experimental at this time and will probably not work. +

    +
  • dxr3view and autocal +

    + Again, run "bootstrap" in the em8300 directory, then run + configure, make, and make install. First, run autocal. This will make the screen + flash for a second. This has to be done every time the microcode is reloaded, which + means that you must load Xine or OMS before running autocal. Yeah, I know its silly. + Should be fixed in the future. Then you have to run dxr3view. This will bring up a + rectangular window with the overlay window on top. It should look akin to the + windows overlay. Now, you should be able to press play in Xine or OMS and watch your + MPEG. The control window in dxr3view can be used to fine tune the size, shape, and + appearance of the overlay to a certain extent. Also, if you press 't' while the + mouse is over the dxr3view window, a menu with several options, including + fullscreen, will appear. +

    +
+ +

Identifying your Card

+ +
    +

    Sometimes it is helpful to know some details about your particular board, especially + if you need help getting the driver to work. You can use the following table to help + figure out what card you have and if there are any special notes about it. +

    +
  • Sigma Designs Hollywood Plus Variants +

    + + + + + + + + + + + + + + + + + + + +
    Board IDEM8300 VersionVideo ChipNotes
    ???Rev 2ADV7170Requires pixelport_16=0
    ???Rev 2ADV7175Requires pixelport_16=1, dicom_control=1, dicom_fix=1
    +

    +
  • Creative Labs Dxr3 Variants +

    + + + + + + + + + + + + + +
    Board IDEM8300 VersionVideo ChipNotes
    ct7235-vbq (9938 rev b) board:ct7260Rev 2Conexant bt865akrf 
    +

    +
+ + +

Getting Help

+
    +

    + Eventually, every one of us needs a little help, especially with this hardware ;). There + are currently three ways to get help: IRC, the mailing list, and the Sourceforge Fora. + Note, the best way to get help is the Mailing list, and the least favorable is the + SourceForge Fora. This may change in the future, but currently not many developers visit + the SourceForge Fora. +

    +
  • Mailing List - Preferred Method +

    + By far the best way to get help is to send a message to the mailing list. This is + because all the developers are subscribed and read their email throughout the day. + The list is dxr3-devel@lists.sourceforge.net + and you can subscribe or unsubscribe at The SourceForge Project Mail + Page. +

    +
  • IRC Channel +

    + We have an IRC channel! Its #dxr3 on irc.openprojects.net. Come join us and ask + questions about the driver or just chat with the developers and other users. +

    +
  • Sourceforge Fora +

    + As nice as they are, we don't use them. But you really can't tell that by the number + of people who have posted to them. Do us all a favor, and just stay away from them + for now. Perhaps one day we may be popular enough to need them, but right now, just + say "no". +

    +
+ + + + 		  
+ + SourceForge Logo +   
 
+ +
dxr3-devel mailing list
+ + +Last modified: Thu Apr 13 21:50:11 EEST 2006 + + + --- em8300-0.18.0.orig/debian/sourceforge.html/faq.html +++ em8300-0.18.0/debian/sourceforge.html/faq.html @@ -0,0 +1,374 @@ + + +Linux DXR3 and Hollywood+ Driver + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Dxr3 Logo

DXR3 & Hollywood Plus Logo

+ +Linux DXR3 and Hollywood+ Driver Project FAQ + +
   
  + + + + News
+ About
+ FAQ
+ Howto
+ Download
+ Links
+ Developers
+ Project Page
+ + + + 		  + + + +Table of Contents + + +
+ +
+Answers +
+ +
Question: +
I'm unable to change the audio volume in my mixer, what gives? +
Answer: +
The em8300 does not contain an audio mixer, so this feature cannot be implemented. You could write a software mixer but we have decided that something like that does not belong in a kernel module. +

+ +Alternatively you can output your audio through a native OSS or Alsa +device, and then just use your regular mixer controls. Think of the +the em8300 audio out as what it really is, a line out. Which is perfect +for hooking up to stereo equipment. + +

+ +
Question: +
I get unresolved symbols when running "make install" or loading modules, what's wrong? +
Answer: +
+First thing's first. The kernel source you are compiling against must match +your running kernel. i.e. if you're running say RedHat-2.4.18-14 you +must point the Makefile for the kernel modules at the correct source tree +for your "running kernel". You can verify that your running kernel and +sources match by typing "uname -a" and looking at the Makefile in the +root directory of the kernel source.

+ +e.g. output from uname

+ +root@barney# uname -a
+Linux barney 2.4.18-14custom #1 Wed Sep 4 13:35:50 EDT 2002 i686 i686 i386 GNU/Linux + +

+Excerpt from Makefile in /usr/src/linux-2.4 +

+ +VERSION = 2
+PATCHLEVEL = 4
+SUBLEVEL = 18
+EXTRAVERSION = -14custom
+ +

+See these match so it should be safe to compile kernel modules against +this tree. You really need to compile your own kernel tree, and boot it. +This establishes that a) the kernel source you have runs, b) creates +all the dependency files and links that em8300 uses to compile itself +correctly. Think of it as a pre-requisite to getting em8300 running. +

+Before compiling a "vendor" kernel it is recommended you type: +make mrproper this will clean up any lingering files +from previous compilations. If you have your own .config file you +will need to back it up before doing this otherwise it is gone +forever and you have to set it up again. +

+Vendor kernels are typically set up correctly for em8300, i.e. they +have I2C, I2C-bit-banging and OSS Sound support enabled. You can +usually short cut the whole process and get the default configuration by typing +make oldconfig. If you download a "Marcelo/Linus" kernel you will +need to configure both these options in using something like make +menuconfig + +

+For more in-depth discussion on how to compile a linux kernel check +out the +Kernel HOW-TO. +

+ +
Question: +
My kernel source is not in /usr/src/linux, how can I get the darned thing to compile? +
Answer: +
Edit the KERNEL_LOCATION line in the Makefile. This must be the source directory for the kernel +you are currently running, not the version that shipped with your distribution (which you should +keep in /usr/src/linux for other reasons). Also, you must have run make config and make dep in the +kernel tree before compiling the driver kernel modules. +

+ +
Question: +
Microcode upload to /dev/em8300-1 failed. What does that mean? +
Answer: +
This error message is normal. /dev/em8300-1, /dev/em8300-2, and /dev/em8300-3 are used for multi card support only. If you don't have more than one dxr3 don't worry about it. +

+ +
Question: +
Does this actually work for anyone? Where can I find their results? +
Answer: +
Yes. Unfortunately Patryk Laurent's dxr3 users database domain appears to be down. We'll update this link if things change. +

+ +
Question: +
+Can I use my DXR3/H+ to watch movies other than DVDs or MPEG1/2? Is this accelerated? +
Answer: +
+Yes, you will be able to play DivX and other supported video formats on your card as well. Though +this has to happen through an MPEG1 filter which means it needs lots of CPU power, you should have +at least a 400MHz CPU or preferably faster.

+The em8300 cannot decode anything other than MPEG1/2 in hardware so this will never happen in an +accelerated form. If that is what you want, look for another card. What it can and will do is to +handle postprocessing for you, so the output will look alot nicer than it would do if you play it +on your monitor without any postprocessing enabled. And, this is a real cheap way of getting a +tv-out for watching movies.
+For further information regardning this please refer to the DXR3 howto +or MPlayer manual. +

+ +
Question: +
+Will the driver ever become part of the official Linux kernel or will +I have to download and compile this thing separately for the rest of +my life? + +
Answer: +
+Development of a new driver in the official Linux kernel tree is +difficult because Linus doesn't like to apply lots of little patches; +he would rather apply fewer larger patches to revise an already working +driver. So, once we get this thing stable and working with the known +revisions of the cards, we may seek to include the kernel portion of +this driver in the official kernel source tree. + +

+ +
Question: +
When I cat a .mpg file to /dev/em8300_mv-* a bunch of garbage appears on the screen. Whats wrong? +
Answer: +
+Only mpeg video can be sent to /dev/em8300_mv-*. If an mpeg system file, +which is both mpeg video and audio, is sent to the device, garbage like +that will show up on the screen. First separate the mpeg system into +separate video and audio files, then send those to the appropriate device. +See the Howto. + +

+ +
Question: +
Only two microcode files are extracted from my driver file. What gives? +
Answer: +
+Some revisions of the driver (seems like those shipped with boards with +a bt865) only came with two microcode files. Just use one of these two +and the card should work correctly. You can also download the latest +version of the driver from either Creative Labs or Sigma Designs and +use the microcode shipped with those drivers instead. +

+Update: (12/06/2002) This question is somewhat obsolete +now as the latest driver, 0.13 at this time, comes with a microcode file. + +

+ +
Question: +
How can I uncompress rmquasar.vx_ or enc2dev.vx_? +
Answer: +
A utility written by Paul Laufer called msexpand.pl is included in the em8300/scripts directory +that will uncompress microsoft compressed files. Just run it without any arguments to get the usage +information. See the Howto. +

+Update: (12/06/2002) See the previous question as to why you don't need to do this anymore. + +

+ +
Question: +
I left a message in the Sourceforge project site forums and nobody has answered! +
Answer: +
In general, use the mailing list. Unfortunately, at this point the Sourceforge project forums +are not visited very often by developers. See the Howto +

+ +
Question: +
The video is all green! How can I fix it? +
Answer: +
Check to make sure you are passing the correct module options to the em8300.o and adv717x.o +kernel modules. See the Howto for further information about these options. In +the future detection of these settings should be automated. +

+ +
Question: +
The tv output looks like a scrambled cable-channel, what's wrong? +
Answer: +
+There are a couple of possibilities. Firstly check that you've configured your Dxr3 for the correct TV standard. PAL in Europe and parts of South America, NTSC in the US and Japan and SECAM in France or Russia. SECAM is not supported. +

+Secondly, if you are using an SVHS/S-Video to Composite converter cable, +make sure the SVHS connector has 7 pins and not 4. Most video cards +are delivered with 4-pin SVHS->Composite converters because they use +only 2 outputs for video (Luminance and Chrominance). But the DXR3/H+ +is a very high quality card that uses 3 outputs (Luminance, and 2 +Chrominance outputs) which also requires that you use a converter cable +that recognizes this. If you can't find one, the solution is to buy an +SVHS cable and a scart contact which accepts an SVHS input. + +

+If your TV has SVHS inputs you can also modify a regular SVHS cable by +removing the plastic leg on one end of the cable. Only do this if you +know what you are doing as it is not reversable and basically removes +the key allowing you to try plugging it in upside down. However it +works quite well and lets you use a high quality cable rather than the +cheap one the DXR3 comes with. + +

+ +
Question: +
The video is only on one half of my screen! What's wrong? +
Answer: +
Check to make sure you are passing the correct module options to the em8300.o and adv717x.o +kernel modules. See the Howto for further information about these options.In +the future detection of these settings should be automated. +

+ +
Question: +
I can only play low bit rate mpeg videos, higher bit rate streams lock up the card. What could +be the problem? +
Answer: +
+Try using microcode from a newer driver version or one of the +other microcode files that were extracted from your rmquasar.vxd or +enc2dev.vxd. Some microcode files seem only to work with some versions +of the card.

+ +Update: (12/05/2002) Try downloading the latest version +of the driver. It includes a universal microcode as part of the source. + +

+ +
Question: +
When I load the microcode, my monitor starts making funny noises! +
Answer: +
Remove the passthrough cable and connect your monitor to the video card directly. VGA overlay +and passthrough are not working on some revisions of the card. More reverse engineering is much +needed. If you own one of these cards you currently have to watch your DVDs using the TV out +connector. +

+ +
Question: +
When I load the microcode, my monitor screen goes blank! +
Answer: +
Some cards disable the passthrough when the microcode is uploaded. +Use the 'activate_loopback' module parameter to fix this. However, you may +not be able to use the tv out connector with activate_loopback. If you want to +use tvout you'll need to disconnect the passthrough cable for now. +See the Howto. +

+ + +
Question +
What is libdxr3? +
Answer +
libdxr3 was a library that served as an interface between client programs +like Xine and OMS and the kernel modules. The original idea was to provide a +reusable library and avoid code duplication in client programs, but the +library was never quite finished and its use never really took off, so it was +removed from the em8300 distribution as of version 0.15.1 after being +unmaintained and unused for a few years. In case someone's interested in +finishing and maintaining it, the code can still be resurrected from CVS. +

+ +
Question: +
Can I help with the project? +
Answer: +
Of course! We need people to help write better documentation, reverse engineer the windows +driver, implement new features in the Linux driver, and better integrate the driver into the DVD +player software. +

+ +
+ + + 		  
+ + SourceForge Logo +   
 
+ +
dxr3-devel mailing list
+ + +Last modified: Sun Nov 6 11:01:15 EET 2005 + + + --- em8300-0.18.0.orig/debian/local/em8300-mc_up.sgml +++ em8300-0.18.0/debian/local/em8300-mc_up.sgml @@ -0,0 +1,115 @@ + manpage.1'. You may view + the manual page with: `docbook-to-man manpage.sgml | nroff -man | + less'. A typical entry in a Makefile or Makefile.am is: + +manpage.1: manpage.sgml + docbook-to-man $< > $@ + --> + + + Michael"> + Moerz"> + + Sep 17, 2001"> + + 8"> + mikem@debian.org"> + + EM8300"> + + + Debian GNU/Linux"> + GNU"> +]> + + + +
+ &dhemail; +
+ + &dhfirstname; + &dhsurname; + + + 2001 + &dhusername; + + &dhdate; + + + &dhucpackage; + + &dhsection; + + + &dhpackage; + + tool for uploading microcode to the em8300 chip + + + + &dhpackage; + + microcodefile + + + + + DESCRIPTION + + This manual page documents briefly the + &dhpackage; command. + + + This manual page was written for the &debian; distribution + because the original program does not have a manual page. + + + &dhpackage; is a program that uploads + microcode to the em8300 chip(s). Up to 4 cards are supported. + Currently they will all utilize the same microcode, so all cards + will have to be from the same vendor. + + + + + SEE ALSO + + em8300-dhc (1), em8300-mc_ex (8), em8300-mc_info (8). + + + + AUTHOR + + This manual page was written by &dhusername; &dhemail; for + the &debian; system (but may be used by others). Permission is + granted to copy, distribute and/or modify this document under + the terms of the GNU Free Documentation + License, Version 1.1 or any later version published by the Free + Software Foundation; with no Invariant Sections, no Front-Cover + Texts and no Back-Cover Texts. + + + + + --- em8300-0.18.0.orig/debian/local/autocal.1 +++ em8300-0.18.0/debian/local/autocal.1 @@ -0,0 +1,104 @@ +.\" This -*- nroff -*- file has been generated from +.\" DocBook SGML with docbook-to-man on Debian GNU/Linux. +...\" +...\" transcript compatibility for postscript use. +...\" +...\" synopsis: .P! +...\" +.de P! +\\&. +.fl \" force out current output buffer +\\!%PB +\\!/showpage{}def +...\" the following is from Ken Flowers -- it prevents dictionary overflows +\\!/tempdict 200 dict def tempdict begin +.fl \" prolog +.sy cat \\$1\" bring in postscript file +...\" the following line matches the tempdict above +\\!end % tempdict % +\\!PE +\\!. +.sp \\$2u \" move below the image +.. +.de pF +.ie \\*(f1 .ds f1 \\n(.f +.el .ie \\*(f2 .ds f2 \\n(.f +.el .ie \\*(f3 .ds f3 \\n(.f +.el .ie \\*(f4 .ds f4 \\n(.f +.el .tm ? font overflow +.ft \\$1 +.. +.de fP +.ie !\\*(f4 \{\ +. ft \\*(f4 +. ds f4\" +' br \} +.el .ie !\\*(f3 \{\ +. ft \\*(f3 +. ds f3\" +' br \} +.el .ie !\\*(f2 \{\ +. ft \\*(f2 +. ds f2\" +' br \} +.el .ie !\\*(f1 \{\ +. ft \\*(f1 +. ds f1\" +' br \} +.el .tm ? font underflow +.. +.ds f1\" +.ds f2\" +.ds f3\" +.ds f4\" +'\" t +.ta 8n 16n 24n 32n 40n 48n 56n 64n 72n +.TH "EM8300" "1" +.SH "NAME" +autocal and dxr3view \(em tools for adjusting various overlay values +.SH "SYNOPSIS" +.PP +\fBautocal and dxr3view\fP +.SH "DESCRIPTION" +.PP +This manual page documents briefly the +\fBautocal and dxr3view\fP commands. + +.PP +This manual page was written for the \fBDebian GNU/Linux\fP distribution +because the original program does not have a manual page. + +.PP +\fBautocal and dxr3view\fP are program that can be used to +fine tune the size, shape, and appearance of the overlay to a certain +extent. + +.PP +First, run autocal. This will make the screen flash for a second. This +has to be done every time the microcode is reloaded, which means that +you must load Xine or OMS before running autocal. Yeah, I know its silly. +Should be fixed in the future. Then you have to run dxr3view. This will +bring up a rectangular window with the overlay window on top. It should +look akin to the windows overlay. Now, you should be able to press play +in Xine or OMS and watch your MPEG. + +.PP +The control window in dxr3view can be +used to fine tune the size, shape, and appearance of the overlay to a +certain extent. Also, if you press 't' while the mouse is over the +dxr3view window, a menu with several options, including fullscreen, will +appear. + +.SH "SEE ALSO" +.PP +em8300-mc_upload (8), em8300-mc_extract (8), em8300-dhc (8). +.SH "AUTHOR" +.PP +This manual page was written by Michael Moerz mikem@debian.org for +the \fBDebian GNU/Linux\fP system (but may be used by others). Permission is +granted to copy, distribute and/or modify this document under +the terms of the GNU Free Documentation +License, Version 1.1 or any later version published by the Free +Software Foundation; with no Invariant Sections, no Front-Cover +Texts and no Back-Cover Texts. +...\" created by instant / docbook-to-man, Sun 09 Feb 2003, 19:09 --- em8300-0.18.0.orig/debian/local/em8300-mc_ex.1 +++ em8300-0.18.0/debian/local/em8300-mc_ex.1 @@ -0,0 +1,101 @@ +...\" $Header: /aolnet/dev/src/CVS/sgml/docbook-to-man/cmd/docbook-to-man.sh,v 1.1.1.1 1998/11/13 21:31:59 db3l Exp $ +...\" +...\" transcript compatibility for postscript use. +...\" +...\" synopsis: .P! +...\" +.de P! +.fl +\!!1 setgray +.fl +\\&.\" +.fl +\!!0 setgray +.fl \" force out current output buffer +\!!save /psv exch def currentpoint translate 0 0 moveto +\!!/showpage{}def +.fl \" prolog +.sy sed -e 's/^/!/' \\$1\" bring in postscript file +\!!psv restore +. +.de pF +.ie \\*(f1 .ds f1 \\n(.f +.el .ie \\*(f2 .ds f2 \\n(.f +.el .ie \\*(f3 .ds f3 \\n(.f +.el .ie \\*(f4 .ds f4 \\n(.f +.el .tm ? font overflow +.ft \\$1 +.. +.de fP +.ie !\\*(f4 \{\ +. ft \\*(f4 +. ds f4\" +' br \} +.el .ie !\\*(f3 \{\ +. ft \\*(f3 +. ds f3\" +' br \} +.el .ie !\\*(f2 \{\ +. ft \\*(f2 +. ds f2\" +' br \} +.el .ie !\\*(f1 \{\ +. ft \\*(f1 +. ds f1\" +' br \} +.el .tm ? font underflow +.. +.ds f1\" +.ds f2\" +.ds f3\" +.ds f4\" +'\" t +.ta 8n 16n 24n 32n 40n 48n 56n 64n 72n +.TH "EM8300" "1" +.SH "NAME" +em8300-mc_ex \(em for extracting microcodes from vxds +.SH "SYNOPSIS" +.PP +\fBem8300-mc_ex\fR [\fIFILE\fR] [\fB\fINAMEBASE\fR\fP] +.SH "DESCRIPTION" +.PP +This manual page documents briefly the +\fBem8300-mc_ex\fR command. + +.PP +This manual page was written for the \fBDebian GNU/Linux\fP distribution +because the original program does not have a manual page. + +.PP +\fBem8300-mc_ex\fR is a program that is for +extracting the microcode from windows vxds. After running this +program two or three microcode files will be written to the +current directory, the number depending on the driver you have. +The different microcode versions seem to be for different +revisions of the cards. Currently, the only way to determine +which microcode is correct for your card is to try them all +and pick the one that works the best. Do not be alarmed if some +of them do not work at all. + +.SH "OPTIONS" +.IP "\fBFILE\fP " 10 +refers to the VXD file which comes with the Windows drivers +and is found in the Windows\\System folder. The file is usually called +rmquasar.vxd (H+) or enc2dev.vxd (Creative Labs). +.IP "\fBNAMEBASE\fP " 10 +is the prefix of the saved microcode files. +.SH "SEE ALSO" +.PP +em8300-dhc (1), em8300setup (1). +.SH "AUTHOR" +.PP +This manual page was written by Michael Moerz + for the \fBDebian GNU/Linux\fP system (but may be used by +others). It was updated by Nicolas Boullis +. Permission is granted to copy, +distribute and/or modify this document under the terms of the +GNU Free Documentation License, Version 1.1 +or any later version published by the Free Software Foundation; +with no Invariant Sections, no Front-Cover Texts and no +Back-Cover Texts. +...\" created by instant / docbook-to-man, Sun 19 Oct 2003, 20:36 --- em8300-0.18.0.orig/debian/local/em8300-source +++ em8300-0.18.0/debian/local/em8300-source @@ -0,0 +1,2 @@ +EM8300_VIDEOMODE_DEFAULT=EM8300_VIDEOMODE_PAL +EM8300_AUDIOMODE_DEFAULT=EM8300_AUDIOMODE_ANALOG --- em8300-0.18.0.orig/debian/local/em8300-mc_info.sgml +++ em8300-0.18.0/debian/local/em8300-mc_info.sgml @@ -0,0 +1,134 @@ + manpage.1'. You may view + the manual page with: `docbook-to-man manpage.sgml | nroff -man | + less'. A typical entry in a Makefile or Makefile.am is: + +manpage.1: manpage.sgml + docbook-to-man $< > $@ + --> + + + Michael"> + Moerz"> + + Sep 21, 2001"> + + 8"> + mikem@debian.org"> + + EM8300"> + + + Debian GNU/Linux"> + GNU"> +]> + + + +
+ &dhemail; +
+ + &dhfirstname; + &dhsurname; + + + 2001 + &dhusername; + + &dhdate; + + + &dhucpackage; + + &dhsection; + + + &dhpackage; + + for getting information about microcodes within vxds + + + + &dhpackage; + + FILE + + + + + DESCRIPTION + + This manual page documents briefly the + &dhpackage; command. + + + This manual page was written for the &debian; distribution +because the original program does not have a manual page. + + + &dhpackage; is a program that is for + getting some information about the microcode within windows + vxds. It will only work for rmquasar.vxd (H+) or enc2dev.vxd + (Creative Labs). After running this program several informational + tags are printed. + Normally you won't need this tool at all, but in the case that + something goes wrong with em8300-mc_ex + you will be able to verify that the microcodes are found. + + + + + OPTIONS + + + + + + + refers to the VXD file which comes with the Windows drivers +and is found in the Windows\System folder. The file is usually called +rmquasar.vxd (H+) or enc2dev.vxd (Creative Labs). + + + + + + SEE ALSO + + em8300-dhc (1), em8300-mc_up (8), em8300-mc_ex (8). + + + + AUTHOR + + This manual page was written by &dhusername; &dhemail; for + the &debian; system (but may be used by others). Permission is + granted to copy, distribute and/or modify this document under + the terms of the GNU Free Documentation + License, Version 1.1 or any later version published by the Free + Software Foundation; with no Invariant Sections, no Front-Cover + Texts and no Back-Cover Texts. + + + + + --- em8300-0.18.0.orig/debian/local/em8300-dhc.1 +++ em8300-0.18.0/debian/local/em8300-dhc.1 @@ -0,0 +1,90 @@ +.\" This -*- nroff -*- file has been generated from +.\" DocBook SGML with docbook-to-man on Debian GNU/Linux. +...\" +...\" transcript compatibility for postscript use. +...\" +...\" synopsis: .P! +...\" +.de P! +\\&. +.fl \" force out current output buffer +\\!%PB +\\!/showpage{}def +...\" the following is from Ken Flowers -- it prevents dictionary overflows +\\!/tempdict 200 dict def tempdict begin +.fl \" prolog +.sy cat \\$1\" bring in postscript file +...\" the following line matches the tempdict above +\\!end % tempdict % +\\!PE +\\!. +.sp \\$2u \" move below the image +.. +.de pF +.ie \\*(f1 .ds f1 \\n(.f +.el .ie \\*(f2 .ds f2 \\n(.f +.el .ie \\*(f3 .ds f3 \\n(.f +.el .ie \\*(f4 .ds f4 \\n(.f +.el .tm ? font overflow +.ft \\$1 +.. +.de fP +.ie !\\*(f4 \{\ +. ft \\*(f4 +. ds f4\" +' br \} +.el .ie !\\*(f3 \{\ +. ft \\*(f3 +. ds f3\" +' br \} +.el .ie !\\*(f2 \{\ +. ft \\*(f2 +. ds f2\" +' br \} +.el .ie !\\*(f1 \{\ +. ft \\*(f1 +. ds f1\" +' br \} +.el .tm ? font underflow +.. +.ds f1\" +.ds f2\" +.ds f3\" +.ds f4\" +'\" t +.ta 8n 16n 24n 32n 40n 48n 56n 64n 72n +.TH "EM8300" "1" +.SH "NAME" +em8300-dhc \(em Gtk tool for adjusting various values +.SH "SYNOPSIS" +.PP +\fBem8300-dhc\fP +.SH "DESCRIPTION" +.PP +This manual page documents briefly the +\fBem8300-dhc\fP + +.PP +This manual page was written for the \fBDebian GNU/Linux\fP distribution +because the original program does not have a manual page. + +.PP +\fBem8300-dhc\fP is a program that can be used to +adjust the brightness, contrast, saturation, aspect ration, +TV output standard (PAL, NTSC, and PAL 60), turn on and off +the subpicture (subtitles, etc.), and change between analog +and spdif audio outputs. + +.SH "SEE ALSO" +.PP +em8300-mc_upload (8), em8300-mc_extract (8). +.SH "AUTHOR" +.PP +This manual page was written by Michael Moerz mikem@debian.org for +the \fBDebian GNU/Linux\fP system (but may be used by others). Permission is +granted to copy, distribute and/or modify this document under +the terms of the GNU Free Documentation +License, Version 1.1 or any later version published by the Free +Software Foundation; with no Invariant Sections, no Front-Cover +Texts and no Back-Cover Texts. +...\" created by instant / docbook-to-man, Sun 09 Feb 2003, 19:09 --- em8300-0.18.0.orig/debian/local/em8300-dhc.sgml +++ em8300-0.18.0/debian/local/em8300-dhc.sgml @@ -0,0 +1,114 @@ + manpage.1'. You may view + the manual page with: `docbook-to-man manpage.sgml | nroff -man | + less'. A typical entry in a Makefile or Makefile.am is: + +manpage.1: manpage.sgml + docbook-to-man $< > $@ + --> + + + Michael"> + Moerz"> + + Sep 16, 2001"> + + 1"> + mikem@debian.org"> + + EM8300"> + + + Debian GNU/Linux"> + GNU"> +]> + + + +
+ &dhemail; +
+ + &dhfirstname; + &dhsurname; + + + 2001 + &dhusername; + + &dhdate; + + + &dhucpackage; + + &dhsection; + + + &dhpackage; + + Gtk tool for adjusting various values + + + + &dhpackage; + + + + + DESCRIPTION + + This manual page documents briefly the + &dhpackage; + + + This manual page was written for the &debian; distribution + because the original program does not have a manual page. + + + &dhpackage; is a program that can be used to + adjust the brightness, contrast, saturation, aspect ration, + TV output standard (PAL, NTSC, and PAL 60), turn on and off + the subpicture (subtitles, etc.), and change between analog + and spdif audio outputs. + + + + + SEE ALSO + + em8300-mc_upload (8), em8300-mc_extract (8). + + + + AUTHOR + + This manual page was written by &dhusername; &dhemail; for + the &debian; system (but may be used by others). Permission is + granted to copy, distribute and/or modify this document under + the terms of the GNU Free Documentation + License, Version 1.1 or any later version published by the Free + Software Foundation; with no Invariant Sections, no Front-Cover + Texts and no Back-Cover Texts. + + + + + --- em8300-0.18.0.orig/debian/local/autocal.sgml +++ em8300-0.18.0/debian/local/autocal.sgml @@ -0,0 +1,128 @@ + manpage.1'. You may view + the manual page with: `docbook-to-man manpage.sgml | nroff -man | + less'. A typical entry in a Makefile or Makefile.am is: + +manpage.1: manpage.sgml + docbook-to-man $< > $@ + --> + + + Michael"> + Moerz"> + + Oct 16, 2001"> + + 1"> + mikem@debian.org"> + + EM8300"> + + + Debian GNU/Linux"> + GNU"> +]> + + + +
+ &dhemail; +
+ + &dhfirstname; + &dhsurname; + + + 2001 + &dhusername; + + &dhdate; + + + &dhucpackage; + + &dhsection; + + + &dhpackage; + + tools for adjusting various overlay values + + + + &dhpackage; + + + + + DESCRIPTION + + This manual page documents briefly the + &dhpackage; commands. + + + This manual page was written for the &debian; distribution + because the original program does not have a manual page. + + + &dhpackage; are program that can be used to + fine tune the size, shape, and appearance of the overlay to a certain + extent. + + + First, run autocal. This will make the screen flash for a second. This + has to be done every time the microcode is reloaded, which means that + you must load Xine or OMS before running autocal. Yeah, I know its silly. + Should be fixed in the future. Then you have to run dxr3view. This will + bring up a rectangular window with the overlay window on top. It should + look akin to the windows overlay. Now, you should be able to press play + in Xine or OMS and watch your MPEG. + + + The control window in dxr3view can be + used to fine tune the size, shape, and appearance of the overlay to a + certain extent. Also, if you press 't' while the mouse is over the + dxr3view window, a menu with several options, including fullscreen, will + appear. + + + + + SEE ALSO + + em8300-mc_upload (8), em8300-mc_extract (8), em8300-dhc (8). + + + + AUTHOR + + This manual page was written by &dhusername; &dhemail; for + the &debian; system (but may be used by others). Permission is + granted to copy, distribute and/or modify this document under + the terms of the GNU Free Documentation + License, Version 1.1 or any later version published by the Free + Software Foundation; with no Invariant Sections, no Front-Cover + Texts and no Back-Cover Texts. + + + + + --- em8300-0.18.0.orig/debian/local/em8300-mc_ex.sgml +++ em8300-0.18.0/debian/local/em8300-mc_ex.sgml @@ -0,0 +1,146 @@ + manpage.1'. You may view + the manual page with: `docbook-to-man manpage.sgml | nroff -man | + less'. A typical entry in a Makefile or Makefile.am is: + +manpage.1: manpage.sgml + docbook-to-man $< > $@ + --> + + + Michael"> + Moerz"> + + Oct 19, 2003"> + + 1"> + mikem@debian.org"> + + EM8300"> + + + Debian GNU/Linux"> + GNU"> +]> + + + +
+ &dhemail; +
+ + &dhfirstname; + &dhsurname; + + + 2001 + &dhusername; + + &dhdate; + + + &dhucpackage; + + &dhsection; + + + &dhpackage; + + for extracting microcodes from vxds + + + + &dhpackage; + + FILE + + + + + + + DESCRIPTION + + This manual page documents briefly the + &dhpackage; command. + + + This manual page was written for the &debian; distribution +because the original program does not have a manual page. + + + &dhpackage; is a program that is for + extracting the microcode from windows vxds. After running this + program two or three microcode files will be written to the + current directory, the number depending on the driver you have. + The different microcode versions seem to be for different + revisions of the cards. Currently, the only way to determine + which microcode is correct for your card is to try them all + and pick the one that works the best. Do not be alarmed if some + of them do not work at all. + + + + + OPTIONS + + + + + + + refers to the VXD file which comes with the Windows drivers +and is found in the Windows\\System folder. The file is usually called +rmquasar.vxd (H+) or enc2dev.vxd (Creative Labs). + + + + + + + is the prefix of the saved microcode files. + + + + + + SEE ALSO + + em8300-dhc (1), em8300setup (1). + + + + AUTHOR + + This manual page was written by &dhusername; + <&dhemail;> for the &debian; system (but may be used by + others). It was updated by Nicolas Boullis + <nboullis@debian.org>. Permission is granted to copy, + distribute and/or modify this document under the terms of the + GNU Free Documentation License, Version 1.1 + or any later version published by the Free Software Foundation; + with no Invariant Sections, no Front-Cover Texts and no + Back-Cover Texts. + + + + + --- em8300-0.18.0.orig/debian/local/devfs.conf +++ em8300-0.18.0/debian/local/devfs.conf @@ -0,0 +1,5 @@ +# device permissions for em8300 video devices. +REGISTER ^em8300* PERMISSIONS root.video 0660 + +REGISTER ^(em8300.*)-0$ CFUNCTION GLOBAL mksymlink $devname \1 +UNREGISTER ^(em8300.*)-0$ CFUNCTION GLOBAL unlink \1 --- em8300-0.18.0.orig/debian/local/examples/both +++ em8300-0.18.0/debian/local/examples/both @@ -0,0 +1,5 @@ +i2c_algo_bit +eeprom +adv717x +bt865 +em8300 --- em8300-0.18.0.orig/debian/local/examples/adv717x +++ em8300-0.18.0/debian/local/examples/adv717x @@ -0,0 +1,4 @@ +i2c_algo_bit +eeprom +adv717x +em8300 --- em8300-0.18.0.orig/debian/local/examples/bt865 +++ em8300-0.18.0/debian/local/examples/bt865 @@ -0,0 +1,4 @@ +i2c_algo_bit +eeprom +bt865 +em8300 --- em8300-0.18.0.orig/debian/scripts/dh_docbook +++ em8300-0.18.0/debian/scripts/dh_docbook @@ -0,0 +1,47 @@ +#!/usr/bin/perl + +$debiandir = 'debian'; + +if ( -d 'debian/local' ) { + $dir = 'debian/local'; +} else { + $dir = 'debian'; +} + +$needclean = 0; +$needlist = 0; +$needdeps = 0; +if (@ARGV) { + $temp = shift; + if ($temp eq "clean") { $needclean = 1; } + elsif ($temp eq "makedeps") { $needlist = 1; } + elsif ($temp eq "gendeps") { $needdeps = 1; } +} + +opendir( DIR, $dir ); +while( $file = readdir( DIR ) ) { + if ( $file =~ m/\.sgml$/ ) { + open( FILE, "<$dir/$file" ); + $man_section = -1; + while ( ($man_section == -1) && ($line = ) ) { + if ( $line =~ m/manvolnum.(.)/ ) { + $man_section = $1; + } + } + close( FILE ); + if ( $man_section > -1 ) { + $newfile=$file; + $newfile=~s/\.sgml/\.$man_section/; + if ( $needclean ) { + system( "rm -f $debiandir/$newfile" ); + } elsif ( $needlist ) { + print( "$debiandir/$newfile " ); + } elsif ( $needdeps ) { + print( "$dir/$file " ); + } else { + system( "docbook-to-man $dir/$file > debian/$newfile" ); + } + } + } +} +closedir( DIR ); --- em8300-0.18.0.orig/debian/scripts/dh_modulecontrol +++ em8300-0.18.0/debian/scripts/dh_modulecontrol @@ -0,0 +1,98 @@ +#!/usr/bin/perl + +$debdir = 'debian'; + +# parameter +$clean = grep( /^--clean$/, @ARGV ); +$packagename = grep( /^-p.*$/, @ARGV ); +$module = grep( /^--module$/, @ARGV ); + +$packagename = '' if ($packagename == 0); + +$source = ''; +open( FILE, "<$debdir/control" ); +while( defined( $line = ) && ( $source eq '' ) ) { + if ( $line =~ m/^Source:\s+(.*)$/ ) { + $source = $1; + } +} +close( FILE ); + +if ( $module ) { + # read kvers, kversdeb and kstem + $kvers = ''; + $kversdeb = ''; + $kstem = ''; + open( FILE, "<$debdir/substvars" ); + while( defined( $line = ) && ( $kvers eq '' || $kversdeb eq '' || $kstem eq '' ) ) { + $kvers= $1 if ( $line =~ m/^kvers=(.*)$/ ); + $kversdeb= $1 if ( $line =~ m/^kversdeb=(.*)$/ ); + $kstem= $1 if ( $line =~ m/^kstem=(.*)$/ ); + } + close( FILE ); + # and read module package name (if $packagename is not set) + open( FILE, "<$debdir/control" ); + while( defined( $line = ) && ($packagename eq '') ) { + if ( $line =~ m/^Package: ([a-zA-Z0-9\_]+-modules-\$\{kvers\})/ ) { + $packagename = $1; + $packagename =~ s/\$\{kvers\}/$kvers/; + } + } + if ( $clean ) { + system( "rm", "-f", "$packagename.control" ); + exit( 0 ); + } + # create package specific control file + close( FILE ); + open( FILE, "<$debdir/control" ); + open( NFILE, ">$debdir/$packagename.control" ); + while( defined( $line = ) ) { + $line =~ s/\$\{kvers\}/$kvers/; + $line =~ s/\$\{kversdeb\}/$kversdeb/; + $line =~ s/\$\{kstem\}/$kstem/; + print( NFILE $line ); + } + close( NFILE ); + close( FILE ); + + print( "packagename: $packagename, kvers: $kvers, kversdeb: $kversdeb, kstem: $kstem\n" ); + + exit( 0 ); + +} + +$name="$source"; +#print( "$name\n$dir\n" ); +opendir( DIR, $debdir ); +while ( $file = readdir( DIR ) ) { + if ( $file =~ m/^(.*)\.modulecontrol$/ ) { + $package = $1; +# print( "package: $package\n" ); + if ( ! -d "$debdir/$package/usr/src/modules/$name/debian" ) { + system( "install", "-d", + "$debdir/$package/usr/src/modules/$name/debian/scripts" ); + } + if ( ! -e "$debdir/$package/usr/src/modules/$name/debian/scripts/". + "dh_modulecontrol" ) { + system( "cp", "$debdir/scripts/dh_modulecontrol", + "$debdir/$package/usr/src/modules/$name/debian/scripts/" ); + } + open( OUT, ">$debdir/$package/usr/src/modules/$name/debian/control") || + die "couldn't open $debdir/$package/usr/src/modules/$name/debian/". + "control"; + open( FILE, "<$debdir/control" ) || + die "couldn't open $debdir/control"; + while( defined($line = ) && ( $line !~ m/^\s/ ) ) { + print( OUT $line ) + if ( $line !~ m/Depends/ || $ENV{'DH_COMPAT'} < 2 ); + } + close( FILE ); + print( OUT "\n" ); + open( FILE, "<$debdir/$package.modulecontrol" ); + while( ) { + print( OUT $_ ); + } + close( FILE ); + } +} +closedir( DIR );