From mboxrd@z Thu Jan  1 00:00:00 1970
From: Joey Oravec <joravec@drewtech.com>
Date: Wed, 11 Jul 2007 13:21:36 -0400
Subject: [U-Boot-Users] Interrupts in at91rm9200 u-boot.
References: <9a7969e20707110120l150cc3b2y382c561fd69f92b5@mail.gmail.com>
	<406A31B117F2734987636D6CCC93EE3C01CAD749@ehost011-3.exch011.intermedia.net>
Message-ID: <f733jb$b0v$1@sea.gmane.org>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

"Leonid" <Leonid@a-k-a.net> wrote in message 
news:406A31B117F2734987636D6CCC93EE3C01CAD749 at ehost011-3.exch011.intermedia.net...
> I'm trying to implement simple USB device in u-boot for at91rm9200 and
> as a first step I want to see that I can work with interrupts there. I
> added temporary device initialization code to usb_lowlevel_init():

I used the USB Device port as a console for my at91sam9261, acting as a 
usbser.sys compatible usb-to-serial port. It was a lot easier to use a 
polling interface because there was some Atmel sample code available.

During early startup, I add the usb driver with device_register(). Each 
function polls the status register, which works out fine since uboot calls 
tstc constantly to look for a new character or putc to display something. 
Finally I added a check for the device sense (power) to skip the 
initialization completely if we know it's not connected to anything.

-joey