At Sat, 19 Feb 2011 15:53:46 +0100,
Linux User #330250 wrote:
Hello!
About two years ago Johannes Berg wrote support for the PowerMac3,6 aka G4
MDD
which I was using as a desktop computer then. Johannes wrote all the code,
and
I tested it.
I now have a PowerMac3,5 – yes, an
Hi everyone,
I've this PowerMac G5 machine I'd like to use as a server. It makes
perfect sense to install Linux on it for several reasons :
- OS X isn't maintained on this hardware anymore
- Those machine are still reasonnably fast. They sure aren't the
latest and greatest, but they still do a
Surprisingly, the Linux kernel does a very good job on this machine in
terms of hardware support and stability : everything works perfectly.
But the global OS fails pathetically in the two said points.
Here are my findings so far, I hope it will help people in the same situation
:
1/
On Mon, 2011-02-21 at 07:05 +1100, Benjamin Herrenschmidt wrote:
Yes, there is. We reverse engineered that a while back and somebody even
wrote a little tool to control it, though I don't remember where that
can be found... If necessary, we can try to dig again, the RE wasn't
that hard.
a
Hello again!
Sorry for sending the patch three times. (This is the fourth...)
About the sign-off: I use the name I've been using since I started
participating. The document $LINUX/Documentation/SubmittingPatches clearly
states that one has to use real names. I'm breaking this rule, but I'm not
RHEL6 problem was that it crashed when doing
echo 3 /sys/devices/system/cpu/dscr_default
because access methods for SYSDEV_ATTR and SYSDEV_CLASS_ATTR have
different number of parameters in RHEL6. It was not correct for 2.6.36
either but the parameters number is the same for both SYSDEV_ATTR
When a single device error is detected, the device under the error is indicated
by the error bit set in the DER. There is a one to one mapping between register
bit and devices on Port multiplier(PMP) i.e. bit 0 represents PMP device 0 and
bit 1 represents PMP device 1 etc.
Current implementation
RX_WATER_MARK sets the number of locations in Rx FIFO that can be used before
the transport layer instructs the link layer to transmit HOLDS. Note that it
can take some time for the HOLDs to get to the other end, and that in the
interim there must be enough room in the FIFO to absorb all data that
