LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
* Re: request_8xxirq
From: Tiago Dall'Agnol @ 2005-08-01 13:25 UTC (permalink / raw)
  To: Alex Zeffertt; +Cc: linuxppc-embedded
In-Reply-To: <20050801140407.5b6e4d36.ajz@cambridgebroadband.com>

Hi Alex

All right. But where are request_8xxirq? That's my doubt.

Thank you,
Tiago

Alex Zeffertt wrote:

>On Fri, 29 Jul 2005 14:01:21 -0300
>"Tiago Dall'Agnol" <tdallagnol@parks.com.br> wrote:
>  
>
>>But this code doesn't help to find request_8xxirq. It just do the 
>>opposite. This code defines request_irq to be request_8xxirq when 
>>CONFIG_8xx is defined. But where is located the implementation of 
>>request_8xxirq?
>>
>>    
>>
>
>See the code snippet in my last email.  The C preprocessor replaces 'int request_irq(...' with 'int
>request_8xxirq(...' prior to compilation.
>
>
>  
>
>>Alex Zeffertt wrote:
>>
>>    
>>
>>>Maybe you're using a really old kernel.  In linux-2.4.4 it's in
>>>arch/ppc/kernel/irq.c:
>>>
>>>-- snip --
>>>#if (defined(CONFIG_8xx) || defined(CONFIG_8260))
>>>/* Name change so we can catch standard drivers that potentially mess up
>>>* the internal interrupt controller on 8xx and 8260.  Just bear with me,
>>>* I don't like this either and I am searching a better solution.  For
>>>* now, this is what I need. -- Dan
>>>*/
>>>#define request_irq	request_8xxirq
>>>
>>>...
>>>...
>>>...
>>>
>>>int request_irq(unsigned int irq, void (*handler)(int, void *, struct pt_regs *),
>>>	unsigned long irqflags, const char * devname, void *dev_id)
>>>{
>>>--/snip --
>>>
>>>
>>>I don't know why it was done like this....
>>>
>>>Alex
>>>
>>>
>>>On Fri, 29 Jul 2005 10:52:33 -0300
>>>"Tiago Dall'Agnol" <tdallagnol@parks.com.br> wrote:
>>>
>>> 
>>>
>>>      
>>>
>>>>Thank you Alex.
>>>>
>>>>But in my linux, this is different.
>>>>What I have in that file is just
>>>>
>>>>extern int request_8xxirq(unsigned int irq,
>>>>              void (*handler)(int, void *, struct pt_regs *),
>>>>              unsigned long flags,
>>>>              const char *device,
>>>>              void *dev_id);
>>>>
>>>>And the request_8xxirq is declared as a
>>>>
>>>>EXPORT_SYMBOL(request_8xxirq);
>>>>
>>>>in arch/ppc/kernel/ppc_ksyms.c.
>>>>
>>>>I already tried to find out where the code that implements the function 
>>>>is located, but it seems that it doesn't exist in my distribuction. 
>>>>Maybe is it a "binary version"?
>>>>
>>>>Any other information will be apreciated ;-)
>>>>
>>>>Best Regards,
>>>>Tiago
>>>>
>>>>Alex Zeffertt wrote:
>>>>
>>>>   
>>>>
>>>>        
>>>>
>>>>>In linux-2.4 it's in 
>>>>>
>>>>>	include/asm-ppc/mpc8xx.h
>>>>>
>>>>>-- snip --
>>>>>#define request_8xxirq request_irq
>>>>>--/snip --
>>>>>
>>>>>And request_irq is in arch/ppc/kernel/irq.c
>>>>>
>>>>>Alex
>>>>>
>>>>>On Fri, 29 Jul 2005 10:07:58 -0300
>>>>>"Tiago Dall'Agnol" <tdallagnol@parks.com.br> wrote:
>>>>>
>>>>>
>>>>>
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>>>Hi,
>>>>>>
>>>>>>I had some problems with irq in my embedded system. I'm interested in 
>>>>>>this function source code, but I didn't find it in my linux distribuction?
>>>>>>
>>>>>>Does anyone know where I can find it?
>>>>>>
>>>>>>Thanks a lot
>>>>>>Tiago
>>>>>>
>>>>>>Manish Joshi wrote:
>>>>>>
>>>>>>  
>>>>>>
>>>>>>       
>>>>>>
>>>>>>            
>>>>>>
>>>>>>>Hi,
>>>>>>>
>>>>>>>I am working on an old code which uses  request_8xxirq() call which I 
>>>>>>>can't find in latest kernel.
>>>>>>>Has this been replaced by something else ?
>>>>>>>
>>>>>>>I see the references on net about replacing request_8xxirq()  with 
>>>>>>>request_irq(). Can I do it ?
>>>>>>>
>>>>>>>TIA,
>>>>>>>Manish
>>>>>>>
>>>>>>>
>>>>>>>------------------------------------------------------------------------
>>>>>>>Start your day with Yahoo! - make it your home page 
>>>>>>><http://us.rd.yahoo.com/evt=34442/*http://www.yahoo.com/r/hs>
>>>>>>>
>>>>>>>------------------------------------------------------------------------
>>>>>>>
>>>>>>>_______________________________________________
>>>>>>>Linuxppc-embedded mailing list
>>>>>>>Linuxppc-embedded@ozlabs.org
>>>>>>>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>>>>>>
>>>>>>>    
>>>>>>>
>>>>>>>         
>>>>>>>
>>>>>>>              
>>>>>>>
>>>>>>-- 
>>>>>>Tiago Dall'Agnol
>>>>>>Pesquisa e Desenvolvimento
>>>>>>Tel.: +55.51.470.05.64
>>>>>>Fax.: +55.51.470.05.70
>>>>>>e-mail: tdallagnol@parks.com.br
>>>>>>www.parks.com.br
>>>>>>
>>>>>>_______________________________________________
>>>>>>Linuxppc-embedded mailing list
>>>>>>Linuxppc-embedded@ozlabs.org
>>>>>>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>>>>>  
>>>>>>
>>>>>>       
>>>>>>
>>>>>>            
>>>>>>
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>-- 
>>>>   
>>>>
>>>>        
>>>>
>>> 
>>>
>>>      
>>>
>>-- 
>>Tiago Dall'Agnol
>>Pesquisa e Desenvolvimento
>>Tel.: +55.51.470.05.64
>>Fax.: +55.51.470.05.70
>>e-mail: tdallagnol@parks.com.br
>>www.parks.com.br
>>    
>>
>
>  
>

^ permalink raw reply

* Re: mpc8248  SEC -- interrupt handler "is" invoked
From: Kim Phillips @ 2005-08-01 17:37 UTC (permalink / raw)
  To: Vikas Aggarwal; +Cc: linuxppc-embedded
In-Reply-To: <33216.24.92.61.26.1122857296.squirrel@24.92.61.26>

On Sun, 31 Jul 2005 20:48:16 -0400 (EDT)
"Vikas Aggarwal" <va824363@albany.edu> wrote:

> Tried it as u said . No luck :(
> But something more i noted now in CPSR(channel pointer status
> register=0x2040)  that before ISR invoked it has 0x0:0x7.
> 
> After ISR invoked it has 0x7:0x2007 .  The 7 in low bits means
> channel_error and 2 is at "reserved" bits as per documentation, don't know
> what that means.
> 
> I also tried kmalloc with GFP_DMA, for the memory where i create the
> Descriptor.
> Please keep giving ideas for debugging this as this is what driving me
> right now.
> regards
> -vikas


So you reset the master, then the channel, allocate the RNG descriptor, allocate the random data buffer, fill the descriptor with values for an RNG request the size of your buffer (filling with the physical address of your random data buffer), and submit the descriptor's physical address to the FR..

btw, I'm finding it hard to help without seeing sec register transaction data, descriptor data, virtual and physical addresses, etc.

Kim

^ permalink raw reply

* endianness of Linux kernel RAID
From: Gregory Seidman @ 2005-08-01 17:42 UTC (permalink / raw)
  To: LinuxPPC dev list

It turns out that if one uses the kernel (2.4.x-2.6.x) RAID support (RAID5,
anyway, since that's all I've tested), the RAID'd disks cannot be moved to
another system with a different endianness. I don't know how hard that
would be to fix, but it did mean that when my ancient Mac clone I was using
as a server died I couldn't bring the RAID over to my spare x86 Linux box;
I had to dedicate other hardware (my dual G4 that I had been happily using
with OS X) to the task instead.

Unfortunately, I haven't gotten into kernel development and, therefore, do
not have the necessary expertise to fix it. Is anyone here interested in
this issue?

--Greg

^ permalink raw reply

* Re: endianness of Linux kernel RAID
From: Eugene Surovegin @ 2005-08-01 18:18 UTC (permalink / raw)
  To: LinuxPPC dev list
In-Reply-To: <20050801174238.GA31016@anthropohedron.net>

On Mon, Aug 01, 2005 at 01:42:39PM -0400, Gregory Seidman wrote:
> It turns out that if one uses the kernel (2.4.x-2.6.x) RAID support (RAID5,
> anyway, since that's all I've tested), the RAID'd disks cannot be moved to
> another system with a different endianness. I don't know how hard that
> would be to fix, but it did mean that when my ancient Mac clone I was using
> as a server died I couldn't bring the RAID over to my spare x86 Linux box;
> I had to dedicate other hardware (my dual G4 that I had been happily using
> with OS X) to the task instead.
> 
> Unfortunately, I haven't gotten into kernel development and, therefore, do
> not have the necessary expertise to fix it. Is anyone here interested in
> this issue?

It's a known Linux sw RAID problem. Please, bug RAID maintainers, not 
PPC people, as it's not a Linux PPC problem - RAID code is completely 
generic one.

-- 
Eugene

^ permalink raw reply

* Re: mpc8248  SEC -- interrupt handler 'is' invoked
From: Vikas Aggarwal @ 2005-08-01 18:50 UTC (permalink / raw)
  To: Kim Phillips; +Cc: linuxppc-embedded
In-Reply-To: <20050801123728.62764c7e.kim.phillips@freescale.com>

Hi Kim,
Yes, i checked to my knowledge that i am doing all these steps and also
checked the
bit positions.

I will send you the code excerpts. The code was written for 2.4 kernel and
8555E(downloaded from freescale)  and i ported it to  8248/kernel 2.6.

thanks for your help
-vikas


> On Sun, 31 Jul 2005 20:48:16 -0400 (EDT)
> "Vikas Aggarwal" <va824363@albany.edu> wrote:
>
>> Tried it as u said . No luck :(
>> But something more i noted now in CPSR(channel pointer status
>> register=0x2040)  that before ISR invoked it has 0x0:0x7.
>>
>> After ISR invoked it has 0x7:0x2007 .  The 7 in low bits means
>> channel_error and 2 is at "reserved" bits as per documentation, don't
>> know
>> what that means.
>>
>> I also tried kmalloc with GFP_DMA, for the memory where i create the
>> Descriptor.
>> Please keep giving ideas for debugging this as this is what driving me
>> right now.
>> regards
>> -vikas
>
>
> So you reset the master, then the channel, allocate the RNG descriptor,
> allocate the random data buffer, fill the descriptor with values for an
> RNG request the size of your buffer (filling with the physical address of
> your random data buffer), and submit the descriptor's physical address to
> the FR..
>
> btw, I'm finding it hard to help without seeing sec register transaction
> data, descriptor data, virtual and physical addresses, etc.
>
> Kim
>

^ permalink raw reply

* Bad Magic Number when boot linux kernel with ppcboot (PPC860 board)
From: FCG WANG Baohua @ 2005-08-02  2:08 UTC (permalink / raw)
  To: linuxppc-embedded

[-- Attachment #1: Type: text/plain, Size: 351 bytes --]

Dear All:
  I use a PPC860 board and ELDK 3.1.1 (kernel 2.4.25) to boot the linux kernel, after I loaded it print the following messages:

=> bootm 0x180000
## Booting image at 00000000 ...
Bad Magic Number
=>


How to slove it, thanks a lot!
I use:  zImage, 
vmlinux.UBoot,
 vmlinux 
 it all print the same messages, How can I do? 



[-- Attachment #2: Type: text/html, Size: 1504 bytes --]

^ permalink raw reply

* Reply: Bad Magic Number when boot linux kernel with ppcboot (PPC860 board)
From: FCG WANG Baohua @ 2005-08-02  2:31 UTC (permalink / raw)
  To: linuxppc-embedded

[-- Attachment #1: Type: text/plain, Size: 453 bytes --]

Dear All:
  I use a PPC860 board and ELDK 3.1.1 (kernel 2.4.25) to boot the linux kernel, after I loaded it print the following messages:

=> bootm 0x180000
## Booting image at 00000000 ...
Bad Magic Number
=>


How to slove it, thanks a lot!
I use:  zImage, 
vmlinux.UBoot,
 vmlinux 
 it all print the same messages, 
 I use "imi 0x180000"
 is also print the
 "
Checking Image at 00000000 ...
   Bad Magic Number"

How can I do?  

[-- Attachment #2: Type: text/html, Size: 2054 bytes --]

^ permalink raw reply

* Re: Bad Magic Number when boot linux kernel with ppcboot (PPC860 board)
From: Debora Liu @ 2005-08-02  3:17 UTC (permalink / raw)
  To: FCG WANG Baohua; +Cc: Linuxppc-embedded

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 463 bytes --]

Hello, FCG WANG Baohua

In message <2005-08-02 10:08:35 Baohua.WANG@alcatel-sbell.com.cn> you wrote:

>Dear All:
>  I use a PPC860 board and ELDK 3.1.1 (kernel 2.4.25) to boot the linux kernel, after I loaded it print the following messages:
>
>=> bootm 0x180000
>## Booting image at 00000000 ...
>Bad Magic Number
>=>
Please check your boot load image address.

				 
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡Debora Liu
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡deboralh@fel.com.cn
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2005-08-02

^ permalink raw reply

* PPC860 board and PPCBoot "verifying Checksum ... Bad Data CRC"
From: FCG WANG Baohua @ 2005-08-02  3:26 UTC (permalink / raw)
  To: wd; +Cc: Linuxppc-embedded

[-- Attachment #1: Type: text/plain, Size: 234 bytes --]

Dear All:
 I build the ELDK3.1.1  kernel 2.4.25, When bootm or "imi" it shows the  "verifying Checksum ... Bad Data CRC", then stop.
  But the vmlinux.UBoot is right in Host, How can I do? I use tftpboot to download it. 
 Thanks!

[-- Attachment #2: Type: text/html, Size: 922 bytes --]

^ permalink raw reply

* 答复: Bad Magic Number when boot linux kernel with ppcboot (PPC860 board)
From: FCG WANG Baohua @ 2005-08-02  3:28 UTC (permalink / raw)
  To: Debora Liu; +Cc: Linuxppc-embedded

Dear Mr Liu:
 I have corrected it, Now another question:
 when bootm or imi , it shows the "Verifying Checksum ... Bad Data CRC", =
But I checked the vmlinux.UBoot on host, it is right,
 I download it using TFTP, How can I slove it? Thanks!


-----=D4=AD=CA=BC=D3=CA=BC=FE-----
=B7=A2=BC=FE=C8=CB: Debora Liu [mailto:deboralh@fel.com.cn]
=B7=A2=CB=CD=CA=B1=BC=E4: 2005=C4=EA8=D4=C22=C8=D5 11:17
=CA=D5=BC=FE=C8=CB: FCG WANG Baohua
=B3=AD=CB=CD: Linuxppc-embedded
=D6=F7=CC=E2: Re: Bad Magic Number when boot linux kernel with ppcboot =
(PPC860
board)


Hello, FCG WANG Baohua

In message <2005-08-02 10:08:35 Baohua.WANG@alcatel-sbell.com.cn> you =
wrote:

>Dear All:
>  I use a PPC860 board and ELDK 3.1.1 (kernel 2.4.25) to boot the linux =
kernel, after I loaded it print the following messages:
>
>=3D> bootm 0x180000
>## Booting image at 00000000 ...
>Bad Magic Number
>=3D>
Please check your boot load image address.

				=20
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1Debora Liu
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1deboralh@fel.com.cn
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A12005-08-02

^ permalink raw reply

* RE: Serial console
From: JohnsonCheng @ 2005-08-02  3:38 UTC (permalink / raw)
  To: 'Daniel Ann', 'Anton Wöllert'; +Cc: linuxppc-embedded
In-Reply-To: <9b7ca65705073118276e89b29@mail.gmail.com>

Dear Daniel,

I also meet this problem on MPC8245 with linux-2.6.12.3, and I found it =
uses
LEVEL for interrupt in sandpoint.c. Do you have any idea for it?

Thanks,
Johnson Cheng

-----Original Message-----
From: linuxppc-embedded-bounces@ozlabs.org
[mailto:linuxppc-embedded-bounces@ozlabs.org] On Behalf Of Daniel Ann
Sent: Monday, August 01, 2005 9:27 AM
To: Anton W=F6llert
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Serial console

Thanks for your input Anton.
I'm not all that certain about sandpoint platform has its own serial
driver so I've worked with 8250.c. Anyway, I've got it working now. It
was problem with interrupt. As soon as I changed interrupt from EGDE
to LEVEL it began working. Altho I'm faced with yet another problem
with openpic but I'm digging thru it at the moment.

BTW, I have no idea why EDGE didnt work and LEVEL does.

Cheers,
Daniel

On 7/30/05, Anton W=F6llert <a.woellert@gmail.com> wrote:
> Daniel Ann wrote:
> > Hi folks,
> >
> > Having all the kernel boot up log on console means that I've done =
some
> > part right. But why am I not getting anything from the user =
processes
> > on the console screen ?
> >
> > Is there anything I need to do on the kernel config ?
> >
>=20
> Hi, we've had the same problem some time ago on a tqm850l (mpc850). =
Our
> problem was, that we had registered two serial consoles in the kernel
> config or something like that. we had to disable all serial-driver =
stuff
> and enable just the platform-specific serial-console driver. we =
tracked
> this down with inserting a printk(buf) into the tty_write fs-op of the
> serial-port driver in drivers/char/tty_io.c. the ttyS0 was used but =
has
> taken another serial-driver than the platform specific.
>=20
> may this help you :)
>=20
>=20
> anton
>=20


--=20
Daniel
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

^ permalink raw reply

* serial console no response after print "Transferring control to Linux (at address 00000000)" on PPC860
From: FCG WANG Baohua @ 2005-08-02  4:52 UTC (permalink / raw)
  To: linuxppc-embedded

[-- Attachment #1: Type: text/plain, Size: 366 bytes --]

Dear All:
  I use ppcboot and ELDK 3.1.1 kernel 2.4.25 to boot a PPC860 board, I select the ttyS0, 9600, root=/de/ram during config the kernel.
   I select the SMC1,SMC2 device too. 
  But when bootm 180000, it print the "Transferring control to Linux (at address 00000000)"  then halt. 
  How can I do? Tell me the detail when config the kernel, thanks!

  

[-- Attachment #2: Type: text/html, Size: 1228 bytes --]

^ permalink raw reply

* Re: Bad Magic Number when boot linux kernel with ppcboot (PPC860 board)
From: Wolfgang Denk @ 2005-08-02  7:12 UTC (permalink / raw)
  To: FCG WANG Baohua; +Cc: linuxppc-embedded
In-Reply-To: <A9DE2BAF233E444FA9C5E77A5825A01E8652F9@ydmail.sbell.com.cn>

In message <A9DE2BAF233E444FA9C5E77A5825A01E8652F9@ydmail.sbell.com.cn> you wrote:
> 
> kernel, after I loaded it print the following messages:
> 
> => bootm 0x180000
> ## Booting image at 00000000 ...
> Bad Magic Number
> =>

Which address did you load the image to?

> How to slove it, thanks a lot!
> I use:  zImage, 
> vmlinux.UBoot,
>  vmlinux 
>  it all print the same messages, How can I do? 

Please read the documentation. Only uImage = vmlinux.UBoot can work.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"Confound these ancestors.... They've stolen our best ideas!"
- Ben Jonson

^ permalink raw reply

* Re: Reply: Bad Magic Number when boot linux kernel with ppcboot (PPC860 board)
From: Wolfgang Denk @ 2005-08-02  7:15 UTC (permalink / raw)
  To: FCG WANG Baohua; +Cc: linuxppc-embedded
In-Reply-To: <A9DE2BAF233E444FA9C5E77A5825A01E8652FA@ydmail.sbell.com.cn>

In message <A9DE2BAF233E444FA9C5E77A5825A01E8652FA@ydmail.sbell.com.cn> you wrote:
> 
> => bootm 0x180000
> ## Booting image at 00000000 ...
> Bad Magic Number
> =>

The funny thing is that you seem to enter "0x180000" but the  address
printed  is  00000000.  make  sure  you  have  no funny characters or
control keys in this number. Re-type  it  carefully.  Omit  the  "0x"
part, i. e. try a plain "bootm 180000'


Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Brontosaurus Principle: Organizations  can  grow  faster  than  their
brains  can manage them in relation to their environment and to their
own physiology: when this occurs, they are an endangered species.
                                                - Thomas K. Connellan

^ permalink raw reply

* Re: serial console no response after print "Transferring control to Linux (at address 00000000)" on PPC860
From: Wolfgang Denk @ 2005-08-02  7:18 UTC (permalink / raw)
  To: FCG WANG Baohua; +Cc: linuxppc-embedded
In-Reply-To: <A9DE2BAF233E444FA9C5E77A5825A01E8652FD@ydmail.sbell.com.cn>

In message <A9DE2BAF233E444FA9C5E77A5825A01E8652FD@ydmail.sbell.com.cn> you wrote:
> 
>   I use ppcboot and ELDK 3.1.1 kernel 2.4.25 to boot a PPC860 board, I
> select the ttyS0, 9600, root=/de/ram during config the kernel.
>    I select the SMC1,SMC2 device too. 
>   But when bootm 180000, it print the "Transferring control to Linux (at
> address 00000000)"  then halt. 
>   How can I do? Tell me the detail when config the kernel, thanks!

After all the questions you posted to the mailing list I want to give
two recommendations:

* Please continue to try things for a while (dasy a day or so) before
  posting. This will avoid a lot of unnecessary postings.

* Please do yourself (and us) a favour and  read  the  documentation,
  especially  the  FAQ  section  of the DULG. If you already read it,
  then read it agaion, carefully.
  
Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
You may call me by my name, Wirth, or by my value, Worth.
- Nicklaus Wirth

^ permalink raw reply

* ??: Bad Magic Number when boot linux kernel with ppcboot (PPC860 board)
From: FCG WANG Baohua @ 2005-08-02  7:29 UTC (permalink / raw)
  To: wd; +Cc: linuxppc-embedded

Dear Denk:
  The magic number is right when using vmlinux.UBoot instead of vmlinux =
or zImage, Why?
  Another question puzzle me:
  The kernel print the "Transferring control to Linux (at address =
00000000) ... "  then halt ,no any response from serial port.
  I tried ramdiak and nfs, there are the same result.
  So why not print the=20
  "Linux version 2.4.25 (root at FedoraCore2) (gcc version 3.3.3 (DENX =
ELDK 3.1
3.3.3-8)) #94 Tue Jul 5 18:59:08 PDT 2005"=20
 =20
  How to not print the "Transferring control to Linux (at address =
00000000) ... "  ? Is it right ?=20
  Thanks a lot!


-----????-----
???: wd@denx.de [mailto:wd@denx.de]
????: 2005?8?2? 15:13
???: FCG WANG Baohua
??: linuxppc-embedded@ozlabs.org
??: Re: Bad Magic Number when boot linux kernel with ppcboot (PPC860 =
board)=20


In message <A9DE2BAF233E444FA9C5E77A5825A01E8652F9@ydmail.sbell.com.cn> =
you wrote:
>=20
> kernel, after I loaded it print the following messages:
>=20
> =3D> bootm 0x180000
> ## Booting image at 00000000 ...
> Bad Magic Number
> =3D>

Which address did you load the image to?

> How to slove it, thanks a lot!
> I use:  zImage,=20
> vmlinux.UBoot,
>  vmlinux=20
>  it all print the same messages, How can I do?=20

Please read the documentation. Only uImage =3D vmlinux.UBoot can work.

Best regards,

Wolfgang Denk

--=20
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"Confound these ancestors.... They've stolen our best ideas!"
- Ben Jonson

^ permalink raw reply

* AW: Bad Magic Number when boot linux kernel with ppcboot (PPC860 board)
From: David Grab @ 2005-08-02  8:08 UTC (permalink / raw)
  To: 'FCG WANG Baohua'; +Cc: linuxppc-embedded
In-Reply-To: <A9DE2BAF233E444FA9C5E77A5825A01E865051@ydmail.sbell.com.cn>

[-- Attachment #1: Type: text/plain, Size: 1413 bytes --]

>Dear Denk:
>  The magic number is right when using vmlinux.UBoot instead of vmlinux or
zImage, Why?

u-boot needs an u-boot image. Wolfgang did already say that vmlinux.UBoot is
that image. So use this image and nothing else. Also read the manual
especially this chapter
http://www.denx.de/twiki/bin/view/DULG/BootingEmbeddedLinux

>  Another question puzzle me:
>  The kernel print the "Transferring control to Linux (at address 00000000)
... "  then halt ,no any response 
> from serial port.

Seems for me that the serial configuration did not match. Are you sure you
chosen and cofigured the right UART? If so then debug with BDI2000. 

>  I tried ramdiak and nfs, there are the same result.
>  So why not print the 
>  "Linux version 2.4.25 (root at FedoraCore2) (gcc version 3.3.3 (DENX ELDK
3.1
>3.3.3-8)) #94 Tue Jul 5 18:59:08 PDT 2005" 

The console output has nothing to do with ramdisk or nfs. So check your
configuration of the active console. An quick check, if your u-boot did not
pass the console parameters is to set the console parameter in linux. For
that you have to activate command line to yes and set the command line
parameter to 'console=ttySx'. x=0 is UART0 and x=1 is UART1. If this not
help then debug again with BDI.

>  How to not print the "Transferring control to Linux (at address 00000000)
... "  ? Is it right ? 
>  Thanks a lot!

This print might be ok.

Best regards,

David

[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 2328 bytes --]

^ permalink raw reply

* MPC8245+2.6.12=oops
From: Carl Ljungmark @ 2005-08-02  8:44 UTC (permalink / raw)
  To: linuxppc-embedded

Hello everyone!
Trying to boot linux 2.6.12 on an MPC8245 board from MEN (a12) with MenMo=
n =20
firmware. Nothing is printed to the console (ttyS0), but the __log_buf =20
contains this:

<4>entering platform_init.
<4>MENMON parameter string: MPAR brd=3DA012a brdrev=3D01.04.00 brdmod=3D0=
0 =20
sernbr=3D74 cbr=3D38400 cons=3DCOM1 mem0=3D262144 cpu=3DMPC8245 cpuclk=3D=
250memclk=3D100 =20
vmeirqenb=3DFEclun=3D02dlun=3D00 mm=3Dsmm =20
MMST=3D_00+_12+_1B+_1C+_0C+_17+_1A+_1D+_1E-SPD+RTC+LM75+WDOG+CHKS+ALL+.
<4>Command line now console=3DttyS0,38400.
<4>Using memory size from MENMON 0x10000000.
<3>Non-recoverable exception at PC=3Dc0007af0 MSR=3Db930.
<4>Oops: nonrecoverable exception,sig: 9 [#1].
<4>NIP: C0007AF0 LR:C000E474 SP: C00F7F70 REGS: c00f7ec0 TRAP: 0600 Not =20
tainted.
<4>MSR: 0000b930 EE: 1 PR: 0 FP:1 ME: 1 IR/DR:11.
<4>DAR: C0138000, DSISR: 00017C00.
<4>TASK =3D c00dda10[0] 'swapper' THREAD: c00f6000.
<4>Last syscall: 0 .
<6>GPR00: 00000080 C00F7F70 C00DDA10 C0138000 0000000000001000 00000001 =20
00000001 .
<6>GPR08: 0000000200000000 00000001 00000000 00000000 00000000 00008081 =20
2A090A86 .
<6>GPR16: 10588403 1E21D063 21218986 50022502 3C0185B8 011368CA00FFF010 =20
00FFF024 .
<6>GPR24: 00000000 01F8FA68 40000000 C00DC000000005A9 FD000000 FD000000 =20
C0138000 .
<4>NIP [c0007af0] clear_pages+0x10/0x1c.
<4>LR [c000e474] pte_alloc_one_kernel+0x60/0x78.
<4>Call trace:.
<4> [c003e948] pte_alloc_kernel+0x54/0x84.
<4> [c000e5e4] map_page+0x3c/0xdc.
<4> [c00ff61c] io_block_mapping+0x78/0xdc.
<4> [c00fe560] men824xali_map_io+0x20/0x44.
<4> [c00fec38] MMU_init+0x194/0x204.
<4> [c00032a4]start_here+0x48/0x80.
0>Kernelpanic - not syncing: Attempted to kill the idletask!.
<4> ......

adding 'nobats' to the command line changes the boot output slightly (I =20
then get two oops).

In order to get the whole output I had to turn off caching, maybe this ha=
s =20
influenced the boot process.. with dcache on, the __log_buf is practicall=
y =20
empty.

Has anyone managed to boot 6.12 on this board successfully?

Thanks in advance,
Carl.

^ permalink raw reply

* Re: PPC860 board and PPCBoot "verifying Checksum ... Bad Data CRC"
From: Alex Zeffertt @ 2005-08-02  8:47 UTC (permalink / raw)
  To: FCG WANG Baohua; +Cc: Linuxppc-embedded
In-Reply-To: <A9DE2BAF233E444FA9C5E77A5825A01E8652FB@ydmail.sbell.com.cn>

On Tue, 2 Aug 2005 11:26:30 +0800
"FCG WANG Baohua" <Baohua.WANG@alcatel-sbell.com.cn> wrote:

> Dear All:
>  I build the ELDK3.1.1  kernel 2.4.25, When bootm or "imi" it shows the  "verifying Checksum ...
>  Bad Data CRC", then stop.
>   But the vmlinux.UBoot is right in Host, How can I do? I use tftpboot to download it. 
>  Thanks!
> 

You may have a RAM error.  Try running mtest in uboot.  (And make sure CFG_MEMTEST_START and
CFG_MEMTEST_END cover the region to which you are downloading uImage.)

Alex

^ permalink raw reply

* [PATCH] fix gcc4 warning in asm-ppc/time.h
From: Christoph Hellwig @ 2005-08-02  9:55 UTC (permalink / raw)
  To: paulus, akpm; +Cc: linuxppc-dev

A function must not return a const value, instead use
__attribute_const__.


Index: linux-2.6/include/asm/time.h
===================================================================
--- linux-2.6.orig/include/asm/time.h	2005-04-30 10:17:19.000000000 +0200
+++ linux-2.6/include/asm/time.h	2005-08-01 11:57:12.000000000 +0200
@@ -10,6 +10,7 @@
 #define __ASM_TIME_H__
 
 #include <linux/config.h>
+#include <linux/compiler.h>
 #include <linux/types.h>
 #include <linux/rtc.h>
 #include <linux/threads.h>
@@ -58,7 +59,7 @@
 /* Accessor functions for the timebase (RTC on 601) registers. */
 /* If one day CONFIG_POWER is added just define __USE_RTC as 1 */
 #ifdef CONFIG_6xx
-extern __inline__ int const __USE_RTC(void) {
+extern __inline__ int __attribute_const__ __USE_RTC(void) {
 	return (mfspr(SPRN_PVR)>>16) == 1;
 }
 #else

^ permalink raw reply

* [PATCH] fix asm-ppc/dma-mapping.h sparse warning
From: Christoph Hellwig @ 2005-08-02  9:56 UTC (permalink / raw)
  To: paulus, akpm; +Cc: linuxppc-dev

GFP flags must be passed as unisgned int __nocast these days, else we'll get
tons of sparse warnings in every driver.


Index: linux-2.6/include/asm-ppc/dma-mapping.h
===================================================================
--- linux-2.6.orig/include/asm-ppc/dma-mapping.h	2005-07-28 19:32:32.000000000 +0200
+++ linux-2.6/include/asm-ppc/dma-mapping.h	2005-07-31 16:22:20.000000000 +0200
@@ -60,7 +60,8 @@
 }
 
 static inline void *dma_alloc_coherent(struct device *dev, size_t size,
-				       dma_addr_t * dma_handle, int gfp)
+				       dma_addr_t * dma_handle,
+				       unsigned int __nocast gfp)
 {
 #ifdef CONFIG_NOT_COHERENT_CACHE
 	return __dma_alloc_coherent(size, dma_handle, gfp);

^ permalink raw reply

* A PPC kernel issue with UART ??
From: JohnsonCheng @ 2005-08-02 11:41 UTC (permalink / raw)
  To: linuxppc-embedded

[-- Attachment #1: Type: text/plain, Size: 790 bytes --]

Dear All,

 

I meet a wired UART problem on linux-2.6 with MPC8241 chip.

 

My Environment is as following: 

CPU: MPC8241

Linux: 2.6.12.3

COM1 offset: 0x4500, COM2 offset: 0x4600

 

When I booting my rootfs, it hangs at following message:

RAMDISK: Compressed image found at block 0

VFS: Mounted root (ext2 filesystem) readonly.

Freeing unused kernel memory: 104k init

EXT2-fs warning: checktime reached, running e2fsck is recommended

 

I had add printk in tty_write() of drivers/char/tty_io.c, the message from
rootfs have printed.

The conclusion is that message can be printed by printk() in linux kernel,
but can't be printed by printf() in user mode. I think it must be something
wrong for my UART configurations, does anybody know it??

 

 

Best Regards,

Johnson Cheng


[-- Attachment #2: Type: text/html, Size: 5274 bytes --]

^ permalink raw reply

* Re: ??: Bad Magic Number when boot linux kernel with ppcboot (PPC860 board)
From: Wolfgang Denk @ 2005-08-02 12:16 UTC (permalink / raw)
  To: FCG WANG Baohua; +Cc: linuxppc-embedded
In-Reply-To: <A9DE2BAF233E444FA9C5E77A5825A01E865051@ydmail.sbell.com.cn>

In message <A9DE2BAF233E444FA9C5E77A5825A01E865051@ydmail.sbell.com.cn> you wrote:
> >
>   The magic number is right when using vmlinux.UBoot instead of vmlinux
> or zImage, Why?

Because vmlinux.UBoot is a correct U-Boot image,  while  vmlinux  and
zImage are not. Read the documentation.

>   Another question puzzle me:
>   The kernel print the "Transferring control to Linux (at address
> 00000000) ... "  then halt ,no any response from serial port.

Read the documentation. This is a FAQ.

>   How to not print the "Transferring control to Linux (at address
> 00000000) ... "  ? Is it right ? 

Yes, this is correct.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Punishment becomes ineffective after a certain point. Men become  in-
sensitive.
	-- Eneg, "Patterns of Force", stardate 2534.7

^ permalink raw reply

* Re: MPC8245+2.6.12=oops
From: Kumar Gala @ 2005-08-02 13:24 UTC (permalink / raw)
  To: Carl Ljungmark; +Cc: linuxppc-embedded
In-Reply-To: <op.suvg7mug0c7u6q@clj.sysgo.com>

This looks like an issue with the MEN port.  without that code its  
difficult to comment on what exactly may be wrong.

- kumar

On Aug 2, 2005, at 3:44 AM, Carl Ljungmark wrote:

> Hello everyone!
> Trying to boot linux 2.6.12 on an MPC8245 board from MEN (a12) with  
> MenMon
> firmware. Nothing is printed to the console (ttyS0), but the __log_buf
> contains this:
>
> <4>entering platform_init.
> <4>MENMON parameter string: MPAR brd=A012a brdrev=01.04.00 brdmod=00
> sernbr=74 cbr=38400 cons=COM1 mem0=262144 cpu=MPC8245  
> cpuclk=250memclk=100
> vmeirqenb=FEclun=02dlun=00 mm=smm
> MMST=_00+_12+_1B+_1C+_0C+_17+_1A+_1D+_1E-SPD+RTC+LM75+WDOG+CHKS+ALL+.
> <4>Command line now console=ttyS0,38400.
> <4>Using memory size from MENMON 0x10000000.
> <3>Non-recoverable exception at PC=c0007af0 MSR=b930.
> <4>Oops: nonrecoverable exception,sig: 9 [#1].
> <4>NIP: C0007AF0 LR:C000E474 SP: C00F7F70 REGS: c00f7ec0 TRAP: 0600  
> Not
> tainted.
> <4>MSR: 0000b930 EE: 1 PR: 0 FP:1 ME: 1 IR/DR:11.
> <4>DAR: C0138000, DSISR: 00017C00.
> <4>TASK = c00dda10[0] 'swapper' THREAD: c00f6000.
> <4>Last syscall: 0 .
> <6>GPR00: 00000080 C00F7F70 C00DDA10 C0138000 0000000000001000  
> 00000001
> 00000001 .
> <6>GPR08: 0000000200000000 00000001 00000000 00000000 00000000  
> 00008081
> 2A090A86 .
> <6>GPR16: 10588403 1E21D063 21218986 50022502 3C0185B8  
> 011368CA00FFF010
> 00FFF024 .
> <6>GPR24: 00000000 01F8FA68 40000000 C00DC000000005A9 FD000000  
> FD000000
> C0138000 .
> <4>NIP [c0007af0] clear_pages+0x10/0x1c.
> <4>LR [c000e474] pte_alloc_one_kernel+0x60/0x78.
> <4>Call trace:.
> <4> [c003e948] pte_alloc_kernel+0x54/0x84.
> <4> [c000e5e4] map_page+0x3c/0xdc.
> <4> [c00ff61c] io_block_mapping+0x78/0xdc.
> <4> [c00fe560] men824xali_map_io+0x20/0x44.
> <4> [c00fec38] MMU_init+0x194/0x204.
> <4> [c00032a4]start_here+0x48/0x80.
> 0>Kernelpanic - not syncing: Attempted to kill the idletask!.
> <4> ......
>
> adding 'nobats' to the command line changes the boot output  
> slightly (I
> then get two oops).
>
> In order to get the whole output I had to turn off caching, maybe  
> this has
> influenced the boot process.. with dcache on, the __log_buf is  
> practically
> empty.
>
> Has anyone managed to boot 6.12 on this board successfully?
>
> Thanks in advance,
> Carl.
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>

^ permalink raw reply

* Re : MPC8245+2.6.12=oops
From: Sam Song @ 2005-08-02 13:38 UTC (permalink / raw)
  To: Carl Ljungmark; +Cc: linuxppc-embedded
In-Reply-To: <op.suvg7mug0c7u6q@clj.sysgo.com>

Carl Ljungmark <carl.ljungmark@sysgo.com> wrote:
> Trying to boot linux 2.6.12 on an MPC8245 board from
> MEN (a12) with MenMon  
> firmware. Nothing is printed to the console (ttyS0),
> but the __log_buf contains this:
> 
> <4>entering platform_init.

Seems sth wrong on target init configuration. Pls 
check some values like MPC10X_MAPB_EUMB_BASE or 
UART related stuff like SERIAL_PORT_DFNS. Well, I 
just have the successful experience on a MPC8241 
target based on SANDPOINT board with 2.6.12-rc2 and 
2.6.13-rc3. 

In addition, enable early console is also a help to
debug.

Best regards,

Sam

__________________________________________________
赶快注册雅虎超大容量免费邮箱?
http://cn.mail.yahoo.com

^ permalink raw reply


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox