Hello Heiko,
On Mon, 06 Dec 2010 08:30:37 +0100
Heiko Schocher wrote:
> Hello Wolfram,
>
> Wolfram Sang wrote:
> > On Sat, Dec 04, 2010 at 09:21:54AM +0100, Heiko Schocher wrote:
> >
> > There shall be only one mpc5200-defconfig. Does the genric one work with
> > your
> > board?
>
> Just tri
Hello Anatolij,
Anatolij Gustschin wrote:
> On Mon, 06 Dec 2010 08:30:37 +0100
> Heiko Schocher wrote:
>
>> Hello Wolfram,
>>
>> Wolfram Sang wrote:
>>> On Sat, Dec 04, 2010 at 09:21:54AM +0100, Heiko Schocher wrote:
>>>
>>> There shall be only one mpc5200-defconfig. Does the genric one work wit
On Mon, Dec 06, 2010 at 10:13:00AM +0100, Heiko Schocher wrote:
> If such a file is accepted in mainline, I make a v2 post.
===
commit 0a0a5af30b9831e4f049610b5a2d9d5108ff027a
Author: Grant Likely
Date: Mon Jan 21 11:22:22 2008 -0700
[POWERPC] mpc5200: merge defconfigs for all mpc5200 boa
Hello Wolfram,
Wolfram Sang wrote:
> On Mon, Dec 06, 2010 at 10:13:00AM +0100, Heiko Schocher wrote:
>> If such a file is accepted in mainline, I make a v2 post.
>
> ===
>
> commit 0a0a5af30b9831e4f049610b5a2d9d5108ff027a
> Author: Grant Likely
> Date: Mon Jan 21 11:22:22 2008 -0700
>
>
Thank you for the detailed answer. I'm trying to digest it...
> > What's a good source, besides grepping the kernel to no end ?
>
> Nothing really I'm afraid.
8-|
> So you have a device, it appears in your device tree, and you want to
> write a driver for it.
That's the idea. Communication betwe
> Wolfram Sang wrote:
> > On Mon, Dec 06, 2010 at 10:13:00AM +0100, Heiko Schocher wrote:
> >> If such a file is accepted in mainline, I make a v2 post.
> >
> > ===
> >
> > commit 0a0a5af30b9831e4f049610b5a2d9d5108ff027a
> > Author: Grant Likely
> > Date: Mon Jan 21 11:22:22 2008 -0700
> >
>
Hello Wolfram,
Wolfram Sang wrote:
>> Wolfram Sang wrote:
>>> On Mon, Dec 06, 2010 at 10:13:00AM +0100, Heiko Schocher wrote:
If such a file is accepted in mainline, I make a v2 post.
>>> ===
>>>
>>> commit 0a0a5af30b9831e4f049610b5a2d9d5108ff027a
>>> Author: Grant Likely
>>> Date: Mon Jan
On Mon, 2010-12-06 at 14:35 +0800, Jeremy Kerr wrote:
> Hi Michael,
>
> > So you have a device, it appears in your device tree, and you want to
> > write a driver for it.
>
> Nice write up, mind if I steal this for the devicetree.org wiki?
Sure thing, feel free to correct any mistakes too ;D
ch
On Mon, 2010-12-06 at 10:58 +0100, Guillaume Dargaud wrote:
> Thank you for the detailed answer. I'm trying to digest it...
>
> > > What's a good source, besides grepping the kernel to no end ?
> >
> > Nothing really I'm afraid.
> 8-|
>
> > So you have a device, it appears in your device tree, a
> That's the idea. Communication between usermode and the driver is
limited to
> simple ioctl calls and the driver receives an interrupt when certain
data has
> been placed in memory blocks by the hardware (like a DMA).
> Then the user prog figures out where that latest data buffer is (mmap)
Hello all,
> OK, that should be all pretty straight forward, and covered by the
> material in LDD and similar references. You just need to get your device
> probed.
I'm not sure what you mean with that term: simply identifying that the device
works using device specific code ?
I've looked at sev
> Another question: I just spent 10 minutes trying to find
> where "struct device" was defined.
Dirty trick #4:
At the top of a source file (before the first include) add:
struct device { int fubar; };
Then try to compile it.
The compiler will the tell where it is defined!
David
From: Dirk Brandewie
This patch set adds the ability to link device tree blobs into
vmlinux.
Patch 1 implements the changes to include/asm-generic/vmlinux.lds.h and
adds a generic rule for generating DTB objects to be linked vmlinux.
Patch 2 implements linking a DTB into an x86 image.
Patch 3
From: Dirk Brandewie
This patch adds support for linking device tree blob(s) into
vmlinux. Modifies asm-generic/vmlinux.lds.h to add linking
.dtb sections into vmlinux. To maintain compatiblity with the of/fdt
driver code platforms MUST copy the blob to a non-init memory location
before the kerne
From: Dirk Brandewie
Modify arch/powerpc/boot/Makefile to use dtc command in
scripts/Makefile.lib
Signed-off-by: Dirk Brandewie
---
arch/microblaze/boot/Makefile | 10 ++
1 files changed, 2 insertions(+), 8 deletions(-)
diff --git a/arch/microblaze/boot/Makefile b/arch/microblaze/bo
From: Dirk Brandewie
This patch adds linking device tree blob into vmlinux. DTB's are
added by adding the blob object name to list of objects to be linked
into the image.
Signed-off-by: Dirk Brandewie
---
arch/x86/platform/ce4100/Makefile | 10 ++
1 files changed, 10 insertions(+), 0
From: Dirk Brandewie
Modify arch/powerpc/boot/Makefile to use dtc command in
scripts/Makefile.lib
Signed-off-by: Dirk Brandewie
---
arch/powerpc/boot/Makefile |8 +++-
1 files changed, 3 insertions(+), 5 deletions(-)
diff --git a/arch/powerpc/boot/Makefile b/arch/powerpc/boot/Makefile
Hi,
On a sort of related issue, if anyone out there has a PowerMac7,3
(dual 2.5 GHz 970Fx, PCI-X), I would appreciate it if you could do me
a favor.
I think this therm_pm72 thing creates the sysfs temperature and
voltage attributes for the cpus. I noticed on my machine that if I use
the cpufreq d
On Mon, Dec 06, 2010 at 09:35:59AM -0800, dirk.brande...@gmail.com wrote:
> From: Dirk Brandewie
>
> This patch adds support for linking device tree blob(s) into
> vmlinux. Modifies asm-generic/vmlinux.lds.h to add linking
> .dtb sections into vmlinux. To maintain compatiblity with the of/fdt
> d
When the watchdog period is changed, it needs to be propagated to all cores
in addition to the core that performed the change.
Signed-off-by: Randy Vinson
---
drivers/watchdog/booke_wdt.c | 19 +--
1 files changed, 17 insertions(+), 2 deletions(-)
diff --git a/drivers/watchdog
This implements lazy save of FP, VMX and VSX state on SMP 64bit and 32
bit powerpc.
Currently we only do lazy save in UP, but this patch set extends this to
SMP. We always do lazy restore.
For VMX, on a context switch we do the following:
- if we are switching to a CPU that currently holds the
Add csd_locked function to determine if a struct call_single_data is
currently locked. This can be used to see if an IPI can be called
again using this call_single_data.
Signed-off-by: Michael Neuling
---
kernel/smp.c | 17 +
1 file changed, 17 insertions(+)
Index: linux-lazy
We need to put struct call_single_data in the powerpc thread_struct,
but can't without this.
The thread_struct is in processor.h. To add a struct call_single_data
to the thread_struct asm/processor.h must include linux/smp.h. When
linux/smp.h is added to processor.h this creates an include loop
Currently we don't restore r0, r7, r8 and CTR in
fast_exception_return. This changes fast_exception_return to restore
these, which were saved anyway on exception entry.
This seems like a bug waiting to happen, plus we do it in hash_page
for 32bit anyway.
Signed-off-by: Michael Neuling
---
arc
We need to put struct call_single_data in the powerpc thread_struct,
but can't without this.
In processor.h this moves up the prefetch() functions before the
#include of types.h to ensure __builtin_prefetch doesn't get defined
twice.
Similarly in hw_irq.h move arch_irqs_disabled_flags() to befo
This enables lazy save of FP registers for SMP configurations.
This adds a pointer to the thread struct to say which CPU holds this
processes FP register state. On 64 bit, this points to the paca of
the CPU holding the state or NULL if it's in the thread_struct. On 32
bit, this is the CPU number
This enables lazy save of VMX registers for SMP configurations.
This adds a pointer to the thread struct to say which CPU holds this
processes VMX register state. On 64 bit, this points to the paca of
the CPU holding the state or NULL if it's in the thread_struct. On 32
bit, this is the CPU numb
This enables lazy save of VSX state for SMP configurations.
Most of the logic for this is in the FP and VMX code, since VSX has no
additional state over these.
When context switching to a new process:
- if both VMX and FP state are on the CPU we are switch to, turn VSX
on also.
- if either
On 12/06/2010 11:02 AM, Sam Ravnborg wrote:
On Mon, Dec 06, 2010 at 09:35:59AM -0800, dirk.brande...@gmail.com wrote:
From: Dirk Brandewie
-
+# DTC
+# ---
+
+# Generate an assembly file to wrap the output of the device tree
A few months ago I ran into some performance problems involving
UBI/NAND erases holding other devices off the LBC on an MPC8315. I
found a solution for this, which worked well, at least with the
hardware I was working with. I suspect the same problem affects other
PPCs, probably including multico
From: Ian Munsie
This patch implements the raw syscall tracepoints on PowerPC and exports
them for ftrace syscalls to use.
To minimise reworking existing code, I slightly re-ordered the thread
info flags such that the new TIF_SYSCALL_TRACEPOINT bit would still fit
within the 16 bits of the andi.
Oops, It seems that I missed LKML in the to address of the cover email
for this set. Guess I shouldn't send a patch set just as the fire alarm
goes off. Resending:
Hi all,
This is a partial version of my 'ftrace syscalls, PowerPC: Various fixes,
Compat Syscall support and PowerPC implementation
Signed-off-by: Heiko Schocher
cc: Wolfram Sang
---
- based against 2.6.37-rc4
./scripts/checkpatch.pl 0001-powerpc-5200-add-support-for-charon-board.patch
total: 0 errors, 0 warnings, 233 lines checked
0001-powerpc-5200-add-support-for-charon-board.patch has no obvious style
problems and is re
Signed-off-by: Heiko Schocher
cc: linux-fb...@vger.kernel.org
cc: devicetree-disc...@ozlabs.org
---
- based against 2.6.37-rc4
./scripts/checkpatch.pl
0003-powerpc-video-add-SM501-support-for-charon-board.patch
total: 0 errors, 0 warnings, 21 lines checked
0003-powerpc-video-add-SM501-support-f
Hi Dave,
I have a question with the below patch you made before:
powerpc/booke: Add support for advanced debug registers
From: Dave Kleikamp
Based on patches originally written by Torez Smith.
-
I meet a kernel p
35 matches
Mail list logo
