On Sun, Nov 7, 2010 at 11:36 PM, Felipe Contreras
<felipe.contreras@xxxxxxxxx> wrote:
> The situation of tidspbridge driver on staging has been pretty sad,
> basically, it has never worked. This is a step backwards from the
> previous situation where it was clear which branch to use to get it
> working. Unfortunately, the ARM and OMAP trees haven't made it easy,
> as changes in those trees have broken it even further.
Here's another try, this one has only one patch that needs omap
maintainers to ack.
git://gitorious.org/~felipec/linux-omap/felipec.git fc-dsp-fix-v37-rc1-min
These are the changes since v2.6.37-rc1:
Felipe Contreras (14):
Revert "staging: tidspbridge - update Kconfig to select IOMMU module"
Revert "staging: tidspbridge - remove dmm custom module"
Revert "staging: tidspbridge - deprecate
reserve/unreserve_memory funtions"
Revert "staging: tidspbridge - remove reserved memory clean up"
Revert "staging: tidspbridge: remove dw_dmmu_base from cfg_hostres struct"
Revert "staging: tidspbridge - move all iommu related code to a new file"
Revert "staging: tidspbridge - remove hw directory"
Revert "staging: tidspbridge - fix mmufault support"
Revert "staging: tidspbridge - remove custom mmu code from tiomap3430.c"
Revert "staging: tidspbridge - rename bridge_brd_mem_map/unmap
to a proper name"
Revert "staging: tidspbridge - move shared memory iommu maps to
tiomap3430.c"
Revert "staging: tidspbridge: replace iommu custom for
opensource implementation"
staging: tidspbridge: hack to make it compile on v37-rc1
omap: dsp: remove shm from normal memory
--
Felipe Contreras
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
