Adding a new architecture to the kernel

[Bozhidar Batsov]

Yes, I'm sorry for the confusion - I needed to add a new board, not a
new arch - arch is PXA25x of course. I have a dev board here similar to
lubbock, and the latest kernel for it by its manifacturer was 2.6.7. I
need at least 2.6.10 for my current project, but this board has an ASIX
AX88796 controller which does not have build in kernel support, so I
have to use the driver from the 2.6.7 kernel. Anyway are you certain
that this are all the step required to add a new board because a
followed them exactly but with the new board the kernel won't boot:
ARMboot 1.2.0 by Voipac <www.voipac.com> (Nov 24 2004 - 14:29:51)

ARMboot code: a1000000 -> a1019034
CPU: Intel XScale-PXA255 (ARM 5TE) revision A0
Clock: Mem=99.53MHz (*27), Run=199.07MHz (*2), Turbo=199.07MHz
(*1.0,inactive)
DRAM Configuration:
Bank #0: a0000000 16 MB
Bank #1: a4000000 0 KB
Bank #2: a8000000 0 KB
Bank #3: ac000000 0 KB
Flash: 16 MB
Hit any key to stop autoboot:  0

Starting Linux kernel image at 0x40000
         Architecture type: 89
         Command line: mem=16M root=/dev/mtdblock2 rootfstype=jffs2
console=ttyS0,115200

Uncompressing
Linux......................................................... done,
booting the kernel.

And that is all. The two boards are very simillar, I had to change but a
few things in lubbock.c to create the new voipac.c. Can someone take a
look at their source files (there quite small) and tell me if has some
idea what could be wrong. This 2.6.11 kernel works file with lubbock.c...
Nicolas Pitre wrote:

>On Wed, 23 Nov 2005, Bozhidar Batsov wrote:
>
>  
>
>>ARMboot code: a1000000 -> a1019034
>>CPU: Intel XScale-PXA255 (ARM 5TE) revision A0
>>Clock: Mem=99.53MHz (*27), Run=199.07MHz (*2), Turbo=199.07MHz
>>(*1.0,inactive)
>>DRAM Configuration:
>>Bank #0: a0000000 16 MB
>>Bank #1: a4000000 0 KB
>>Bank #2: a8000000 0 KB
>>Bank #3: ac000000 0 KB
>>Flash: 16 MB
>>Hit any key to stop autoboot:  0
>>
>>Starting Linux kernel image at 0x40000
>>        Architecture type: 89
>>        Command line: mem=16M root=/dev/mtdblock2 rootfstype=jffs2
>>console=ttyS0,115200
>>
>>Uncompressing
>>Linux......................................................... done,
>>booting the kernel.
>>    
>>
>
>Try enabling CONFIG_DEBUG_KERNEL and CONFIG_DEBUG_LL.
>
>
>Nicolas
>  
>
Somehow I got the kernel booting, but now I have some problems with
lubbock-flash.c and since I noticed you have written it I'd like to ask
for your help.
Lubbock configured to boot from ROM (bank 0)
Probing Lubbock Boot ROM at physical address 0x00000000 (16-bit bankwidth)
Lubbock Boot ROM: Found 1 x16 devices at 0x0 in 16-bit bank
Intel/Sharp Extended Query Table at 0x0031
Using buffer write method
cfi_cmdset_0001: Erase suspend on write enabled
RedBoot partition parsing not available
cmdlinepart partition parsing not available
Probing Lubbock Application Flash at physical address 0x04000000 (16-bit
bankwidth)
Using static partitions on Lubbock Boot ROM
Creating 3 MTD partitions on "Lubbock Boot ROM":
0x00000000-0x00040000 : "Bootloader"
0x00040000-0x00140000 : "Kernel"
0x00140000-0x01000000 : "Filesystem"
Lubbock Application Flash is absent. Skipping
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
NET: Registered protocol family 1
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(31,2)

I haven't changed the mappings at all. With lubbock board it works OK,
but with mine - kernel panic. Root fs is of course at the correct
address. I have edited appropriately(or at least I think so) all the
Kconfig and Makefiles. And the difference between lubbock.c and voipac.c
- as you can see prost my previous letter is pretty much minimal. I'm
out of ideas and would really appreciate any help that I can get.

TIA,
Bozhidar

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: config
Url: http://lists.infradead.org/pipermail/linux-mtd/attachments/20051123/727de907/attachment.pl 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lubbock.c
Type: text/x-csrc
Size: 5908 bytes
Desc: not available
Url : http://lists.infradead.org/pipermail/linux-mtd/attachments/20051123/727de907/attachment.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: voipac.c
Type: text/x-csrc
Size: 7581 bytes
Desc: not available
Url : http://lists.infradead.org/pipermail/linux-mtd/attachments/20051123/727de907/attachment-0001.bin