Hi Kumar
Commit 4484079d517c2b6521621be0b1ea246ccc55c7d7 from your next branch
breaks my 8xx test config with the following error:
/home/benh/linux-powerpc-test/drivers/net/fs_enet/fs_enet-main.c: In function
‘setup_immap’:
/home/benh/linux-powerpc-test/drivers/net/fs_enet/fs_enet-main.c:947: er
In message you wrote:
> On Mon, 18 May 2009, Michael Neuling wrote:
> > > > We can compile and boot with NR_CPUS=3D8192, so make this the max. 102
4
> > > > was an arbitrary decision anyway.
> > >
> > > Is 8192 still arbitrary? Or does something break above that?
> >
> > Yeah, the compile break
On Fri, 2009-05-15 at 07:50 -0500, Kumar Gala wrote:
> On May 15, 2009, at 7:47 AM, Kumar Gala wrote:
>
> > We shouldn't directly access sysdata to get the device node. We
> > should
> > be calling pci_device_to_OF_node().
> >
> > Signed-off-by: Kumar Gala
> > ---
> > * Updated based on sfr's
Just a quick note before I leave the office...
I've just pushed out a bunch of stuff to my "test" branch. There's a
couple of known breakage (iseries and 8xx) which will have to be sorted
out before that stuff goes into "next". hopefully in a couple of days.
Still... feel free to take a peek, tes
The remove function uses __devexit, so the .remove assignment needs
__devexit_p() to fix a build error with hotplug disabled.
Signed-off-by: Mike Frysinger
CC: linuxppc-dev@ozlabs.org
CC: linux-ker...@vger.kernel.org
---
drivers/char/hvc_iseries.c |2 +-
1 files changed, 1 insertions(+), 1 d
The remove function uses __devexit, so the .remove assignment needs
__devexit_p() to fix a build error with hotplug disabled.
Signed-off-by: Mike Frysinger
CC: linuxppc-dev@ozlabs.org
---
v2
- include all hvc files
drivers/char/hvc_iseries.c |2 +-
drivers/char/hvc_vio.c |2
Support EDAC INT mode for AMD8131 EDAC driver, which may post upstream
NMI interrupt request messages that will latch MPIC INT0 pin.
Following aspects for this patch have been tested:
1, module initialization and deletion for NMI mode;
2, creation and deletion for the mapping between hwirq==0 to a
Support EDAC INT mode and add a new EDAC MCE mode for CPC925 EDAC driver.
CPC925 Hypertransport hostbridge controller may trigger interrupt that
latches MPIC INT2 pin on Hypertransport Link Errors, and generate MCE on
memory ECC Errors and Processor Interface Errors.
The global variable "edac_op_s
Support EDAC INT mode for AMD8111 EDAC driver, which may post upstream
NMI interrupt request messages that will latch MPIC INT0 pin.
Following aspects for this patch have been tested:
1, module initialization and deletion for NMI mode;
2, creation and deletion for the mapping between hwirq==0 to a
Collect the machine specific code that creates the hwirq2virq mapping
for the possible multiple EDAC modules on the same machine that supports
MPIC.
Multiple calling of irq_create_of_mapping() for the same hwirq will
always return the same virq, since the mapping won't be refcounted so
we just do
Hi Ben,
This is the v2 patches that have integrated your suggestions to
remove the refcount for a hwriq2virq mapping as long as we don't
dispose it, the changes are mostly within the 1/4 patch where the
unnecessary refcount and irqmap structure are removed, and callings
to edac_put_mpic_irq() are
> Could we go forward with my initial patch, and then continue the work
> on this repeated START approach for future releases?
Then could you please send another version of your patch with the CodingStyle
issue removed and an updated description what this patch fixes and what still
needs to be res
If CONFIG_PPC_EMULATED_STATS is enabled, make available counters for the
various classes of emulated instructions under
/sys/kernel/debug/powerpc/emulated_instructions/ (assumed debugfs is mounted on
/sys/kernel/debug). Optionally (controlled by
/sys/kernel/debug/powerpc/emulated_instructions/do_w
We shouldn't directly access sysdata to get the device node. We should
be calling pci_device_to_OF_node().
Signed-off-by: Kumar Gala
---
* Fixed compile error (dev -> pdev)
arch/powerpc/platforms/iseries/iommu.c |2 +-
arch/powerpc/platforms/iseries/pci.c |8
2 files changed
On May 18, 2009, at 2:01 AM, Benjamin Herrenschmidt wrote:
Hi Kumar
Commit 4484079d517c2b6521621be0b1ea246ccc55c7d7 from your next branch
breaks my 8xx test config with the following error:
/home/benh/linux-powerpc-test/drivers/net/fs_enet/fs_enet-main.c: In
function ‘setup_immap’:
/home/be
On May 17, 2009, at 11:49 PM, Benjamin Herrenschmidt wrote:
On Thu, 2009-05-14 at 17:42 -0500, Becky Bruce wrote:
This patch includes the basic infrastructure to use swiotlb
bounce buffering on 32-bit powerpc. It is not yet enabled on
any platforms. Probably the most interesting bit is the
a
> Right. Furthermore, the i2c-mpc.c should be extened to support bus speed
> setting for the MPC512x, which has been merged recently (see commit id
> f2bd5efe).
I have simple question about bus speed setting support. Existing
implementation uses default safe speed if there is no 'clock-frequency'
2009/5/18 Piotr Zięcik :
>> Right. Furthermore, the i2c-mpc.c should be extened to support bus speed
>> setting for the MPC512x, which has been merged recently (see commit id
>> f2bd5efe).
>
> I have simple question about bus speed setting support. Existing
> implementation uses default safe speed
Piotr Zięcik wrote:
>> Right. Furthermore, the i2c-mpc.c should be extened to support bus speed
>> setting for the MPC512x, which has been merged recently (see commit id
>> f2bd5efe).
>
> I have simple question about bus speed setting support. Existing
> implementation uses default safe speed if
> From: Grant Likely
> Date: Fri, 15 May 2009 08:52:19 -0600
> Subject: Re: FEC & SDMA (bestcomm) interaction on the 5200
> To: Dimiter Popoff
> Cc: linuxppc-dev@ozlabs.org
>
> On Fri, May 15, 2009 at 2:36 AM, Dimiter Popoff wrote:
> > Hi people,
> >
> > I am porting my (not linux) OS to the 52
On Thu, May 14, 2009 at 04:20:04PM -0400, Alan Stern wrote:
> On Fri, 15 May 2009, K.Prasad wrote:
>
> > I see that you're referring to this code in __switch_to() :
> > if (unlikely(__get_cpu_var(current_dabr) != new->thread.dabr))
> > set_dabr(new->thread.dabr);
> >
> > a
On Thu, May 14, 2009 at 04:21:48PM -0400, Alan Stern wrote:
> On Thu, 14 May 2009, K.Prasad wrote:
>
> > Index: linux-2.6-tip.hbkpt/samples/hw_breakpoint/data_breakpoint.c
> > ===
> > --- linux-2.6-tip.hbkpt.orig/samples/hw_breakpoint
On Mon, May 18, 2009 at 01:35:32PM +1000, Benjamin Herrenschmidt wrote:
> On Thu, 2009-05-14 at 19:13 +0530, K.Prasad wrote:
> > plain text document attachment (ppc64_prepare_code_01)
> > Prepare the PowerPC code for HW Breakpoint infrastructure patches by
> > including
> > relevant constant defin
On Mon, 18 May 2009, K.Prasad wrote:
> > > > > +int __kprobes hw_breakpoint_handler(struct die_args *args)
> > > > > +{
> > > > > + int rc = NOTIFY_STOP;
> > > > > + struct hw_breakpoint *bp;
> > > > > + struct pt_regs *regs = args->regs;
> > > > > + unsigned long dar;
> > > > > +
On Sun, May 17, 2009 at 01:45:30AM -0700, Chris Plasun wrote:
> Hi,
>
> (I haven't found any answers in the archives)
>
> How would I access a NTFS shared directory from a Freescale MPC8313?
>
> Will Samba run on a Freescale MPC8313?
It should (and if it doesn't, file a bug with them).
Users
On Fri, May 01, 2009 at 07:48:46AM +1000, Benjamin Herrenschmidt wrote:
> On Thu, 2009-04-30 at 21:59 +0100, Mel Gorman wrote:
>
> > This patch fixes the problem by not asseting the PTE is locked for VMAs
> > backed by huge pages.
>
> Thanks, will apply.
>
What's the story with this patch? I'm
On Mon, May 18, 2009 at 08:23:17AM -0500, Kumar Gala wrote:
>
> On May 18, 2009, at 2:01 AM, Benjamin Herrenschmidt wrote:
>
> >Hi Kumar
> >
> >Commit 4484079d517c2b6521621be0b1ea246ccc55c7d7 from your next branch
> >breaks my 8xx test config with the following error:
> >
> >/home/benh/linux-powe
On Mon, 18 May 2009, Mel Gorman wrote:
>
> What's the story with this patch? I'm still hearing of failures with huge
> pages
> that this patch fixes but I'm no seeing it upstream. Was the patch
> rejected or did it just slip through the cracks?
It didn't slip through the cracks, it was apparen
On Mon, May 18, 2009 at 01:24:49PM +1000, Benjamin Herrenschmidt wrote:
> On Fri, 2009-05-15 at 20:18 +0200, Gabriel Paubert wrote:
> > Since PPC_MUTIPLATFORM was removed, it was impossible to select the
> > driver for mv643xx_eth on the Pegasos. Fix by allowing to select
> > the driver on CHRP pla
Since PPC_MUTIPLATFORM was removed, it was impossible to select the
driver for mv643xx_eth on the Pegasos. Fix by allowing to select
the driver on CHRP platforms; Pegasos is a CHRP platform and the driver
will not work without arch/powerpc/platforms/chrp/pegasos_eth.
Signed-off-by: Gabriel Paubert
> -Original Message-
> From: linuxppc-dev-bounces+emilian.medve=freescale@ozlabs.org
[mailto:linuxppc-dev-
> bounces+emilian.medve=freescale@ozlabs.org] On Behalf Of Gabriel
Paubert
> Sent: Monday, May 18, 2009 12:38 PM
> To: Lennert Buytenhek
> Cc: t...@cyrius.com; LinuxPPC; pac...
Scott Wood wrote:
On Sun, May 17, 2009 at 01:45:30AM -0700, Chris Plasun wrote:
Hi,
(I haven't found any answers in the archives)
How would I access a NTFS shared directory from a Freescale MPC8313?
Will Samba run on a Freescale MPC8313?
It should (and if it doesn't, file a bug with them).
Hello Chris,
On Mon, May 18, 2009 at 8:06 PM, Chris Plasun wrote:
> Scott Wood wrote:
>> On Sun, May 17, 2009 at 01:45:30AM -0700, Chris Plasun wrote:
>>> (I haven't found any answers in the archives)
>>> How would I access a NTFS shared directory from a Freescale MPC8313?
>>> Will Samba run on a
Hi Leon,
Leon Woestenberg wrote:
Hello Chris,
On Mon, May 18, 2009 at 8:06 PM, Chris Plasun wrote:
Scott Wood wrote:
On Sun, May 17, 2009 at 01:45:30AM -0700, Chris Plasun wrote:
(I haven't found any answers in the archives)
How would I access a NTFS shared directory from a Freescale MPC831
On Mon, May 18, 2009 at 10:48:58AM -0700, Medve Emilian-EMMEDVE1 wrote:
> > -Original Message-
> > From: linuxppc-dev-bounces+emilian.medve=freescale@ozlabs.org
> [mailto:linuxppc-dev-
> > bounces+emilian.medve=freescale@ozlabs.org] On Behalf Of Gabriel
> Paubert
> > Sent: Monday, M
Segher, what are we missing here ?
The symbol name is misleading, and the help text is incorrect.
With those things fixed, I won't oppose the patch; it would
be nice if the logic here was cleaned up to avoid all the
double negations, but I'm not going to do it, so I won't ask
others to either.
Hello Gabriel,
> -Original Message-
> From: Gabriel Paubert [mailto:paub...@iram.es]
> Sent: Monday, May 18, 2009 1:48 PM
> To: Medve Emilian-EMMEDVE1
> Cc: Lennert Buytenhek; t...@cyrius.com; LinuxPPC; pac...@kosh.dhis.org;
net...@vger.kernel.org; David
> Miller
> Subject: Re: [PATCH] Al
On Mon, 2009-05-18 at 08:25 -0500, Kumar Gala wrote:
>
> Part of this is how the generic swiotlb code works and part of it
> was
> our desire not to bloat dev archdata by adding such info that as you
> say is either bus specific or conveyed in the dma addr mask.
Right but perf sucks :-)
Mayb
On Mon, 2009-05-18 at 12:20 -0500, Scott Wood wrote:
> > I'm pretty sure the driver changes to address this are in dave's
> net-
> > next tree.
>
> Won't this break git bisect?
>
> Not to mention anyone trying to use your tree now...
Right, though if you have the commit ID in DaveM tree, I can
Hello Medve
On Mon, May 18, 2009 at 01:15:12PM -0700, Medve Emilian-EMMEDVE1 wrote:
>
> You're correct. MV64360 seems to be stale. Do you want to re-spin your
> patch to get rid of it?
No problem, bu should I respin in from the current official git
or on top of yours?
>
> (I wouldn't create a
On Thu, 2009-05-14 at 08:00 -0600, Grant Likely wrote:
>
> All of this doesn't actually affect the driver code at all. It's all
> handled by the kernel and the DMA apis. What it does affect is
> multiplatform kernels. The DMA behaviour is set at compile time, not
> run time, depending on the se
On Thu, May 14, 2009 at 11:10 AM, Grant Likely
wrote:
> In other words, write your patches which use it and submit the lot as
> a patch series with this patch as the first. That gives some evidence
> that this macro will actually be used and useful.
This is going to be more difficult than you th
Hello Gabriel,
> -Original Message-
> From: Gabriel Paubert [mailto:paub...@iram.es]
> Sent: Monday, May 18, 2009 5:19 PM
> To: Medve Emilian-EMMEDVE1
> Cc: Lennert Buytenhek; t...@cyrius.com; LinuxPPC; pac...@kosh.dhis.org;
net...@vger.kernel.org; David
> Miller
> Subject: Re: [PATCH] Al
Since PPC_MUTIPLATFORM was removed, it was impossible to select the
driver for mv643xx_eth on the Pegasos. Fix it and take the opportunity
to remove the stale MV64360 config option.
Signed-off-by: Gabriel Paubert
diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig
index 214a92d..aff4f8c 10064
Hi,every one,
I want to drive the Rcomp circuit for ixp460, because I found that the ixp460
could not power up on low temperature(-40 degree). I want to add those code on
start.s, follow is the instruction from ixp460 developer's manual. Does anyone
can help me realize those code from No.4 t
Hello all,
I am testing a 2.6.29.3 (with preempt_rt patches) kernel on a phytec
pcm030 and am getting a kernel hang when testing the fec Ethernet
controller. The error only occurs when running the preempt-patched
kernel, an unmodified kernel works fine. Is anyone out there using
preempt_rt on
We experience exactly the same problem. Our client is Debian Testing
(_Squeeze_) x86 – diskless node which uses nfsroot and boots from the server
also Debian Testing (_Squeeze_) x86. While the client hang the server is
responding to everyone else's requests. Restarting the nfsd on the server
doesn
Hi Kumar,
On Mon, 18 May 2009 07:56:27 -0500 Kumar Gala wrote:
>
> We shouldn't directly access sysdata to get the device node. We should
> be calling pci_device_to_OF_node().
>
> Signed-off-by: Kumar Gala
> ---
> * Fixed compile error (dev -> pdev)
I tested the previous version with the typo
From: Gabriel Paubert
Date: Tue, 19 May 2009 01:21:13 +0200
> Since PPC_MUTIPLATFORM was removed, it was impossible to select the
> driver for mv643xx_eth on the Pegasos. Fix it and take the opportunity
> to remove the stale MV64360 config option.
>
> Signed-off-by: Gabriel Paubert
This patch
On Mon, May 18, 2009 at 4:49 PM, Timur Tabi wrote:
> On Thu, May 14, 2009 at 11:10 AM, Grant Likely
> wrote:
>> In other words, write your patches which use it and submit the lot as
>> a patch series with this patch as the first. That gives some evidence
>> that this macro will actually be used
On Mon, 18 May 2009 20:58:03 -0600
Grant Likely wrote:
> Then let it lie fallow on the list and in patchwork. It is published,
> and people know that it is available (I'll certainly consider it as I
> do driver work), but there must be real (not just theoretical) in
> kernel users of the interfa
Since you have reuse most part of our BSP, why should you reinvent wheel for
MPC512x DMA? We have one ready DMA driver, which has been used by AC97, ATA,
VIU etc.
Hongjun Chen
2009-05-19
发件人： Wolfgang Denk
发送时间： 2009-05-07 04:15:18
收件人： linuxppc-dev@ozlabs.org
抄送： Piotr Ziecik; Wolfgang De
This fixes MAL (arbitration lost) bug caused by illegal use of
RSTA (repeated START) after STOP condition generated after last byte
of reads. With this patch, it is possible to do an i2c_transfer() with
additional i2c_msg's following the I2C_M_RD messages.
It still needs to be resolved if it is p
CC'ed linux-kernel
On Thu, 14 May 2009 17:42:28 -0500
Becky Bruce wrote:
> This patch includes the basic infrastructure to use swiotlb
> bounce buffering on 32-bit powerpc. It is not yet enabled on
> any platforms. Probably the most interesting bit is the
> addition of addr_needs_map to dma_op
Ben,
This is based on benh/next and fixes the cpm cruft patch to drop the
removal of IMAP_ADDR from cpm1 so we still build on 8xx. Will deal with
that when we get into the merge window for 2.6.31.
- k
Please pull from 'next' branch of
master.kernel.org:/pub/scm/linux/kernel/git/galak/p
55 matches
Mail list logo
