linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gertjan van Wingerde <gwingerde@home.nl>
To: B.Zolnierkiewicz@elka.pw.edu.pl
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: 2.6.0-test11-bart1
Date: Mon, 8 Dec 2003 20:31:38 +0100	[thread overview]
Message-ID: <200312082029.58214.gwingerde@home.nl> (raw)

Hi Bart,

I'd like to have my IDE modularisation patch included in this. See the following link for the details.

	http://marc.theaimsgroup.com/?l=linux-kernel&m=107004921520850&w=2

In the current state of the IDE driver none of the modules can be loaded.

Please let me know if you think that this can be handled in a different way.

    Best regards,

        Gertjan.

On 8 december 2003 Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl> wrote:
>
>Lets start the ball rolling...
>
>If you have problems ide-tape.c, siimage.c or cmd640.c (in PCI mode)
>you should try this patch.
>
>It also contains untested fixes for Promise IDE driver (pdc202xx_old.c),
>they should be safe but better backup your data first :-), feedback needed.
>
>Workarounds for nForce2 chipset are also included.
>
>Get it from:
>ftp://ftp.kernel.org/pub/linux/kernel/people/bart/2.6.0-test11-bart1/
>
>If you have some patches you think are worth merging just mail me
>(cleanups are also welcomed).
>
>--bart
>
>Merged:
>
>linux-2.6.0-test11-bk5.patch
>  -bk snapshot (patch-2.6.0-test11-bk5)
>
>extraversion.patch
>  add -bartX to EXTRAVERSION
>
>ide-tape-update.patch
>  [IDE] ide-tape.c update
>
>ide-tape-rq-special.patch
>  [IDE] ide-tape.c: stop abusing rq->flags
>
>ide-siimage-seagate.patch
>  [IDE] siimage.c: limit requests to 15kB only for Seagate SATA drives
>
>ide-siimage-stack-fix.patch
>  [IDE] siimage.c: fix PIO settings programming
>
>ide-siimage-sil3114.patch
>  [IDE] siimage.c: add very basic support for Silicon Image 3114 SATA
>
>ide-cmd640-pci1.patch
>  [IDE] cmd640.c: fix PCI type1 access
>
>ide-pdc_old-pio-fix.patch
>  [IDE] pdc202xx_old.c: fix PIO autotuning
>
>ide-pdc_old-udma66-fix.patch
>  [IDE] pdc202xx_old.c: fix enabling 66MHz clock for modes > UDMA2
>
>ide-pdc_old-66mhz_clock-fix.patch
>  [IDE] pdc202xx_old.c: sanitize 66MHz clock use
>
>nforce2-disconnect-quirk.patch
>  [x86] fix lockups with APIC support on nForce2
>
>nforce2-apic.patch
>  [x86] do not wrongly override mp_ExtINT IRQ
>
>ide-recovery-time.patch
>  [IDE] remove dead and broken DISK_RECOVERY_TIME support
>
>ide-pdc_new-proc.patch
>  [IDE] pdc202xx_new.c: remove useless /proc/ide/pdcnew
>
>-
>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/


             reply	other threads:[~2003-12-08 19:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-08 19:31 Gertjan van Wingerde [this message]
2003-12-08 19:52 ` 2.6.0-test11-bart1 Bartlomiej Zolnierkiewicz
  -- strict thread matches above, loose matches on Subject: below --
2003-12-08  0:38 2.6.0-test11-bart1 Bartlomiej Zolnierkiewicz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200312082029.58214.gwingerde@home.nl \
    --to=gwingerde@home.nl \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).