qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: Artyom Tarasenko <atar4qemu@googlemail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: sparc esp dma endianness [patch-rfc]
Date: Tue, 1 Sep 2009 20:11:50 +0300	[thread overview]
Message-ID: <f43fc5580909011011l7c563e2eh3a4876189c77abf1@mail.gmail.com> (raw)
In-Reply-To: <fb8d4f70909011008m3941241dw8e758c25429d2bc7@mail.gmail.com>

On Tue, Sep 1, 2009 at 8:08 PM, Artyom
Tarasenko<atar4qemu@googlemail.com> wrote:
> 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?
>

It could be pushed into FIFO with PIO.

      reply	other threads:[~2009-09-01 17:12 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
2009-09-01 17:11     ` Blue Swirl [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=f43fc5580909011011l7c563e2eh3a4876189c77abf1@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=atar4qemu@googlemail.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).