spu_create and spu_run are wrapped by the cell syscall layer, so
we don't need the asmlinkage.
Signed-off-by: Jeremy Kerr <[EMAIL PROTECTED]>
---
include/asm-powerpc/spu.h |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/asm-powerpc/spu.h b/include/asm-powerpc/s
From: Sebastian Siewior <[EMAIL PROTECTED]>
There are a few symbols used only in one file within spufs; this change
makes them static where suitable.
Signed-off-by: Sebastian Siewior <[EMAIL PROTECTED]>
Signed-off-by: Jeremy Kerr <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/cell/spu_base.c
From: Michael Ellerman <[EMAIL PROTECTED]>
Because the SPU coredump code might be built as part of a module (spufs),
we have a stub which is called by the coredump code, this routine then calls
into spufs if it's loaded.
Unfortunately the stub returns -ENOSYS if spufs is not loaded, which is
inte
From: Michael Ellerman <[EMAIL PROTECTED]>
Currently the spu coredump code doesn't respect the ulimit, it should.
Signed-off-by: Michael Ellerman <[EMAIL PROTECTED]>
Signed-off-by: Jeremy Kerr <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/cell/spufs/coredump.c |4
1 file changed, 4 in
From: Andre Detsch <[EMAIL PROTECTED]>
Affinity reference point location (gang->aff_ref_spu) is reset
when the whole gang is descheduled. However, the last member of
a gang can be descheduled while we are trying to schedule another
member of the gang. This was leading to a race condition, and
the
From: Michael Ellerman <[EMAIL PROTECTED]>
Unfortunately GDB expects some of the SPU coredump values to be identical
in format to what is found in spufs. This means we need to dump some of
the values as ASCII strings, not the actual values.
Because we don't know what the values will be, we always
Based on an initial patch from Sebastian Siewior
<[EMAIL PROTECTED]>
spu_harvest isn't used, remove it.
Signed-off-by: Jeremy Kerr <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/cell/spufs/switch.c | 13 -
1 file changed, 13 deletions(-)
diff --git a/arch/powerpc/platforms/cell/s
From: Michael Ellerman <[EMAIL PROTECTED]>
Extract the logic for searching through the file descriptors for spu contexts
into a separate routine, coredump_next_context(), so we can use it elsewhere
in future. In the process we flatten the for loop, and move the NOSCHED test
into coredump_next_cont
From: Michael Ellerman <[EMAIL PROTECTED]>
To start with, arch_notes_size() etc. is a little too ambiguous a name for
my liking, so change the function names to be more explicit.
Calling through macros is ugly, especially with hidden parameters, so don't
do that, call the routines directly.
Use
From: Michael Ellerman <[EMAIL PROTECTED]>
Signed-off-by: Michael Ellerman <[EMAIL PROTECTED]>
Signed-off-by: Jeremy Kerr <[EMAIL PROTECTED]>
Acked-by: Arnd Bergmann <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/cell/spufs/file.c |8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
Based on an original patch from Masato Noguchi
<[EMAIL PROTECTED]>.
We're currently not restoring the SPE decrementer as specified by the
CBE handbook. This change fixes our implementation to match, and makes
the function read more like the docs.
Signed-off-by: Jeremy Kerr <[EMAIL PROTECTED]>
--
From: Michael Ellerman <[EMAIL PROTECTED]>
The spufs_coredump_read array is NULL terminated, and we also store the size.
We only need one or the other, and the other arrays in file.c are NULL
terminated, so do that.
Signed-off-by: Michael Ellerman <[EMAIL PROTECTED]>
Signed-off-by: Jeremy Kerr <[
From: Michael Ellerman <[EMAIL PROTECTED]>
The routine to dump the local store, __spufs_mem_read(), does not take the
spu_lslr_RW value into account - so we shouldn't check it when we're
calculating the size either.
Signed-off-by: Michael Ellerman <[EMAIL PROTECTED]>
Signed-off-by: Jeremy Kerr <[
At present, a built-in spufs will not use the spufs_calls callbacks, but
directly call sys_spu_create. This saves us an indirect branch, but
means we have duplicated functions - one for CONFIG_SPU_FS=y and one for
=m.
This change unifies the spufs syscall path, and provides access to the
spufs_cal
From: Michael Ellerman <[EMAIL PROTECTED]>
It makes sense to stop the SPU processes as soon as possible. Also if we
dont acquire_saved() I think there's a possibility that the value in
csa.priv2.spu_lslr_RW won't be accurate.
Signed-off-by: Michael Ellerman <[EMAIL PROTECTED]>
Signed-off-by: Jere
From: Sebastian Siewior <[EMAIL PROTECTED]>
According to the comment in spufs_init_isolated_loader(), the isolated
loader should be aligned on a 16 byte boundary.
ARCH_{KMALLOC,SLAB}_MINALIGN is not defined so only 8 byte alignment is
guaranteed.
This patch enforces alignment via __get_free_pages
From: Michael Ellerman <[EMAIL PROTECTED]>
The spufs_coredump_reader array contains the size of the data that will be
returned by the read routine. Currently these are specified as literals, and
though some are obvious, sizeof(u32) == 4, others are not, 69 * 8 == ???
Instead, use sizeof() whatev
do_spu_create doesn't need the asmlinkage qualifier; remove it.
Signed-off-by: Jeremy Kerr <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/cell/spufs/syscalls.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc/platforms/cell/spufs/syscalls.c
b/arch/powerpc/
From: Michael Ellerman <[EMAIL PROTECTED]>
This patch adds DEFINE_SPUFS_ATTRIBUTE(), a wraper around
DEFINE_SIMPLE_ATTRIBUTE which does the specified locking for the get
routine for us.
Unfortunately we need two get routines (a locked and unlocked version) to
support the coredump code. This patch
From: Michael Ellerman <[EMAIL PROTECTED]>
Remove the ctx_info struct entirely, and also the ctx_info_list. This fixes
a race where two processes can clobber each other's ctx_info structs.
Instead of using the list, we just repeat the search through the file
descriptor table.
Signed-off-by: Mich
From: Michael Ellerman <[EMAIL PROTECTED]>
Rework spufs_coredump_extra_notes_write() to check for and return errors.
If we're coredumping to a pipe we can't trust file->f_pos, we need to
maintain the foffset value passed to us. The cleanest way to do this is
to have the low level write routine in
From: Christoph Hellwig <[EMAIL PROTECTED]>
find_victim can dereference a NULL pointer when iterating over the list
of victim spus because list_mutex only guarantees spu->ct to be stable,
but of course not to be non-NULL.
Also fix find_victim to not call spu_unbind_context without list_mutex
beca
From: Michael Ellerman <[EMAIL PROTECTED]>
Because spufs might be built as a module, we can't have other parts of the
kernel calling directly into it, we need stub routines that check first if the
module is loaded.
Currently we have two structures which hold callbacks for these stubs, the
syscall
We don't want SPE programs to be able to flood the kernel log by
invoking the SPE callback handler, so don't enable DEBUG for
spu_callbacks.c by default.
Signed-off-by: Jeremy Kerr <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/cell/spu_callbacks.c |2 +-
1 file changed, 1 insertion(+), 1 de
From: Michael Ellerman <[EMAIL PROTECTED]>
The SPUFS attribute get routines take a void * because the generic attribute
code doesn't know what sort of data it's passing around.
However our internal __spufs_get_foo() routines can take a spu_context *
directly, which saves plonking it in and out of
Currently the rtc driver, rtc-ds1742.c uses an unsigned long to store
the base mmio address of the NVRAM/RTC. This breaks on systems like
PowerPC 440, which is a 32-bit core with 36-bit physical addresses: IO
on the system, including the RTC, is typically above the 4GB point,
and cannot fit into a
The cast to u32 * isn't required, of_get_property returns a void *.
Signed-off-by: Jeremy Kerr <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/cell/spu_manage.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc/platforms/cell/spu_manage.c
b/arch/powerpc/plat
Use a temporary variable of the correct type instead.
Also, this allows us to check the return value in ls_uarts_init, to
avoid dereferencing a null pointer if required properties aren't
present.
Signed-off-by: Jeremy Kerr <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/embedded6xx/ls_uart.c |
On Thu, Sep 13, 2007 at 12:16:40PM +0400, Vitaly Bordug wrote:
[snip]
> > This looks bogus. You're replacing the old crap immr_map() functions,
> > which ioremap()ed the registers every time, with a much simpler
> > version which uses an established-once mapping of the register
> > region. AFAICT
Paulus,
Could you take this as well for 2.6.24?
Remove barriers from the SLB shadow buffer update
http://patchwork.ozlabs.org/linuxppc/patch?id=13116
Mikey
In message <[EMAIL PROTECTED]> you wrote:
> David Gibson (2):
> [POWERPC] Move bootwrapper's strchr() and strncmp() from .h to st
On Thu, Sep 13, 2007 at 08:29:13AM -0500, Olof Johansson wrote:
> On Thu, Sep 13, 2007 at 01:26:26PM +0200, Juergen Beisert wrote:
> > Hi,
> >
> > I'm using an MPC5200B based system with various external connected devices
> > to
> > its LocalPlusBus. On other architectures I would register them
> Update mpc7448hpc2 device tree to be compatible for tsi109 chip.
Do all those boards have a tsi109? If not, this patch is
incorrect. If they do, is tsi109 actually backward-compatible
to tsi108? That is, will a driver that knows about tsi108
only work correctly on a tsi109?
Also, all those n
> EHCI OF bindings for PowerPC 440EPx Sequoia.
Those aren't bindings, they are examples. Bindings are pieces
of documentation that describe what device-specific properties
mean what, what standard properties are required with what
values, etc.
Examples are good to have, of course.
One thing you
> + PowerPC,[EMAIL PROTECTED] {
Maybe it would be good to use "PowerPC,e500" instead -- it would
make it easier to probe for the actual CPU type, that way. Not
that Linux uses the name/compatible here at all ;-)
>>>
>>> I thought about this, not sure what the best s
On Sep 13, 2007, at 11:53 AM, Segher Boessenkool wrote:
>>> What is a "front side cache"? What exactly does it cache? If it's
>>> a cache for one CPU only, that fact should be shown in the device
>>> tree somehow.
>>
>> Its in front of the memory controllers. Its not specific to a
>> given C
Kumar Gala wrote:
> No problem. The cpm2_* code in the kernel is used on 85xx's that have a
> CPM and I don't think we have that much ifdef for 85xx specific CPM
> foo. Only thing I can think of is this bit in cpm2.h:
>
> #if defined(CONFIG_8272) || defined(CONFIG_MPC8555)
> #define CPM_DATAON
Guys,
If you have things you want or think should go into 2.6.24 please
speak up now!
- k
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
On Sep 13, 2007, at 11:05 AM, Scott Wood wrote:
> On Thu, Sep 13, 2007 at 01:39:58AM -0500, Kumar Gala wrote:
>>> + CS: chipselect {
>>
>> We need to document this in booting-without-of.
>
> OK.
cool. Want to make sure we can encompass the 83xx/85xx/86xx local
bus in there.
>>> +
From: Timur Tabi <[EMAIL PROTECTED]>
The current definition of struct ccsr_guts in immap_86xx.h was for 85xx.
This patch fixes that and replaces the vague integer types with sized types
of the correct endianness. The unused struct ccsr_pci is also deleted.
Signed-off-by: Timur Tabi <[EMAIL PROTE
From: Timur Tabi <[EMAIL PROTECTED]>
This patch adds the clrsetbits_xxx() macros, which are used to set and clear
multiple bits in a single read-modify-write operation. Specify the bits to
clear in the 'clear' parameter and the bits to set in the 'set' parameter.
These macros can also be used to
From: Anton Vorontsov <[EMAIL PROTECTED]>
mmc_spi already tested to work. When it will hit mainline
the only change that will be needed is replacing "spidev"
with "mmc_spi".
Signed-off-by: Anton Vorontsov <[EMAIL PROTECTED]>
Signed-off-by: Kumar Gala <[EMAIL PROTECTED]>
---
arch/powerpc/boot/dts
From: John Rigby <[EMAIL PROTECTED]>
Use idx as index into mpc52xx_uart_nodes instead of i
Signed-off-by: John Rigby <[EMAIL PROTECTED]>
Signed-off-by: Kumar Gala <[EMAIL PROTECTED]>
---
drivers/serial/mpc52xx_uart.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drive
From: Anton Vorontsov <[EMAIL PROTECTED]>
Add helper function to setup SPI bus/device information
Signed-off-by: Anton Vorontsov <[EMAIL PROTECTED]>
Signed-off-by: Kumar Gala <[EMAIL PROTECTED]>
---
arch/powerpc/sysdev/fsl_soc.c | 87 +
arch/powerpc/sysd
From: Scott Wood <[EMAIL PROTECTED]>
These I/O accessors will be used in code under drivers/,
which is expected to still work in arch/ppc.
Signed-off-by: Scott Wood <[EMAIL PROTECTED]>
Signed-off-by: Kumar Gala <[EMAIL PROTECTED]>
---
include/asm-ppc/io.h |3 +++
1 files changed, 3 insertion
From: Anton Vorontsov <[EMAIL PROTECTED]>
This is needed to configure and control QE pario pins from the kernel.
Signed-off-by: Anton Vorontsov <[EMAIL PROTECTED]>
Signed-off-by: Kumar Gala <[EMAIL PROTECTED]>
---
include/asm-powerpc/qe.h |3 +++
1 files changed, 3 insertions(+), 0 deletions
We get warnings like the following from the various ppc32 head*.S files:
WARNING: vmlinux.o(.text+0x358): Section mismatch: reference to
.init.text:early_init (between 'skpinv' and 'interrupt_base')
WARNING: vmlinux.o(.text+0x380): Section mismatch: reference to
.init.text:machine_init (between
Make it so that SPE support can be determined at runtime. This is similiar
to how we handle AltiVec. This allows us to have SPE support built in and
work on processors with and without SPE.
Signed-off-by: Kumar Gala <[EMAIL PROTECTED]>
---
arch/powerpc/kernel/cputable.c | 23 +++--
Now that the generic code doesn't assign resources for Freescale
PHBs we dont have to explicitly exclude it.
Signed-off-by: Kumar Gala <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/83xx/mpc8313_rdb.c |2 --
arch/powerpc/platforms/83xx/mpc832x_mds.c |1 -
arch/powerpc/platforms/83xx/mpc83
Removed the following cruft from .dts files:
* 32-bit in cpu node -- doesn't exist in any spec and not used by kernel
* removed built-in (chrp legacy)
* Removed #interrupt-cells in places they don't need to be set
* Fixed ranges on lite5200*
* Removed clock-frequency from i8259 pic node, not sure w
From: Scott Wood <[EMAIL PROTECTED]>
1. Update the way get_brgfreq() finds things in the device tree.
It now uses names that are less namespace polluting. The old names
are supported until all boards are converted.
2. "size" is changed from unsigned int to int, to match what
of_get_property() e
Added basic board port for MPC8572 DS reference platform that is
similiar to the MPC8544/33 DS reference platform in uniprocessor mode.
Signed-off-by: Kumar Gala <[EMAIL PROTECTED]>
---
arch/powerpc/boot/dts/mpc8572ds.dts | 404
arch/powerpc/configs/mpc8572_ds_defconfig | 1496 +++
This adds code to handle alignment traps generated by the following
SPE (signal processing engine) load/store instructions, by emulating
the instruction in the kernel (as is done for other instructions that
generate alignment traps):
evldd[x] Vector Load Double Word into Double Word [Index
From: Jon Loeliger <[EMAIL PROTECTED]>
Signed-off-by: Jon Loeliger <[EMAIL PROTECTED]>
Signed-off-by: Kumar Gala <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/85xx/mpc85xx_ads.c | 13 -
arch/powerpc/platforms/85xx/mpc85xx_cds.c | 13 -
arch/powerpc/platforms/85xx/mpc8
From: Jon Loeliger <[EMAIL PROTECTED]>
Signed-off-by: Jon Loeliger <[EMAIL PROTECTED]>
Signed-off-by: Kumar Gala <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/86xx/mpc86xx_hpcn.c | 14 ++
1 files changed, 2 insertions(+), 12 deletions(-)
diff --git a/arch/powerpc/platforms/86xx/mp
From: Guennadi Liakhovetski <[EMAIL PROTECTED]>
1. Fix RTC type - it is a rs5c372a, not rs5c372b
2. Configure both UART interrupts edge-triggered
3. Add a license header to ls_uart.c
4. Check for running on linkstation in a late_initcall() function. Needed
for multiplatform builds, even though
From: Roy Zang <[EMAIL PROTECTED]>
Update mpc7448hpc2 device tree to be compatible for tsi109 chip.
Signed-off-by: Roy Zang <[EMAIL PROTECTED]>
Signed-off-by: Kumar Gala <[EMAIL PROTECTED]>
---
arch/powerpc/boot/dts/mpc7448hpc2.dts | 13 +++--
1 files changed, 7 insertions(+), 6 deleti
Renamed functions in 85xx_ds from 8544 to 85xx.
Kept an unique machine def/probe for the MPC8544 DS board to
handle some subtle differences between the future board based
on the DS platform.
Also fixed building w/o CONFIG_PCI and minor whitespace fixes.
Signed-off-by: Kumar Gala <[EMAIL PROTECTE
Renamed the mpc8544_ds.c board code to mpc85xx_ds.c to make it more
generic in prep for other boards based on the same platform.
Signed-off-by: Kumar Gala <[EMAIL PROTECTED]>
---
arch/powerpc/configs/mpc8544_ds_defconfig |2 +-
arch/powerpc/platforms/85xx/Kconfig |8 +-
arch/powerpc
The ucc_geth_mii code is based on the gianfar_mii code that use to include
ocp.h. ucc never need this and it causes issues when we want to kill
arch/ppc includes from arch/powerpc.
Signed-off-by: Kumar Gala <[EMAIL PROTECTED]>
---
drivers/net/ucc_geth_mii.c |1 -
1 files changed, 0 insertion
This is the set of patches in:
master.kernel.org:/pub/scm/linux/kernel/git/galak/powerpc.git for-2.6.24
Posted here so everyone knows what's going in. I've asked Paul to pull this
into
his for-2.6.24 branch.
(Sorry for anyone getting duplicates of this, sent to [EMAIL PROTECTED] not
[
On Sep 13, 2007, at 11:56 AM, Segher Boessenkool wrote:
* built-in for non-standard buses (ISA, PCI)
>>>
>>> "built-in" is some weird CHRP property, so yes we don't need it
>>> or want it.
>>
>> Do you suggest we get ride of it from ISA nodes as well?
>
> Yes. You aren't CHRP so you don't h
Please pull from 'for-2.6.24' branch of
master.kernel.org:/pub/scm/linux/kernel/git/galak/powerpc.git for-2.6.24
to receive the following updates:
arch/powerpc/boot/dts/holly.dts |1
arch/powerpc/boot/dts/kuroboxHD.dts |6
arch/powerpc/boot/dts/kuro
Segher Boessenkool wrote:
What tree are you using? Commit
804ace8881d211ac448082e871dd312132393049
in Paul's git tree should have fixed that.
>>>
>>> Strange, I don't see that commit -- maybe gitweb is broken, or
>>> maybe the patch was superseded, or maybe it just disappeared?
>>>
>>> What tree are you using? Commit
>>> 804ace8881d211ac448082e871dd312132393049
>>> in Paul's git tree should have fixed that.
>>
>> Strange, I don't see that commit -- maybe gitweb is broken, or
>> maybe the patch was superseded, or maybe it just disappeared?
>> It's still shown in patchworks wi
EHCI OF bindings for PowerPC 440EPx Sequoia.
Signed-off-by: Valentine Barshak <[EMAIL PROTECTED]>
---
arch/powerpc/boot/dts/sequoia.dts |7 +++
1 files changed, 7 insertions(+)
diff -ruN linux-2.6.orig/arch/powerpc/boot/dts/sequoia.dts
linux-2.6.bld/arch/powerpc/boot/dts/sequoia.dts
---
On Sep 13, 2007, at 12:06 PM, Segher Boessenkool wrote:
+ PowerPC,[EMAIL PROTECTED] {
>>>
>>> Maybe it would be good to use "PowerPC,e500" instead -- it would
>>> make it easier to probe for the actual CPU type, that way. Not
>>> that Linux uses the name/compatible here at all ;-)
On Thu, 13 Sep 2007 21:57:02 +0400
Valentine Barshak <[EMAIL PROTECTED]> wrote:
> Some PowerPC systems have a built-in EHCI controller.
> This is a device tree aware version of the EHCI controller driver.
> Currently it's been tested on the PowerPC 440EPx Sequoia board.
> Other platforms can be ad
On Thu, Sep 13, 2007 at 01:16:31AM +1000, Paul Mackerras wrote:
> asm-generic/termios.h).
>
> Signed-off-by: Paul Mackerras <[EMAIL PROTECTED]>
Acked-by: Alan Cox <[EMAIL PROTECTED]>
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.o
This patch adapts the ppc64 code to use the generic parse_crashkernel()
function introduced in the generic patch of that series.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/powerpc/kernel/machine_kexec.c | 52 ++--
1 file changed, 26 insertions(+
Some PowerPC systems have a built-in EHCI controller.
This is a device tree aware version of the EHCI controller driver.
Currently it's been tested on the PowerPC 440EPx Sequoia board.
Other platforms can be added later.
The code is based on the ehci-ppc-soc driver by Stefan Roese <[EMAIL
PROTECTE
David Gibson (2):
[POWERPC] Move bootwrapper's strchr() and strncmp() from .h to string.S
[POWERPC] Document and implement an improved flash device binding for
powerpc
Geert Uytterhoeven (1):
[POWERPC] PS3: Add new LV1 error codes
Geoff Levand (1):
[POWERPC] PS3: Enhance
> Removed the following cruft from .dts files:
> * 32-bit in cpu node -- doesn't exist in any spec and not used by
> kernel
> * removed built-in (chrp legacy)
> * Removed #interrupt-cells in places they don't need to be set
> * Fixed ranges on lite5200*
> * Removed clock-frequency from i8259 pic n
> Hi, Dan,
>
> Does I have followed your new API? :-)
>
[..]
> > > +static struct dma_chan
> > *of_find_dma_chan_by_phandle(phandle phandle)
> > > +{
> > > + struct device_node *np;
> > > + struct dma_chan *chan;
> > > + struct fsl_dma_device *fdev;
> > > +
> > > + np = of_f
>>> + PowerPC,[EMAIL PROTECTED] {
>>
>> Maybe it would be good to use "PowerPC,e500" instead -- it would
>> make it easier to probe for the actual CPU type, that way. Not
>> that Linux uses the name/compatible here at all ;-)
>
> I thought about this, not sure what the best solution is.
>>> * built-in for non-standard buses (ISA, PCI)
>>
>> "built-in" is some weird CHRP property, so yes we don't need it
>> or want it.
>
> Do you suggest we get ride of it from ISA nodes as well?
Yes. You aren't CHRP so you don't have to follow the CHRP binding.
Of course it is good to copy from t
>> What is a "front side cache"? What exactly does it cache? If it's
>> a cache for one CPU only, that fact should be shown in the device
>> tree somehow.
>
> Its in front of the memory controllers. Its not specific to a given
> CPU.
Ah, I see. That relationship is implicit in the device tree
On 9/13/07, Zhang Wei-r63237 <[EMAIL PROTECTED]> wrote:
> Hi,
>
> > > +static void fsl_dma_set_src(dma_addr_t addr,
> > > + struct dma_async_tx_descriptor
> > *tx, int index)
> > > +{
> >
> > What is index supposed to mean? It's not used, or documented
> > anywhere than
>
...because, on virtualized hardware like System p, we can't be sure that the
physical pages behind them are contiguous.
Signed-off-by: Joachim Fenkes <[EMAIL PROTECTED]>
---
drivers/infiniband/hw/ehca/ehca_mrmw.c | 25 +++--
1 files changed, 15 insertions(+), 10 deletions(-)
During ib_umem_get(), determine whether all pages from the memory region are
hugetlb pages and report this in the "hugetlb" field. Low-level driver can
use this information if they need it.
Signed-off-by: Joachim Fenkes <[EMAIL PROTECTED]>
---
drivers/infiniband/core/umem.c | 20 +++
From: Hoang-Nam Nguyen <[EMAIL PROTECTED]>
Signed-off-by: Joachim Fenkes <[EMAIL PROTECTED]>
---
drivers/infiniband/hw/ehca/ehca_classes.h |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/infiniband/hw/ehca/ehca_classes.h
b/drivers/infiniband/hw/ehca/ehca_c
This patchset replaces Nam's previous MR/MW patch (posted by me). I split
the #define fixes into a separate patch and moved the "is the memory from
hugetlbfs?" code into ib_umem_get().
[1/3] fixes the page size HW cap defines
[2/3] adds the hugetlb test to ib_umem_get()
[3/3] finally uses the huge
On Thu, Sep 13, 2007 at 01:39:58AM -0500, Kumar Gala wrote:
> >+CS: chipselect {
>
> We need to document this in booting-without-of.
OK.
> >+PIC: [EMAIL PROTECTED] {
> >+#interrupt-cells = <2>;
> >+interrupt-controller;
> >+
Currently qe_bd_t is used in the macro call -- dma_unmap_single,
which is a no-op on PPC32, thus error is hidden today. Starting
with 2.6.24, macro will be replaced by the empty static function,
and erroneous use of qe_bd_t will trigger compilation error.
Signed-off-by: Anton Vorontsov <[EMAIL PRO
On Sep 13, 2007, at 9:52 AM, Scott Wood wrote:
> On Thu, Sep 13, 2007 at 04:09:29AM +0200, Segher Boessenkool wrote:
I have a strange issue here. If I rename 'fsl,dma' to
'fsl,mpc8540-dma',
the 'fsl,mpc8540-dma-channel' will be also regarded as DMA
device not
DMA channe
On Thu, Sep 13, 2007 at 04:09:29AM +0200, Segher Boessenkool wrote:
> >>I have a strange issue here. If I rename 'fsl,dma' to
> >>'fsl,mpc8540-dma',
> >>the 'fsl,mpc8540-dma-channel' will be also regarded as DMA device not
> >>DMA channel.
> >
> >What tree are you using? Commit
> >804ace8881d211
On Thu, Sep 13, 2007 at 03:13:06AM -0700, Zhang Wei-r63237 wrote:
> > After dropping the lock, you can no longer assume that your
> > iterator is
> > still valid; you need to work off of the list head.
> >
>
> list_for_each_entry_safe() is used here. I think the safe should be ok.
> :P
Nope. T
On Thu, Sep 13, 2007 at 05:11:25PM +1000, David Gibson wrote:
> > -#define immr_unmap(addr) iounmap(addr)
> > +#define immr_map(member) (&mpc8xx_immr->member)
> > +#define immr_map_size(member, size) (&mpc8xx_immr->member)
> > +#define immr_unmap(addr) iounmap(addr)
>
> This looks bogus.
Roland Dreier <[EMAIL PROTECTED]> wrote on 13.09.2007 06:33:45:
> > -#define HCA_CAP_MR_PGSIZE_4K 1
> > -#define HCA_CAP_MR_PGSIZE_64K 2
> > -#define HCA_CAP_MR_PGSIZE_1M 4
> > -#define HCA_CAP_MR_PGSIZE_16M 8
> > +#define HCA_CAP_MR_PGSIZE_4K 0x8000
> > +#define HCA_CAP_MR_PGSIZE_64K
On Thu, Sep 13, 2007 at 01:26:26PM +0200, Juergen Beisert wrote:
> Hi,
>
> I'm using an MPC5200B based system with various external connected devices to
> its LocalPlusBus. On other architectures I would register them as platform
> devices (no chance to autodetect these devices). But on PowerPC
On Thursday 13 September 2007, Michael Ellerman wrote:
> Well that'd be nice, but I don't see anywhere that that happens. AFAICT
> the acquire we do in the first coredump callback is the first the SPU
> contexts know about their PPE process dying. And spufs is still live, so
> I think we definitely
Hi,
I'm using an MPC5200B based system with various external connected devices to
its LocalPlusBus. On other architectures I would register them as platform
devices (no chance to autodetect these devices). But on PowerPC architecture?
Is the oftree description also intended to describe these ki
On Thu, 13 Sep 2007 18:53:46 +0900 Paul Mundt <[EMAIL PROTECTED]> wrote:
> On Thu, Sep 13, 2007 at 05:22:36PM +1000, Michael Neuling wrote:
> > > > Commit f629307c857c030d5a3dd777fee37c8bb395e171 introduced uses of
> > > > kernel_termios_to_user_termios_1 and user_termios_to_kernel_termios_1
> > >
On Thu, Sep 13, 2007 at 05:22:36PM +1000, Michael Neuling wrote:
> > > Commit f629307c857c030d5a3dd777fee37c8bb395e171 introduced uses of
> > > kernel_termios_to_user_termios_1 and user_termios_to_kernel_termios_1
> > > on all architectures. However, powerpc, s390, avr32 and frv don't
> > > curren
Hi,
> > +static void fsl_dma_set_src(dma_addr_t addr,
> > + struct dma_async_tx_descriptor
> *tx, int index)
> > +{
>
> What is index supposed to mean? It's not used, or documented
> anywhere than
> I can see.
I've also got more document here. Hi, Dan, could you giv
On Wednesday 12 September 2007 03:56, [EMAIL PROTECTED] wrote:
> Note:
>
> This patch consolidates all the previous patches regarding
> the conversion of static arrays sized by NR_CPUS into per_cpu
> data arrays and is referenced against 2.6.23-rc6 .
Looks good to me from the x86 side. I'll leave
Roland Dreier wrote on 13.09.2007 06:33:45:
>
> Also if someone runs a kernel with 64K pages on a machine where they
> end up being simulated from 4K pages, do you have the same issue with
> the hypervisor ganging together non-contiguous pages?
With todays hypervisor and todays pagesizes and today
On Thu, 13 Sep 2007 17:11:25 +1000
David Gibson wrote:
> Didn't notice this before - only when some yak shaving led me into
> looking at the horrors of the 8xx imm mapping code...
>
> But..
> [snip]
> > diff --git a/include/asm-powerpc/fs_pd.h
> > b/include/asm-powerpc/fs_pd.h index c624915..733e
Paul Mackerras wrote:
> Commit f629307c857c030d5a3dd777fee37c8bb395e171 introduced uses of
> kernel_termios_to_user_termios_1 and user_termios_to_kernel_termios_1
> on all architectures. However, powerpc, s390, avr32 and frv don't
> currently define those functions since their termios struct didn'
> > Commit f629307c857c030d5a3dd777fee37c8bb395e171 introduced uses of
> > kernel_termios_to_user_termios_1 and user_termios_to_kernel_termios_1
> > on all architectures. However, powerpc, s390, avr32 and frv don't
> > currently define those functions since their termios struct didn't
> > need to
From: Jan Dittmer <[EMAIL PROTECTED]>
Date: Thu, 13 Sep 2007 08:57:13 +0200
> Paul Mackerras wrote:
> > Commit f629307c857c030d5a3dd777fee37c8bb395e171 introduced uses of
> > kernel_termios_to_user_termios_1 and user_termios_to_kernel_termios_1
> > on all architectures. However, powerpc, s390, av
1 - 100 of 102 matches
Mail list logo
