On Sat, 27 Feb 1999 19:20:34 +1100, Bruce Evans wrote:
I sent this in for review a year or so ago, but received no reply.
The main points are that it honours ATA timing in atapi_wait() and
checks for ARS_BUSY in atapi_wait().
I guess we'll need to wait and see whether this is still an issue
Nope, that code snippet is in atapi.c its not in any of the drivers...
(and newer has been).
You're right. Goes to show how long I haven't touched this part of
the code. Alas, just reviewed it out of curiosity. It sure got more
readable... :-) But I still hate those inb loops without DELAY...
Bruce Evans wrote:
There's only one, at least in my version.
There is the PC98 one you removed, and then this one in
atapi_request_immediate():
/* Wait for data i/o phase. */
for (cnt=2; cnt0; --cnt)
if (((inb (ata-port +
On Fri, 26 Feb 1999 16:27:52 +0900, Daniel C. Sobral wrote:
It was somehow distressing, though, that the new code had the exact
same bug as the old, even though it was quite different code.
When you say the new code, are you referring to the newer acd driver
as opposed to the older wcd
Sheldon Hearn wrote:
It was somehow distressing, though, that the new code had the exact
same bug as the old, even though it was quite different code.
When you say the new code, are you referring to the newer acd driver
as opposed to the older wcd driver? If so, do you think it'll be
It seems Daniel C. Sobral wrote:
On the code:
ireason = inb (ata-port + AR_IREASON);
ac-result.status = inb (ata-port + AR_STATUS);
phase = (ireason (ARI_CMD | ARI_IN)) |
- (ac-result.status ARS_DRQ);
Søren Schmidt wrote:
The problem is the ARS_BSY signal. If my memory doesn't fail me, if
ARS_BSY is active, then the other signals may contain trash. In this
particular loop, ARS_BSY could be active, but it wasn't being
checked for, on the assumption that ARS_DRQ would only be up (down?)
It seems Daniel C. Sobral wrote:
Søren Schmidt wrote:
The problem is the ARS_BSY signal. If my memory doesn't fail me, if
ARS_BSY is active, then the other signals may contain trash. In this
particular loop, ARS_BSY could be active, but it wasn't being
checked for, on the
Søren Schmidt wrote:
Nope, that code snippet is in atapi.c its not in any of the drivers...
(and newer has been).
You're right. Goes to show how long I haven't touched this part of
the code. Alas, just reviewed it out of curiosity. It sure got more
readable... :-) But I still hate those inb
On Thu, Feb 25, 1999 at 02:09:31PM +1030, Greg Lehey wrote:
Wow. Thanks a million! I didn't even have to go so far, I just
deleted wd2 and wd3 and acd0 now appears as if by magic. I can't
tell you how extremely stupid I now feel...
You shouldn't do. What you did shouldn't have any effect
On Thu, Feb 25, 1999 at 04:20:20PM +1100, Bruce Evans wrote:
doesn't see the slave, and control passes to the atapi probe which does
support cdrom drives. It works worst with a cdrom master and no slave.
Sadly, that's exactly the out-of-the-box Dell configuration: 2
disks on the first IDE,
On Thu, 25 Feb 1999 17:16:53 +0100, Pierre Beyssac wrote:
I tried to find out why it worked with a Linux kernel by comparing
our IDE code and theirs, but it was way beyond my comprehension.
I'm not trained for the black magic of IDE probing.
I used this particular issue for the launch of my
On Thu, 25 Feb 1999 17:26:14 +0100, Pierre Beyssac wrote:
I'd have changed the hardware configuration to swap the second disk
with the CDROM, but I thought it would be much better if it could
be made to work, since it apparently can...
Nope, it's almost certainly better to have your random
-Original Message-
From: Sheldon Hearn [SMTP:sheld...@iafrica.com]
Sent: Thursday, February 25, 1999 5:40 PM
To: Pierre Beyssac
Cc: Greg Lehey; freebsd-current@FreeBSD.ORG
Subject: Re: IDE CDROM not found with PIIX4 chipset, -current
kernel
On Thu, 25 Feb 1999 17
On Thu, 25 Feb 1999 18:07:39 +0100, Ladavac Marino wrote:
How about this brilliant idea: put a logic analyzer on the IDE
cable and measure the timings the prevailing OS family/BIOS uses?
My understanding from previous conversations is that the situation
you're often faced with is that
On Thu, Feb 25, 1999 at 06:40:35PM +0200, Sheldon Hearn wrote:
I'd have changed the hardware configuration to swap the second disk
with the CDROM, but I thought it would be much better if it could
be made to work, since it apparently can...
Nope, it's almost certainly better to have your
Sheldon Hearn wrote:
2) I found that stepping through the kernel caused exactly the same
problems I was having with accessing my one ATAPI drive that I
experience just running normally with my other drive. So it looks
like at least one problem regarding ATAPI has to do with timings.
I've been having problems with an IDE controller on my motherboard.
I can't seem to be able to get it to recognize a CDROM drive (it's
the only device plugged on the second IDE controller). The kernel
seems to timeout on that second controller during the probe phase.
Maybe that's one of the
On Wed, 24 Feb 1999 23:51:17 +0100, Pierre Beyssac wrote:
Here's an excerpt from my kernel config. Did I miss something obvious?
controller wdc0[...]
diskwd0 at wdc0 drive 0
diskwd1 at wdc0 drive 1
controller wdc1[...]
disk
On Thu, Feb 25, 1999 at 01:01:09AM +0200, Sheldon Hearn wrote:
controller wdc1[...]
diskwd2 at wdc1 drive 0
diskwd3 at wdc1 drive 1
Um... Do you really have 4 wd devices plugged in?
Uh, well, no, just 2 (on the first IDE controller).
Assuming
On Thursday, 25 February 1999 at 1:04:48 +0100, Pierre Beyssac wrote:
On Thu, Feb 25, 1999 at 01:01:09AM +0200, Sheldon Hearn wrote:
controller wdc1[...]
diskwd2 at wdc1 drive 0
diskwd3 at wdc1 drive 1
Um... Do you really have 4 wd devices plugged
I've been having problems with an IDE controller on my motherboard.
I can't seem to be able to get it to recognize a CDROM drive (it's
the only device plugged on the second IDE controller). The kernel
seems to timeout on that second controller during the probe phase.
Maybe that's one of the
22 matches
Mail list logo
