qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: SH: support 7785 serial
Date: Mon, 06 Apr 2009 19:23:57 +0400	[thread overview]
Message-ID: <grd6qd$edf$1@ger.gmane.org> (raw)
In-Reply-To: 49DA0064.2070909@juno.dti.ne.jp

Shin-ichiro KAWASAKI wrote:

> Hi, Vladimir.
> Thank you for your work.
> 
> Vladimir Prus wrote:
>> These 3 patches make sh_serial.c support 7785 serial. The primary
>> difference is that on 7785, instead of single fifo count register
>> there are two separate ones -- for rx and tx. Patch 3 adds necessary
>> conditional logic. Patches 1 and 2 are cleanups that I've done alone
>> the way:
>> 
>> - Patch 1 makes it possible to change the size of RX fifo. It's 16
>> on 7751 and 64 on 7785. While I do not know of any breakage if we
>> use wrong size, it's still best to be correct.
>> - Patch 2 replaces a pile of hardcoded constants with macroses.
>> Also, the FSR register was handled strangely -- when written, we'd
>> look at the written value and set bits in the 'flags' field, and on
>> read, we'd reconstruct the value from the 'flags' field. There does
>> not seem to be any reason for such roundabout, so I've made the code
>> work with 'sr' directly.
>> 
>> This patch was tested both with r2d, using kernel and userland found
>> at:
>> 
>> thttp://www.assembla.com/wiki/show/qemu-sh4/BuildingEnvironment
>> 
>> and with 7785, using a hand-made kernel.
> 
> Patch 2 produces a trouble in my environment.
> For r2d, the output to SCIF from kernel is OK, but output from
> shell is broken by inserted white space, like follows.
> 
> (before applying patch 2)
>  # ls
> 
> (after applying patch2)
>  #    l  s
> 
> Do you have time to investigate it?

Shin-ichiro,

I could not reproduce this locally. Did you tried typing this in virtual console
that QEMU pops up, or in the console where QEMU was started. For me, the former
does not accept any input at all.

Would it be possible for you to provide me with
- Source tree of qemu that you've tested this with? Pointer to some git commit
in some branch in some git repository will be OK.
- The kernel zImage you have used it
- The disk image you have used
- The command line for qemu

For the latter three, I have used what you have put at:

        http://www.assembla.com/wiki/show/qemu-sh4/BuildingEnvironment

but I want to be sure there's no accidental differences. And for qemu source tree,
I want to make sure I did not unintentially based by patch on some wrong state.

Thanks,
Volodya

  reply	other threads:[~2009-04-06 15:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-02 17:29 [Qemu-devel] SH: support 7785 serial Vladimir Prus
2009-04-06 13:15 ` Shin-ichiro KAWASAKI
2009-04-06 15:23   ` Vladimir Prus [this message]
2009-04-06 16:49     ` [Qemu-devel] " Shin-ichiro KAWASAKI
2009-04-06 18:04       ` [Qemu-devel] " Vladimir Prus
2009-04-15 13:18   ` [Qemu-devel] " Vladimir Prus
2009-04-18 11:47     ` Shin-ichiro KAWASAKI
2009-04-18 16:37       ` Aurelien Jarno
2009-05-11 15:44         ` Vladimir Prus

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='grd6qd$edf$1@ger.gmane.org' \
    --to=vladimir@codesourcery.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).