VIA VT610 IDE support for 2.4.28 (trivial)
Mathias Kretschmer
I found an older version of this patch (against 2.4.22) on some website.
After a little bit of editing it applied cleanly to 2.4.27 (and now
2.4.28). It works fine for me on a ASUS P4P800-Deluxe with 4x 300GB disks.
Maybe someone finds this patch helpful. Any reason why the original
patch did not make it into the kernel ?
-Mathias
Jeff Garzik
Why not add it to the existing via82cxxx driver, and get better
performance and device tuning?
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Mathias Kretschmer
> Mathias Kretschmer wrote:
>
>> hi,
>>
>> I found an older version of this patch (against 2.4.22) on some
>> website. After a little bit of editing it applied cleanly to 2.4.27
>> (and now 2.4.28). It works fine for me on a ASUS P4P800-Deluxe with
>> 4x 300GB disks.
>>
>> Maybe someone finds this patch helpful. Any reason why the original
>> patch did not make it into the kernel ?
>
>
> Why not add it to the existing via82cxxx driver, and get better
> performance and device tuning?
I only have that one ASUS board and there's data on the disks that I do
not want to loose.
The current patch worked well for me (performance is pretty decent), so
I went with it.
I can modify the VIA driver code, but looking at the various
exceptions/quirks for the various VIA chip sets, I'm a bit hesitant to
test it on my box.
-Mathias
Mathias Kretschmer
> Jeff Garzik wrote:
>
>> Mathias Kretschmer wrote:
>>
>>> hi,
>>>
>>> I found an older version of this patch (against 2.4.22) on some
>>> website. After a little bit of editing it applied cleanly to 2.4.27
>>> (and now 2.4.28). It works fine for me on a ASUS P4P800-Deluxe with
>>> 4x 300GB disks.
>>>
>>> Maybe someone finds this patch helpful. Any reason why the original
>>> patch did not make it into the kernel ?
>>
>>
>>
>> Why not add it to the existing via82cxxx driver, and get better
>> performance and device tuning?
OK, the attached patch adds support for the VIA 6410 chip to the
via82cxxx driver (instead of the generic driver).
I've tested it on the board mentioned above. Works fine for me.
Cheers,
Mathias
Jeff Garzik
Bart, got this one?
Jeff
Bartlomiej Zolnierkiewicz
> Mathias Kretschmer wrote:
> > Mathias Kretschmer wrote:
> >
> >> Mathias Kretschmer wrote:
> >>
> >>> Jeff Garzik wrote:
> >>>
> >>>> Mathias Kretschmer wrote:
> >>>>
> >>>>> hi,
> >>>>>
> >>>>> I found an older version of this patch (against 2.4.22) on some
> >>>>> website. After a little bit of editing it applied cleanly to 2.4.27
> >>>>> (and now 2.4.28). It works fine for me on a ASUS P4P800-Deluxe with
> >>>>> 4x 300GB disks.
> >>>>>
> >>>>> Maybe someone finds this patch helpful. Any reason why the original
> >>>>> patch did not make it into the kernel ?
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> Why not add it to the existing via82cxxx driver, and get better
> >>>> performance and device tuning?
> >>
> >>
> >>
> >> OK, the attached patch adds support for the VIA 6410 chip to the
> >> via82cxxx driver (instead of the generic driver).
> >> I've tested it on the board mentioned above. Works fine for me.
> >>
> >> Cheers,
> >>
> >> Mathias
> >
> >
> > as above, but for 2.6.11-rc3
>
> Bart, got this one?
I applied it (after whitespace cleanup) to ide-dev-2.6.
Thanks,
Bartlomiej
Sergey Vlasov
> On Mon, 07 Feb 2005 12:27:47 -0500, Jeff Garzik <jga...@pobox.com> wrote:
> > Mathias Kretschmer wrote:
> > > Mathias Kretschmer wrote:
> > >> Mathias Kretschmer wrote:
> > >>> Jeff Garzik wrote:
> > >>>> Mathias Kretschmer wrote:
> > >>>>> hi,
> > >>>>>
> > >>>>> I found an older version of this patch (against 2.4.22) on some
> > >>>>> website. After a little bit of editing it applied cleanly to 2.4.27
> > >>>>> (and now 2.4.28). It works fine for me on a ASUS P4P800-Deluxe with
> > >>>>> 4x 300GB disks.
> > >>>>>
> > >>>>> Maybe someone finds this patch helpful. Any reason why the original
> > >>>>> patch did not make it into the kernel ?
> > >>>>
> > >>>> Why not add it to the existing via82cxxx driver, and get better
> > >>>> performance and device tuning?
> > >>
> > >> OK, the attached patch adds support for the VIA 6410 chip to the
> > >> via82cxxx driver (instead of the generic driver).
> > >> I've tested it on the board mentioned above. Works fine for me.
> > >
> >
> > Bart, got this one?
>
> I applied it (after whitespace cleanup) to ide-dev-2.6.
Sorry to bother you, but what's the status of this patch? Since that
time, 2.6.11 and 2.6.12 kernels were released, now 2.6.13 is almost
ready, and the VT6410 support does not seem to appear even in -mm.
Has the patch been lost, or is it broken?
Sergey Vlasov
for 2 days and suspect that it has been lost; sorry if someone
receives a duplicate)
On Fri, Feb 11, 2005 at 07:33:59PM +0100, Bartlomiej Zolnierkiewicz wrote:
> On Mon, 07 Feb 2005 12:27:47 -0500, Jeff Garzik <jga...@pobox.com> wrote:
> > Mathias Kretschmer wrote:
> > > Mathias Kretschmer wrote:
> > >> Mathias Kretschmer wrote:
> > >>> Jeff Garzik wrote:
> > >>>> Mathias Kretschmer wrote:
> > >>>>> hi,
> > >>>>>
> > >>>>> I found an older version of this patch (against 2.4.22) on some
> > >>>>> website. After a little bit of editing it applied cleanly to 2.4.27
> > >>>>> (and now 2.4.28). It works fine for me on a ASUS P4P800-Deluxe with
> > >>>>> 4x 300GB disks.
> > >>>>>
> > >>>>> Maybe someone finds this patch helpful. Any reason why the original
> > >>>>> patch did not make it into the kernel ?
> > >>>>
> > >>>> Why not add it to the existing via82cxxx driver, and get better
> > >>>> performance and device tuning?
> > >>
> > >> OK, the attached patch adds support for the VIA 6410 chip to the
> > >> via82cxxx driver (instead of the generic driver).
> > >> I've tested it on the board mentioned above. Works fine for me.
> > >
> > > as above, but for 2.6.11-rc3
> >
> > Bart, got this one?
>
> I applied it (after whitespace cleanup) to ide-dev-2.6.
Sorry to bother you, but what's the status of this patch? Since that