linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Saso Kavcic <saso@activetools.si>
To: Steven Blakeslee <BlakesleeS@embeddedplanet.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Some issues with kernel 2.6 for MPC8260 target
Date: Wed, 12 Jan 2005 15:53:08 +0100	[thread overview]
Message-ID: <41E539D4.2000502@activetools.si> (raw)
In-Reply-To: <1628E43D99629C46988BE46087A3FBB912F225@ep-01.EmbeddedPlanet.local>

Thanks for the info. Nice to know that it can work.

Steven Blakeslee wrote:

>I ported it to the Embedded Planet ep8260 board with FCC3, ep8248 board
>with FCC1 and FCC2 and ep8280 with FCC2 and FCC3.  I had to make very
>little, if anything, to get it to work.  I did not try 2.6.9.  I am
>currently using 2.6.10-rc3 which I believe after the last merge is now
>2.6.10.  I did practically nothing to get all of these to work. 
>
>  
>
>>-----Original Message-----
>>From: Saso Kavcic [mailto:saso@activetools.si] 
>>Sent: Wednesday, January 12, 2005 9:27 AM
>>To: Steven Blakeslee
>>Cc: linuxppc-embedded@ozlabs.org
>>Subject: Re: Some issues with kernel 2.6 for MPC8260 target
>>
>>Hi Steven,
>>
>>Have you noticed any improvements in 2.6.10. over 2.6.9? We 
>>were porting
>>2.6.9 to a custom mpc8275vr
>>board and we were able to get everything working except 
>>ethernet (fcc enet). We did manage to get a few packets over 
>>it but it was all very slow, unstable and unpredictable and 
>>it seemed that fcc enet driver doesn't work well in 2.6. Were 
>>you able to use fcc under 2.6.9?
>>
>>Best Regards, Saso
>>
>>Steven Blakeslee wrote:
>>
>>    
>>
>>>I would suggest going to the latest 2.6.10 kernel.  I have 
>>>      
>>>
>>it running 
>>    
>>
>>>with several ethernets running on all the 82xx processors.
>>>
>>> 
>>>
>>>      
>>>
>>>>-----Original Message-----
>>>>From: linuxppc-embedded-bounces@ozlabs.org
>>>>[mailto:linuxppc-embedded-bounces@ozlabs.org] On Behalf Of Vijay 
>>>>Padiyar
>>>>Sent: Wednesday, January 12, 2005 5:37 AM
>>>>To: LinuxPPC Support
>>>>Subject: Some issues with kernel 2.6 for MPC8260 target
>>>>
>>>>Hi all
>>>>
>>>>I wish to discuss some strange issues that I faced with 
>>>>        
>>>>
>>respect to the 
>>    
>>
>>>>Linux
>>>>2.6.8 kernel (downloaded from kernel.org). Firstly, I wish to know 
>>>>whether this has been known to work on an MPC8260 PowerPC target.
>>>>
>>>>Secondly, when I tried to compile the Linux kernel with my 
>>>>        
>>>>
>>toolchain 
>>    
>>
>>>>(built with Dan Kegel's crosstool for the PowerPC 603e 
>>>>        
>>>>
>>core, which is 
>>    
>>
>>>>what my processor has), I got some errors which I found to rather 
>>>>queer after investigation. Firstly, let me state the errors that I 
>>>>got:
>>>>
>>>>------------------------------------------------------
>>>>
>>>> LD      init/built-in.o
>>>> LD      .tmp_vmlinux1
>>>>arch/ppc/8260_io/built-in.o(.text+0x103c): In function
>>>>`mii_queue_relink':
>>>>arch/ppc/8260_io/fcc_enet.c:1254: undefined reference to 
>>>>`schedule_task'
>>>>arch/ppc/8260_io/built-in.o(.text+0x1074): In function
>>>>`mii_queue_config':
>>>>arch/ppc/8260_io/fcc_enet.c:1263: undefined reference to 
>>>>`schedule_task'
>>>>
>>>>------------------------------------------------------
>>>>
>>>>On further investigation, I find that 'schedule_task()' is 
>>>>        
>>>>
>>simply not 
>>    
>>
>>>>defined anywhere in the 2.6.8 kernel sources. This is quite wierd! 
>>>>However, it is defined in a file 'context.c'
>>>>(linux-src/kernel) in the 2.4.27 kernel sources, which we 
>>>>        
>>>>
>>were using 
>>    
>>
>>>>earlier. How is it that a function is being called but its 
>>>>        
>>>>
>>definition 
>>    
>>
>>>>has been removed from the sources?
>>>>
>>>>Another such example is with the structure 'tq_struct'. It 
>>>>        
>>>>
>>is referred 
>>    
>>
>>>>to in the file 'fcc_enet.c'
>>>>(linux-src/arch/ppc/8260_io) but it's not defined anywhere! 
>>>>Again, after checking in the 2.4.27 sources, I find that 
>>>>        
>>>>
>>it's defined 
>>    
>>
>>>>in the file 'tqueue.h' (linux-src/include/linux)!
>>>>
>>>>A third thing is that the 2.4.27 kernel source file 'uart.c'
>>>>(linux-src/arch/ppc/cpm2_io) is not present in the corresponding 
>>>>folder in the 2.6.8 source (linux-src/arch/ppc/8260_io). 
>>>>        
>>>>
>>There is one 
>>    
>>
>>>>'uart.c' in the folder '8xx_io', but it doesn't get compiled during 
>>>>the kernel build process. Will my UART work correctly with 
>>>>        
>>>>
>>this build?
>>    
>>
>>>>Can someone please tell me if there's some explanation for 
>>>>        
>>>>
>>this that 
>>    
>>
>>>>I'm unaware of? Which would be the proper forum to report 
>>>>        
>>>>
>>this? Again 
>>    
>>
>>>>I would like to ask: Has the 2.6.8 kernel been tested 
>>>>        
>>>>
>>successfully on 
>>    
>>
>>>>the MPC8260 PowerPC platform?
>>>>
>>>>Lastly, where can I get the latest stable Linux kernel 
>>>>        
>>>>
>>source for the 
>>    
>>
>>>>PowerPC platform?
>>>>
>>>>Regards
>>>>
>>>>Vijay Padiyar
>>>>_______________________________________________
>>>>Linuxppc-embedded mailing list
>>>>Linuxppc-embedded@ozlabs.org
>>>>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>>>
>>>>   
>>>>
>>>>        
>>>>
>>>_______________________________________________
>>>Linuxppc-embedded mailing list
>>>Linuxppc-embedded@ozlabs.org
>>>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>> 
>>>
>>>      
>>>
>>    
>>

  reply	other threads:[~2005-01-12 14:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-12 14:34 Some issues with kernel 2.6 for MPC8260 target Steven Blakeslee
2005-01-12 14:53 ` Saso Kavcic [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-12 13:55 Steven Blakeslee
2005-01-12 14:27 ` Saso Kavcic
2005-01-12 14:38   ` Hans Schillstrom
2005-01-12 10:37 Vijay Padiyar

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=41E539D4.2000502@activetools.si \
    --to=saso@activetools.si \
    --cc=BlakesleeS@embeddedplanet.com \
    --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).