Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 28 8月, 2009 1 次提交
  3. 20 8月, 2009 1 次提交
  5. 08 7月, 2009 1 次提交
  7. 15 6月, 2009 1 次提交
  9. 07 4月, 2009 1 次提交
  11. 25 3月, 2009 1 次提交
  13. 16 1月, 2009 3 次提交
  15. 16 12月, 2008 2 次提交
  17. 31 10月, 2008 1 次提交
    • M
      powerpc: Update remaining dma_mapping_ops to use map/unmap_page · f9226d57
      由 Mark Nelson 提交于 
      After the merge of the 32 and 64bit DMA code, dma_direct_ops lost
their map/unmap_single() functions but gained map/unmap_page().  This
caused a problem for Cell because Cell's dma_iommu_fixed_ops called
the dma_direct_ops if the fixed linear mapping was to be used or the
iommu ops if the dynamic window was to be used.  So in order to fix
this problem we need to update the 64bit DMA code to use
map/unmap_page.

First, we update the generic IOMMU code so that iommu_map_single()
becomes iommu_map_page() and iommu_unmap_single() becomes
iommu_unmap_page().  Then we propagate these changes up through all
the callers of these two functions and in the process update all the
dma_mapping_ops so that they have map/unmap_page rahter than
map/unmap_single.  We can do this because on 64bit there is no HIGHMEM
memory so map/unmap_page ends up performing exactly the same function
as map/unmap_single, just taking different arguments.

This has no affect on drivers because the dma_map_single_attrs() just
ends up calling the map_page() function of the appropriate
dma_mapping_ops and similarly the dma_unmap_single_attrs() calls
unmap_page().

This fixes an oops on Cell blades, which oops on boot without this
because they call dma_direct_ops.map_single, which is NULL.
Signed-off-by: NMark Nelson <markn@au1.ibm.com>
Signed-off-by: NPaul Mackerras <paulus@samba.org>
      f9226d57
  19. 25 9月, 2008 1 次提交
  21. 22 7月, 2008 1 次提交
  23. 09 7月, 2008 2 次提交
  25. 25 1月, 2008 2 次提交
  27. 23 10月, 2007 1 次提交
  29. 16 10月, 2007 1 次提交
  31. 15 10月, 2007 1 次提交
  33. 13 10月, 2007 1 次提交
    • K
      Driver core: change add_uevent_var to use a struct · 7eff2e7a
      由 Kay Sievers 提交于 
      This changes the uevent buffer functions to use a struct instead of a
long list of parameters. It does no longer require the caller to do the
proper buffer termination and size accounting, which is currently wrong
in some places. It fixes a known bug where parts of the uevent
environment are overwritten because of wrong index calculations.

Many thanks to Mathieu Desnoyers for finding bugs and improving the
error handling.
Signed-off-by: NKay Sievers <kay.sievers@vrfy.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>
Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      7eff2e7a
  35. 28 6月, 2007 3 次提交
  37. 12 5月, 2007 1 次提交
  39. 10 3月, 2007 1 次提交
  41. 09 3月, 2007 1 次提交
  43. 10 2月, 2007 1 次提交
  45. 07 2月, 2007 3 次提交
  47. 04 12月, 2006 2 次提交
    • A
      [POWERPC] ps3: multiplatform build fixes · e22ba7e3
      由 Arnd Bergmann 提交于 
      A few code paths need to check whether or not they are running
on the PS3's LV1 hypervisor before making hcalls. This introduces
a new firmware feature bit for this, FW_FEATURE_PS3_LV1.

Now when both PS3 and IBM_CELL_BLADE are enabled, but not PSERIES,
FW_FEATURE_PS3_LV1 and FW_FEATURE_LPAR get enabled at compile time,
which is a bug. The same problem can also happen for (PPC_ISERIES &&
!PPC_PSERIES && PPC_SOMETHING_ELSE). In order to solve this, I
introduce a new CONFIG_PPC_NATIVE option that is set when at least
one platform is selected that can run without a hypervisor and then
turns the firmware feature check into a run-time option.

The new cell oprofile support that was recently merged does not
work on hypervisor based platforms like the PS3, therefore make
it depend on PPC_CELL_NATIVE instead of PPC_CELL. This may change
if we get oprofile support for PS3.
Signed-off-by: NArnd Bergmann <arnd.bergmann@de.ibm.com>
      e22ba7e3
    • G
      [POWERPC] ps3: add ps3 platform system bus support · a3d4d643
      由 Geoff Levand 提交于 
      Adds a PS3 system bus driver.  This system bus is a virtual bus used to present
the PS3 system devices in the LDM.
Signed-off-by: NGeoff Levand <geoffrey.levand@am.sony.com>
Signed-off-by: NArnd Bergmann <arnd.bergmann@de.ibm.com>
      a3d4d643