From: Andrew Morton <akpm@osdl.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org,
Thomas Kleffel <tk@maintech.de>,
Dominik Brodowski <linux@dominikbrodowski.net>
Subject: Re: pcmcia IDE broken in 2.6.18-rc1
Date: Sun, 9 Jul 2006 16:13:30 -0700 [thread overview]
Message-ID: <20060709161330.9fda040d.akpm@osdl.org> (raw)
In-Reply-To: <20060709224700.GA1707@elf.ucw.cz>
On Mon, 10 Jul 2006 00:47:08 +0200
Pavel Machek <pavel@ucw.cz> wrote:
> Hi!
>
> > > > ide2: I/O resource 0xF887E00E-0xF887E00E not free.
> > > > ide2: ports already in use, skipping probe
> > > > ide2: I/O resource 0xF887E01E-0xF887E01E not free.
> > > > ide2: ports already in use, skipping probe
> > >
> > >
> > > Looks like ioremap values not I/O ports. Probably the various IDE layer
> > > changes from 2.6.17-mm.
> > >
> > > My first guess would be the PCMCIA layer changes to use mmio ports are
> > > not setting hwif->mmio (I think its ->mmio) to 2 and doing their own
> > > resource management.
> > >
> >
> > 5040cb8b7e61b7a03e8837920b9eb2c839bb1947 looks like a good one to try
> > reverting.
>
> 2.6.18-rc1-mm1 works okay. Is that enough, or do you want me to try
> reverting just this patch?
Nope, that's fine, thanks. I think we can say that
5040cb8b7e61b7a03e8837920b9eb2c839bb1947 is busted.
Let's give Thomas and Dominik a few days to think about it before we do the
deed..
prev parent reply other threads:[~2006-07-09 23:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-08 14:55 pcmcia IDE broken in 2.6.18-rc1 Pavel Machek
2006-07-08 16:47 ` Andrew Morton
2006-07-13 18:00 ` Jan Engelhardt
2006-07-08 17:36 ` Alan Cox
2006-07-08 17:41 ` Andrew Morton
2006-07-08 21:35 ` Alan Cox
2006-07-08 22:04 ` Andrew Morton
2006-07-09 22:47 ` Pavel Machek
2006-07-09 23:13 ` Andrew Morton [this message]
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=20060709161330.9fda040d.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=pavel@ucw.cz \
--cc=tk@maintech.de \
/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