> "John" == John Stoffel <[EMAIL PROTECTED]> writes:
> "John" == John Stoffel <[EMAIL PROTECTED]> writes:
> Ok, so do I need to do anything special with the next -mm release and
> the next version?
Well, let Alan decide that (2Alan: and I said that HPT code is bogus
> "John" == John Stoffel <[EMAIL PROTECTED]> writes:
>>> > Ok, so do I need to do anything special with the next -mm release and
>>> > the next version?
>>>
>>> Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).
Alan> Try drivers/ide/pci/hpt366 - if that works grab a
John == John Stoffel [EMAIL PROTECTED] writes:
Ok, so do I need to do anything special with the next -mm release and
the next version?
Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).
Alan Try drivers/ide/pci/hpt366 - if that works grab a dmesg and let
Alan me
John == John Stoffel [EMAIL PROTECTED] writes:
John == John Stoffel [EMAIL PROTECTED] writes:
Ok, so do I need to do anything special with the next -mm release and
the next version?
Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).
Alan Try drivers/ide/pci/hpt366
Sergei Shtylyov wrote:
HPT chips are surely not a good example of how to do things, more like
an example how *not* to do. :-)
That explains a lot! :)
(guess who's first ATA work was on the Highpoint driver..
.. no need to post the answer here, though)
Cheers
-
To unsubscribe from this
Hello.
John Stoffel wrote:
Ok, so do I need to do anything special with the next -mm release and
the next version?
Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).
Alan> Try drivers/ide/pci/hpt366 - if that works grab a dmesg and let
Alan> me know. It means that
>> > Ok, so do I need to do anything special with the next -mm release and
>> > the next version?
>>
>> Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).
Alan> Try drivers/ide/pci/hpt366 - if that works grab a dmesg and let
Alan> me know. It means that Sergei's DPLL
> > Ok, so do I need to do anything special with the next -mm release and
> > the next version?
>
>Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).
Try drivers/ide/pci/hpt366 - if that works grab a dmesg and let me know.
It means that Sergei's DPLL sync code seems to
John Stoffel wrote:
I was just testing out 2.6.21-rc6-mm1 to test some Cyclades patches
and I noticed that my HPT302 (rev1) controller with a pair of 120gb WD
disks are not longer detected and I get the following in the dmesg
logs:
[ 148.121490] hpt37x: DPLL did not stabilize.
Where
> "Sergei" == Sergei Shtylyov <[EMAIL PROTECTED]> writes:
Sergei> Hello.
Sergei> John Stoffel wrote:
>> I was just testing out 2.6.21-rc6-mm1 to test some Cyclades patches
>> and I noticed that my HPT302 (rev1) controller with a pair of 120gb WD
>> disks are not longer detected and I get the
Hello.
John Stoffel wrote:
I was just testing out 2.6.21-rc6-mm1 to test some Cyclades patches
and I noticed that my HPT302 (rev1) controller with a pair of 120gb WD
disks are not longer detected and I get the following in the dmesg
logs:
[ 148.121490] hpt37x: DPLL did not stabilize.
Sergei == Sergei Shtylyov [EMAIL PROTECTED] writes:
Sergei Hello.
Sergei John Stoffel wrote:
I was just testing out 2.6.21-rc6-mm1 to test some Cyclades patches
and I noticed that my HPT302 (rev1) controller with a pair of 120gb WD
disks are not longer detected and I get the following in the
Hello.
John Stoffel wrote:
I was just testing out 2.6.21-rc6-mm1 to test some Cyclades patches
and I noticed that my HPT302 (rev1) controller with a pair of 120gb WD
disks are not longer detected and I get the following in the dmesg
logs:
[ 148.121490] hpt37x: DPLL did not stabilize.
John Stoffel wrote:
I was just testing out 2.6.21-rc6-mm1 to test some Cyclades patches
and I noticed that my HPT302 (rev1) controller with a pair of 120gb WD
disks are not longer detected and I get the following in the dmesg
logs:
[ 148.121490] hpt37x: DPLL did not stabilize.
Where
Ok, so do I need to do anything special with the next -mm release and
the next version?
Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).
Try drivers/ide/pci/hpt366 - if that works grab a dmesg and let me know.
It means that Sergei's DPLL sync code seems to work
Ok, so do I need to do anything special with the next -mm release and
the next version?
Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).
Alan Try drivers/ide/pci/hpt366 - if that works grab a dmesg and let
Alan me know. It means that Sergei's DPLL sync code seems
Hello.
John Stoffel wrote:
Ok, so do I need to do anything special with the next -mm release and
the next version?
Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).
Alan Try drivers/ide/pci/hpt366 - if that works grab a dmesg and let
Alan me know. It means that
Sergei Shtylyov wrote:
HPT chips are surely not a good example of how to do things, more like
an example how *not* to do. :-)
That explains a lot! :)
(guess who's first ATA work was on the Highpoint driver..
.. no need to post the answer here, though)
Cheers
-
To unsubscribe from this
Hi Jeff and crew,
I was just testing out 2.6.21-rc6-mm1 to test some Cyclades patches
and I noticed that my HPT302 (rev1) controller with a pair of 120gb WD
disks are not longer detected and I get the following in the dmesg
logs:
[ 148.121490] hpt37x: DPLL did not stabilize.
Where before,
Hi Jeff and crew,
I was just testing out 2.6.21-rc6-mm1 to test some Cyclades patches
and I noticed that my HPT302 (rev1) controller with a pair of 120gb WD
disks are not longer detected and I get the following in the dmesg
logs:
[ 148.121490] hpt37x: DPLL did not stabilize.
Where before,
20 matches
Mail list logo
