On Wed, Jan 14, 2009 at 11:43 PM, Michael Ellerman
wrote:
> Several platforms implement ppc_md.progress as a simple printk. Now that
> we have the ppc_progress() wrapper which falls back to printk if no
> routine is specified, we can remove all the printk-only progress
> implementations.
>
> This
On Wed, Jan 14, 2009 at 11:43 PM, Michael Ellerman
wrote:
> Signed-off-by: Michael Ellerman
Acked-by: Grant Likely
> ---
> arch/powerpc/kernel/setup_32.c| 11 +--
> arch/powerpc/mm/init_32.c | 15 +--
> arch/powerpc/mm/ppc_mm
On Wed, Jan 14, 2009 at 11:43 PM, Michael Ellerman
wrote:
> There's quite a lot of code that does:
>
> if (ppc_md.progress)
>ppc_md.progress(...)
>
> So move that idiom into a wrapper. Having a wrapper also allows us
> to have a fallback to printk if no progress routine is specified.
>
> S
> I'm afraid I haven't seen any readily available sources for their
> driver. If you meant Ben's version, you can find the latest revision
> here:
>
> http://marc.info/?t=12282326615
>
> Unfortunately marc.info didn't sort out the threading, but you should
> be able to find all the patches th
From: Michael Ellerman
Date: Thu, 15 Jan 2009 17:46:02 +1100 (EST)
> The lmb_dump_all() output didn't include the RMO size, which is
> interesting on powerpc. The output was also a bit spacey and not well
> aligned, and didn't show you the end addresses.
>
> Signed-off-by: Michael Ellerman
Ack
From: Michael Ellerman
Date: Thu, 15 Jan 2009 17:46:01 +1100 (EST)
> The lmb debugging can be turned on at boottime with lmb=debug on the
> command line. However on powerpc that doesn't work, because we don't
> necessarily call lmb_dump_all().
>
> So always call lmb_dump_all() after lmb_analyze(
The lmb_dump_all() output didn't include the RMO size, which is
interesting on powerpc. The output was also a bit spacey and not well
aligned, and didn't show you the end addresses.
Signed-off-by: Michael Ellerman
---
lib/lmb.c | 42 +-
1 files changed,
The lmb debugging can be turned on at boottime with lmb=debug on the
command line. However on powerpc that doesn't work, because we don't
necessarily call lmb_dump_all().
So always call lmb_dump_all() after lmb_analyze(), no output is
generated unless lmb=debug is found on the command line.
Signe
Several platforms implement ppc_md.progress as a simple printk. Now that
we have the ppc_progress() wrapper which falls back to printk if no
routine is specified, we can remove all the printk-only progress
implementations.
This leaves us with iSeries_progress(), rtas_progress() and udbg_progress()
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/setup_32.c| 11 +--
arch/powerpc/mm/init_32.c | 15 +--
arch/powerpc/mm/ppc_mmu_32.c |8
arch/powerpc/platforms/52xx/efika.c
There's quite a lot of code that does:
if (ppc_md.progress)
ppc_md.progress(...)
So move that idiom into a wrapper. Having a wrapper also allows us
to have a fallback to printk if no progress routine is specified.
Signed-off-by: Michael Ellerman
---
arch/powerpc/include/asm/machdep.h |
Signed-off-by: Michael Ellerman
---
arch/powerpc/include/asm/machdep.h |2 --
arch/powerpc/kernel/setup_64.c |7 ---
2 files changed, 0 insertions(+), 9 deletions(-)
diff --git a/arch/powerpc/include/asm/machdep.h
b/arch/powerpc/include/asm/machdep.h
index 2740c44..6c34a0d 10064
On Thu, 15 Jan 2009 14:11:09 +0800
"Liu Dave" wrote:
> > Probably because it was quicker. Samsung did the same thing, but now
> > Ben Dooks has patches to properly support it via sdhci.
>
> Pierre,
> What samsung driver are you talking? Could you point it to me?
>
I'm afraid I haven't seen any
Timur Tabi wrote:
Peter Korsgaard wrote:
The only minor issues we have is the cosmetic problem of the driver
printing NO_IRQ (E.G. this patch), and the driver calling
free_irq(NO_IRQ) (E.G. the other patch I sent today) in the release
path.
Ok, I understand.
ACK on the patches.
Ok, Li Yan
> Probably because it was quicker. Samsung did the same thing, but now
> Ben Dooks has patches to properly support it via sdhci.
Pierre,
What samsung driver are you talking? Could you point it to me?
Thanks, Dave
___
Linuxppc-dev mailing list
Linuxppc-d
On Thu, 15 Jan 2009 02:56:05 +0300
Anton Vorontsov wrote:
>
> Ah. I wonder why Freescale just didn't write some patches for sdhci,
> but copied the code instead...
>
Probably because it was quicker. Samsung did the same thing, but now
Ben Dooks has patches to properly support it via sdhci.
Rg
On Jan 14, 2009, at 11:15 PM, Ken Williams wrote:
I am trying to configure a dts file for the pci subsystem of a
MPC8540 based system.
I am expecting (hoping) that the value specified in the interrupts
property (98 in this example)
will be used as the virtual interrupt number and that I ca
I am trying to configure a dts file for the pci subsystem of a MPC8540 based
system.
I am expecting (hoping) that the value specified in the interrupts property
(98 in this example)
will be used as the virtual interrupt number and that I can later do a
request_irq using that number.
kernel: 2.6.2
From: Geert Uytterhoeven
Date: Wed, 14 Jan 2009 11:00:05 +0100 (CET)
> On Wed, 14 Jan 2009, Benjamin Herrenschmidt wrote:
> > This adds an init_dummy_netdev() function that gets a network device
> > structure (allocation and lifetime entirely under caller's control) and
> > initialize the minimum
From: Kumar Gala
Date: Tue, 13 Jan 2009 10:28:15 -0600
>
> On Oct 27, 2008, at 4:46 PM, Mike Ditto wrote:
>
> > If something goes wrong attaching to phy driver, we weren't freeing
> > the IRQ.
> >
> > Signed-off-by: Mike Ditto
...
> This seems to have gotten lost in the shuffle. Can you plea
On Jan 14, 2009, at 1:46 PM, Anton Vorontsov wrote:
From: Xie Xiaobo
This patch adds support for the Freescale Enhanced Secure Digital
Host Controller Interface as found in some Freescale PowerPC
microprocessors (e.g. MPC837x SOCs).
Signed-off-by: Xie Xiaobo
Signed-off-by: Konjin Lai
Signe
Hello Yuri,
On Tue, Jan 13, 2009 at 03:43:55AM +0300, Yuri Tikhonov wrote:
> Adds the platform device definitions and the architecture specific support
> routines for the ppc440spe adma driver.
>
> Any board equipped with PPC440SP(e) controller may utilize this driver.
>
> Signed-off-by: Yuri Ti
On Wed, 2009-01-14 at 13:09 -0600, Dave Kleikamp wrote:
> powerpc: is_hugepage_only_range() must account for both 4kB and 64kB slices
>
> The subpage_prot syscall fails on second and subsequent calls for a given
> region, because is_hugepage_only_range() is mis-identifying the 4 kB
> slices when t
Stefan Strobl wrote:
Hi
I'm new to Kernel 2.6 and OF.
I'm using a ADS5121 board with kernel from denx (ads5121 branch from
linux-2.6-denx). According to my dts file both PSC3 and PSC4 should be
accessible through /dev/ttyPSC0 and /dev/ttyPSC1 respectively.
When I simply try to run: "$ echo "He
On Mon, Jan 12, 2009 at 5:43 PM, Yuri Tikhonov wrote:
> + /* (2) Calculate Q+Qxy */
> + lptrs[0] = ptrs[failb];
> + lptrs[1] = ptrs[disks-1];
> + lptrs[2] = NULL;
> + tx = async_pq(lptrs, NULL, 0, 1, bytes, ASYNC_TX_DEP_ACK,
> + tx, NULL, NULL);
>
On Mon, Jan 12, 2009 at 5:43 PM, Yuri Tikhonov wrote:
> This adds support for doing asynchronous GF multiplication by adding
> four additional functions to async_tx API:
>
> async_pq() does simultaneous XOR of sources and XOR of sources
> GF-multiplied by given coefficients.
>
> async_pq_zero_s
On Tue, Jan 13, 2009 at 06:42:53PM +0100, Arnd Bergmann wrote:
> On Tuesday 13 January 2009, Ira Snyder wrote:
> > So do you program one channel of the DMA engine from the host side and
> > another channel from the guest side?
>
> Yes.
>
> > I tried to avoid having the host program the DMA contro
On Thu, Jan 15, 2009 at 07:37:00AM +0800, Liu Dave wrote:
> > This patch adds support for the Freescale Enhanced Secure Digital
> > Host Controller Interface as found in some Freescale PowerPC
> > microprocessors (e.g. MPC837x SOCs).
>
> The Freescale ESDHC controller is basically compatible with
The PAPR says that the property for specifying the number of SLBs should
be called "slb-size". We currently only look for "ibm,slb-size" because
this is what firmware actually presents.
This patch makes us look for the "slb-size" property as well and in
preference to the "ibm,slb-size". This sho
> This patch adds support for the Freescale Enhanced Secure Digital
> Host Controller Interface as found in some Freescale PowerPC
> microprocessors (e.g. MPC837x SOCs).
The Freescale ESDHC controller is basically compatible with the
standard SDHC controller. but the eshdc expand some bits.
The e
Stephen Rothwell wrote:
> Signed-off-by: Stephen Rothwell
> ---
> drivers/net/ps3_gelic_wireless.c |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Acked-by: Geoff Levand
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://o
Stephen Rothwell wrote:
> Signed-off-by: Stephen Rothwell
> ---
> drivers/block/ps3disk.c | 18 +-
> 1 files changed, 9 insertions(+), 9 deletions(-)
Acked-by: Geoff Levand
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
ht
Stephen Rothwell wrote:
> Also some min -> mint_t conversion.
>
> Signed-off-by: Stephen Rothwell
> ---
> drivers/ps3/ps3-lpm.c | 16
> drivers/ps3/ps3-vuart.c |8
> drivers/ps3/ps3stor_lib.c | 14 +++---
> 3 files changed, 19 insertions(+), 19 del
Stephen Rothwell wrote:
> Also a couple of min -> min_t changes.
>
> Signed-off-by: Stephen Rothwell
> ---
> drivers/char/ps3flash.c | 18 +-
> 1 files changed, 9 insertions(+), 9 deletions(-)
Acked-by: Geoff Levand
___
Linuxppc
Stephen Rothwell wrote:
> Signed-off-by: Stephen Rothwell
> ---
> drivers/scsi/ps3rom.c |6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
Acked-by: Geoff Levand
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.o
Stephen Rothwell wrote:
> Signed-off-by: Stephen Rothwell
> ---
> drivers/video/ps3fb.c |4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
Acked-by: Geoff Levand
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org
Stephen Rothwell wrote:
> Signed-off-by: Stephen Rothwell
> ---
> sound/ppc/snd_ps3.c |4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
Acked-by: Geoff Levand
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/m
Stephen Rothwell wrote:
> Signed-off-by: Stephen Rothwell
> ---
> arch/powerpc/platforms/ps3/device-init.c | 26 +-
> arch/powerpc/platforms/ps3/htab.c|2 +-
> arch/powerpc/platforms/ps3/interrupt.c | 16
> arch/powerpc/platforms/ps3/mm.c
Stephen Rothwell wrote:
> We just fix up the reference parameters as the others are dealt with by
> arithmetic promotion rules and don't cause warnings.
>
> This removes warnings like this:
>
> arch/powerpc/platforms/ps3/interrupt.c:327: warning: passing argument 1 of
> 'lv1_construct_event_rece
Stephen Rothwell wrote:
> Fixes compiler warnings:
>
> arch/powerpc/platforms/ps3/mm.c:1205: warning: passing argument 2 of
> 'ps3_repository_read_mm_info' from incompatible pointer type
> arch/powerpc/platforms/ps3/mm.c:1205: warning: passing argument 3 of
> 'ps3_repository_read_mm_info' from i
Stephen Rothwell wrote:
> This fixes these compiler warning:
>
> arch/powerpc/platforms/ps3/interrupt.c:109: warning: passing argument 2 of
> 'clear_bit' from incompatible pointer type
> arch/powerpc/platforms/ps3/interrupt.c:130: warning: passing argument 2 of
> 'set_bit' from incompatible poin
Stephen Rothwell wrote:
> Push the dma_addr_t type usage all the way down to where the actual
> values are manipulated.
>
> Now that u64 is "unsigned long long", this removes warnings like:
>
> arch/powerpc/platforms/ps3/system-bus.c:532: warning: passing argument 4 of
> 'ps3_dma_map' from incom
Hi Stephen,
Thanks for working through it and making these fixups. I
tested the set applied onto Ben's powerpc tree and they
seem to work OK (with ps3_defconfig).
Stephen Rothwell wrote:
> Also silences this warning:
>
> arch/powerpc/platforms/ps3/setup.c:275: warning: initialization from
> in
From: Andy Fleming
Date: Wed, 14 Jan 2009 12:20:35 -0600
> On Jan 14, 2009, at 9:03 AM, Anton Vorontsov wrote:
> >>
> >> There is one thing I don't actually understand though...
> >>
> >> Andy, were you testing the TBI support on a hardware where PHY ID
> >> != 0x0 or maybe your TBI PHY support p
On Wed, 2009-01-14 at 11:48 -0800, Andrew Klossner wrote:
> When I moved from 2.6.27 to 2.6.28, one of my devices didn't work
> until I devised the attached patch. The kernel disallowed PCI I/O
> space resources behind the pseudo-bridge in the Freescale MPC8545
> because that bridge's config-space
When I moved from 2.6.27 to 2.6.28, one of my devices didn't work
until I devised the attached patch. The kernel disallowed PCI I/O
space resources behind the pseudo-bridge in the Freescale MPC8545
because that bridge's config-space registers incorrectly report that
it doesn't forward I/O space tr
On Tue, Jan 13, 2009 at 4:14 PM, Kumar Gala wrote:
> Create a new header that becomes a single location for defining PowerPC
> opcodes used by code that is either generationg instructions
> at runtime (fixups, debug, etc.), emulating instructions, or just
> compiling instructions old assemblers do
From: Xie Xiaobo
This patch adds support for the Freescale Enhanced Secure Digital
Host Controller Interface as found in some Freescale PowerPC
microprocessors (e.g. MPC837x SOCs).
Signed-off-by: Xie Xiaobo
Signed-off-by: Konjin Lai
Signed-off-by: Joe D'Abbraccio
Signed-off-by: Anton Vorontso
Peter Korsgaard wrote:
> The only minor issues we have is the cosmetic problem of the driver
> printing NO_IRQ (E.G. this patch), and the driver calling
> free_irq(NO_IRQ) (E.G. the other patch I sent today) in the release
> path.
Ok, I understand.
ACK on the patches.
--
Timur Tabi
Linux kerne
> "Timur" == Timur Tabi writes:
Timur> Peter Korsgaard wrote:
>> Documentation/powerpc/dts-bindings/fsl/dma.txt and
>> The NO_IRQ check in fsldma.c:fsl_dma_chan_probe()
>>
>> And it makes sense, there's no per-channel DMAC interrupts on mpc83xx.
Timur> But the device trees do have IRQ
powerpc: is_hugepage_only_range() must account for both 4kB and 64kB slices
The subpage_prot syscall fails on second and subsequent calls for a given
region, because is_hugepage_only_range() is mis-identifying the 4 kB
slices when the process has a 64 kB page size.
Signed-off-by: Dave Kleikamp
C
On Mon, Jan 12, 2009 at 5:42 PM, Yuri Tikhonov wrote:
> Hello,
>
> This is the next attempt on asynchronous RAID-6 support. This patch-set
> has the Dan Williams' comments (Dec, 17) addressed with the following
> exception:
>
> - I still think that using 'enum dma_ctrl_flags' for PQ-specific
> o
On Jan 14, 2009, at 9:03 AM, Anton Vorontsov wrote:
There is one thing I don't actually understand though...
Andy, were you testing the TBI support on a hardware where PHY ID
!= 0x0 or maybe your TBI PHY support patch (commit b31a1d8b41513b,
dated Tue Dec 16 15:29:15 2008) was based on a bit o
Hi
I'm new to Kernel 2.6 and OF.
I'm using a ADS5121 board with kernel from denx (ads5121 branch from
linux-2.6-denx). According to my dts file both PSC3 and PSC4 should be
accessible through /dev/ttyPSC0 and /dev/ttyPSC1 respectively.
When I simply try to run: "$ echo "Hello" > /dev/ttyPSC*" I
Peter Korsgaard wrote:
> Documentation/powerpc/dts-bindings/fsl/dma.txt and
> The NO_IRQ check in fsldma.c:fsl_dma_chan_probe()
>
> And it makes sense, there's no per-channel DMAC interrupts on mpc83xx.
But the device trees do have IRQs in the channels:
arch/powerpc/boot/dts/mpc836x_mds.dts:
d
> "Timur" == Timur Tabi writes:
Timur> Peter Korsgaard wrote:
>> Why? Does it buy us anything to request_irq again for each channel?
>>
>> Now we're at it, it seems like there's a check for != NO_IRQ missing
>> in fsl_dma_chan_remove().
Timur> If the device tree doesn't specify an int
Peter Korsgaard wrote:
> Why? Does it buy us anything to request_irq again for each channel?
>
> Now we're at it, it seems like there's a check for != NO_IRQ missing
> in fsl_dma_chan_remove().
If the device tree doesn't specify an interrupts property in the device channel,
then I think that's a
There's no per-channel IRQ on mpc83xx, so only call free_irq if we have one.
Signed-off-by: Peter Korsgaard
---
drivers/dma/fsldma.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/drivers/dma/fsldma.c b/drivers/dma/fsldma.c
index ca70a21..f48c0e6 100644
--- a/drivers/
> "Timur" == Timur Tabi writes:
Timur> Peter Korsgaard wrote:
>> @@ -875,7 +875,8 @@ static int __devinit fsl_dma_chan_probe(struct
>> fsl_dma_device *fdev,
>> }
>>
>> dev_info(fdev->dev, "#%d (%s), irq %d\n", new_fsl_chan->id,
>> - compatible, new_fsl_chan-
Peter Korsgaard wrote:
> @@ -875,7 +875,8 @@ static int __devinit fsl_dma_chan_probe(struct
> fsl_dma_device *fdev,
> }
>
> dev_info(fdev->dev, "#%d (%s), irq %d\n", new_fsl_chan->id,
> - compatible, new_fsl_chan->irq);
> + compatible,
> +
Hi Showair , >> Note that my target is to transfer data from memory location to another >>memory location & it will be an overhead if i copy the data from the >>src to >>the DMA buffer then from the DMA buffer to the Destination. >>isn't there any other way to avoid using that DMA buffer & to co
On Mon, Jan 12, 2009 at 09:51:23AM -0600, Milton Miller wrote:
> Is SLOF just exposing the user image part of the flash device? Or is it
> the raw flash device?
SLOF is exposing the raw flash device.
> I need to keep this quick, but am intrested in a few more details. My
> first reaction is
On Tue, Jan 13, 2009 at 07:05:13PM +0300, Anton Vorontsov wrote:
> Freescale on-chip TBI PHYs reports PHY ID as 0x0, but as of
>
> commit 3ee82383f0098a2e13acc8cf1be8e47512f41e5a
> Author: Giulio Benetti
> Date: Thu Nov 13 21:53:13 2008 +
>
> phy: fix phy address bug
>
> PHYID ret
Signed-off-by: Peter Korsgaard
---
Documentation/powerpc/dts-bindings/fsl/dma.txt | 34
1 files changed, 17 insertions(+), 17 deletions(-)
diff --git a/Documentation/powerpc/dts-bindings/fsl/dma.txt
b/Documentation/powerpc/dts-bindings/fsl/dma.txt
index cc45311..0732
> "Anton" == Anton Vorontsov writes:
Hi,
>> interrupt-parent = <&ipic>;
>> - interrupts = <47 8>;
>> + interrupts = <71 8>;
Anton> 0x47 = 71 ;-) The example is in the dts-v0 format, all the numbers
Anton> are hexadecimal.
Ahh ;)
--
Bye, Peter Korsgaard
__
The mpc83xx variant uses a shared IRQ for all channels, so the individual
channel nodes don't have an interrupt property. Fix the code to print the
controller IRQ instead if there isn't any for the channel.
Signed-off-by: Peter Korsgaard
---
drivers/dma/fsldma.c |3 ++-
1 files changed, 2 in
On Jan 14, 2009, at 8:21 AM, Anton Vorontsov wrote:
Hi Peter,
On Wed, Jan 14, 2009 at 03:14:13PM +0100, Peter Korsgaard wrote:
The DMAC IRQ number of the mpc8349 is 71 and not 47, according to
http://www.freescale.com/files/32bit/doc/ref_manual/MPC8349EARMAD.pdf
Signed-off-by: Peter Korsgaar
Hi Peter,
On Wed, Jan 14, 2009 at 03:14:13PM +0100, Peter Korsgaard wrote:
> The DMAC IRQ number of the mpc8349 is 71 and not 47, according to
> http://www.freescale.com/files/32bit/doc/ref_manual/MPC8349EARMAD.pdf
>
> Signed-off-by: Peter Korsgaard
> ---
> Documentation/powerpc/dts-bindings/fs
The DMAC IRQ number of the mpc8349 is 71 and not 47, according to
http://www.freescale.com/files/32bit/doc/ref_manual/MPC8349EARMAD.pdf
Signed-off-by: Peter Korsgaard
---
Documentation/powerpc/dts-bindings/fsl/dma.txt |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Docu
On Wed, 14 Jan 2009, Benjamin Herrenschmidt wrote:
> This adds an init_dummy_netdev() function that gets a network device
> structure (allocation and lifetime entirely under caller's control) and
> initialize the minimum amount of fields so it can be used to schedule
> NAPI polls without registerin
florian.bel...@freenet.de wrote:
>>> On Mon, Jan 12, 2009 at 2:07 AM,
>> wrote:
hello,
I have some problems with an mpc5200b based board. It's nearly
>> compatible to
the lite5200b board.
I connected an samsung k9k8g08u0a nand flash via the lpb bus. This
>> works
fin
> On Mon, Jan 12, 2009 at 2:07 AM,
wrote:
> > hello,
> >
> > I have some problems with an mpc5200b based board. It's nearly
compatible to
> > the lite5200b board.
> > I connected an samsung k9k8g08u0a nand flash via the lpb bus. This
works
> > fine with an self written nand driver.
> > Now I
72 matches
Mail list logo
