From: Ashlesha Shintre <ashlesha@kenati.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: Atsushi Nemoto <anemo@mba.ocn.ne.jp>, linux-mips@linux-mips.org
Subject: Re: console stuck
Date: Sat, 09 Dec 2006 16:09:41 -0800 [thread overview]
Message-ID: <1165709381.6518.13.camel@sandbar.kenati.com> (raw)
In-Reply-To: <457AEA8B.9030605@ru.mvista.com>
Another basic query:
I m pretty sure I cant see my user space messages on the console due to
the fact that the ttyS0 device is not registered --
The board specific platform_init function that I wrote returns non-error
values and executes fine! --
Also, I figured that the ttyS0 uart regsitration is a separate process
that runs independently of the above arch_initcall --
It is spawned from the serial8250_register_ports function which is part
of the __init routines --
The "name" of the uart driver in this case is "serial" and is the struct
uart_driver serial8250_reg defined in the drivers/serial/8250.c file and
not "serial8250" which is the name of the struct device_driver
serial8250_isa_driver
-- how are these two processes -- the arch_initcall encm3_platform_init
function and the __init serial8250_register_ports function related? and
how come they use separate drivers?
Thank you,
Ashlesha.
On Sat, 2006-12-09 at 19:55 +0300, Sergei Shtylyov wrote:
> Hello.
>
> Ashlesha Shintre wrote:
> > Hi,
>
> > I m very much confused as to why there is an infinite loop in the
> > __request_resource function in the linux/kernel/resource.c file?
>
> It has 2 exit points (return statements).
>
> > The serial console is getting stuck at this point.
>
> Then there's something very wrong with your resources...
>
> >>for (;;) {
> >> tmp = *p;
> >> if (!tmp || tmp->start > end) {
> >> new->sibling = tmp;
> >> *p = new;
> >> new->parent = root;
> >> return NULL;
> >> }
> >> p = &tmp->sibling;
> >> if (tmp->end < start){
> >> printk("tmp->end = %d\n",tmp->end);
> >> printk("tmp->start = %d\n",tmp->start);
> >> printk("*********!!!!!!!*******sibling?!!\n");
> >> continue;
> >> }
> >> return tmp;
> >
> >
> > Thanks and Regards,
> > Ashlesha.
>
> WBR, Sergei
>
prev parent reply other threads:[~2006-12-09 23:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 2:22 console stuck Ashlesha Shintre
2006-12-09 16:55 ` Sergei Shtylyov
2006-12-10 0:09 ` Ashlesha Shintre [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=1165709381.6518.13.camel@sandbar.kenati.com \
--to=ashlesha@kenati.com \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.org \
--cc=sshtylyov@ru.mvista.com \
/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