From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stanislav G. Prihodko Date: Wed, 26 Sep 2007 05:49:02 -0700 (PDT) Subject: [U-Boot-Users] U-BOOT and UART TX with interrupts (need help please) In-Reply-To: <46FA4F9D.30803@smiths-aerospace.com> References: <12896654.post@talk.nabble.com> <20070926090439.51AE22405D@gemini.denx.de> <12897695.post@talk.nabble.com> <46FA4F9D.30803@smiths-aerospace.com> Message-ID: <12900271.post@talk.nabble.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Yes, yes, I know what you are going to say. With the use of off fully, not built originally in the program U-BOOT. But the interruption did not have any relationship to the operating system. The same level of hardware implementation exchange data with pereferiey. And as logical, therefore have to complete events or otherwise. If you send a lot of data or data to do so is through the interruption, is not it? I understand that this remarkable U-BOOT actually loader. And it is remarkable opportunities. For example implement the programme as "Standalone", and so can get through this opportunity to interrupt? I just want to build their program on the basis of good, enabled solutions. Jerry Van Baren wrote: > > U-Boot is a boot loader, used to > * Initialize the hardware > * Load an operating system > * Start the operating system running > > You are looking for an operating system with interrupts and possibly > multi-tasking. U-Boot may be helpful in *loading and starting* your > operating system, but it is *not* an operating system. It does not > normally use, and thus has no support for, interrupts. > > -- View this message in context: http://www.nabble.com/U-BOOT-and-UART-TX-with-interrupts-%28need-help-please%29-tf4520884.html#a12900271 Sent from the Uboot - Users mailing list archive at Nabble.com.