Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 04 12月, 2006 3 次提交
    • D
      [POWERPC] Cleanup zImage handling of kernel entry with flat device tree · 35af89eb
      由 David Gibson 提交于 
      This makes 2 changes to clean up the flat device tree handling
logic in the zImage wrapper.

First, there were two callbacks from the dt_ops structure used for
producing a final flat tree to pass to the kerne: dt_ops.ft_pack()
which packed the flat tree (possibly a no-op) and dt_ops.ft_addr()
which retreived the address of the final blob.  Since they were only
ever called together, this patch combines the two into a single new
callback, dt_ops.finalize().  This new callback does whatever
platform-dependent things are necessary to produce a final flat device
tree blob, and returns the blob's addres.

Second, the current logic calls the kernel with a flat device tree if
one is build into the zImage wrapper, otherwise it boots the kernel
with a PROM pointer, expecting the kernel to copy the OF device tree
itself.  This approach precludes the possibility of the platform
wrapper code building a flat device tree from whatever
platform-specific information firmware provides.  Thus, this patch
takes the more sensible approach of invoking the kernel with a flat
tree if the dt_ops.finalize callback provides one (by whatever means).

So, the dt_ops.finalize callback can be NULL, or can be a function
which returns NULL.  In either case, the zImage wrapper logic assumes
that this is a platform with OF and invokes the kernel accordingly.
Signed-off-by: NDavid Gibson <dwg@au1.ibm.com>
Signed-off-by: NPaul Mackerras <paulus@samba.org>
      35af89eb
    • D
      [POWERPC] Small clarification of initrd handling · f79e083c
      由 David Gibson 提交于 
      This patch makes the handling of the initrd (or initramfs) in the
zImage wrapper a little easier to follow.  Instead of passing the
initrd addresses out from prep_kernel() via the cryptic a1 and a2
parameters, use the global struct add_range, 'initrd'.  prep_kernel()
already passes information through the 'vmlinux' addr_range struct, so
this seems like a reasonable extension.

Some comments also clarify the logic with prep_kernel(): we use an
initrd included in the zImage if present, otherwise we use an initrd
passed in by the bootloader in the a1 and a2 parameters (yaboot, at
least, uses this mechanism to pass an initrd).
Signed-off-by: NDavid Gibson <dwg@au1.ibm.com>
Signed-off-by: NPaul Mackerras <paulus@samba.org>
      f79e083c
    • Z
      [POWERPC] Make pci_read_irq_line the default on mpc7448hpc2 board · 5873c9bd
      由 Zang Roy-r61911 提交于 
      The following patch adds a tsi108/9 pci interrupt controller host.
On mpc7448hpc2 board, pci_irq_fixup function is removed, which makes the
pci_read_irq_line be the default pci irq fixup.
Signed-off-by: NRoy Zang <tie-fei.zang@freescale.com>
Signed-off-by: NPaul Mackerras <paulus@samba.org>
      5873c9bd
  3. 13 11月, 2006 3 次提交
  5. 09 11月, 2006 1 次提交
  7. 25 10月, 2006 1 次提交
  9. 24 10月, 2006 1 次提交
  11. 23 10月, 2006 4 次提交
  13. 18 10月, 2006 1 次提交
  15. 10 10月, 2006 2 次提交
  17. 06 10月, 2006 2 次提交
  19. 04 10月, 2006 4 次提交
  21. 28 9月, 2006 1 次提交
    • P
      [POWERPC] Create a "wrapper" script and use it in arch/powerpc/boot · 2bf11819
      由 Paul Mackerras 提交于 
      This puts the knowledge of how to create various sorts of zImage
wrappers into a script called "wrapper" that could be used outside of
the kernel tree.  This changes arch/powerpc/boot so it first builds
the files that the wrapper script needs, then runs it to create
whatever flavours of zImage are required.

