Merge pull request #190 from P33M/rpi-3.6.y

dwc_otg: fix bug in dwc_otg_hcd.c resulting in silent kernel memory corruption
Add config options for netfilter log and more dvb modules
Add more dvb modules
Return error value from bcm2708_setup_state. Thanks notro
spi/spi-bcm2708: respect per-transfer SPI clock speed_hz value

The bcm2708 SPI driver's bcm2708_process_transfer() was ignoring the
per-transfer speed_hz value even when it was provided (it always just
used the spi device's max_speed_hz value).  Now, per-transfer speed_hz
values are respected.

Also added debug print to bcm2708_setup_state() to help keep an eye on
the configured SPI parameters.

Signed-off-by: Kamal Mostafa <kamal@whence.com>
Add hwrng (hardware random number generator) driver
Add HW_RANDOM, BATMAN_ADV and CONFIG_NET_IPGRE
Add raid0 module
Update vchiq to version supporting querying peer version of services. Should be backwards compatible
Use control messages for audio data to fix scratch hang.
Use vchiq versioning to try to handle mismatches kernel.img/start.elf
Default force_bulk to false
Add missing newlines to log messages
Changed wording on logging. Previously, we received errors like this:
mmc0: could read SD Status register (SSR) at the 3th attempt
A more sensible response is now returned.
A typo also fixed in comments.
Merge pull request #219 from technion/rpi-3.6.y

Changed wording on logging.
Fix for low bogomips value reported.
The delay loop was badly aligned and generated extra stalls
dwc_otg: Fix unsafe access of QTD during URB enqueue

In dwc_otg_hcd_urb_enqueue during qtd creation, it was possible that the
transaction could complete almost immediately after the qtd was assigned
to a host channel during URB enqueue, which meant the qtd pointer was no
longer valid having been completed and removed. Usually, this resulted in
an OOPS during URB submission. By predetermining whether transactions
need to be queued or not, this unsafe pointer access is avoided.

This bug was only evident on the Pi model A where a device was attached
that had no periodic endpoints (e.g. USB pendrive or some wlan devices).
dwc_otg: Fix incorrect URB allocation error handling

If the memory allocation for a dwc_otg_urb failed, the kernel would OOPS
because for some reason a member of the *unallocated* struct was set to
zero. Error handling changed to fail correctly.