Instruction: Given a question and the related document, and generate the answer to the question based on the information provided in the document.

Input:
Question: What did you use for a power supply? If it didn't work out of the box with Rpi then where did you find the drivers?
Document: But, I'm sure they'd respond quickly if other reviews are an indication.Just a note, for people who want to use it with windows 7/8/8.1 64 bit: The touch controller included isn't HID compatible. This means that, without the proper drivers (which I haven't been able to find after weeks of searching), the touch overlay will read as a mouse, rather than true touch input.
Also, there was no need to install a driver on my Win 8.1 desktop, it worked out of the box. It will need to be configured though.Bottom Line:Great display! But SainSmart, please make your drivers available online.
That was an unexpected bonus that was perfect for my needs.The display will automatically turn on once it receives power, and then shut off as a screen-saving measure. I was able to use a USB cable lying around that matched the power connector on the board. So, in short, USB voltage is sufficient. Setup was easy, although it took a bit of figuring out.My one legitimate complaint is that it did not include the remote control listed in the description.
Ordered the screen and controller for a small monitor for extra functions in windows. Did not get to install and play immediately and finally made time this week. System will not power on at all. tried multiple power adapters from 7.5v to 12v. not a click of life at all. Just another 90 bucks in the scrap heap. Be sure to test yours while it is still returnable.
I love this touchscreen, however the first model had a bad touch interface. Luckily SainSmart's customer service is great and after a little troubleshooting they confirmed my interface film was bad and sent me a new one.I was able to get this touchscreen setup on both my windows 8.1 laptop and windows 7 pc, just needed to download the latest eGalax Touch drivers. With the latest drivers this thing rocks.
Came packaged in an envelope. There was bubble wrap around the LCD display. There was a CD included, but no instructions at all. I was able to get it put together pretty easily based on some youtube videos others had posted.I want to use the monitor as a head for a raspberry pi project. I was able to get it up and running, but I need to figure out the PSU and play around with the resolution.
works good.
The default resolution isn't so great although I suspect using the correct river will solve that.installation sheet would be helpful.The touch overlay connector can be connected either way round...
Overall, this was a good buy, but it wasn't without some problems.I purchased this screen so that I could mount it to the front of my MicroATX tower. I'm running windows 8.1 64 bit. The screen arrived promptly, and was adequately packaged. The board automatically set the screen to display at 1920x1080 right off the bat. And, oddly enough, it does not seem to have a 'native,' resolution.
Onscreen display shows it as 720P. I could get by with 640x480.Display seems pretty clear. Not super bright. Build quality is OK. I will post more as I fool around with the thing.
Answer: The drivers are already there for the RPi, at least it was for the B+ (which is the one I have).I had to build the kernel to get the screen to work.  I did that from an Ubuntu VM running 3.13.0-35-generic 32-bit (VMWare Player).This is what I did:Attach the controller to the RPi and check that it sees the screen, you're looking for an eGalax entry:$ lsusbBus 001 Device 005: ID 0eef:0001 D-WAV Scientific Co., Ltd eGalax TouchScreen$ cd ~$ mkdir src$ cd srcGet the kernel sources: $ wget https://github.com/raspberrypi/linux/archive/rpi-3.12.y.tar.gz$ tar -zxvf  rpi-3.12.y.tar.gz$ cd linux-rpi-3.12.yInstall dependencies:$ sudo apt-get install git libncurses5 libncurses5-dev qt4-dev-tools build-essentialInstall toolchain:$ sudo apt-get install gcc-arm-linux-gnueabihfMake sure the source objects are clean:$ make mrproperCreate a folder for the generated kernel:$ mkdir ../kernelGenereate the .config file:$ make O=../kernel/ ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf- bcmrpi_cutdown_defconfigConfigure the kernel:$ make O=../kernel/ ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf- menuconfigNavigate to Device Drivers -> Input Device Support -> Touch Screens and select it. Go to USB Touchscreen Driver select it.  Go to "eGalax, eTurboTouch CT-410/510/700 device support" and select it.  Exit all the way and save the file when prompted.Compile the kernel:$ make O=../kernel/ ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf- -k -j3The -j3 option enables parallel build.  The number should be the number of cores (of the machine where you're compiling) +1.The build took about 10 minutes on my pc.  When the build completes, you will have the new kernel in ../kernel created above.Create the kernel image:$ cd ../$ git clone git://github.com/raspberrypi/tools.git$ cd ~/src/tools/mkimage$ ./imagetool-uncompressed.py ../../kernel/arch/arm/boot/ImageBuild the modules$ cd ../../kernel$ mkdir ../modules$ make modules_install ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf- INSTALL_MOD_PATH=../modules/To replace the kernel, get the latest firmware:$ wget https://github.com/raspberrypi/firmware/archive/next.tar.gz$ tar -zxvf next.tar.gzIn the small partition of the SD card (/boot):- replace the /boot/bootcode.bin in the SD card with ~/src/kernel/firmware-next/boot/bootcode.bin- replace the /boot/kernel.img in the SD card with ~/src/tools/mkimage/kernel.img- replace the /boot/start.elf in the SD card with ~/src/kernel/firmware-next/boot/start.elfIn the big partition of the SD card (/root):- replace the /lib/firmware in the SD card with ~/src/modules/lib/firmware- replace the /lib/modules in the SD card with ~/src/modules/lib/modules- replace the /opt/vc in the SD card with ~/src/kernel/firmware-next/hardfp/opt/vcNow your SD card contains the new image.  Safely eject the SD card, plug the touch controller to your RPi, boot it with the SD card, run startx, and check that you can move the cursor.Once I was in the desktop, my touch input was working but it needed to be calibrated.To calibrate, you need to install an X input calibrator and some dependencies:$ sudo apt-get install libx11-dev libxext-dev libxi-dev x11proto-input-dev$ cd ~$ wget http://github.com/downloads/tias/xinput_calibrator/xinput_calibrator-0.7.5.tar.gz$ tar -zxvf xinput_calibrator-0.7.5.tar.gz$ cd configure$ make$ sudo make install$ xinput_calibratorFollow the instructions on the screen.  After calibration you should see something like this:Calibrating EVDEV driver for "eGalax Inc. USB TouchController" id=8    current calibration values (from XInput): min_x=1938, max_x=114 and min_y=1745, max_y=341Doing dynamic recalibration:    Setting new calibration data: 121, 1917, 317, 1741--> Making the calibration permanent <--  copy the snippet below into '/etc/X11/xorg.conf.d/99-calibration.conf'Section "InputClass"    Identifier    "calibration"    MatchProduct    "eGalax Inc. USB TouchController"    Option    "Calibration"    "121 1917 317 1741"    Option    "SwapAxes"    "1"EndSectionFor Raspbian, you have to create the file:$ sudo nano /usr/share/X11/xorg.conf.d/01-input.confAdd in this file the content above, starting with Section "InputClass" line and save the file.Note: Make sure that you don't have sections like MatchProduct    "eGalax Inc. USB TouchController" in other files from /usr/share/X11/xorg.conf.d/ folder (highest number files are processed last).Now touchscreen should be calibrated and after reboot it will keep the settings.  Yolu can run xinput_calibration again in order to have the pointer to the desired points. You can update the numbers given by the xinput_calibration utility in the usr/share/X11/xorg.conf.d/01-input.conf file in order to have the best calibration at boot.