1. 28 9月, 2005 1 次提交
  2. 09 9月, 2005 2 次提交
    • P
      Allow PCI config space syscalls to be used by 64-bit processes. · b2ad7b5e
      Paul Mackerras 提交于
      The pciconfig_iobase, pciconfig_read and pciconfig_write system calls
      were only implemented for 32-bit processes; for 64-bit processes they
      returned an ENOSYS error.  This allows them to be used by 64-bit
      processes as well.  The X server uses pciconfig_iobase at least, and
      this change is necessary to allow a 64-bit X server to work on my G5.
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      b2ad7b5e
    • P
      [PATCH] Separate pci bits out of struct device_node · 1635317f
      Paul Mackerras 提交于
      This patch pulls the PCI-related junk out of struct device_node and
      puts it in a separate structure, struct pci_dn.  The device_node now
      just has a void * pointer in it, which points to a struct pci_dn for
      nodes that represent PCI devices.  It could potentially be used in
      future for device-specific data for other sorts of devices, such as
      virtual I/O devices.
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      1635317f
  3. 08 9月, 2005 1 次提交
  4. 08 7月, 2005 2 次提交
  5. 22 6月, 2005 1 次提交
  6. 09 6月, 2005 1 次提交
    • P
      [PATCH] ppc64: Fix PER_LINUX32 behaviour · ce10d979
      Paul Mackerras 提交于
      This patch fixes some bugs in the ppc64 PER_LINUX32 implementation,
      noted by Juergen Kreileder:
      
      * uname(2) doesn't respect PER_LINUX32, it returns 'ppc64' instead of 'ppc'
      * Child processes of a PER_LINUX32 process don't inherit PER_LINUX32
      
      Along the way I took the opportunity to move things around so that
      sys_ppc32.c only has 32-bit syscall emulation functions and to remove
      the obsolete "fakeppc" command line option.
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      ce10d979
  7. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4