public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miquel van Smoorenburg <miquels@cistron.nl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Willy Tarreau <wtarreau@free.fr>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.2.18pre25
Date: Fri, 8 Dec 2000 17:07:55 +0100	[thread overview]
Message-ID: <20001208170755.A28838@cistron.nl> (raw)
In-Reply-To: <976268866.3a30ae4296b71@imp.free.fr> <E144OCf-0003ws-00@the-village.bc.nu>
In-Reply-To: <E144OCf-0003ws-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, Dec 08, 2000 at 02:08:46PM +0000

According to Alan Cox:
> > my server currently works with that patch, but I'm sure it won't boot anymore
> > if I apply this 2.2.18pre25 alone. 
> 
> Some days I don't know why I bother

Bad day, Alan? ;)

> > just in case, here it is again.
> It doesnt even apply

Hmm, it did apply for me. Do newer versions of patch have the -l option
on by default?

Anyway. I just threw together a testmachine with a megaraid card.
With 2.2.18pre18, it doesn't boot. With 2.2.18pre18 + Willy's patch,
it does boot.

And with 2.2.18pre25 without any extra patches, it magically works.

So I took the plunge and compiled 2.2.18pre25 on the production
machine with the megaraid. And well, it's coming up as I write this.

I see that another patch _has_ been applied between pre18 and pre25
that tooks out some forward/backwards-compat logic with LINUX_VERSION_CODE
magic (beneath /* Read the base port and IRQ from PCI */). And
reading the patch, it makes sense. It probably does about the same
as Willy's patch, but the "right" way by using pci_resource_start()
which the one in pre18 only did for kernels > 2.3.0

So, it looks like pre25 has a working megaraid driver. Thanks Alan.

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

  reply	other threads:[~2000-12-08 16:38 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-07 20:03 Linux 2.2.18pre25 Alan Cox
2000-12-07 23:23 ` Miquel van Smoorenburg
2000-12-07 23:41   ` Alan Cox
2000-12-08  9:47     ` Willy Tarreau
2000-12-08 14:08       ` Alan Cox
2000-12-08 16:07         ` Miquel van Smoorenburg [this message]
2000-12-08 17:08           ` Alan Cox
2000-12-08 18:12       ` Philipp Rumpf
2000-12-08  0:20 ` Andrea Arcangeli
2000-12-08  0:27   ` Alan Cox
2000-12-08  0:41     ` Andrea Arcangeli
2000-12-08  0:47       ` Alan Cox
2000-12-08  1:27         ` Linus Torvalds
2000-12-08  0:44     ` Signal 11 Rainer Mager
2000-12-08  1:05       ` Jeff V. Merkey
2000-12-08  1:09       ` Michel LESPINASSE
2000-12-08  2:14         ` Rainer Mager
2000-12-08  1:20       ` Andi Kleen
2000-12-08  1:24         ` Jeff V. Merkey
2000-12-08  1:40           ` Andi Kleen
2000-12-08  1:43             ` Jeff V. Merkey
2000-12-08  1:55               ` Jeff V. Merkey
2000-12-08 19:20               ` Dr. Kelsey Hudson
2000-12-08  2:28           ` davej
2000-12-08  3:13             ` Jeff V. Merkey
2000-12-08  3:25               ` davej
2000-12-08 16:44                 ` Matthew Vanecek
2000-12-08 19:43                 ` Dr. Kelsey Hudson
2000-12-08 13:52             ` Alan Cox
2000-12-15  0:11             ` lamont
2000-12-08  1:58       ` Richard B. Johnson
2000-12-08  2:04         ` Peter Samuelson
2000-12-08 16:36           ` Matthew Vanecek
2000-12-08 16:49             ` Richard B. Johnson
2000-12-08 17:40               ` Peter Samuelson
2000-12-08 19:36           ` Dr. Kelsey Hudson
2000-12-08  9:46       ` David Woodhouse
2000-12-08 14:06         ` Alan Cox
2000-12-09 19:01           ` Matthew Vanecek
2000-12-09 19:20             ` davej
2000-12-09 23:31               ` Matthew Vanecek
2000-12-11  1:31                 ` OOPS when using 4GB memory setting Rainer Mager
2000-12-11  0:58           ` Signal 11 Rainer Mager
2000-12-11  9:05             ` Rainer Mager
2000-12-11 13:33               ` Mike Galbraith
2000-12-11 23:24                 ` Rainer Mager
2000-12-13  0:22                   ` Signal 11 - the continuing saga Rainer Mager
2000-12-13  2:17                     ` Jeff V. Merkey
2000-12-13  1:45                       ` Rainer Mager
2000-12-13  4:29                         ` Mike Galbraith
2000-12-13  9:34                           ` Rainer Mager
2000-12-13 15:40                             ` Mike Galbraith
2000-12-13  3:17                       ` Linus Torvalds
2000-12-13  9:34                         ` Rainer Mager
2000-12-13 17:43                         ` Jeff V. Merkey
2000-12-13 12:10                     ` R: " CMA
2000-12-11 14:14               ` Signal 11 davej
2000-12-08 16:21         ` Horst von Brand
2000-12-08 19:34         ` Mark Vojkovich
2000-12-08 23:16           ` Jeff V. Merkey
2000-12-08 22:24             ` David Woodhouse
2000-12-09  0:56               ` Jeff V. Merkey
2000-12-08 17:02   ` Linux 2.2.18pre25 Martin Kacer
2000-12-08 17:20     ` Alan Cox
2000-12-08 17:36       ` Martin Kacer
2000-12-08 18:08     ` Andrea Arcangeli
2000-12-08 18:30       ` Martin Kacer
2000-12-08 23:55         ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2000-12-08 15:16 willy tarreau
2000-12-08 17:06 ` Alan Cox
2000-12-08 20:03 willy tarreau
2000-12-08 20:12 willy tarreau

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=20001208170755.A28838@cistron.nl \
    --to=miquels@cistron.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wtarreau@free.fr \
    /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