Important: Before you start, be sure you go through the previous chapter: YOCTO uBoot: How to add support for a custom board (or OpenRex)
Be sure you start with empty meta-openrex (no patches inside). Run this to get clean starting source code. Run this: We need to do a small correction for github. Delete the old .git: and edit .gitignore Go on the end of the file and add following line (a folder .pc/ is added during applying patches and we dont want to have it in github): We need to upload the original YOCTO Kernel source code to github. Create a new repository and put it there. I normally also create a branch: Change to the branch 'jethro': Very often, there are differences between software versions. Therefore, there are no general instruction how to add custom support into the software. You may need to figure out by yourself what everything has to be changed and added to support a new board. One of the ways how to do it, is to search for files with your reference board name. For example, in our case we look for 'sabresd'. Here are the results: Set the compiler: Try if you can compile linux without any changes:
Trusted Windows (PC) download Streamzap Remote Drivers 3.0.0.0. Virus-free and 100% clean download. Get Streamzap Remote Drivers alternative downloads. They dont list any older driver versions on the streamzap website, but if you copy the URL for the 3.0.0 download and change the numbers from '3.0.0' to '2.9.6' you can still download the older driver. Driver, right-click on the Streamzap systray icon, and choose “Help” from the menu. The xhci can not work correctly. Next is the log: ffs2: version 2.2. (NAND) 漏 2001-2006 Red Hat, Inc. Fuse init (API version 7.22) msgmni has been set to 1999 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) imx-weim 21b8000.weim: Driver regist.
Adding support for a new custom board
Edit: 'arch/arm/boot/dts/Makefile' Find 'imx6q-sabresd' and add: This is how it will look
Edit: 'arch/arm/boot/dts/imx6q-openrex.dts' Replace with Edit: 'arch/arm/boot/dts/imx6qdl-openrex.dtsi' You may noticed that imx6q-openrex.dts calls imx6qdl-sabresd.dtsi. Let's create it for openrex: You may need to have a look also inside 'arch/arm/mach-imx/mach-imx6q.c'. There is something about sabresd, but we don't need to edit it, at least not now.That's it. Try to compile our new custom board: *Note: If you get error 'piggy.lzo Error' just install lzop. Run 'sudo apt-get install lzop'.
The output files are located at: Now the hard part. You will need to go through 'arch/arm/boot/dts/imx6q-openrex.dts' and 'arch/arm/boot/dts/imx6qdl-openrex.dtsi' files and correct them. Advice: After some changes always try to recompile, and check if you have not changed/removed something critical.
How to edit dts / dtsi files?
Go through the files, remove the peripherals you don't need and correct pin assigment. For example: Original Go to our schematic and have a look where CSPI1_MISO is connected. You can see it's GPIO3_IO17. Go to arch/arm/boot/dts/imx6q-pinfunc.h and search for 'GPIO3_IO17'. You will find 'MX6QDL_PAD_EIM_D17__GPIO3_IO17' .. we would like to work this pin in MISO mode, so select 'MX6QDL_PAD_EIM_D17__ECSPI1_MISO' and paste it into dtsi file. It will look then: Do it for all the pins. If you are not sure where the pin from reference board is connected, search through reference schematic. Board releated files File where you can find default configuration: File where you can find pin names: Copy the files to /tftp directory Now, be careful. It is important, that your uBoot environment variables are set correctly. If an important parameter is missing, something may not work (for example ethernet may not work or Linux will freeze at Starting Linux ...).Here is example of uBoot parameters from working uBoot 2014. You may find them useful (they work also with uBoot 2015): In our case, I had to add following parameters to be able to boot Linux: To test our Linux (it will not fully boot up, we do not have file system yet), run: It may look like this: Perfect! Linux booted up, we can upload the changes to github. When you are happy with changes, you can upload the source code to github:
LIRC is a package that allows you to decode and send infra-red signals of many (but not all) commonly used remote controls.
Streamzap Driver
Recent linux kernels makes it possible to use some IR remote controls as regular input devices. Sometimes this makes LIRC redundant. However, LIRC offers more flexibility and functionality and is still the right tool in a lot of scenarios.
The most important part of LIRC is the lircd daemon which decodes IR signals received by the device drivers and provides the information on a socket. It also accepts commands for IR signals to be sent if the hardware supports this.
The user space applications allows you to control your computer with your remote control. You can send X11 events to applications, start programs and much more on just one button press. The possible applications are obvious: Infra-red mouse, remote control for your TV tuner card or CD-ROM, shutdown by remote, program your VCR and/or satellite tuner with your computer, etc. Using lirc on Raspberry Pie is quite popular these days.
There are some config files for remote controls at the remotes database. This is about 2500 devices and counting. These devices should work with the general drivers or (if it lacks timing info) the driver used to create them.
If you can't find your remote control here it does not mean that your remote control is not supported. It's just that there is no config file for it yet. All remote controls that are supported by learning remote controls i.e., almost any, should also work with LIRC.
Besides a remote control you also need a capture device to read the data from the remote. Former versions focussed on home-brew capture hardware connected to the serial or parallel port. Descriptions how to build such hardware can be found here. Current versions of LIRC also support a broad range of other hardware. As a starter, you can use the kernel built-in support for many USB dongles and similar. Besides this LIRC supports basically any conceivable way to capture your data including serial devices, parallel ports, sound input etc. You can see the complete list in the left pane.
Streamzap Driver
- [28-May 2017]
lirc-0.10.0rc1 released.
- [2-Feb 2017]
lirc-0.9.4d released. Drivers terratec sound cards & media devices.
[22-Oct 2016] - [9-Aug 2016]
lirc-0.9.4b released.
- [29-June2016]
lirc-0.9.4a released.
- [22-May-2016]
lirc-0.9.4 released.
- [4-Sep-2015]
lirc-0.9.3 released.
- [9-Dec-2014]
lirc-0.9.2 released.
- [10-Jun-2014]
lirc-0.9.1 released.
- [10-Jun-2014]
LIRC has a new maintainer! Yay!
- [26-Mar-2011]
lirc-0.9.0 released.
- [06-Sep-2010]
lirc-0.8.7 released. After more than 10 years LIRC has a new maintainer. Jarod Wilson is taking over. Good luck for the next 10 years!
- [13-Sep-2009]
lirc-0.8.6 released.
- [21-May-2009]
lirc-0.8.5 released.
- [12-Oct-2008]
lirc-0.8.4 released.
- [04-May-2008]
lirc-0.8.3 released.
- [09-Jun-2007]
lirc-0.8.2 released.
- [07-Jan-2007]
lirc-0.8.1 released.
- [25-Feb-2006]
A new 0.4.4 maintenance release of libirman fixes incompatibilities with gcc 4.0.
- [21-Jan-2006]
lirc-0.8.0 released.
- [14-Aug-2005]
lirc-0.7.2 released.
- [17-Apr-2005]
lirc-0.7.1 released.
- [07-Nov-2004]
lirc-0.7.0 released. In memoriam Manuel Estrada Sainz.
- [04-Apr-2004]
I have made a 0.4.3 maintenance release of libirman. This should fix incompatibilities with 2.6 kernels.
- [12-Jul-2003]
article in c't issue 15/03 features LIRC's UDP driver. Sysnucleus network & wireless cards driver.
- [03-May-2003]
New lirc-xmms-plugin released.
- [01-Feb-2003]
New releases of xirw, xrc and the lirc-xmms-plugin are available.
- [06-Oct-2002]
lirc-0.6.6 released.
- [26-Jan-2002]
lirc-0.6.5 released.
- [23-Jan-2002]
lircrc_config-0.1.0 released.
- [11-Nov-2000]
www.lirc.org online.
- [10-Nov-2000]
The REALmagic remote control that is bundled with Hollywood Plus DVD cards does work with the PixelView RemoteMaster driver. You will just need the proper config file from CVS.
- [19-Oct-2000]
My LIRC article was published in the c't netherlands.
- [18-Sep-2000]
Tonu Raitviir has added support for Chronos Video Shuttle II TV card.
- [26-Aug-2000]
There's a c't article about LIRC.
- [23-Aug-2000]
Hans-Hermann Redenius has contributed a IRdeo device. Receiving of IR signals already works. I will add code for sending as soon as I find some free time.
- [23-Aug-2000]
Konrad Riedel has added support for CARACA
- [10-Aug-2000]
An article about LIRC published in the Linux Magazin.
- [21-Jul-2000]
lirc-0.6.1 released.
- [19-Jun-2000]
New xmms plugin released.
- [02-Apr-2000]
lirc-0.6.0 released.
- [03-Mar-2000]
Milan Pikula has provided a driver for the SIR (serial infrared) mode of IrDA ports available in many notebooks. It's available now through CVS.
- [30-Apr-1999]
LIRC now has a CVS tree at gdev.net!
- [29-Apr-1999]
First test code for Fly Video 98 TV cards available.
- [03-Apr-1999]
A patch to add Avermedia TV98 support to lirc-0.5.5pre8 has been provided by Ryan Gammon.
- [23-Mar-1999]
LIRC X11AMP Plugin by Carl van Schaik.
- [07-Mar-1999]
First test code for Hauppauge remote controls available.
- [03-Mar-1999]
lirc-0.5.4 released. Major homepage update.
- [02-Mar-1999]
There is a Windows port of LIRC available at the WinLIRC Homepage.
- [03-Feb-1999]
Got it! I have the specs for the Hauppauge remote control. :-) Many thanks go to Roger Hardiman for providing the necessary information and Peter Stevenson for finding Roger.
- [31-Jan-1999]
Recently a Tekram IRMate IR-210 fell into my hands. I managed to send IR signals to my satellite receiver using my linux box within 1 hour! Receiving of IR signals was also possible but has some limitations. You can see this as a motivation for you to work on support for IrDA compliant hardware as I don't have the time to do it myself.
lirc-0.9.4c released.
Streamzap Remote Driver
Last modified by Christoph Bartelmus: 26-May-2016