From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] DCR register read/write for PPC440EP
Date: Sat, 30 Sep 2006 04:13:57 +0200 [thread overview]
Message-ID: <200609300413.57847.sr@denx.de> (raw)
In-Reply-To: <406A31B117F2734987636D6CCC93EE3C2D3B66@ehost011-3.exch011.intermedia.net>
Hi Leonid,
On Thursday 28 September 2006 23:54, Leonid wrote:
> I think it would be better to provide both address and data DCR register
> numbers (DCRNs) in the first parameter, separated by "." or ":", like
> this:
>
> getidcr e.f 40
>
> or simple (omitted data DCRN will be 0xE+1=0xF as you have suggested):
>
> getidcr e 40
>
> This is more "u-bootish" style I deem (it's used in cp command for
> example). This way offset will always be the second parameter which is
> more convenient.
>
> Help line will look like this:
>
> => help getidcr
> getidcr addr_dcrn[.data_dcrn] offset
> - return a value of register, addressed indirectly via DCR. data_dcrn
> is assumed to be addr_dcrn+1 if not specified.
OK.
> > Yes, you should definitely disable the interrupts in this function.
>
> What is simplest way of doing that for PPC440? I mean, should I insert
> asm into C code, or u-boot already has something better to use?
You could use the enable_interrupts() and disable_interrupts() calls.
Best regards,
Stefan
prev parent reply other threads:[~2006-09-30 2:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 16:06 [U-Boot-Users] DCR register read/write for PPC440EP Leonid
2006-09-28 12:54 ` Stefan Roese
2006-09-28 16:58 ` Leonid
2006-09-28 18:44 ` Stefan Roese
2006-09-28 21:54 ` Leonid
2006-09-30 2:13 ` Stefan Roese [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=200609300413.57847.sr@denx.de \
--to=sr@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox