From: Stanislav G. Prihodko <veter2000@rambler.ru>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] U-BOOT and UART TX with interrupts (need help please)
Date: Wed, 26 Sep 2007 05:38:18 -0700 (PDT) [thread overview]
Message-ID: <12900023.post@talk.nabble.com> (raw)
In-Reply-To: <12897695.post@talk.nabble.com>
Here's see, I have reasons why this should be:
... via DMA and interrupt, we must be a mechanism to exchange DMA
(namely model:
MEMORY <> MEMORY,
MEMORY->UART-TX,
SPI <-> MEMORY)
And if to do so without interruption of use, the program simply will not
work because you need and will be very slow!
Therefore, a mechanism is needed to process the interruption.
Now we build our program directly into the source code of programs U-BOOT.
And we want to use interrupts.
Could really do better to write our attachment (application) and use it as a
"Standalone Applications?
and already in the program to break as we need?
.... please tell how to use the break to our processor (BlackFin 532)?
... how do we best get out of this situation?
Help Please!
--
View this message in context: http://www.nabble.com/U-BOOT-and-UART-TX-with-interrupts-%28need-help-please%29-tf4520884.html#a12900023
Sent from the Uboot - Users mailing list archive at Nabble.com.
next prev parent reply other threads:[~2007-09-26 12:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 8:50 [U-Boot-Users] U-BOOT and UART TX with interrupts (need help please) veter
2007-09-26 9:04 ` Wolfgang Denk
2007-09-26 10:02 ` veter
2007-09-26 12:25 ` Jerry Van Baren
2007-09-26 12:49 ` Stanislav G. Prihodko
2007-09-26 13:03 ` Jerry Van Baren
2007-09-26 13:43 ` Stanislav G. Prihodko
2007-09-26 13:59 ` Wolfgang Denk
2007-09-26 14:13 ` Stanislav G. Prihodko
2007-09-26 12:38 ` Stanislav G. Prihodko [this message]
2007-09-26 19:12 ` Mike Frysinger
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=12900023.post@talk.nabble.com \
--to=veter2000@rambler.ru \
--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