Signed-off-by: Grant Likely
---
For RFC only. I do not plan to merge this change yet.
g.
Documentation/devicetree/booting-without-of.txt | 40 +++
1 files changed, 40 insertions(+), 0 deletions(-)
diff --git a/Documentation/devicetree/booting-without-of.txt
b/Documenta
32 and 64 bit powerpc support has been merged for a while now, but
the booting-without-of.txt document still describes 32 bit as not
supporting multiplatform, which is no longer true. This patch fixes
the documentation.
Also remove references to powerpc-specific details outside of section
I in pr
The device tree is used by more than just PowerPC. Make the documentation
directory available to all.
v2: reorganized files while moving to create arch and driver specific
directories.
Signed-off-by: Grant Likely
---
Documentation/devicetree/bindings/ata/fsl-sata.txt |0
Documentation
This series reorganizes and cleans up the device tree documentation
to make the directory useful for non-powerpc users.
Patch 3 of this series adds some documentation about the ARM device
tree boot interface, but I'm posting this one for RFC only at the
moment. I'll not merge this until dt suppor
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
arch/powerpc/kernel/exceptions-64s.S: Assembler messages:
arch/powerpc/kernel/exceptions-64s.S:989: Error: attempt to move .org backwards
arch/powerpc/kernel/exceptions-64s.S:999: Error: attemp
On Sun, 2011-01-30 at 12:03 +0100, Mathias Krause wrote:
> Hi all!
>
> First of all: Sorry, this is the wrong mailing list, but I searched a
> lot and found none that would fit to PPC user-related problems --
> linux-ppc would have been one but this one seems to be dead since
> 2004?
.../
T
Hi all!
First of all: Sorry, this is the wrong mailing list, but I searched a lot and
found none that would fit to PPC user-related problems -- linux-ppc would have
been one but this one seems to be dead since 2004?!
I've a G4 based Mac mini and would like to suspend it to RAM, though the
vani
Stijn Devriendt wrote:
> As far as I know, you're violating PCIe spec.
> PCIe base spec (rev1.0a) states that a device must start link training
> within 80ms
> after a fundamental reset and that each device must be ready to accept config
> requests within 100ms after fundamental reset.
Nope.
From