Hello.
Albert Lee wrote:
b) puts more work [the enter test mode stuff] in between the start
and and sampling points, reducing the precision of the PLL
detection; I actually observed quite noticeable differences
in detected PLL frequency based on whether the start was sampled
before or
Hello.
Jeff Garzik wrote:
What have really surpried me about Promise was that they gave their
SATA chip docs to Jeff who made them public and yet they continue to
conceal the old PATA chip docs... :-/
They probably just need to be poked. I've been sitting on the sata_sx4
It's not
On Friday 24 August 2007, Sergei Shtylyov wrote:
Hello.
Albert Lee wrote:
b) puts more work [the enter test mode stuff] in between the start
and and sampling points, reducing the precision of the PLL
detection; I actually observed quite noticeable differences
in detected PLL
Hello.
Bartlomiej Zolnierkiewicz wrote:
b) puts more work [the enter test mode stuff] in between the start
and and sampling points, reducing the precision of the PLL
detection; I actually observed quite noticeable differences
in detected PLL frequency based on whether the start was sampled
Sergei Shtylyov wrote:
Hello.
Mikael Pettersson wrote:
Previously I reported that the pata_pdc2027x PLL detection changes
in kernel 2.6.22 broke the driver on my PowerMac:
pata_pdc2027x: Invalid PLL input clock 1691742kHz, give up!
This is followed by a number of errors and speed
Mikael Pettersson wrote:
Previously I reported that the pata_pdc2027x PLL detection changes
in kernel 2.6.22 broke the driver on my PowerMac:
pata_pdc2027x: Invalid PLL input clock 1691742kHz, give up!
This is followed by a number of errors and speed reduction
steps on the affected ports.
On Sun, 19 Aug 2007 20:13:46 +0400, Sergei Shtylyov wrote:
Mikael Pettersson wrote:
Previously I reported that the pata_pdc2027x PLL detection changes
in kernel 2.6.22 broke the driver on my PowerMac:
pata_pdc2027x: Invalid PLL input clock 1691742kHz, give up!
This is followed by a
Hello.
Mikael Pettersson wrote:
Previously I reported that the pata_pdc2027x PLL detection changes
in kernel 2.6.22 broke the driver on my PowerMac:
pata_pdc2027x: Invalid PLL input clock 1691742kHz, give up!
This is followed by a number of errors and speed reduction
steps on the
Sergei Shtylyov wrote:
What have really surpried me about Promise was that they gave their
SATA chip docs to Jeff who made them public and yet they continue to
conceal the old PATA chip docs... :-/
They probably just need to be poked. I've been sitting on the sata_sx4
docs and cards,
Previously I reported that the pata_pdc2027x PLL detection changes
in kernel 2.6.22 broke the driver on my PowerMac:
pata_pdc2027x: Invalid PLL input clock 1691742kHz, give up!
This is followed by a number of errors and speed reduction
steps on the affected ports.
There are two bugs in
Mikael Pettersson wrote:
Previously I reported that the pata_pdc2027x PLL detection changes
in kernel 2.6.22 broke the driver on my PowerMac:
pata_pdc2027x: Invalid PLL input clock 1691742kHz, give up!
This is followed by a number of errors and speed reduction
steps on the affected ports.
Mikael Pettersson wrote:
Previously I reported that the pata_pdc2027x PLL detection changes
in kernel 2.6.22 broke the driver on my PowerMac:
pata_pdc2027x: Invalid PLL input clock 1691742kHz, give up!
This is followed by a number of errors and speed reduction
steps on the affected
Jeff Garzik wrote:
Mikael Pettersson wrote:
Previously I reported that the pata_pdc2027x PLL detection changes
in kernel 2.6.22 broke the driver on my PowerMac:
pata_pdc2027x: Invalid PLL input clock 1691742kHz, give up!
This is followed by a number of errors and speed reduction
steps
Albert Lee wrote:
The first rmb() is to make sure bccrl is read before bccrlv for later
(bccrl = bccrlv) check since both reading the same memory address.
That's already guaranteed without the rmb(), AFAICS.
Jeff
-
To unsubscribe from this list: send the line unsubscribe linux-ide
Jeff Garzik wrote:
Albert Lee wrote:
The first rmb() is to make sure bccrl is read before bccrlv for later
(bccrl = bccrlv) check since both reading the same memory address.
That's already guaranteed without the rmb(), AFAICS.
Hmm, thanks for the advice. Will remove both rmb()s.
Will
15 matches
Mail list logo