> Sorry for this delay response since I'm a bit busying recently:)
No. Don't feel sorry about it. You're not obligated to answer any
questions here. I believe it is the free and willing to help spirit
that drive the open source community (linux particularly) to be such a
success. We all benefit fr
Bounine, Alexandre wrote:
Micha Nelissen wrote:
that switch. The tag uses one extra bit to identify the device as a
switch instead of an endpoint. This provides the information to
unambiguously identify a switch from an endpoint.
OK taking away #2. But do not see how it justifies storing two
Hi,
I have a G5 (dual 970FX, june 2004?) running YDL 6.0. After fighting
to get a compiler that will build 2.6.29+ (4.2.1 -> 4.2.2) I can't get
it to boot. It spits out a bunch of message about devices (I think the
last ones are USB related) and then says:
Restarting System
and then reboots. I'v
Micha Nelissen wrote:
>
> Bounine, Alexandre wrote:
> > 1. The destid for the switch needs an additional mechanism to share
it
> > among processors in the RIO network,
>
> ? See comment for 2)
>
> > 2. It takes ID value away from the pool of available IDs, what will
>
> It does not take an ID
Bounine, Alexandre wrote:
Micha Nelissen wrote:
rid of rswitch->switchid and use component_tag directly for
switches).
I still prefer the destid as the single identification id.
In your patch you allocate individual destid for switches. This method
has two problems:
1. The destid for the sw
On Mon, 2010-10-18 at 17:46 +0800, tiejun.chen wrote:
>
> >>> Looks you always iounmap(fsl_lbc_ctrl_dev->regs) on position 'err' but
> >>> here
> >>> of_iomap() is already failed you should skip iounmap()
> >>> fsl_lbc_ctrl_dev->regs
> >>> again. So you should improve that as the following on 'e
On Mon, Oct 25, 2010 at 09:57:10PM +0800, Yong Zhang wrote:
> On Mon, Oct 25, 2010 at 04:32:01PM +0530, divya wrote:
> > http://lkml.org/lkml/2010/10/13/67 resolves the issue.
> >
> > But this is not a part of 2.6.36-git6 , when will it be pulled into the
> > upstream?
>
> That patch is splited
On Mon, Oct 25, 2010 at 04:32:01PM +0530, divya wrote:
> http://lkml.org/lkml/2010/10/13/67 resolves the issue.
>
> But this is not a part of 2.6.36-git6 , when will it be pulled into the
> upstream?
That patch is splited into two parts.
The lockdep one is 4ba053c04aece1f4734056f21b751eee47ea3fb
Micha Nelissen wrote:
> Bounine, Alexandre wrote:
> > If we will need to identify the same physical switch by different
> > processors we may use the component tag which now is unique for
every
> > device.
>
> Yes, identification is the point. I think it might be confusing to
have
> a destid *and
Hello,
I recently tried to switch to 2.6.36 (torvalds/master) using a
Lite5200B compatible board.
Using 2.6.34 we were running ATA in MWDMA 2 to avoid MPC5200B HW
problems with UDMA.
But with 2.6.36 I get only ATA errors (PIO4 is working fine):
...
ata: MPC52xx IDE/ATA libata driver
scsi0 : mpc
On Saturday 23 October 2010 03:06 PM, Yong Zhang wrote:
On Sat, Oct 23, 2010 at 12:43:21AM +0530, Subrata Modak wrote:
This is equally seen for both Power6 and Power7 machines.
Seems resolved by part of http://lkml.org/lkml/2010/10/13/67
Thanks,
Yong
Regards--
Subrata
On Sat,
On Friday 15 October 2010 02:16 AM, Frank Ch. Eigler wrote:
divya writes:
While running systemtap tests on the p6 machine , against the kernel
version 2.6.36-rc7-git3 Oops occured , here are the call trace
Did the oops happen during a systemtap module startup vs. operation
vs. shutd
PT7C4338 chip is manufactured by Pericom Technology Inc.
It is a serial real-time clock which provides:
1)Low-power clock/calendar.
2)Programmable square-wave output.
It has 56 bytes of nonvolatile RAM.
Freescale P1010RDB uses PT7C4338 as RTC.
Signed-off-by: Priyanka Jain
---
Based of unified g
Shawn Jin wrote:
>> The problem for me is that the PHY failed to be probed. The related
>> error messages are shown below. I even tried the patch Tiejun pointed
>> out. But that doesn't help. The phy ID read from the bus was all Fs.
>>
>> FEC MII Bus: probed
>> mdio_bus fa200e00: error probing PHY
Hello List Members,
I updated to v2.6.34 from torvalds/master.
While playing around with ATA settings (I have problems with MWDMA2 on
a Lite5200B compatible board, the problems are not related to this
patch here), I also turned off BMDMA, which caused compile errors on
pata_mpc52xx. So my questio
15 matches
Mail list logo
