Adam Litke wrote:
> On Tue, 2008-03-04 at 11:51 -0800, Andrew Morton wrote:
>> hugetlb-correct-page-count-for-surplus-huge-pages.patch adds:
>>
>> if (page) {
>> /*
>> * This page is now managed by the hugetlb allocator and has
>> * no users
Hi Paul,
There was a small conflict with Linus' tree (in arch/powerpc/Kconfig) in
merging the powerpc next branch into today's linux-next tree. Commit
d9b2b2a277219d4812311d995054ce4f95067725 ('[LIB]: Make PowerPC LMB code
generic so sparc64 can use it too') conflicted with
9edddaa200df18e08fe0cf
>> Anyway, this asm code has bugs, as do both the current C version in
>> the
>> kernel, and the code I posted. We need to do better :-)
>
> The only bug I know of in the asm code is the behaviour when the count
> is zero. Do you know of any other?
No, that's the bug I meant. Sorry for using s
Segher Boessenkool writes:
> Anyway, this asm code has bugs, as do both the current C version in the
> kernel, and the code I posted. We need to do better :-)
The only bug I know of in the asm code is the behaviour when the count
is zero. Do you know of any other?
Paul.
___
>> Do we have any indication that it performs better than the C one ?
>
> I would expect it to, given that the assembler one has two branches in
> the per-byte loop compared to 3 in the C version.
But really, does it matter for strncmp() in the kernel?
Anyway, this asm code has bugs, as do both t
This patch adds some testcases checking corner cases of dtc's input
file handling. Specifically it checks that dtc works correctly when
given input via stdin, and it checks that dtc fails gracefully if
given a nonexistent input file (or directory, in the case of -Ifs
mode).
Signed-off-by: David G
This patch makes several small improvements to the test harness.
* An altered way of invoking shell script testcases from run_tests.sh
means scripts no longer need to me marked executable in the
repository to work properly.
* dtc.sh never did anything that was really dtc specific - with the
> I also attach my current (not working) dts file attempt. It is actually
> a modified mpc8540ads.dts file.
>
> I now thinks that the ide-cs (hda) discovery or not depends on the cold
> or warm reboot.
>
> Here are the patches for my config (MEIP_8540) relative to a vanilla
> linux-2.6.24. I h
On Tue, Mar 04, 2008 at 10:10:59AM +0100, Philippe De Muyter wrote:
> Hi Ben,
>
> On Tue, Mar 04, 2008 at 07:22:19PM +1100, Benjamin Herrenschmidt wrote:
These comments aren't relevant to the problems you're seeing, but
they're a good idea for writing device trees in general.
First, you may want
Benjamin Herrenschmidt writes:
> Do we have any indication that it performs better than the C one ?
I would expect it to, given that the assembler one has two branches in
the per-byte loop compared to 3 in the C version.
Paul.
___
Linuxppc-dev mailing
Fix the following section mismatches:
WARNING: drivers/built-in.o(.exit.text+0x5a): Section mismatch in reference
from the function of_platform_serial_exit() to the variable
.devinit.data:of_platform_serial_driver
The function __exit of_platform_serial_exit() references
a variable __devinitdata
Hi Weu,
On Wed, 5 Mar 2008 09:59:38 +0800 "Zhang Wei" <[EMAIL PROTECTED]> wrote:
>
> Thanks! I'm considering to commit a updated patch or new code cleaning
> patch.
> How about your idea?
Preferably, fix up the patches. If that is a pain, then a followup patch
that cleans up is ok as these do no
Pekka Enberg wrote:
> Christoph Lameter wrote:
>> I think this is the correct fix.
>>
>> The NUMA fallback logic should be passing local_flags to kmem_get_pages()
>> and not simply the flags.
>>
>> Maybe a stable candidate since we are now simply
>> passing on flags to the page allocator on the f
Hi, Stephen,
Thanks! I'm considering to commit a updated patch or new code cleaning
patch.
How about your idea?
Cheers!
Wei
> -Original Message-
> From: Stephen Rothwell [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 04, 2008 6:38 PM
> To: Zhang Wei
> Cc: [EMAIL PROTECTED]; [EMAIL PR
eval_literal() is used only in the parser, so make it a static
function.
Signed-off-by: David Gibson <[EMAIL PROTECTED]>
---
dtc-parser.y |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Applies instead of the earlier patch that also localised yyerror().
Index: dtc/dtc-parser.y
=
On Tue, Mar 04, 2008 at 01:18:44PM -0600, Scott Wood wrote:
> On Tue, Mar 04, 2008 at 03:37:00PM +1100, David Gibson wrote:
> > * The Bison documentation explicitly permits yyerror() to be a
> > variadic function, so fold yyerror() and yyerrorf() into a single
> > printf-style function.
>
> Th
On Tue, Mar 04, 2008 at 07:35:40PM +0300, Alexandr Smirnov wrote:
> Add device tree file for Emerson KSI8560 board.
>
> Signed-off-by: Alexandr Smirnov <[EMAIL PROTECTED]>
[snip]
> + enet0: [EMAIL PROTECTED] {
> + linux,network-index = <0>;
We're trying to get rid
>> Every occurrence of r7 here is wrong (and some of the r6). Is there
>> any reason to do this in assembler code at all?
>
> The fact that the obvious C code generates ... a call to __ucmpdi2? :)
Hrm? Here's the "obvious" C code, portable to all architectures
(modulo the specific types used, th
I'm trying to run my 2.6.14 Gentoo distro on a 7447A system I have
with different cache configurations (ie, write back vs write thru) for
both the kernel, system apps (sshd, etc) and user apps. I first
wanted to run entirely in Write-Thru to get a worst-case benchmark,
but after discovering (to my
On Tue, 2008-03-04 at 11:51 -0800, Andrew Morton wrote:
> hugetlb-correct-page-count-for-surplus-huge-pages.patch adds:
>
> if (page) {
> /*
> * This page is now managed by the hugetlb allocator and has
> * no users -- drop the buddy alloca
Paul Mackerras wrote:
> Segher Boessenkool writes:
>
>> Every occurrence of r7 here is wrong (and some of the r6). Is there
>> any reason to do this in assembler code at all?
>
> The fact that the obvious C code generates ... a call to __ucmpdi2? :)
So use the correct C code, not the obvious C
On Tue, 4 Mar 2008, Pekka Enberg wrote:
> Looking at the code, it's triggerable in 2.6.24.3 at least. Why we don't have
> a report yet, probably because (1) the default allocator is SLUB which doesn't
> suffer from this and (2) you need a big honkin' NUMA box that causes fallback
> allocations to
Segher Boessenkool writes:
> Every occurrence of r7 here is wrong (and some of the r6). Is there
> any reason to do this in assembler code at all?
The fact that the obvious C code generates ... a call to __ucmpdi2? :)
Paul.
___
Linuxppc-dev mailing li
On Tue, Mar 04 2008, at 17:15 +0100, Wolfgang Pfeiffer wrote:
>
>
> [ ... ]
> I uploaded this fresh kernel .deb, patched with your code, up to
> rapidshare:
> http://rapidshare.com/files/96992135/linux-image-2.6.25-rc3-g7704a8b-with-ben.s-pmu-patch_2008.02.29_powerpc.deb.html
>
> md5sum for th
On Tue, 2008-03-04 at 21:59 +0100, Segher Boessenkool wrote:
> >> More generally, the target interrupt descriptors (sense values, in
> >> particular) in a device tree interrupt map describe the interrupts as
> >> seen on the target interrupt controller, *not* as seen on this
> >> (source)
> >> in
>> More generally, the target interrupt descriptors (sense values, in
>> particular) in a device tree interrupt map describe the interrupts as
>> seen on the target interrupt controller, *not* as seen on this
>> (source)
>> interrupt domain. This should be obvious, but since the source
>> interru
Hi Ben
On Tue, Mar 04, 2008 at 05:15:18PM +0100, Wolfgang Pfeiffer wrote:
> Hi Ben, Gaudenz - Hi All
>
> On Mon, Mar 03 2008, at 17:27 +1100, Benjamin Herrenschmidt wrote:
> > The PMU backlight code would kick in during sleep/resume even on
> > machines that use a different backlight method. Thi
Andrew Morton wrote:
> On Tue, 4 Mar 2008 12:07:39 -0800 (PST)
> Christoph Lameter <[EMAIL PROTECTED]> wrote:
>
>> I think this is the correct fix.
>>
>> The NUMA fallback logic should be passing local_flags to kmem_get_pages()
>> and not simply the flags.
>>
>> Maybe a stable candidate since we
On Tue, 2008-03-04 at 21:39 +0100, Segher Boessenkool wrote:
> >> Using '8' is correct. PCI interrupts are *always* level sensitive and
> >> active
> >> low.
> >
> > Unless you use one of those strange bridges that stick not gates on the
> > PCI IRQ inputs :-) But I don't think that's the case on
>> Using '8' is correct. PCI interrupts are *always* level sensitive and
>> active
>> low.
>
> Unless you use one of those strange bridges that stick not gates on the
> PCI IRQ inputs :-) But I don't think that's the case on the 440EP.
More generally, the target interrupt descriptors (sense values
On Tue, 4 Mar 2008 12:07:39 -0800 (PST)
Christoph Lameter <[EMAIL PROTECTED]> wrote:
> I think this is the correct fix.
>
> The NUMA fallback logic should be passing local_flags to kmem_get_pages()
> and not simply the flags.
>
> Maybe a stable candidate since we are now simply
> passing on fl
>> Every occurrence of r7 here is wrong (and some of the r6).
>
> Can you elucidate?
Sure! It should read either "7" or "cr7".
>> Is there any reason to do this in assembler code at all?
>
> Is there any particular reason not to?
1) If written in assembler, it needs to be written for every
a
Christoph Lameter wrote:
> I think this is the correct fix.
>
> The NUMA fallback logic should be passing local_flags to kmem_get_pages()
> and not simply the flags.
>
> Maybe a stable candidate since we are now simply
> passing on flags to the page allocator on the fallback path.
>
> Signed-o
I think this is the correct fix.
The NUMA fallback logic should be passing local_flags to kmem_get_pages()
and not simply the flags.
Maybe a stable candidate since we are now simply
passing on flags to the page allocator on the fallback path.
Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]
On Tue, 4 Mar 2008, Pekka J Enberg wrote:
> On Tue, 4 Mar 2008, Christoph Lameter wrote:
> > Slab allocations should never be passed these flags since the slabs do
> > their own thing there.
> >
> > The following patch would clear these in slub:
>
> Here's the same fix for SLAB:
That is an imm
On Tue, 4 Mar 2008, Pekka Enberg wrote:
> > > >> [c9edf5f0] [c00b56e4]
> > .__alloc_pages_internal+0xf8/0x470
> > > >> [c9edf6e0] [c00e0458] .kmem_getpages+0x8c/0x194
> > > >> [c9edf770] [c00e1050] .fallback_alloc+0x194/0x254
> > > >> [c
On Tue, 4 Mar 2008, Christoph Lameter wrote:
> Slab allocations should never be passed these flags since the slabs do
> their own thing there.
>
> The following patch would clear these in slub:
Here's the same fix for SLAB:
diff --git a/mm/slab.c b/mm/slab.c
index 473e6c2..c6dbf7e 100644
--- a
On Wed, 05 Mar 2008 00:50:17 +0530
Kamalesh Babulal <[EMAIL PROTECTED]> wrote:
> Hi Andrew,
>
> kernel bug is triggered while running libhugetlbfs test with 2.6.25-rc3-mm1
> kernel
> over the x86 and power machines.
>
> [ cut here ]
> kernel BUG at mm/hugetlb.c:295!
> in
On Tue, 4 Mar 2008, Pekka Enberg wrote:
> > > I suspect the WARN_ON() is bogus although I really don't know that part
> > > of the code all too well. Mel?
> > >
> >
> > The warn-on is valid. A situation should not exist that allows both flags
> > to
> > be set. I suspect if remove-set_migra
(adding Christoph as cc)
On Tue, Mar 4, 2008 at 9:35 PM, Mel Gorman <[EMAIL PROTECTED]> wrote:
> > >> [c9edf5f0] [c00b56e4] .__alloc_pages_internal+0xf8/0x470
> > >> [c9edf6e0] [c00e0458] .kmem_getpages+0x8c/0x194
> > >> [c9edf770] [c00e1050] .fal
On (04/03/08 21:18), Pekka Enberg didst pronounce:
> Andrew Morton wrote:
> >> [c9edf5f0] [c00b56e4] .__alloc_pages_internal+0xf8/0x470
> >> [c9edf6e0] [c00e0458] .kmem_getpages+0x8c/0x194
> >> [c9edf770] [c00e1050] .fallback_alloc+0x194/0x254
> >> [c
Andrew Morton wrote:
> > [c9edf5f0] [c00b56e4] .__alloc_pages_internal+0xf8/0x470
> > [c9edf6e0] [c00e0458] .kmem_getpages+0x8c/0x194
> > [c9edf770] [c00e1050] .fallback_alloc+0x194/0x254
> > [c9edf820] [c00e14b0] .kmem_cache_alloc+0xd
Hi Andrew,
kernel bug is triggered while running libhugetlbfs test with 2.6.25-rc3-mm1
kernel
over the x86 and power machines.
[ cut here ]
kernel BUG at mm/hugetlb.c:295!
invalid opcode: [#1] SMP
last sysfs file: /sys/devices/system/node/possible
Modules linked in:
On Tue, Mar 04, 2008 at 03:37:00PM +1100, David Gibson wrote:
> * The Bison documentation explicitly permits yyerror() to be a
> variadic function, so fold yyerror() and yyerrorf() into a single
> printf-style function.
Then the bison documentation is not consistent with the bison
implementati
Use the generic pci_enable_resources() instead of the arch-specific code.
Unlike this arch-specific code, the generic version:
- checks PCI_NUM_RESOURCES (11), not 6, resources
- skips resources that have neither IORESOURCE_IO nor IORESOURCE_MEM set
- skips ROM resources unless IORESOU
Use the generic pci_enable_resources() instead of the arch-specific code.
Unlike this arch-specific code, the generic version:
- checks PCI_NUM_RESOURCES (11), not 6, resources
- skips resources that have neither IORESOURCE_IO nor IORESOURCE_MEM set
- skips ROM resources unless IORESOU
Use the generic pci_enable_resources() instead of the arch-specific code.
Unlike this arch-specific code, the generic version:
- skips resources that have neither IORESOURCE_IO nor IORESOURCE_MEM set
- skips ROM resources unless IORESOURCE_ROM_ENABLE is set
- checks for resource collis
Use the generic pci_enable_resources() instead of the arch-specific code.
Unlike this arch-specific code, the generic version:
- checks PCI_NUM_RESOURCES (11), not DEVICE_COUNT_RESOURCE (12), resources
- skips resources that have neither IORESOURCE_IO nor IORESOURCE_MEM set
- skips ROM
Use the generic pci_enable_resources() instead of the arch-specific code.
Unlike this arch-specific code, the generic version:
- checks for resource collisions with "!r->parent"
Signed-off-by: Bjorn Helgaas <[EMAIL PROTECTED]>
Index: work8/arch/x86/pci/common.c
==
Use the generic pci_enable_resources() instead of the arch-specific code.
Unlike this arch-specific code, the generic version:
- checks PCI_NUM_RESOURCES (11), not 6, resources
- skips resources that have neither IORESOURCE_IO nor IORESOURCE_MEM set
- skips ROM resources unless IORESOU
Use the generic pci_enable_resources() instead of the arch-specific code.
Unlike this arch-specific code, the generic version:
- checks PCI_NUM_RESOURCES (11), not 6, resources
- skips resources that have neither IORESOURCE_IO nor IORESOURCE_MEM set
- skips ROM resources unless IORESOU
Use the generic pci_enable_resources() instead of the arch-specific code.
The generic version is functionally equivalent, but uses dev_printk.
Signed-off-by: Bjorn Helgaas <[EMAIL PROTECTED]>
Index: work8/arch/powerpc/kernel/pci-common.c
===
Use the generic pci_enable_resources() instead of the arch-specific code.
Unlike this arch-specific code, the generic version:
- checks PCI_NUM_RESOURCES (11), not 6, resources
- skips resources that have neither IORESOURCE_IO nor IORESOURCE_MEM set
- skips ROM resources unless IORESOU
Use the generic pci_enable_resources() instead of the arch-specific code.
Unlike this arch-specific code, the generic version:
- checks for resource collisions with "!r->parent"
Signed-off-by: Bjorn Helgaas <[EMAIL PROTECTED]>
Index: work8/arch/mips/pci/pci.c
Use the generic pci_enable_resources() instead of the arch-specific code.
Unlike this arch-specific code, the generic version:
- checks PCI_NUM_RESOURCES (11), not 6, resources
- skips resources that have neither IORESOURCE_IO nor IORESOURCE_MEM set
- skips ROM resources unless IORESOU
Use the generic pci_enable_resources() instead of the arch-specific code.
Unlike this arch-specific code, the generic version:
- does not check for a NULL dev pointer
- skips resources that have neither IORESOURCE_IO nor IORESOURCE_MEM set
Signed-off-by: Bjorn Helgaas <[EMAIL PROTECTED]>
Use the generic pci_enable_resources() instead of the arch-specific code.
Unlike this arch-specific code, the generic version:
- checks PCI_NUM_RESOURCES (11), not 6, resources
- skips resources that have neither IORESOURCE_IO nor IORESOURCE_MEM set
- skips ROM resources unless IORESOU
Use the generic pci_enable_resources() instead of the arch-specific code.
Unlike this arch-specific code, the generic version:
- skips resources unless requested in "mask"
- skips ROM resources unless IORESOURCE_ROM_ENABLE is set
- checks for resource collisions with "!r->parent"
Sign
Use the generic pci_enable_resources() instead of the arch-specific code.
Unlike this arch-specific code, the generic version:
- checks PCI_NUM_RESOURCES (11), not 6, resources
- skips resources that have neither IORESOURCE_IO nor IORESOURCE_MEM set
- skips ROM resources unless IORESOU
Each architecture has its own pcibios_enable_resources() implementation.
These differ in many minor ways that have nothing to do with actual
architectural differences. Follow-on patches will make most arches
use this generic version instead.
This version is based on powerpc, which seemed most up-
This series replaces most of the arch-specific pcibios_enable_resources()
implementations with a single generic pci_enable_resources().
I think this is ready for -mm, but of course, I'm still interested in
any other comments.
Changes between v2 and v3:
- Renamed the generic version to pc
On Tue, 04 Mar 2008 18:42:19 +0530 Kamalesh Babulal
<[EMAIL PROTECTED]> wrote:
> > 3) Third attempt kernel booted up but had the following call trace 264
> times while running
> > test
> >
> > Badness at include/linux/gfp.h:110
> > NIP: c00b4ff0 LR: c00b4fa0 CTR: c019c
On Tue, 04 Mar 2008 18:42:19 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> wrote:
> 3) Third attempt kernel booted up but had the following call trace 264 times
> while running
> test
>
> Badness at include/linux/gfp.h:110
> NIP: c00b4ff0 LR: c00b4fa0 CTR: c019cdb4
> REGS: c
On Tue, 04 Mar 2008 15:40:56 +0100 Michael Neuling <[EMAIL PROTECTED]> wrote:
> In message <[EMAIL PROTECTED]> you wrote:
> > Hi Andrew,
> >
> > The 2.6.25-rc3-mm1 kernel panics while bootup on power box. The machine
> > boote
> d up
> > without the panic on the third attempt, but badness call t
On Tue, Mar 04, 2008 at 04:37:28PM +, David Woodhouse wrote:
>
> On Sun, 2008-03-02 at 22:53 +0100, Segher Boessenkool wrote:
> > Every occurrence of r7 here is wrong (and some of the r6).
>
> Can you elucidate?
They were being used as condition registers rather than GPRs.
> > Is there an
On Sun, 2008-03-02 at 22:53 +0100, Segher Boessenkool wrote:
> Every occurrence of r7 here is wrong (and some of the r6).
Can you elucidate?
> Is there any reason to do this in assembler code at all?
Is there any particular reason not to?
--
dwmw2
__
Add default config for Emerson KSI8560 board.
Signed-off-by: Alexandr Smirnov <[EMAIL PROTECTED]>
arch/powerpc/configs/ksi8560_defconfig | 899 +
1 file changed, 899 insertions(+)
diff --git a/arch/powerpc/configs/ksi8560_defconfig
b/arch/powerpc/configs/ksi856
Add device tree file for Emerson KSI8560 board.
Signed-off-by: Alexandr Smirnov <[EMAIL PROTECTED]>
arch/powerpc/boot/dts/ksi8560.dts | 267 ++
1 file changed, 267 insertions(+)
diff --git a/arch/powerpc/boot/dts/ksi8560.dts
b/arch/powerpc/boot/dts/ksi8560.
Add boot wrapper for Emerson KSI8560 board.
Signed-off-by: Alexandr Smirnov <[EMAIL PROTECTED]>
arch/powerpc/boot/Makefile |1 +
arch/powerpc/boot/wrapper |2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/powerpc/boot/Makefile b/arch/powerpc/boot/Makefile
index e
The KSI8560 is a single compact, mid-, or full-size Advanced Mezzanine Card
(AdvancedMC™) based on the Freescale™ Semiconductor MPC8560 PowerQUICC III™
microprocessor. This product will serve in data and signaling applications such
as signaling gateways (SGW) and softswitch signaling interface car
Hi Ben, Gaudenz - Hi All
On Mon, Mar 03 2008, at 17:27 +1100, Benjamin Herrenschmidt wrote:
> The PMU backlight code would kick in during sleep/resume even on
> machines that use a different backlight method. This appears to
> break sleep on my PowerBook, though I can't test that patch at
> the mo
Hi Paul,
I've added short description for this board as header for the base support
patch.
Hope this is enough, board diagram is available at Emerson website. Let me know
more information needed.
Thanks,
Alexandr.
___
Linuxppc-dev mailing list
Linuxpp
In message <[EMAIL PROTECTED]> you wrote:
> Hi Andrew,
>
> The 2.6.25-rc3-mm1 kernel panics while bootup on power box. The machine boote
d up
> without the panic on the third attempt, but badness call trace were seen whil
e running
> tests
>
> 1) The kernel panic on first attempt
>
> Unable to h
[EMAIL PROTECTED] wrote:
> Now I get an "inconsistent locking state", but I need help in
> trying to
> fiure out what I should look for.
I did figure out htat lockdep only complains about inonsistent locking
state when PREEMPT_RT paches are applied.
Now I just need some help interpreting this outp
Hi Andrew,
The 2.6.25-rc3-mm1 kernel panics while bootup on power box. The machine booted
up
without the panic on the third attempt, but badness call trace were seen while
running
tests
1) The kernel panic on first attempt
Unable to handle kernel paging request for data at address 0x
F
On Wed, 5 Mar 2008 00:29:56 +0800 Zhang Wei <[EMAIL PROTECTED]> wrote:
>
> + if (!(rmem->virt = dma_alloc_coherent(NULL, rmem->size,
> + &rmem->iores.start, GFP_KERNEL))) {
Please separate assignments from tests.
> + if ((ret = rio_space_claim(rmem))) {
Again
On Wed, 5 Mar 2008 00:29:51 +0800 Zhang Wei <[EMAIL PROTECTED]> wrote:
>
> + if (!(rionet_active = (struct rio_dev **)__get_free_pages(GFP_KERNEL,
> + mport->sys_size ? __ilog2(sizeof(void *)) + 4
> + : 0))) {
Please separate the assignm
On Wed, 5 Mar 2008 00:29:50 +0800 Zhang Wei <[EMAIL PROTECTED]> wrote:
>
> +static struct of_device_id fsl_of_rio_rpn_ids[] = {
const, please.
--
Cheers,
Stephen Rothwell[EMAIL PROTECTED]
http://www.canb.auug.org.au/~sfr/
pgpLbcHShFXuD.pgp
Description: PGP signature
__
Hi Ben,
On Tue, Mar 04, 2008 at 07:22:19PM +1100, Benjamin Herrenschmidt wrote:
>
> On Tue, 2008-03-04 at 09:08 +0100, Philippe De Muyter wrote:
> > With ARCH=ppc, all those interrupt's info's are hardcoded in the .c
> > files.
> > But I expected I could fill the dts file for ARCH=powerpc from in
Hi Ben,
On Tue, Mar 04, 2008 at 08:26:14AM +1100, Benjamin Herrenschmidt wrote:
>
> > > Maybe your PCI interrupt-map is wrong...
> >
> > Is the PCI-interrupt map that part of the dts file :
> >
> > interrupt-map = <
> >
> > /* IDSEL 0x02 */
> >
The user can select memory mapping mode or message mode in CONFIG.
It is also an example to how-to use memory mapping driver for RapidIO.
Signed-off-by: Zhang Wei <[EMAIL PROTECTED]>
---
drivers/net/Kconfig | 10 ++
drivers/net/rionet.c | 321 ++
Change RapidIO doorbell source and target ID field to 16-bit for
support large system size, which max rio devid is 65535.
Signed-off-by: Zhang Wei <[EMAIL PROTECTED]>
---
arch/powerpc/sysdev/fsl_rio.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/powerpc/sys
Get RapidIO space resource by catting /proc/riores.
Signed-off-by: Zhang Wei <[EMAIL PROTECTED]>
---
drivers/rapidio/Kconfig |8 +++
drivers/rapidio/rio.c | 119 +++
2 files changed, 127 insertions(+), 0 deletions(-)
diff --git a/drivers/rapidio
Add the RapidIO master port maintance and doorbell IO windows to
RIO space resources.
Signed-off-by: Zhang Wei <[EMAIL PROTECTED]>
---
arch/powerpc/sysdev/fsl_rio.c | 26 +-
include/linux/rio.h |1 +
2 files changed, 22 insertions(+), 5 deletions(-)
diff -
Add FSL RapidIO controller (MPC85xx, MPC86xx) memory operation
functions, which include map inbound/outbound window and
unmap incound/outbound window.
Signed-off-by: Zhang Wei <[EMAIL PROTECTED]>
---
arch/powerpc/sysdev/fsl_rio.c | 202 +
1 files changed,
The bitmap is the simplest RapidIO space allocation arithmetic.
It uses the fixed size space for each RapidIO device in the
inter-connection network.
Signed-off-by: Zhang Wei <[EMAIL PROTECTED]>
---
arch/powerpc/sysdev/fsl_rio.c | 11 +
drivers/rapidio/Kconfig |2 +
driver
The memory mapping driver is used for mapping IO address
and system memory address space to RapidIO address space.
The driver support IO space allocation, RapidIO space
inbound window and outbound window creation.
The system can access other RapidIO device by outbound
window and can be accessed by
Signed-off-by: Zhang Wei <[EMAIL PROTECTED]>
---
arch/powerpc/sysdev/fsl_rio.c | 71 +
1 files changed, 71 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/sysdev/fsl_rio.c b/arch/powerpc/sysdev/fsl_rio.c
index 1535d12..585f7d2 100644
--- a/arch/po
Signed-off-by: Zhang Wei <[EMAIL PROTECTED]>
---
arch/powerpc/sysdev/fsl_rio.c | 74 +++-
include/linux/rio.h |6 +++
2 files changed, 70 insertions(+), 10 deletions(-)
diff --git a/arch/powerpc/sysdev/fsl_rio.c b/arch/powerpc/sysdev/fsl_rio.c
i
Signed-off-by: Zhang Wei <[EMAIL PROTECTED]>
---
arch/powerpc/kernel/Makefile |1 -
arch/powerpc/kernel/rio.c | 52 ---
arch/powerpc/sysdev/fsl_rio.c | 110 ++---
arch/powerpc/sysdev/fsl_rio.h | 20 ---
4 files changed, 102 inse
Signed-off-by: Zhang Wei <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/86xx/mpc86xx_hpcn.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/platforms/86xx/mpc86xx_hpcn.c
b/arch/powerpc/platforms/86xx/mpc86xx_hpcn.c
index cfbe8c5..4a3e421 100644
--- a/arch/pow
Signed-off-by: Zhang Wei <[EMAIL PROTECTED]>
---
arch/powerpc/boot/dts/mpc8641_hpcn.dts | 12
1 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/boot/dts/mpc8641_hpcn.dts
b/arch/powerpc/boot/dts/mpc8641_hpcn.dts
index 79385bc..4b296af 100644
--- a/arch/pow
The RapidIO system size will auto probe in RIO setup. The route
table and rionet_active in rionet.c are changed to be allocated
dynamically according the system size.
Signed-off-by: Zhang Wei <[EMAIL PROTECTED]>
---
arch/powerpc/sysdev/fsl_rio.c |6 +
drivers/net/rionet.c | 16
The original RapidIO driver suppose there is only one mpc85xx RIO
controller in system. So, some data structures are defined as
mpc85xx_rio global, such as 'regs_win', 'dbell_ring', 'msg_tx_ring'.
Now, I changed them to mport's private members. And you can define
multi RIO OF-nodes in dts file for
Signed-off-by: Zhang Wei <[EMAIL PROTECTED]>
---
include/asm-powerpc/rio.h | 18 ++
include/asm-ppc/rio.h | 18 --
2 files changed, 18 insertions(+), 18 deletions(-)
create mode 100644 include/asm-powerpc/rio.h
delete mode 100644 include/asm-ppc/rio.h
dif
The driver is also fit for Freescale MPC8641 processor.
Signed-off-by: Zhang Wei <[EMAIL PROTECTED]>
---
arch/powerpc/sysdev/fsl_rio.c | 80
1 files changed, 40 insertions(+), 40 deletions(-)
diff --git a/arch/powerpc/sysdev/fsl_rio.c b/arch/powerpc/sys
Signed-off-by: Zhang Wei <[EMAIL PROTECTED]>
---
arch/powerpc/Kconfig| 13 +
arch/powerpc/platforms/86xx/Kconfig |1 +
2 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
index 485513c..70789e8 100644
--- a/a
On Tue, 2008-03-04 at 09:08 +0100, Philippe De Muyter wrote:
> With ARCH=ppc, all those interrupt's info's are hardcoded in the .c
> files.
> But I expected I could fill the dts file for ARCH=powerpc from info's
> I
> could collect in /proc on a running ARCH=ppc linux without dts file
> for the sa
Hi Ben,
On Tue, Mar 04, 2008 at 08:41:33AM +1100, Benjamin Herrenschmidt wrote:
>
> > Thanks
> >
> > The following seems important also :
> >
> > /*
> > interrupts = <18 2>;
> > */
> > /* interrupts number are coded in hexa ! */
> > interrupts = <
Hi Scott,
On Mon, Mar 03, 2008 at 03:55:26PM -0600, Scott Wood wrote:
> Philippe De Muyter wrote:
>> The following seems important also :
>> /*
>> interrupts = <18 2>;
>> */
>> /* interrupts number are coded in hexa ! */
>> interrupts = <12 2 19 2 1a
100 matches
Mail list logo
