From: Artyom Tarasenko <atar4qemu@googlemail.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: sparc esp dma endianness [patch-rfc]
Date: Tue, 1 Sep 2009 19:08:00 +0200 [thread overview]
Message-ID: <fb8d4f70909011008m3941241dw8e758c25429d2bc7@mail.gmail.com> (raw)
In-Reply-To: <f43fc5580909010854m7e259849g93e09d7f27f65da1@mail.gmail.com>
2009/9/1 Blue Swirl <blauwirbel@gmail.com>:
> Usually the first byte is bus id. What if you changed (as a hack) here:
> DPRINTF("do_cmd: busid 0x%x\n", buf[0]);
> lun = buf[0] & 7;
> datalen = s->current_dev->send_command(s->current_dev, 0, &buf[1], lun);
> &buf[1] to &buf[0]?
Yep, figured that out too, but did a little more complex hack:
lun = buf[1] >>5;
datalen = s->current_dev->send_command(s->current_dev, 0, &buf[0], lun);
with this hack OBP checks proper LUNs.
So, the problem is not endianness, but the missing bus id. But how the
bus id should get into the dma buffer?
It should be generated by esp, right?
next prev parent reply other threads:[~2009-09-01 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 20:48 [Qemu-devel] sparc esp dma endianness [patch-rfc] Artyom Tarasenko
2009-09-01 15:54 ` [Qemu-devel] " Blue Swirl
2009-09-01 17:08 ` Artyom Tarasenko [this message]
2009-09-01 17:11 ` Blue Swirl
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=fb8d4f70909011008m3941241dw8e758c25429d2bc7@mail.gmail.com \
--to=atar4qemu@googlemail.com \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).