itialization issue
seen on the P4080.
Tested on a P4080-based system and compile tested on mpc512x_defconfig
with Freescale EHCI driver enabled.
Cc: Anatolij Gustschin
Cc: David Brownell
Cc: Kumar Gala
Cc: linuxppc-dev@lists.ozlabs.org
Signed-off-by: Peter Tyser
---
drivers/usb/host/ehci-fsl.
Previously SPRGs 4-7 were improperly read and written in
kvm_arch_vcpu_ioctl_get_regs() and kvm_arch_vcpu_ioctl_set_regs();
Signed-off-by: Peter Tyser
---
I noticed this while grepping for somthing unrelated and assume its
a typo. Feel free to add to the patch description; I don't use K
> > On Thu, 2010-07-22 at 04:03 +0400, Dmitry Eremin-Solenikov wrote:
> >> Add definitions for PCI error detection device to be handled by (already
> >> existing) mpc85xx_edac.c driver.
> >>
> >> Signed-off-by: Dmitry Eremin-Solenikov
> >> ---
> >> arch/powerpc/boot/dts/mpc8536ds.dts|
Hi Dmitry,
On Thu, 2010-07-22 at 04:03 +0400, Dmitry Eremin-Solenikov wrote:
> Add definitions for PCI error detection device to be handled by (already
> existing) mpc85xx_edac.c driver.
>
> Signed-off-by: Dmitry Eremin-Solenikov
> ---
> arch/powerpc/boot/dts/mpc8536ds.dts|7 +++
Hi Timur,
> +/**
> + * Global Utility Registers.
> + *
> + * Not all registers defined in this structure are available on all chips, so
> + * you are expected to know whether a given register actually exists on your
> + * chip before you access it.
> + *
> + * Also, some registers are similar on d
On Thu, 2009-11-19 at 18:42 -0600, Peter Tyser wrote:
> Some unused, unsupported debug code existed in the mpc85xx EDAC driver
> that resulted in a build failure when CONFIG_EDAC_DEBUG was defined:
>
> drivers/edac/mpc85xx_edac.c: In function 'mpc85xx_mc_err_probe&#
On Fri, 2009-12-18 at 16:50 -0600, Peter Tyser wrote:
> Recent U-Boot commit 5ccd29c3679b3669b0bde5c501c1aa0f325a7acb caused
> the "cpu-release-addr" device tree property to contain the physical RAM
> location that secondary cores were spinning at. Previously, the
> "
Note that the FIT image can also be made to contain a number of DT
blobs, and selection of a "board profile" then can be used to boot the
very sane FIT image file on any of the supported boards - so FIT
images inherently support multibooting.
I agree with Wolfgang. Additionally, if a FIT ima
Hi Wolfgang,
The "new" FIT image type should become the default, and old "legacy"
images should only be generated upon special request (i. e. if some-
one needs these for compatibility with an old, not yet FIT-aware
version of the boot loader).
Agreed.
What do you think about changing the U-
Hi Wolfgang,
> > IIRC, uImage.fit.initrd.% should appear before uImage.fit.% in the
> > Makefile so that make behaves more consistently. Speaking of which,
> > the number of '.' in the name is getting rather large. Would you
> > consider using 'fitImage' instead of 'uImage.fit'?
>
> Why chose a
On Wed, 2009-12-30 at 17:01 -0700, Grant Likely wrote:
> On Wed, Dec 30, 2009 at 4:39 PM, Peter Tyser wrote:
> > Hi Grant,
> > I put U-Boot ML on CC.
>
> Thinking further, I do actually have another concern, at least with
> regard to the way the current patch set i
Hi Grant,
I put U-Boot ML on CC.
On Wed, 2009-12-30 at 16:02 -0700, Grant Likely wrote:
> On Mon, Dec 21, 2009 at 6:50 PM, Peter Tyser wrote:
> > The PowerPC architecture has the ability to embed the ramdisk located
> > at arch/powerpc/boot/ramdisk.image.gz into a bootable ke
Hi Olof,
On Mon, 2009-12-21 at 21:48 -0600, Olof Johansson wrote:
> Hi,
>
> On Mon, Dec 21, 2009 at 07:50:42PM -0600, Peter Tyser wrote:
> > diff --git a/arch/powerpc/boot/Makefile b/arch/powerpc/boot/Makefile
> > index bb2465b..e56ec21 100644
> > --- a/arch/powerpc/b
and a ram filesystem.
The ramdisk at arch/powerpc/boot/ramdisk.image.gz can either be an older
style "ramdisk" or a newer "ramfs" gzipped cpio archive.
Signed-off-by: Peter Tyser
---
Changes since v1:
- Don't strip leading 0x from dts ramdisk address
arch/powerpc/boot/Mak
as well as a device tree blob. U-Boot versions compiled with FIT
support can directly boot this image using the "bootm" command.
Additional information about the FIT format and its uses can be found in
doc/uImage.FIT/howto.txt of U-Boot's source tree.
Signed-off-by: Peter Tyser
-
uImage that
combines the functionality of an "old" uImage format, a device
tree blob, and possibly a ramdisk.
Changes since v1:
- Add 'dts-v1' header to scripts/mkits.sh output
- Don't strip leading 0x from dts addresses
- Default to using kernel dtc if the user doesn't
s
which already call mkimage via mkuboot.sh.
Signed-off-by: Peter Tyser
---
arch/powerpc/boot/wrapper |7 +--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc/boot/wrapper b/arch/powerpc/boot/wrapper
index 390512a..f4594ed 100755
--- a/arch/powerpc/boot/wrappe
n address: 0xc05df9b0
Oops: Kernel access of bad area, sig: 11 [#1]
SMP NR_CPUS=2 P2020 RDB
Modules linked in:
<... eventual kernel panic>
Adding logic to conditionally ioremap or access memory directly resolves
the issue.
Signed-off-by: Peter Tyser
Signed-off-by: Nate Case
Hi Anton,
I've CC-ed devicetree-discuss. The original patch is at
http://patchwork.ozlabs.org/patch/40361/ for reference.
On Sat, 2009-12-05 at 23:51 +0300, Anton Vorontsov wrote:
> On Sat, Dec 05, 2009 at 01:32:32PM -0600, Peter Tyser wrote:
> [...]
> > > > Adding a new
Hi Anton,
Thanks for the feedback.
> On Fri, Dec 04, 2009 at 01:43:40PM -0600, Peter Tyser wrote:
> > This change resolves 2 issues:
> > - Different chips have a different number of GPIO pins per controller.
> > For example, the MPC8347 has 32, the P2020 16, and the mpc857
the use of GPIO pin 3
(fsl,gpio-mask = 0x8), 'ngpio' would be reported as 4, although
only GPIO pin 3 could be exported and used.
Signed-off-by: Peter Tyser
---
I don't know which GPIO pins are usable on Freescale boards. Let me
know if the default mask for the reference boards
Hi Stefano,
Stefano Babic wrote:
Peter Tyser
+# Create a default, fully populated DTS file
+DATA="/ {
+ description = \"Linux kernel ${VERSION}\";
+ #address-cells = <1>;
+
+ images {
+ kernel 1 {
Is the probably generated by your a
Hi Stefano,
Thanks for trying the patches out.
On Tue, 2009-11-24 at 11:32 +0100, Stefano Babic wrote:
> Peter Tyser > +uboot.fit)
> > +rm -f "$ofile"
> > +${MKITS} -A ppc -C gzip -a $membase -e $membase -v $version \
> > + -d "$srctree/$dtb&quo
on it appears in.)
Signed-off-by: Peter Tyser
---
drivers/edac/mpc85xx_edac.c |4
1 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/drivers/edac/mpc85xx_edac.c b/drivers/edac/mpc85xx_edac.c
index cf27402..28d3211 100644
--- a/drivers/edac/mpc85xx_edac.c
+++ b/drivers/edac/mp
improperly terminated signals,
loose pins, etc.
Note that this feature is only currently enabled for 64-bit wide data
buses, 32-bit wide bus support should be added.
Signed-off-by: Peter Tyser
---
I don't have any 32-bit wide systems to test on. If someone has one
and is willing to give this pa
' variables, thus it is not
necessary to account for it again when setting a chip select's first and
last page address.
Signed-off-by: Peter Tyser
---
drivers/edac/mpc85xx_edac.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/edac/mpc85xx_edac.c b/
When in reality the ECC syndrome is 0x25.
Signed-off-by: Peter Tyser
---
A variety of Freescale manual's say a variety of different things about
how to decode the CAPTURE_ECC (syndrome) register. I don't have a
system with a 32-bit bus to test on, but I believe the change is
correct. It
On Wed, 2009-11-18 at 14:57 -0600, Peter Tyser wrote:
> These patches add support for creating the "new" FIT uImage type
> that U-Boot can use. Additional info about FIT images can be
> found in the doc/uImage.FIT/ directory of the U-Boot source.
> Here's a link to a ho
as well as a device tree blob. U-Boot versions compiled with FIT
support can directly boot this image using the "bootm" command.
Additional information about the FIT format and its uses can be found in
doc/uImage.FIT/howto.txt of U-Boot's source tree.
Signed-off-by: Peter Ty
and a ram filesystem.
The ramdisk at arch/powerpc/boot/ramdisk.image.gz can either be an older
style "ramdisk" or a newer "ramfs" gzipped cpio archive.
Signed-off-by: Peter Tyser
---
arch/powerpc/boot/Makefile |3 +++
arch/powerpc/boot/wrapper | 20
scr
s
which already call mkimage via mkuboot.sh.
Signed-off-by: Peter Tyser
---
arch/powerpc/boot/wrapper |7 +--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc/boot/wrapper b/arch/powerpc/boot/wrapper
index ac9e9a5..1ee9448 100755
--- a/arch/powerpc/boot/wrappe
uImage that
combines the functionality of an "old" uImage format, a device
tree blob, and possibly a ramdisk.
Peter Tyser (3):
powerpc: Use scripts/mkuboot.sh instead of 'mkimage'
powerpc: Add support for creating FIT uImages
powerpc: Add support for ram filesystem
32 matches
Mail list logo
