Re: [PATCH] Merge the changes from siimage 2.4.22-pre9 to 2.6.0-test2

From: Marcelo Penna Guerra (eu_at_marcelopenna.org)
Date: 07/31/03

  • Next message: Ihar \: "Re: Kernel 2.6 size increase" 
    To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Date:	Thu, 31 Jul 2003 16:32:56 -0300

    On Thursday 31 July 2003 12:25, Bartlomiej Zolnierkiewicz wrote:
    > What do you mean by "a lot more stable than before"?

    I mean it doesn't crash the system during intensive read/write operations. It
    has something to do with limiting the max bk per request to 7.5 (hwif-
    >rqsize=15).

    > Can you separate your changes from forward-port?

    They are really small changes. It's the one I mentioned on the first e-mail
    and this one, that was suggested by Andre Hedrick on another post:

            if(is_sata(hwif))
            {
    + drive->id->hw_config |= 0x6000;
                    if(strstr(drive->id->model, "Maxtor"))
                            return 3;
                    return 4;
             }

    > Are you aware of side effect?
    > [ Disabling DMA on ATAPI devices on SiI680. ]
    >
    > Please consult this change with Alan :-).

    No, I'm not. Sorry. I'm look for more information. But dma is working with my
    SiI3112A, everything is stable, so maybe it should be enabled by default for
    this chipset.

    Also, there's a change missing in this patch. The PCI id for SiI1210SA is
    missing in 2.6.x.

    #define PCI_DEVICE_ID_SII_680      0x0680
    +#define PCI_DEVICE_ID_SII_1210SA   0x0240
    #define PCI_DEVICE_ID_SII_3112      0x3112

    Anyway, thank you for taking a look at this.

    Marcelo Penna Guerra
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Ihar \: "Re: Kernel 2.6 size increase"

    Relevant Pages

    • Re: CPU Usage for particular User Login
      ... is their a way to get fair 'equal time / proc percentage per user' ... queueing of the CPU. ... i.e. not limiting the number of processes/user but limiting the total CPU ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • [BK] http://www.openlogging.org
      ... We seem to have worked the bugs out so you can now get correct results on ... We're limiting the summaries to projects that have changed ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: CPU Usage for particular User Login
      ... > i.e. not limiting the number of processes/user but limiting the total CPU ... Digging into the lkml archives on vserver can give you some pointers. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.4.20 and 2.4.21, Firewire, 160 GB Harddisk, 134 GB barrier
      ... > The more likely scenario is that the bridge chip in said box doesn't support ... > the larger drive and is the limiting factor. ... To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)
    • Re: [PATCH] Merge the changes from siimage 2.4.22-pre9 to 2.6.0-test2
      ... On Iau, 2003-07-31 at 20:32, Marcelo Penna Guerra wrote: ... > I mean it doesn't crash the system during intensive read/write operations. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)