All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH 3/3] QE IO - Add pario command
Date: Mon, 31 Mar 2008 22:18:02 +0200	[thread overview]
Message-ID: <20080331201802.8605C248BF@gemini.denx.de> (raw)
In-Reply-To: Your message of "Mon, 31 Mar 2008 18:37:48 +0300." <B27D27F93BC429468DBC3B0DA043AA4401FF2660@ILPTEX02.ecitele.com>

In message <B27D27F93BC429468DBC3B0DA043AA4401FF2660@ILPTEX02.ecitele.com> you wrote:
> 
> > I don't think is a good idea. The code as presented is  actually  not
> > suited  for such an extension. And I definitly don't want to plan for
> > another #ifdef maze.
> 
> > Are you aware of the "reginfo" command? Few people seem to know it.
> 
> > Maybe you should add such code there.
> 
> As far as I managed to understand, reginfo just shows a dump of CPU
> based register values, while pario allows you to set and get the value
> of a GPIO port - two different things. We found this very useful for
> debugging our board, and I think it can be useful for many other
> processor families as well. 

I'm aware of this. Changing register contents seems a useful extension
to me, too. That's why I wrote "add such code". I think something like

Print all (or a predefined set of) registers:
	=> reg

Print a specific register:
	=> reg name

Set a specific register to "value":
	=> reg name value

would be generally useful, not only for parallel I/O registers.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"If it ain't broke, don't fix it."                       - Bert Lantz

  parent reply	other threads:[~2008-03-31 20:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-31 12:28 [U-Boot-Users] [PATCH 3/3] QE IO - Add pario command David Saada
2008-03-31 15:00 ` Wolfgang Denk
2008-03-31 15:19   ` David Saada
2008-03-31 15:27     ` Wolfgang Denk
2008-03-31 15:37       ` David Saada
2008-03-31 16:28         ` Timur Tabi
2008-03-31 20:20           ` Wolfgang Denk
2008-03-31 20:18         ` Wolfgang Denk [this message]
2008-04-01  5:54           ` David Saada
2008-04-01  9:58             ` Wolfgang Denk

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=20080331201802.8605C248BF@gemini.denx.de \
    --to=wd@denx.de \
    --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 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.