This version does uImages as well.  The zImage names are changed
slightly; zImage.pseries is the one with the PT_NOTE program header
entry added, and zImage.pmac is the one without.  If the
zImage.pseries gets made, it will also get hardlinked to zImage;
otherwise, if zImage.pmac is made, it gets hardlinked to zImage.
Signed-off-by: NPaul Mackerras <paulus@samba.org>
      2bf11819
  23. 22 9月, 2006 2 次提交
    • V
      POWERPC: Bring the fs_no calculation to the relevant SoC enumeration · 611a15af
      由 Vitaly Bordug 提交于 
      The fs_no mean used to be fs_enet driver driven, hence it was an
enumeration across all the possible fs_enet "users" in the SoC. Now, with
QE on the pipeline, and to make DTS descriptions more clear, fs_no features
relevant SoC part number, with additional field to describe the SoC type.

Another reason for that is now not only fs_enet is going to utilize those
stuff. There might be UART, HLDC, and even USB, so to prevent confusion and
be ready for upcoming OF_device transfer, fs_enet and cpm_uart drivers were
updated in that concern, as well as the relevant DTS.
Signed-off-by: NVitaly Bordug <vbordug@ru.mvista.com>
      611a15af
    • V
      POWERPC: Add support for the mpc8560 eval board · 902f392d
      由 Vitaly Bordug 提交于 
      This makes the 8560 evaluation board fully supported under arch/powerpc,
as the first board with CPM2 SoC peripherals. The brand new devicetree
nodes are introduced (intending to be a subset of the QuiccEngine-equipped
models, with dts sources placed into the kernel according to the new convention.

Assuming all the preceding stuff applied (PAL+fs_enet related+ CPM_UART
update), the both TSEC eth ,FCC Eths, and both SCC UARTs are
working. The relevant drivers are still capable to drive users in ppc,
which was verified with 8272ADS (SCC uart+FCC eth).

This is also verified on mpc8540 and actually make it work (PCI stuff
working as well)
Signed-off-by: NVitaly Bordug <vbordug@ru.mvista.com>
      902f392d
  25. 20 9月, 2006 1 次提交
  27. 14 9月, 2006 1 次提交
  29. 30 8月, 2006 2 次提交
  31. 23 8月, 2006 2 次提交
  33. 18 8月, 2006 2 次提交
  35. 08 8月, 2006 1 次提交
  37. 07 7月, 2006 1 次提交
  39. 23 6月, 2006 1 次提交
    • R
      [PATCH] zlib_inflate: Upgrade library code to a recent version · 4f3865fb
      由 Richard Purdie 提交于 
      Upgrade the zlib_inflate implementation in the kernel from a patched
version 1.1.3/4 to a patched 1.2.3.

The code in the kernel is about seven years old and I noticed that the
external zlib library's inflate performance was significantly faster (~50%)
than the code in the kernel on ARM (and faster again on x86_32).

For comparison the newer deflate code is 20% slower on ARM and 50% slower
on x86_32 but gives an approx 1% compression ratio improvement.  I don't
consider this to be an improvement for kernel use so have no plans to
change the zlib_deflate code.

Various changes have been made to the zlib code in the kernel, the most
significant being the extra functions/flush option used by ppp_deflate.
This update reimplements the features PPP needs to ensure it continues to
work.

This code has been tested on ARM under both JFFS2 (with zlib compression
enabled) and ppp_deflate and on x86_32.  JFFS2 sees an approx.  10% real
world file read speed improvement.

This patch also removes ZLIB_VERSION as it no longer has a correct value.
We don't need version checks anyway as the kernel's module handling will
take care of that for us.  This removal is also more in keeping with the
zlib author's wishes (http://www.zlib.net/zlib_faq.html#faq24) and I've
added something to the zlib.h header to note its a modified version.
Signed-off-by: NRichard Purdie <rpurdie@rpsys.net>
Acked-by: NJoern Engel <joern@wh.fh-wedel.de>
Signed-off-by: NAndrew Morton <akpm@osdl.org>
Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      4f3865fb
  41. 15 6月, 2006 1 次提交
  43. 16 3月, 2006 1 次提交
  45. 10 2月, 2006 1 次提交
  47. 07 2月, 2006 1 次提交