From: Vitaly Bordug <vbordug@ru.mvista.com>
To: Dmytro Bablinyuk <dmytro.bablinyuk@rftechnology.com.au>
Cc: Linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: cur_ppc_sys_spec is NULL
Date: Mon, 10 Oct 2005 15:29:32 +0400 [thread overview]
Message-ID: <434A509C.3080709@ru.mvista.com> (raw)
In-Reply-To: <4349F072.6050309@rftechnology.com.au>
Dmytro Bablinyuk wrote:
> I have latest linux-2.6-denx (MPC8272ADS board) kernel and I have some
> questions, may be somebody knows:
> Here is the kernel output
>
> Linux version 2.6.14-rc3-g2f70d4fe ..
> Motorola PQ2 ADS PowerPC port
> Built 1 zonelists
> Kernel command line: console=ttyCPM0,115200 /dev/ram rw
> PID hash table entries: 512 (order: 9, 8192 bytes)
> Warning: real time clock seems stuck!
> Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
> Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
> Memory: 62720k available (1628k kernel code, 388k data, 92k init, 0k
> highmem)
> Mount-cache hash table entries: 512
> NET: Registered protocol family 16
> <stuck here>
>
> Using gdb and BDI2000 I have allocated the problem in ppc_sys_init(void)
> - cur_ppc_sys_spec is NULL. There are 3 functions to find an appropriate
> spec:
> identify_ppc_sys_by_id
> identify_ppc_sys_by_name
> identify_ppc_sys_by_name_and_id
> None of them are called by pq2ads.c or from any other place for 8272. I
> am just wondering if anybody might know at what stage spec should be
> selected for 8272ADS?
>
Yes, that's just the point, and I know about this issue. One of those do
need to be called early in the board initialization code.
I'll come with the fix shortly (hopefully today).
> Thank you,
>
> Dimitry
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>
--
Sincerely,
Vitaly
prev parent reply other threads:[~2005-10-10 11:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-10 4:39 cur_ppc_sys_spec is NULL Dmytro Bablinyuk
2005-10-10 11:29 ` Vitaly Bordug [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=434A509C.3080709@ru.mvista.com \
--to=vbordug@ru.mvista.com \
--cc=dmytro.bablinyuk@rftechnology.com.au \
--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).