On Wed, 2009-04-08 at 15:53 -0500, Kumar Gala wrote:
> I was wondering if we have anything that tracks regions associated
> with the "inbound" side of a pci_bus.
>
> What I mean is on embedded PPC we have window/mapping registers for
> both inbound (accessing memory on the SoC) and outbound (a
Michael Ellerman wrote:
On Wed, 2009-04-08 at 23:23 -0500, Kumar Gala wrote:
On Apr 8, 2009, at 6:53 PM, Michael Ellerman wrote:
On Wed, 2009-04-08 at 17:15 -0500, Timur Tabi wrote:
On Wed, Apr 8, 2009 at 4:31 PM, Tejun Heo wrote:
Hmmm... for now,
I think it would be best to revert the orig
On Apr 8, 2009, at 11:38 PM, Michael Ellerman wrote:
On Wed, 2009-04-08 at 23:23 -0500, Kumar Gala wrote:
On Apr 8, 2009, at 6:53 PM, Michael Ellerman wrote:
On Wed, 2009-04-08 at 17:15 -0500, Timur Tabi wrote:
On Wed, Apr 8, 2009 at 4:31 PM, Tejun Heo wrote:
Hmmm... for now,
I think it w
On Wed, 2009-04-08 at 23:23 -0500, Kumar Gala wrote:
> On Apr 8, 2009, at 6:53 PM, Michael Ellerman wrote:
>
> > On Wed, 2009-04-08 at 17:15 -0500, Timur Tabi wrote:
> >> On Wed, Apr 8, 2009 at 4:31 PM, Tejun Heo wrote:
> >>> Hmmm... for now,
> >>> I think it would be best to revert the original
On Apr 8, 2009, at 6:53 PM, Michael Ellerman wrote:
On Wed, 2009-04-08 at 17:15 -0500, Timur Tabi wrote:
On Wed, Apr 8, 2009 at 4:31 PM, Tejun Heo wrote:
Hmmm... for now,
I think it would be best to revert the original change. Jeff, can
you
please do that?
Actually, give me a few days
On Wed, 2009-04-08 at 14:26 +1000, Tony Breeds wrote:
> Also silences the warning:
> arch/powerpc/sysdev/mpic.c: In function 'mpic_irq_set_priority':
> arch/powerpc/sysdev/mpic.c:1382: warning: 'is_ipi' may be used uninitialized
> in this function
>
> Signed-off-by: Tony Breeds
> ---
> Only comp
Hi John,
On Wed, 8 Apr 2009 15:11:25 -0600 John Linn wrote:
>
> * 2002-2007 (c) MontaVista Software, Inc.
> * 2007 (c) Secret Lab Technologies, Ltd.
> + * 2009 (c) Xilinx Inc.
> *
> - * This file is licensed under the terms of the GNU General Public License
> - * version 2. This program is
On Wed, Apr 08, 2009 at 01:47:36PM -0500, Nathan Lynch wrote:
> I think I had some reason for doing it this way, but I'm drawing a
> blank right now.
>
> In the meantime, can someone post the warnings that gcc emits for
> cacheinfo.c, as well as the gcc version? I can't reproduce them with
> 4.3
On Wed, 2009-04-08 at 17:15 -0500, Timur Tabi wrote:
> On Wed, Apr 8, 2009 at 4:31 PM, Tejun Heo wrote:
> > Hmmm... for now,
> > I think it would be best to revert the original change. Jeff, can you
> > please do that?
>
> Actually, give me a few days before you do that. A colleague gave me
> s
Hi everyone,
I have a board similar to the ml410, its been running a linux kernel happily
for about a year now, but now the firmware guys want NPTL threading instead
of the linuxthread library.
I recompiled my gcc 4.0.2 and glibc 2.3.6 library with the NPTL support, and
recompiled my kernel with
On Wed, Apr 8, 2009 at 4:31 PM, Tejun Heo wrote:
> Hmmm... for now,
> I think it would be best to revert the original change. Jeff, can you
> please do that?
Actually, give me a few days before you do that. A colleague gave me
some suggestions to debug this.
--
Timur Tabi
Linux kernel develop
On Wed, Apr 08, 2009 at 03:53:55PM -0500, Kumar Gala wrote:
> I was wondering if we have anything that tracks regions associated with
> the "inbound" side of a pci_bus.
>
> What I mean is on embedded PPC we have window/mapping registers for both
> inbound (accessing memory on the SoC) and outboun
On Apr 8, 2009, at 4:49 PM, Ira Snyder wrote:
On Wed, Apr 08, 2009 at 03:53:55PM -0500, Kumar Gala wrote:
I was wondering if we have anything that tracks regions associated
with
the "inbound" side of a pci_bus.
What I mean is on embedded PPC we have window/mapping registers for
both
inbo
Timur Tabi wrote:
> Tejun Heo wrote:
>
>> Yeah, right. The following patch should do the trick then.
>
> Thanks, I appreciate it. I get this output:
>
> XXX PCI_COMMAND=0x407
^
Yeah, that's INTX disable. Strange that the controller has the bit
set on boot. I'm curious wh
Tejun Heo wrote:
> Yeah, right. The following patch should do the trick then.
Thanks, I appreciate it. I get this output:
XXX PCI_COMMAND=0x407
--
Timur Tabi
Linux kernel developer at Freescale
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
From: Suneel <[mailto:suneel.garap...@xilinx.com]>
Added support for the new xps tft controller.
The new core has PLB interface support in addition to existing
DCR interface.
The driver has been modified to support this new core which
can be connected on PLB or DCR bus.
Signed-off-by: Suneel
S
Timur Tabi wrote:
> Tejun Heo wrote:
>
>> Running "lspci -nnvvvxxx" before loading the driver should be enough.
>
> That might be difficult. My root file system is on my SATA drive.
> It'll be a while before I can build an NFS rootfs.
>
Yeah, right. The following patch should do the trick the
Tejun Heo wrote:
> Running "lspci -nnvvvxxx" before loading the driver should be enough.
That might be difficult. My root file system is on my SATA drive.
It'll be a while before I can build an NFS rootfs.
--
Timur Tabi
Linux kernel developer at Freescale
__
Timur Tabi wrote:
> On Tue, Apr 7, 2009 at 9:09 PM, Michael Ellerman
> wrote:
>
>> Have you confirmed that INTX is disabled before that call?
>
> How do I do that?
Running "lspci -nnvvvxxx" before loading the driver should be enough.
--
tejun
___
L
I was wondering if we have anything that tracks regions associated
with the "inbound" side of a pci_bus.
What I mean is on embedded PPC we have window/mapping registers for
both inbound (accessing memory on the SoC) and outbound (access PCI
device MMIO, IO etc). The combination of the inbo
Hi Johannes,
Thanks for the fast answer.
On Wed, 08 Apr 2009 17:51:39 +0200, Johannes Berg wrote:
> > Basically the idea is to move the I2C device instantiation from the
> > codec drivers (onyx, tas) to the I2C adapter driver (i2c-powermac.)
> > This follows the Linux device driver model, require
Kumar Gala wrote:
>
> On Apr 8, 2009, at 2:25 AM, Wolfgang Grandegger wrote:
>
>>> So I'm a bit concerned with the output we now get:
>>>
>>> mpc-i2c fffe03000.i2c: clock 0 Hz (dfsrr=16 fdr=49)
>>>
>>> why 0? is that right?
>>
>> This is the backward compatibility mode using hard-coded FDR values
Kumar Gala wrote:
>
> On Apr 8, 2009, at 1:27 PM, Wolfgang Grandegger wrote:
>
>> Grant Likely wrote:
>>> On Wed, Apr 8, 2009 at 12:16 AM, Wolfgang Grandegger
>>> wrote:
Grant Likely wrote:
> On Tue, Apr 7, 2009 at 1:20 AM, Wolfgang Grandegger
> wrote:
>> Preserve I2C clock set
Michael Ellerman wrote:
> On Wed, 2009-04-08 at 15:51 +1000, Tony Breeds wrote:
> > On Wed, Apr 08, 2009 at 03:08:55PM +1000, Michael Ellerman wrote:
> >
> > > The getter routines in here could really multiplex their return values
> > > with a negative error code, which I generally prefer, but t
On Apr 8, 2009, at 1:27 PM, Wolfgang Grandegger wrote:
Grant Likely wrote:
On Wed, Apr 8, 2009 at 12:16 AM, Wolfgang Grandegger > wrote:
Grant Likely wrote:
On Tue, Apr 7, 2009 at 1:20 AM, Wolfgang Grandegger > wrote:
Preserve I2C clock settings for the Socrates MPC8544 board.
I had thought
Stefan,
Ack. We usually do all this setup in U-Boot. But as I understand Eddie, he is
using a custom bootloader.
Correct, I'll put this code in the platform initialization. Thanks for the
suggestions everyone.
Eddie, btw: Why are you not using U-Boot?
At Technologic Systems, one of our d
Grant Likely wrote:
> On Wed, Apr 8, 2009 at 12:16 AM, Wolfgang Grandegger
> wrote:
>> Grant Likely wrote:
>>> On Tue, Apr 7, 2009 at 1:20 AM, Wolfgang Grandegger
>>> wrote:
Preserve I2C clock settings for the Socrates MPC8544 board.
>>> I had thought that the preserve-clocking property wa
On Wednesday 08 April 2009, Grant Likely wrote:
> >> I would like to eventually submit our changes for upstream support.
> >> Based on this would you recommend ensuring tx enable is configured
> >> properly in the initialization of the ibm_newemac driver or the platform
> >> initialization?
> >
> >
On Apr 8, 2009, at 12:03 PM, Scott Wood wrote:
On Wed, Apr 08, 2009 at 12:22:29AM -0500, Kumar Gala wrote:
hrummm. As I mentioned in my reply, I'm not convinced that the
board
one is the right thing in this case. I would have preferred it to
be
deferred.
which part? I missed this whol
Hi!
> Basically the idea is to move the I2C device instantiation from the
> codec drivers (onyx, tas) to the I2C adapter driver (i2c-powermac.)
> This follows the Linux device driver model, requires slightly less
> code, runs faster and and lets the required chip drivers be loaded by
> udev or sim
On Wed, Apr 08, 2009 at 12:22:29AM -0500, Kumar Gala wrote:
> >hrummm. As I mentioned in my reply, I'm not convinced that the board
> >one is the right thing in this case. I would have preferred it to be
> >deferred.
>
> which part? I missed this whole thread as I had it forwarding to my
> de
On Wed, Apr 8, 2009 at 9:01 AM, Stefan Roese wrote:
> On Wednesday 08 April 2009, Eddie Dawydiuk wrote:
>> > I found the ibm_newemac driver(2.6.29) makes the assumption that the
>> > bootloader has already configured the tx enable pin as it is a
>> > multiplexed pin. Unfortuantley I am not using U
On Wednesday 08 April 2009, Eddie Dawydiuk wrote:
> > I found the ibm_newemac driver(2.6.29) makes the assumption that the
> > bootloader has already configured the tx enable pin as it is a
> > multiplexed pin. Unfortuantley I am not using U-Boot and our minimal
> > bootloader does not do this. Af
On Wed, Apr 08, 2009 at 10:21:54AM -0500, Kumar Gala wrote:
>
> On Apr 8, 2009, at 9:48 AM, Olof Johansson wrote:
>
>> On Wed, Apr 08, 2009 at 09:23:22AM -0500, Kumar Gala wrote:
>>> Do we have anywhere to list out compatible strings that are
>>> deprecated
>>> and warn if the kernel sees one?
>>
On Wed, Apr 08, 2009 at 09:48:45AM -0500, Olof Johansson wrote:
> On Wed, Apr 08, 2009 at 09:23:22AM -0500, Kumar Gala wrote:
> > Do we have anywhere to list out compatible strings that are deprecated
> > and warn if the kernel sees one?
>
> Wouldn't dtc be a better location for that? The kernel
Hello,
I found the ibm_newemac driver(2.6.29) makes the assumption that the
bootloader has already configured the tx enable pin as it is a
multiplexed pin. Unfortuantley I am not using U-Boot and our minimal
bootloader does not do this. After finding tx enable was never
asserting for Eth0 a
On Apr 8, 2009, at 9:48 AM, Olof Johansson wrote:
On Wed, Apr 08, 2009 at 09:23:22AM -0500, Kumar Gala wrote:
Do we have anywhere to list out compatible strings that are
deprecated
and warn if the kernel sees one?
Wouldn't dtc be a better location for that? The kernel has to be
backwards
On Apr 8, 2009, at 2:25 AM, Wolfgang Grandegger wrote:
So I'm a bit concerned with the output we now get:
mpc-i2c fffe03000.i2c: clock 0 Hz (dfsrr=16 fdr=49)
why 0? is that right?
This is the backward compatibility mode using hard-coded FDR values.
The
output is missleading, I agree.
Wo
On Wed, Apr 8, 2009 at 12:16 AM, Wolfgang Grandegger
wrote:
> Grant Likely wrote:
>> On Tue, Apr 7, 2009 at 1:20 AM, Wolfgang Grandegger
>> wrote:
>>> Preserve I2C clock settings for the Socrates MPC8544 board.
>>
>> I had thought that the preserve-clocking property was intended for
>> older bo
On Wed, Apr 08, 2009 at 09:23:22AM -0500, Kumar Gala wrote:
> Do we have anywhere to list out compatible strings that are deprecated
> and warn if the kernel sees one?
Wouldn't dtc be a better location for that? The kernel has to be backwards
compatible anyway, I don't really see a reason to war
Do we have anywhere to list out compatible strings that are deprecated
and warn if the kernel sees one?
- k
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
Hi all,
The legacy i2c model is going away soon, the remaining drivers that
still use it need to be converted very quickly. There are 3 sound
drivers remaining:
sound/aoa/codecs/onyx.c
sound/aoa/codecs/tas.c
sound/ppc/keywest.c
I've given a try to the former two, patch below. I could only
build-
On Tue, Apr 7, 2009 at 9:09 PM, Michael Ellerman wrote:
> Have you confirmed that INTX is disabled before that call?
How do I do that?
--
Timur Tabi
Linux kernel developer at Freescale
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozl
> "Anton" == Anton Vorontsov writes:
Hi,
Anton> The advantages of this:
Anton> - Don't encourage legacy support;
Anton> - Less external symbols, less code to compile-in for !MPC832x_RDB
Anton> platforms.
It's nice with your cleanups, but I wonder how to handle more
complicated chip se
I was executing libhugetlbfs tests on a power6 box [9117-MMA]. One of the
sub test (shm-fork) caused the machine to crash. Here is the information :
llm62 login: cpu 0x1: Vector: 300 (Data Access) at [c000f9827490]
pc: c0038028: .hpte_need_flush+0x1b8/0x2d8
lr: c0037edc:
On Wed, 8 Apr 2009, Michael Ellerman wrote:
> On Wed, 2009-04-08 at 15:51 +1000, Tony Breeds wrote:
> > On Wed, Apr 08, 2009 at 03:08:55PM +1000, Michael Ellerman wrote:
> >
> > > The getter routines in here could really multiplex their return values
> > > with a negative error code, which I gener
Kumar Gala wrote:
>
> On Apr 8, 2009, at 12:11 AM, Kumar Gala wrote:
>
>>
>> On Apr 7, 2009, at 3:20 AM, Wolfgang Grandegger wrote:
>>
>>> This patch series makes the I2C bus speed configurable by using the
>>> I2C node property "clock-frequency". If the property is not defined,
>>> the old fixed
Michael Ellerman wrote:
On Tue, 2009-04-07 at 19:36 -0500, Timur Tabi wrote:
On Tue, Apr 7, 2009 at 6:57 PM, Tejun Heo wrote:
Hmmm... that means intx isn't set by default. I'm not sure what is
the right thing to do here. I think it's something which should be
handled by the PCI layer. Oh w
Kumar Gala wrote:
>
> On Apr 8, 2009, at 12:16 AM, Grant Likely wrote:
>
>> On Tue, Apr 7, 2009 at 10:11 PM, Kumar Gala
>> wrote:
>>>
>>> On Apr 7, 2009, at 3:20 AM, Wolfgang Grandegger wrote:
>>>
This patch series makes the I2C bus speed configurable by using the
I2C node property "cl
Grant Likely wrote:
> On Tue, Apr 7, 2009 at 1:20 AM, Wolfgang Grandegger
> wrote:
>> Preserve I2C clock settings for the Socrates MPC8544 board.
>
> I had thought that the preserve-clocking property was intended for
> older boards that don't currently have any method of getting the clock
> sett
50 matches
Mail list logo
