[okl4-developer] Porting Oklinux

[houwei]

Hi All,

 

I have some questions  when porting oklinux.

 

Now , oklinux has boot  to Mount filesysterm, but never display “Linux
user startup!”

 

When I open debug option, I found the problem is that  uart is continous
printing “uart_open(0) called”, “uart_close(0) called”

 

I don’t know why linux is never startup, and I hope I can get some  useful
informations.

 

 

Thanks to all!

 
Hou wei

 

 

 

 

 

This is some log information:

………………………..

……………………….

TCP cubic registered

NET: Registered protocol family 1

NET: Registered protocol family 17

driver_probe_done: probe_count = 0

sysfs_read_file: count = 32, ppos = 0, buf = 254:0

 

VFS: Mounted root (ext2 filesystem) readonly.

uart_open(0) called

uart_open(0) called

uart_close(0) called

uart_close(0) called

uart_wait_until_sent(0), jiffies=4294937469, expire=4294937473...

uart_wait_until_sent(0), jiffies=4294937475, expire=4294937477...

Trying to free already-free IRQ 12

uart_flush_buffer(0) called

uart_open(0) called

uart_close(0) called

uart_wait_until_sent(0), jiffies=4294937824, expire=4294937828...

uart_flush_buffer(0) called

uart_open(0) called

uart_close(0) called

uart_wait_until_sent(0), jiffies=4294937824, expire=4294937828...

uart_flush_buffer(0) called

uart_open(0) called

uart_close(0) called

uart_wait_until_sent(0), jiffies=4294937824, expire=4294937828...

uart_flush_buffer(0) called

………………………………

………………………………

………………………………

 

 

 

 

 

 

  _____  

发件人: developer-bounces at okl4.org [mailto:developer-bounces at okl4.org] 代表
Kumar Sanghvi
发送时间: 2009年9月15日 11:19
收件人: developer at okl4.org
主题: [okl4-developer] Physical Memory & Virtual Memory

 

Hi All,

I have some very basic / fundamental (may even sound silly) questions:-

How do we determine the values for the following variables in the
platform/SoCXX/tools/machines.py file:-

1) memory[physical]  .. This value I believe corresponds to RAM (silly
question) and probably can be obtained by consulting the TRM of SoCXX. But
still, any advise would be helpful.
2) memory[virtual] ... how this value is determined for any particular
SoCXX?
3) base_vaddr ... again here, how this value is determined for any
particular SoCXX?

4) Based on above values, final memory layout will be reflected in the
image.elf file generated. But any basic explanation related to this would be
helpful.
5) Also, based on above values, the parameters that we pass to u-boot will
also change.

For e.g. consider that an SoCXX has 512MB RAM with address range as : 0x8000
0000 - 0x9FFF FFFF
How do we determine the values of above variables based on this information?

Thanks to all,
Kumar.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.okl4.org/pipermail/developer/attachments/20090927/9c546fd9/attachment.htm