cur_ppc_sys_spec is NULL

cur_ppc_sys_spec is NULL

[Dmytro Bablinyuk]

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?

Thank you,

Dimitry

Re: cur_ppc_sys_spec is NULL

[Vitaly Bordug]

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