ts-7000
[Top] [All Lists]

Re: [ts-7000] 2.6 kernel defconfig for TS-7400 board

To:
Subject: Re: [ts-7000] 2.6 kernel defconfig for TS-7400 board
From: Paulo Marques <>
Date: Tue, 02 Jan 2007 13:19:50 +0000
Petr Stetiar wrote:
> Paulo Marques < <pmarques%40grupopie.com>> 
> [2006-11-28 18:34:39]:
> 
>  > Hi all,
>  >
>  > I was thinking about trying to build a 2.6 kernel for a TS-7400 board.
>  >
>  > Does anyone have a nice default .config file for a recent 2.6 kernel? I
>  > was going to try to compile a 2.6.19-rc6 kernel.
>  >
>  > I searched the archives, but found no one trying to do the same :(
> 
> There is ep93xx_defconfig, which you could use as base. You would also need
> some of ep93xx_* patches available from Lennert's svn repository at
> http://svn.wantstofly.org/kernel/ <http://svn.wantstofly.org/kernel/>
> 
> My actual .config(ts7250_ynezz_config.gz) for ts7250 and my diff against
> 2.6.19-rc6-git10(ts7250_ynezz_kernel.patch.gz) is available at
> http://ynezz.ibawizard.net/ts7250/ <http://ynezz.ibawizard.net/ts7250/>
> 
> I don't have 7400, so I don't know if it will work for you, but at least
> you've some starting point.

Thanks for the info and sorry for the late reply.

In the last couple of days I've been trying to make this work, but I 
think I need some more help from the group.

I was able to compile and boot a 2.4 kernel that I downloaded from the 
TS site. This was just to make sure that I understood the mechanics of 
the bootload system and that I had a working cross-toolchain by using it 
with a "known good" kernel.

I downloaded a 2.6.19 vanilla kernel and patched with 
ts7250_ynezz_kernel.patch.gz. The only cross-toolchain (from the 
available toolchains at the TS site) that was able to build this kernel 
was the gcc-4.0.1 toolchain. This wasn't the one I used for the 2.4 
kernel and this one wasn't able to build the 2.4 kernel :P

I tried booting it nevertheless, but the kernel just hung after 
"Decompressing linux......... done" (or something like that).

So, I took a look at the code (maybe I should have started there ;). The 
code has some "machine_is_ts72xx()" conditionals that probably won't 
work with a ts7400 board and other subtleties that need to be handled 
properly.

Now, I want to ask the collective wisdom of the group to help me chart a 
roadmap. There are basically 2 ways (that I can see) to go from here:

  - pretend that the ts7400 board is just a small variation of the 
ts72xx and do minor tweaks to the code to let it handle _both_ boards.

  - create a new machine type for the ts7400 board and do all the 
infrastructure that is already in place for the ts72xx. Modify the 
driver code to be 7xxx (instead of 72xx) and modify the low-level 72xx 
code to register "generic" 7xxx drivers instead of 72xx.

This really depends on how different the 2 boards are. The first option 
seems to be the easiest way, since the ts72xx support is already in 
place and working. I guess most of the hardware that is provided by the 
EP3902 itself is common between the 2 boards.

Please note that if I just wanted a kernel to work for me, I could just 
tweak the current ts72xx version until I got something workable, but I 
really wanted to do this The Right Way(tm) eventually leading to the 
board being supported by official vanilla kernels.

Thanks in advance for any advice,

-- 
Paulo Marques - www.grupopie.com

"The face of a child can say it all, especially the
mouth part of the face."


 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/ts-7000/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/ts-7000/join
    (Yahoo! ID required)

<*> To change settings via email:
     
    

<*> To unsubscribe from this group, send an email to:
    

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 

<Prev in Thread] Current Thread [Next in Thread>
Admin

Disclaimer: Neither Andrew Taylor nor the University of NSW School of Computer and Engineering take any responsibility for the contents of this archive. It is purely a compilation of material sent by many people to the birding-aus mailing list. It has not been checked for accuracy nor its content verified in any way. If you wish to get material removed from the archive or have other queries about the archive e-mail Andrew Taylor at this address: andrewt@cse.unsw.EDU.AU