From: David Vrabel <dvrabel@arcom.co.uk>
To: mtd@infradead.org
Subject: Re: Can't read bytes from x16 device
Date: Fri, 15 Sep 2000 15:37:32 +0100 [thread overview]
Message-ID: <39C2342C.F24C13F3@arcom.co.uk> (raw)
In-Reply-To: 39C1F36B.8E97D5F4@arcom.co.uk
David Vrabel wrote:
> I have an Intel 28F640J5 part in x16 mode. It appears I can't read
> bytes which are odd aligned. After reading one odd aligned byte all
> reads fail.
Reading the specs for this chip indicates that the high byte is not used
for command or status information. So I changed
do_read_1_by_16_onechip() to align commands and status reads on word
boundaries.
David Vrabel.
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
prev parent reply other threads:[~2000-09-15 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-15 10:01 Can't read bytes from x16 device David Vrabel
2000-09-15 14:37 ` David Vrabel [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=39C2342C.F24C13F3@arcom.co.uk \
--to=dvrabel@arcom.co.uk \
--cc=mtd@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.