> Well, the main thing is the implementation of kmap and kmap_atomic.
>
> They both basically assumes that all the reserved PTEs for kmap and
> kmap_atomic are in a single PTE page since it uses a simple addition
> (substraction for _atomic really but heh, that's about the same).
>
> Note that P
On Thu, 2008-10-16 at 06:22 +0400, Ilya Yanok wrote:
> These patches add support for selecting page size on PPC 44x.
> First one adds support for 16K/64K pages while second one adds support
> for 256K pages along with some hacks.
>
> However there are still number of problems:
> 1. We can't use de
On Mon, 2008-11-10 at 18:33 -0600, Hollis Blanchard wrote:
> I can't tell why this WARN_ON exists, and there's no comment explaining it.
> Whether the pmd is present or not, pte_alloc_kernel() seems to handle both
> cases.
>
> Booting a 440 kernel with 64K PAGE_SIZE triggers the warning, but boot
I can't tell why this WARN_ON exists, and there's no comment explaining it.
Whether the pmd is present or not, pte_alloc_kernel() seems to handle both
cases.
Booting a 440 kernel with 64K PAGE_SIZE triggers the warning, but boot
successfully completes and I see no problems beyond that.
Signed-off
The current CHIP11 errata truncates the device tree memory node, and subtracts
(hardcoded) 4096 bytes. This breaks kernels with larger PAGE_SIZE, since the
bootmem allocator assumes that total memory is a multiple of PAGE_SIZE.
Instead, use a device tree memory reservation to reserve only the 256
wael showair wrote:
i want to add a node for the DMA in this tree. the PIC PDF tells me that DMA
channel 0 is connected to Internal interrupt number 4 so i add the following
node just before the pic node & after the serial node:
**
[EMAIL
Adds in-kernel hctosys functionality that can
be used by ntp sync code.
This is an RFC and has not been tested, I just want
to check if something similar could solve the problems
of those who want the NTP sync mode.
Signed-off-by: Alessandro Zummo <[EMAIL PROTECTED]>
Cc: Paul Mundt <[EMAIL PROTEC
Hi all,
My board processor is MPC8555, it is an AMC board.
i want to add a node for my device to the device tree.
simply here is the old device tree :
***
/ {
model = "MPC8555AMC";
compatible = "mpc85xx";
#address-cells = <1>;
#s
On Mon, 10 Nov 2008 14:57:28 -0800
David Brownell <[EMAIL PROTECTED]> wrote:
> Yeah, we should have one of these. :)
:) great! now let's see if we can get others
to agree!
> A better default might be to update all the RTCs on the system.
>
> I'm thinking of my trusty test-case here: rtc0
Yeah, we should have one of these. :)
On Monday 10 November 2008, Alessandro Zummo wrote:
> @@ -30,7 +30,7 @@ config RTC_HCTOSYS
> unnecessary fsck runs at boot time, and to network better.
>
> config RTC_HCTOSYS_DEVICE
> - string "RTC used to set the system time"
> + string "
On Mon, 2008-11-10 at 10:07 -0800, Victor Gallardo wrote:
> Hello Josh and Ben,
>
> Who should I ask to get this patch integrated into the Linux tree?
> http://ozlabs.org/pipermail/linuxppc-dev/2008-November/064834.html
Either, I've been off for a couple of weeks (new baby) which is why I
d
On Nov 10, 2008, at 3:09 PM, Trent Piepho wrote:
Commit d0fc2eaaf4c56a95f5ed29b6bfb609e19714fc16 "powerpc/fsl: Refactor
device bindings" split out a number of device bindings from
booting-without-of.txt into separate files. Having them all in one
file
was a frequent source of merge conflict
Commit d0fc2eaaf4c56a95f5ed29b6bfb609e19714fc16 "powerpc/fsl: Refactor
device bindings" split out a number of device bindings from
booting-without-of.txt into separate files. Having them all in one file
was a frequent source of merge conflicts.
However, in the next merge, 49997d75152b3d23c53b0fa7
> A previous fix introduced a regression where port activation events were
> dropped unconditionally if port autodetection was not enabled. Fixed.
Is this a fix to "IB/ehca: Remove reference to special QP in case of
port activation failure"? Because if so I can roll it into that patch,
since Li
On Sat, Nov 08, 2008 at 08:52:54PM +0300, Anton Vorontsov wrote:
> Boards should know when QE_USB is used, so that they can configure USB
> clocks and pins.
>
> Another option would be to add 'select QE_USB' into USB_GADGET_FSL_QE,
> but selects are evil since they don't support dependencies.
Can
Hello Josh and Ben,
Who should I ask to get this patch integrated into the Linux tree?
http://ozlabs.org/pipermail/linuxppc-dev/2008-November/064834.html
Thanks,
Victor Gallardo
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozla
On Nov 10, 2008, at 10:11 AM, Milton Miller wrote:
On 2008-11-07 at 02:31:40, David Gibson wrote:
On Thu, Nov 06, 2008 at 06:55:44PM +1100, Michael Ellerman wrote:
This commit adds an output format, which produces python
code. When run, the python produces a data structure that
can then be in
Hello Milton,
Milton Miller wrote:
> I started out looking at the too minimal decription of patch 2/2, and
> that morphed into talking about both patches.
>
>> diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
>> index 587da5e..9627cfd 100644
>> --- a/arch/powerpc/Kconfig
>> +++ b/arch/powe
Hello Milton,
Milton Miller wrote:
>> This patch adds support for 256K pages on PPC 44x along with
>> some hacks needed for this.
>
> This description is insufficient, it describes neither the hacks nor
> why they are required.
Ok. Actually there is only one hack -- increasing kernel stack size.
On 2008-11-07 at 02:31:40, David Gibson wrote:
On Thu, Nov 06, 2008 at 06:55:44PM +1100, Michael Ellerman wrote:
This commit adds an output format, which produces python
code. When run, the python produces a data structure that
can then be inspected in order to do various things.
...
I'm not su
Milton Miller wrote:
On Oct 23, 2008, at 10:15 AM, Mohan Kumar M wrote:
Hi Milton,
My suggestions:
Milton Miller wrote:
i.e.,
[code snip 1]
lwz r7,__run_at_load-_stext(r26)
cmplwi cr0,r7,1/* kdump kernel ? - stay where we are */
bne 1f
add r2
On 2008-10-16 at 02:22:31, Ilya Yanok wrote:
I started out looking at the too minimal decription of patch 2/2, and
that morphed into talking about both patches.
diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
index 587da5e..9627cfd 100644
--- a/arch/powerpc/Kconfig
+++ b/arch/powerpc
On 2008-10-16 at 02:22:32, Ilya Yanok wrote:
This patch adds support for 256K pages on PPC 44x along with
some hacks needed for this.
This description is insufficient, it describes neither the hacks nor
why they are required.
diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
index 9
The following series implements and enables support for the FPGA based
watchdog timers found on GE Fanuc's SBC610.
There are two identical watchdog timers at different offsets in the above
mentioned boards, however the current driver is only capable of supporting
one of them.
The watchdog timers
Support for the FPGA based watchdog timer on GE Fanuc's SBC610.
This patch enables one of the watchdog timers found on the SBC610. There are
two identical watchdog timers at different offsets in the above mentioned
boards, however the current driver is only capable of supporting one of them.
The
GE Fanuc SBC610
Support for the FPGA based watchdog timer as found on GE Fanuc's SBC310,
SBC610 and PPC9A Single Board Computers.
This patch adds support for the watchdog timer found in one of the devices
FPGAs. There are two identical watchdog timers at different offsets in the
above mentioned b
Support for the FPGA based watchdog timer on GE Fanuc's SBC610.
This patch enables one of the watchdog timers found on the SBC610. There are
two identical watchdog timers at different offsets in the above mentioned
boards, however the current driver is only capable of supporting one of them.
The
GE Fanuc SBC610
Support for the FPGA based watchdog timer as found on GE Fanuc's SBC310,
SBC610 and PPC9A Single Board Computers.
This patch adds support for the watchdog timer found in one of the devices
FPGAs. There are two identical watchdog timers at different offsets in the
above mentioned b
The following series implements and enables support for the FPGA based
watchdog timers found on GE Fanuc's SBC610.
There are two identical watchdog timers at different offsets in the above
mentioned boards, however the current driver is only capable of supporting
one of them.
The watchdog timers
On Fri, Nov 07, 2008 at 02:38:22PM +, Martyn Welch wrote:
> Support for the SBC610 VPX Single Baord Computer from GE Fanuc (PowerPC
> MPC8641D).
>
> This patch adds support for the watchdog timer in the devices main FPGA.
> There are two identical watchdog timers at different offsets in the ma
30 matches
Mail list logo
