From: Steven Seeger <steven.seeger@flightsystems.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] pci modify [.l .w .b]
Date: Sun, 18 Mar 2018 02:38:31 -0400 [thread overview]
Message-ID: <2111747.tqiAZ2LkMF@wirbelwind> (raw)
Hi list.
If a pci modify command is issued, do_pci() takes the size specifier (.l, .w,
.b) and turns it into one of PCI_SIZE_8, PCI_SIZE_16, or PCI_SIZE_32, which
correspond to 0, 1, and 2.
Consequently, the address increment moves at 0, 1, or 2 bytes.
This would be a trivial patch for me to make, but before I do that I wanted to
make sure that this was not the desired behavior, or that I am not missing
something.
Thanks,
Steven
reply other threads:[~2018-03-18 6:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2111747.tqiAZ2LkMF@wirbelwind \
--to=steven.seeger@flightsystems.net \
--cc=u-boot@lists.denx.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