Without going into much details of your particular case, I can share
my experience doing a similar thing with a different freescale CPU:
- CONFIG_FIXED_PHY needs to be enabled (this activates a "pseudo phy")
- the TBI (ten bit interface) is an internal device attached to the
MII interface associa
I have a system with an SGMII interface on an MPC8536E, attached to a
Marvel 88E6152 Ethernet switch chip. I can access Ethernet from u-boot,
if I initially configure the MII "phy" and the switch port PHY to
disable auto-negotiation and assert link up. The link speed is 10Mbps
and it is half-dupl
Hi,
I'm trying to drive SCC of MPC860 as HDLC mode under linux2.6.
Is there a completely driver? Who know this?
Best regards!
Alex ho.
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxp
On 02/24/2010 03:25 PM, Kumar Gala wrote:
On Feb 24, 2010, at 4:14 PM, Gary Thomas wrote:
On 02/24/2010 01:51 PM, Anton Vorontsov wrote:
On Wed, Feb 24, 2010 at 02:26:20PM -0600, Scott Wood wrote:
Gary Thomas wrote:
Yes, I'm using the exact same kernel with these two different PCI
setups (d
On Feb 24, 2010, at 4:14 PM, Gary Thomas wrote:
> On 02/24/2010 01:51 PM, Anton Vorontsov wrote:
>> On Wed, Feb 24, 2010 at 02:26:20PM -0600, Scott Wood wrote:
>>> Gary Thomas wrote:
Yes, I'm using the exact same kernel with these two different PCI
setups (done by the boot loader).
On 2/19/2010 1:54 PM, Benjamin Herrenschmidt wrote:
On Fri, 2010-02-19 at 14:43 -0200, Breno Leitao wrote:
Hi Ben,
I'd like to ask about this patch ? Should I re-submit ?
Thanks,
Breno Leitao wrote:
During a EEH recover, the pci_dev structure can be null, mainly if an
eeh event is detected d
On 02/24/2010 01:51 PM, Anton Vorontsov wrote:
On Wed, Feb 24, 2010 at 02:26:20PM -0600, Scott Wood wrote:
Gary Thomas wrote:
Yes, I'm using the exact same kernel with these two different PCI
setups (done by the boot loader).
Restricting the memory via mem=128M has no effect - the PCI layout
i
This is started as swsusp_32.S modifications, but the amount of #ifdefs
made the whole file horribly unreadable, so let's put the support into
its own separate file.
The code should be relatively easy to modify to support 44x BookEs as
well, but since I don't have any 44x to test, let's confine th
On Wed, Feb 24, 2010 at 02:26:20PM -0600, Scott Wood wrote:
> Gary Thomas wrote:
> >Yes, I'm using the exact same kernel with these two different PCI
> >setups (done by the boot loader).
> >
> >Restricting the memory via mem=128M has no effect - the PCI layout
> >is the same.
> >
> >I think the out
Gary Thomas wrote:
Yes, I'm using the exact same kernel with these two different PCI
setups (done by the boot loader).
Restricting the memory via mem=128M has no effect - the PCI layout is
the same.
I think the outbound window size is required because of how the Linux PCI
remaps the space (no
Alexandre Bounine wrote:
/**
+ * rio_em_set_ops- Sets Error Managment operations for a particular vendor
switch
+ * @rdev: RIO device
+ *
+ * Searches the RIO EM ops table for known switch types. If the vid
+ * and did match a switch table entry, then set the em_init() and
+ * em_handle() ops t
Alexandre Bounine wrote:
@@ -369,6 +380,10 @@ static struct rio_dev __devinit *rio_set
rdev->rswitch->switchid);
rio_route_set_ops(rdev);
+ if (do_enum && rdev->rswitch->clr_table)
+ rdev->rswitch->clr_table(port, destid, hopc
On 02/24/2010 12:31 PM, Scott Wood wrote:
Gary Thomas wrote:
On 02/24/2010 11:48 AM, Scott Wood wrote:
Gary Thomas wrote:
Does anyone have experience setting up the PCI controller on
the MPC8349? I have it running fine when my system has 128MB
or less of main memory, but when I have 256MB or m
Alexandre Bounine wrote:
+ /* Attempt to acquire device lock */
+ rio_mport_write_config_32(port, destid,
+ hopcount,
+ RIO_H
Gary Thomas wrote:
On 02/24/2010 11:48 AM, Scott Wood wrote:
Gary Thomas wrote:
Does anyone have experience setting up the PCI controller on
the MPC8349? I have it running fine when my system has 128MB
or less of main memory, but when I have 256MB or more, it all
falls apart :-(
Any indication
On 02/24/2010 11:48 AM, Scott Wood wrote:
Gary Thomas wrote:
Does anyone have experience setting up the PCI controller on
the MPC8349? I have it running fine when my system has 128MB
or less of main memory, but when I have 256MB or more, it all
falls apart :-(
Any indication of the pertinent se
Hi,
I'm working on implementing a linux 2.6.23 kernel for a machine based
on the MPC8313. It's
basically a clone of the Freescale ERDB dev kit module with the
addition of an FPGA on CS3 of the localbus.
(it also has NAND and a FLASH NOR part on the localbus as well).
All of the code is based off
Gary Thomas wrote:
Does anyone have experience setting up the PCI controller on
the MPC8349? I have it running fine when my system has 128MB
or less of main memory, but when I have 256MB or more, it all
falls apart :-(
Any indication of the pertinent settings would be appreciated.
Check the i
From: Thomas Moll
Fix the maintenance access functions to farend RapidIO devices.
1. Fixed shift of the given offset, to open the maintenance window
2. Mask offset to limit access to the opened maintenance window
3. Added extended destid part to rowtear register, required for 16bit mode
For eas
From: Alexandre Bounine
Extentions to RapidIO switch support:
1. modify switch route operation declarations to allow using single
switch-specific file for family of switches that share the same route
table operations.
2. add standard route table operations for switches that that support
From: Thomas Moll
Add the functionality to enable Input receiver and Output
transmitter of every port, to allow non-maintenance traffic.
Signed-off-by: Thomas Moll
---
drivers/rapidio/Kconfig| 11 ++
drivers/rapidio/rio-scan.c | 79 -
i
From: Alexandre Bounine
Add Machine Check exception handling into RapidIO port driver
for Freescale SoCs (MPC85xx).
Signed-off-by: Alexandre Bounine
Tested-by: Thomas Moll
---
fsl_rio.c | 74 ++
1 files changed, 70 insertions(+),
From: Alexandre Bounine
Add RapidIO Port-Write message handler for Freescale SoCs with RapidIO port.
Signed-off-by: Alexandre Bounine
Tested-by: Thomas Moll
---
fsl_rio.c | 263 +-
1 files changed, 260 insertions(+), 3 deletions(-
From: Alexandre Bounine
Add RapidIO Port-Write message handling in the context
of Error Management Extensions Specification Rev.1.3.
Signed-off-by: Alexandre Bounine
Tested-by: Thomas Moll
---
drivers/rapidio/rio-scan.c| 197 +++-
drivers/rapidio/rio.c
From: Alexandre Bounine
Add switch access locking during RapidIO discovery. Access lock is
required when reading switch routing table contents due to indexed mechanism
of RT addressing.
Signed-off-by: Alexandre Bounine
Tested-by: Thomas Moll
---
rio-scan.c | 88 +++
Does anyone have experience setting up the PCI controller on
the MPC8349? I have it running fine when my system has 128MB
or less of main memory, but when I have 256MB or more, it all
falls apart :-(
Any indication of the pertinent settings would be appreciated.
Thanks
--
-
On Tue, 23 Feb 2010, Anton Blanchard wrote:
> zone_reclaim_mode.txt
> Now we set zone_reclaim_mode = 1. On each iteration we continue to improve,
> but even after 10 runs of stream we have > 10% remote node memory usage.
The intend of zone reclaim was never to allocate all memory from on node.
Yo
Hi Ben,
Just sending a reminder on this pull request. I haven't seen these
commits show up in your -next branch yet.
Thanks,
g.
On Wed, Feb 17, 2010 at 11:37 PM, Grant Likely
wrote:
> Hi Ben,
>
> Here's all the stuff I've got queued up for 2.6.34. Mostly mpc5121
> support, but some 5200 stuff
On Wed, Feb 24, 2010 at 06:40:37AM -0700, Grant Likely wrote:
> On Wed, Feb 24, 2010 at 1:51 AM, Marcus Meissner wrote:
> > This fixes this build failure:
> > cc1: warnings being treated as errors
> > /usr/src/packages/BUILD/kernel-default-2.6.33/linux-2.6.32/arch/powerpc/platforms/52xx/mpc52xx_gp
On Wed, Feb 24, 2010 at 1:51 AM, Marcus Meissner wrote:
> This fixes this build failure:
> cc1: warnings being treated as errors
> /usr/src/packages/BUILD/kernel-default-2.6.33/linux-2.6.32/arch/powerpc/platforms/52xx/mpc52xx_gpt.c:
> In function 'mpc52xx_gpt_probe':
> /usr/src/packages/BUILD/ker
In message <11927.1267010...@neuling.org> you wrote:
> > > If there's less the group will normally be balanced and we fall out and
> > > end up in check_asym_packing().
> > >
> > > So what I tried doing with that loop is detect if there's a hole in the
> > > packing before busiest. Now that I thin
> > If there's less the group will normally be balanced and we fall out and
> > end up in check_asym_packing().
> >
> > So what I tried doing with that loop is detect if there's a hole in the
> > packing before busiest. Now that I think about it, what we need to check
> > is if this_cpu (the remov
This fixes this build failure:
cc1: warnings being treated as errors
/usr/src/packages/BUILD/kernel-default-2.6.33/linux-2.6.32/arch/powerpc/platforms/52xx/mpc52xx_gpt.c:
In function 'mpc52xx_gpt_probe':
/usr/src/packages/BUILD/kernel-default-2.6.33/linux-2.6.32/arch/powerpc/platforms/52xx/mpc52xx
33 matches
Mail list logo
