All of lore.kernel.org
 help / color / mirror / Atom feed
From: walimis <walimisdev@gmail.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] hw/pflash_cfi01: change print method to	avoid complaint
Date: Wed, 21 Mar 2012 09:59:43 +0800	[thread overview]
Message-ID: <20120321015943.GC5223@walimis-desktop> (raw)
In-Reply-To: <4F691635.10006@weilnetz.de>

On Wed, Mar 21, 2012 at 12:43:49AM +0100, Stefan Weil wrote:
>Am 20.03.2012 15:48, schrieb Liming Wang:
>>Linux guest os often writes invalid cmd data to reset into read mode,
>>which leads many qemu complaint. Here we place all the debug
>>message into macro PFLASH_DEBUG. We can turn on the all debug info by
>>define PFLASH_DEBUG if we want to debug pflash_cfi01.
>>
>>Signed-off-by: Liming Wang <walimisdev@gmail.com>
>>---
>>hw/pflash_cfi01.c | 2 +-
>>1 files changed, 1 insertions(+), 1 deletions(-)
>>
>>diff --git a/hw/pflash_cfi01.c b/hw/pflash_cfi01.c
>>index 2e6fa71..4e39ea6 100644
>>--- a/hw/pflash_cfi01.c
>>+++ b/hw/pflash_cfi01.c
>>@@ -433,7 +433,7 @@ static void pflash_write(pflash_t *pfl,
>>target_phys_addr_t offset,
>>return;
>>
>>error_flash:
>>- printf("%s: Unimplemented flash cmd sequence "
>>+ DPRINTF("%s: Unimplemented flash cmd sequence "
>>"(offset " TARGET_FMT_plx ", wcycle 0x%x cmd 0x%x value 0x%x)\n",
>>__func__, offset, pfl->wcycle, pfl->cmd, value);
>
>Using the trace mechanism of QEMU might be better here than DPRINTF
>It allows users to enable trace messages without recompilation.
>See docs/tracing.txt for details.

Agree, I'm also using that.

>
>I personally like this special printf statement, because it shows me

If we want to reserve it, also don't expect anonying complaint by Linux,
I suggest to skip special cmds that not used in pflash_cfi01, such as 
0xaa, 0x55. How do you think so?

>since several years that there _are_ flash command sequences which should
>be implemented (just boot MIPS Malta with Linux). Maybe one day I'll fix

Do you remeber what issues the command sequences, by bootloader or Linux?
I fixed one Unimplemented flash cmd sequence in my first patch, it prints:
"pflash_write: Unimplemented flash cmd sequence (offset 00000000, 
wcycle 0x0 cmd 0x0 value 0xf0)"

>them. With DPRINTF, I'll never again get a reminder.

If I can reproduce that, I may help to fix them.

Thanks
Liming Wang

>
>Regards,
>Stefan Weil
>

      reply	other threads:[~2012-03-21  2:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20 14:48 [Qemu-devel] [PATCH 1/2] hw/pflash_cfi01: add "0xf0" to select and deselect read mode Liming Wang
2012-03-20 14:48 ` [Qemu-devel] [PATCH 2/2] hw/pflash_cfi01: change print method to avoid complaint Liming Wang
2012-03-20 23:43   ` Stefan Weil
2012-03-21  1:59     ` walimis [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=20120321015943.GC5223@walimis-desktop \
    --to=walimisdev@gmail.com \
    --cc=aliguori@us.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.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 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.