What have you read so far? Have you checked something simple, like Wikipedia?
The main controller issue with SSDs is that the controller (hardware on the motherboard) should be configured (by setting options in the BIOS) to AHCI mode. By default, these are set to IDE mode, which limits the commands that can be sent to the drive and is there for compatibility with older drives and OSes. AHCI mode enables newer features of the drive, be it HDD or SSD.
Two key features that are enabled are Native Command Queueing, which is relevant to both HDDs and SSDs, and the TRIM command. If you have the controllers in AHCI mode, and are running Win7, the OS can pass the TRIM command to the SSD when files are deleted. Otherwise, the SSD will continue to think that that space is in use. As the SSD loses track of available usable space, it slows down in write performance.
Some people believe that the SSD's built in Garbage Collection will deal with this, some do not.
So. The point of all that was that AHCI mode enables features of HDDs and SSDs that are not available in the default IDE mode.
----------------------------------------------------------
Drivers are software in your OS. These should not be much of an issue, since you should get the most recent ones every time you do an update. With an Intel-based motherboard, you should install the Intel RST drivers during your system build.
--------------------------------
RAID0 is a different issue. The driver/controller is not a bottleneck for RAID any more than it is for two single drives. The potential issues are having an SATA II controller, which is slower than most SSDs, and having a seperate controller card. Some separate controller cards have only one PCI-E lane, which makes their connection to your motherboard slower than a single SATA III connection. Unless you have an add-in controller card, this will not be an issue.
Finally, putting SSDs in RAID disables the TRIM command, leading to eventual gunking up of your SSDs.