On Iau, 2005-04-21 at 06:54, Albert Lee wrote:
> A particular revision of the HPT372N oopses hpt366 consistently. It's a
> regression caused by Alan's changes in 2.6.9 to support the HPT372N using
> only PLL timings. The driver works correctly in prior versions, where the the
> PCI clock is
On Iau, 2005-04-21 at 06:54, Albert Lee wrote:
A particular revision of the HPT372N oopses hpt366 consistently. It's a
regression caused by Alan's changes in 2.6.9 to support the HPT372N using
only PLL timings. The driver works correctly in prior versions, where the the
PCI clock is used
A particular revision of the HPT372N oopses hpt366 consistently. It's a
regression caused by Alan's changes in 2.6.9 to support the HPT372N using
only PLL timings. The driver works correctly in prior versions, where the the
PCI clock is used instead. This patch restores that behaviour for this
A particular revision of the HPT372N oopses hpt366 consistently. It's a
regression caused by Alan's changes in 2.6.9 to support the HPT372N using
only PLL timings. The driver works correctly in prior versions, where the the
PCI clock is used instead. This patch restores that behaviour for this
4 matches
Mail list logo