linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "David H. Lynch Jr." <dhlii@dlasys.net>
To: schardt <g.schardt@fz-juelich.de>,
	linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: Init hangs on Xilinx4
Date: Fri, 30 Nov 2007 04:27:08 -0500	[thread overview]
Message-ID: <474FD76C.4060700@dlasys.net> (raw)
In-Reply-To: <474ED262.5010408@fz-juelich.de>

schardt wrote:
> Hi David,
>
> thanks for your help.
>   
>>>   
>>>     
>>>       
>>     I am presuming you are using PK's UartLite driver.
>>   
>>     
> I use the Kernel from Grant's git server,  and let me look... yes its
> from Peter Korsgaard :)
>
>   
>>     Try printing out membase some time possibly in ulite_console_setup.
>>     If the value of membase is 0x406000000 that is your problem.
>>     It should be something like 0xfdxxxxxxxx I think.
>>   
>>     
> Mmmh, my EDK Project maps the uartlite to 0x40600000, so i think its
> okay. but i can try it at a higher adress
>
> it is very strange. i use the same hardware setup and boot from
> system-ace without any problems.
    Another posibility that I thought of since you are using Peter K's
driver.
    If you have any interrupt problems I think you could get your
current behavior.
   
    During boot console I/O is not interrupt driven. When the OS sends a
string the whole string gets sent and then the console write exits,
    but very close to running init, the console switches to using the
full driver. PK's driver is interrupt driven. If the UartLite TX FIFO
empty interrupt
    is broke in anyway, it will send until the first time the FIFO fills
and then stop.  The interrupt could be broken in firmware - not properly
connected to the PIC, or it could be broken in software - however your
driver is receiving its interrupt configuration, the driver may be
receiving the incorrect intterrupt #.

    At one point I tried to add timer driven polling to PK's driver
similar to that in the 8250 and others - we have clients that run
without any PIC,
    but trying to figure out what was going on proved sufficiently
difficult I just went back to my own driver.    


>  
>
>
> Regards
> Georg
>
>
> -------------------------------------------------------------------
> -------------------------------------------------------------------
> Forschungszentrum Jülich GmbH
> 52425 Jülich
>
> Sitz der Gesellschaft: Jülich
> Eingetragen im Handelsregister des Amtsgerichts Düren Nr. HR B 3498
> Vorsitzende des Aufsichtsrats: MinDirig'in Bärbel Brumme-Bothe
> Geschäftsführung: Prof. Dr. Achim Bachem (Vorsitzender),
> Dr. Ulrich Krafft (stellv. Vorsitzender), Dr. Sebastian M. Schmidt
> -------------------------------------------------------------------
> -------------------------------------------------------------------
>   


-- 
Dave Lynch 					  	    DLA Systems
Software Development:  				         Embedded Linux
717.627.3770 	       dhlii@dlasys.net 	  http://www.dlasys.net
fax: 1.253.369.9244 			           Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.

"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein

      parent reply	other threads:[~2007-11-30  9:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-28 15:24 Init hangs on Xilinx4 schardt
2007-11-29 12:41 ` David H. Lynch Jr.
2007-11-29 12:53   ` schardt
     [not found]     ` <474ECB50.90303@dlasys.net>
     [not found]       ` <474ED262.5010408@fz-juelich.de>
2007-11-30  9:27         ` David H. Lynch Jr. [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=474FD76C.4060700@dlasys.net \
    --to=dhlii@dlasys.net \
    --cc=g.schardt@fz-juelich.de \
    --cc=linuxppc-embedded@ozlabs.org \
    /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;
as well as URLs for NNTP newsgroup(s).