From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Warren Date: Tue, 08 Jan 2008 10:35:13 -0500 Subject: [U-Boot-Users] Do we enable Interrupts in U-Boot? In-Reply-To: <7f245da80801080727o460b630esf14697414f76ce33@mail.gmail.com> References: <7f245da80801080411g4f8e4f82xdb0f6271a8b20f5a@mail.gmail.com> <200801081334.49170.sr@denx.de> <7f245da80801080452p3c939977i649b5ecede367348@mail.gmail.com> <200801081427.56350.sr@denx.de> <7f245da80801080727o460b630esf14697414f76ce33@mail.gmail.com> Message-ID: <47839831.1030107@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Chetan Nanda wrote: > On 1/8/08, Stefan Roese wrote: > >> On Tuesday 08 January 2008, Chetan Nanda wrote: >> >>> In that case there must be some threads that continuously check for >>> pending requests from UART, ETHERNET or so .. >>> >> Threads? U-Boot is not an full blown OS. No threads are needed in this >> bootloader. >> >> >>> But I don't find any sort of threading inside u-boot code >>> >> U-Boot "sits" there and waits for some input from the console, or for an >> ethernet reply packet. This can be done using polling without any performance >> penalty. >> >> > Thanks, for explaining the things, > But how can we wait for two events simultaneously (that is also under > a single thread of execution)? Can you give me pointer to the code ? > We don't. Everything's single-threaded and poll-based. regards, Ben