From: Mike Fedyk <mfedyk@matchmail.com>
To: Neil Conway <nconway_kernel@yahoo.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PATCH, IDE corruption, 2.4.18
Date: Sun, 5 May 2002 00:36:56 -0700 [thread overview]
Message-ID: <20020505073656.GD2392@matchmail.com> (raw)
In-Reply-To: <20020505002212.GA2392@matchmail.com> <20020505015417.76681.qmail@web21510.mail.yahoo.com>
On Sun, May 05, 2002 at 02:54:17AM +0100, Neil Conway wrote:
> Hi...
>
> --- Mike Fedyk <mfedyk@matchmail.com> wrote: > On Sat, May 04, 2002 at
> 01:15:20PM +0100, Neil Conway wrote:
> > > - byte stat;
> > > + byte stat,unit;
> >
> > [snip]
> >
> > > #if defined(CONFIG_BLK_DEV_IDEDMA) && !defined(CONFIG_DMA_NONPCI)
> > > - byte unit = (drive->select.b.unit & 0x01);
> > > + unit = (drive->select.b.unit & 0x01);
> >
> > Why are you moving the init of "unit" out of that ifdef?
>
> Basically to make it compile. I'm only moving the declaration, and
> that's only because I need to abort the routine BEFORE the second line
> of the ifdef switches off DMA on that unit. I did compile a version
> with the ifdef split into two bits but I decided that was a little
> messy. (It won't compile if my check goes in before the first line of
> the ifdef as originally written as it declares a variable and C won't
> let declarations follow plain code.)
>
Right. Duh on my part, sorry.
> > Can you see if this problem is still in 2.5 also?
>
> I haven't got a 2.5.13 tree but I found 2.5.7 on a source browser
> online and verified that, back then at least, ide-features.c was still
> basically the same. Of course, the routines in between
> ide_register_subdriver and ide_config_drive_speed might have been
> different. If someone can look at the code-path between these two
> routines in 2.5.13 to see if there is any check on whether or not the
> hwgroup is busy (or simply whether or not DMA is in progress) that
> would clear it up. I'll probably download 2.5.13 sometime soon anyway.
>
Andre cleaims that the situation is worse on 2.5.13 or so. I wouldn't hurt
to test-run the code though.
next prev parent reply other threads:[~2002-05-05 7:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-04 12:15 PATCH, IDE corruption, 2.4.18 Neil Conway
2002-05-04 22:58 ` Andre Hedrick
2002-05-05 2:10 ` Neil Conway
2002-05-05 0:22 ` Mike Fedyk
2002-05-05 0:47 ` Andre Hedrick
2002-05-05 1:54 ` Neil Conway
2002-05-05 7:36 ` Mike Fedyk [this message]
2002-05-05 9:44 ` Neil Conway
-- strict thread matches above, loose matches on Subject: below --
2002-05-05 15:49 Bartlomiej Zolnierkiewicz
2002-05-05 15:04 ` Martin Dalecki
2002-05-05 20:44 ` Neil Conway
2002-05-06 0:23 ` Mike Fedyk
2002-05-03 20:39 Neil Conway
2002-05-03 20:36 Neil Conway
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=20020505073656.GD2392@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nconway_kernel@yahoo.co.uk \
/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