From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Andre Hedrick <andre@linux-ide.org>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IDE udma_status = 0x76 and 2.5.30...
Date: Mon, 5 Aug 2002 22:31:20 +0200 [thread overview]
Message-ID: <12CB5AF43EE@vcnet.vc.cvut.cz> (raw)
On 5 Aug 02 at 13:08, Andre Hedrick wrote:
> Bit 7: Simplex RO
> Bit 6: Device 1 DMA Capable RW
> Bit 5: Device 0 DMA Capable RW
> Bit 4: Reserved "MUST RETURN ZERO ON READS" !!! Vendor Write
> Bit 3: Reserved "MUST RETURN ZERO ON READS" !!! Vendor Write
> Bit 2: Bus Master Interrupt STATUS R Clear W
> Bit 1: Bus Master Error STATUS R Clear W
> Bit 0: Bus Master Active STATUS
>
> Vendor Write, is not a published or listed techincal term.
> It is me trying to present this clearly enough so that the masses will see
> how poorly the general understanding of the basics in 2.5.
If you'll bother with reading code, you'll find that dma status
is reported after:
(dma_stat & 7) != 4 ? (0x10 | dma_stat) : 0;
Because of same code is used in your 2.4.x ide-dma.c (at least in
2.4.19-rc5), I'm really happy that now I know that you are really
familiar with your code.
Code ORs read value with 0x10 to make sure that it reports non-zero
value when error happens (when chip returs dma_stat == 0x00). And 0x10
was choosen because of this bit should be always zero, as you know.
Maybe we should print value after ANDing with 0xEF, but why? Everybody
can read code when in doubt.
Petr Vandrovec
vandrove@vc.cvut.cz
next reply other threads:[~2002-08-05 20:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 20:31 Petr Vandrovec [this message]
2002-08-05 21:10 ` [PATCH] IDE udma_status = 0x76 and 2.5.30 Andre Hedrick
2002-08-05 21:19 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2002-08-05 14:07 Petr Vandrovec
2002-08-05 14:21 ` Marcin Dalecki
2002-08-05 10:18 Petr Vandrovec
2002-08-05 10:28 ` Marcin Dalecki
2002-08-04 22:25 Petr Vandrovec
2002-08-05 9:33 ` Marcin Dalecki
2002-08-05 20:08 ` Andre Hedrick
2002-08-05 21:42 ` Alan Cox
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=12CB5AF43EE@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=andre@linux-ide.org \
--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