Re: [PATCH 2.6.14-rc3] sis5513.c: enable ATA133 for the SiS965 southbridge

[wsong]

This patch has conflict with sata_sis driver. They both register this
id 0x0180. But pci ide driver is loaded first. So if you have sata
drive connected as root, dang, you'll get kernel panic. I had this
problem with 2.6.14_rc4-mm1. Simply delete the third line from
structure sis5513_pci_tbl resolved it.

I know it's just a work around.

Can somebody tell me how to track file history under mm- tree?

On 10/7/05, Wes Newell <w.newell@xxxxxxxxxxx> wrote:
> Aurelien Jarno wrote:
>
> >On Thu, Oct 06, 2005 at 11:40:15AM +0200, Bartlomiej Zolnierkiewicz wrote:
> >
> >
> >>Hi,
> >>
> >>On 10/5/05, Aurelien Jarno <aurelien@xxxxxxxxxxx> wrote:
> >>
> >>
> >>>Hi,
> >>>
> >>>Here is a patch that enables the ATA133 mode for the SiS965 southbridge
> >>>in the SiS5513 driver.
> >>>
> >>>
> >>The patch for SIS965(L) support is already in -mm tree:
> >>http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc2/2.6.14-rc2-mm2/broken-out/sis5513-support-sis-965l.patch
> >>
> >>
> >>
> >
> >Oops, I forget to look at the -mm tree for this driver. You're right, it
> >works, and it seems the patch is cleaner than mine. So please ignore my
> >patch.
> >
> >Thanks,
> >Aurelien
> >
> >
> >
> It appears to me that this patch will try and apply itself to the real
> SIS_180 which has the same true_id of 0x180. Can someone tell me what
> will happen then?
>
>
> --
> KT133 MB, CPU @2400MHz (24x100): SIS755 MB CPU @2330MHz (10x233)
> Need good help? Provide all system info with question.
> My server http://wesnewell.no-ip.com/cpu.php
> Verizon server http://mysite.verizon.net/res0exft/cpu.htm
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/