booting 2.6 kernel on ML403

booting 2.6 kernel on ML403

[Pradeep Sampath]

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

Hello Ameet/Ming!
   
  I am running linux kernel 2.6 on a ML403. Your posts on the list was extremely helpful and saved a lot of time. But i have ran into a number of issues and need your help. I have described both the scenarios.
   
  Problem 1:
  I followed the steps described in http://www.linux.get2knowmore.com/2006/06/30/quick-guide-linux-26-on-xilinx-virtex-ii-pro-boards-part-i/
  After the kernel boots towards the end i get a failure - unknown-block(0,0)

  [    3.012128] VFS: Cannot open root device "sda2" or unknown-block(0,0)
[    3.088465] Please append a correct "root=" boot option
[    3.150933] Kernel panic - not syncing: VFS: Unable to mount root fs on unkno
wn-block(0,0)
[    3.249891]  <0>Rebooting in 180 seconds..
   
  On the linux partition of my CF card i created the following block device files
  # mknod -m 660 console c 5 1
# mknod -m 660 sda b 254 0
# mknod -m 660 sda1 b 254 1
# mknod -m 660 sda2 b 254 2
# mknod -m 660 sda3 b 254 3
  mkdir tts
# mknod -m 660 0 b 4 64


  But the result was same as above. 
  What should be my default bootloader kernel arguments?
  console=ttyS0,9600 root=/dev/sda2
  or 
  console=ttyS0,9600 root=/dev/xsa2
  or
  console=ttyS0,9600 root=/dev/xsysace/disc0/part2 rw
   
  I am confused. How do we determine the device name of the CF card?
   
  I have 2 partitions on my CF card - Partition1 is DOS FAT16 partition, Partition2 is Linux with ext3 filesystem.

  
 
  Here is the full log of the serial terminal:
Linux/PPC load: console=ttyS0,9600 root=/dev/sda2
Uncompressing Linux...done.
Now booting the kernel
[    0.000000] Linux version 2.6.17.1 (psampath@psampath-test) (gcc version 3.4.
1) #3 Mon Oct 2 14:43:23 PDT 2006
[    0.000000] Xilinx ML403 Reference System (Virtex-4 FX)
[    0.000000] Built 1 zonelists
[    0.000000] Kernel command line: console=ttyS0,9600 root=/dev/sda2
[    0.000000] Xilinx INTC #0 at 0xD1000FC0 mapped to 0xFDFFEFC0
[    0.000000] PID hash table entries: 512 (order: 9, 2048 bytes)
[    0.000166] Console: colour dummy device 80x25
[    0.000650] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.001465] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
[    0.014853] Memory: 62524k available (1736k kernel code, 552k data, 84k init,
 0k highmem)
[    0.104274] Security Framework v1.0.0 initialized
[    0.104471] Mount-cache hash table entries: 512
[    0.110096] NET: Registered protocol family 16
[    0.118276] NET: Registered protocol family 2
[    0.152515] IP route cache hash table entries: 512 (order: -1, 2048 bytes)
[    0.153502] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[    0.153689] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.153787] TCP: Hash tables configured (established 2048 bind 1024)
[    0.153814] TCP reno registered
[    0.161503] VFS: Disk quotas dquot_6.5.1
[    0.161747] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.162380] Initializing Cryptographic API
[    0.162433] io scheduler noop registered
[    0.162534] io scheduler anticipatory registered (default)
[    0.162630] io scheduler deadline registered
[    0.162764] io scheduler cfq registered
[    0.773694] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing
enabled
[    0.782331] serial8250.0: ttyS0 at MMIO 0xa0001003 (irq = 9) is a 16450
[    2.663867] RAMDISK driver initialized: 16 RAM disks of 300000K size 1024 blo
cksize
[    2.758159] i8042.c: No controller found.
[    2.806550] mice: PS/2 mouse device common for all mice
[    2.869032] TCP bic registered
[    2.904787] NET: Registered protocol family 8
[    2.956790] NET: Registered protocol family 20
[    3.012128] VFS: Cannot open root device "sda2" or unknown-block(0,0)
[    3.088465] Please append a correct "root=" boot option
[    3.150933] Kernel panic - not syncing: VFS: Unable to mount root fs on unkno
wn-block(0,0)
[    3.249891]  <0>Rebooting in 180 seconds..
   
  Problem 2:
  - Untar the kernel 2.6.17.1
  - Applied the 5 TEMAC patches
  - Applied Ameet's Sysace patch 
  - copied the xparameters_ml403.h to the arch/ppc/platforms/4xx/xparameters/xparameters_ml403.h generated by EDK
   
  - After including the network driver and sysace driver in "make menuconfig" and generating the zImage and booting the board the kernel hangs.
   
  loaded at:     00400000 0051613C
board data at: 00514124 0051413C
relocated to:  004050E8 00405100
zimage at:     00405881 005137E8
avail ram:     00517000 10000000
  Linux/PPC load: console=ttyS0,9600 root=/dev/sda2
Uncompressing Linux...done.
Now booting the kernel

  I suspect the xparameter addresses are incorrect. Which parameter should i modify in the xparameters_ml403.h?
   
  Kindly send a reply at your earliest. 
  Thanks!
  Pradeep


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

Re: booting 2.6 kernel on ML403

[Ameet Patil]

Hi Pradeep,

Pradeep Sampath wrote:
> Hello Ameet/Ming!
>  
> I am running linux kernel 2.6 on a ML403. Your posts on the list was 
> extremely helpful and saved a lot of time. But i have ran into a 
> number of issues and need your help. I have described both the scenarios.
>  
> Problem 1:
> I followed the steps described in 
> http://www.linux.get2knowmore.com/2006/06/30/quick-guide-linux-26-on-xilinx-virtex-ii-pro-boards-part-i/
> After the kernel boots towards the end i get a failure - 
> unknown-block(0,0)
> [    3.012128] VFS: Cannot open root device "sda2" or unknown-block(0,0)
> [    3.088465] Please append a correct "root=" boot option
> [    3.150933] Kernel panic - not syncing: VFS: Unable to mount root 
> fs on unkno
> wn-block(0,0)
> [    3.249891]  <0>Rebooting in 180 seconds..
>  
> On the linux partition of my CF card i created the following block 
> device files
> # mknod -m 660 console c 5 1
> # mknod -m 660 sda b 254 0
> # mknod -m 660 sda1 b 254 1
> # mknod -m 660 sda2 b 254 2
> # mknod -m 660 sda3 b 254 3
Note: my driver creates device xsa and not sda. so create xsa, xsa1, 
xsa2, etc. in /dev of your CF card instead of sda.
> mkdir tts
> # mknod -m 660 0 b 4 64
please check: this should be a character device. Hence use:
# mknod -m 660 0 c 4 64
>
> But the result was same as above.
> What should be my default bootloader kernel arguments?
> console=ttyS0,9600 root=/dev/sda2
> or
> console=ttyS0,9600 root=/dev/xsa2
yes! root=/dev/xsa2. This is the right root parameter.
> or
> console=ttyS0,9600 root=/dev/xsysace/disc0/part2 rw
>  
> I am confused. How do we determine the device name of the CF card?
>  
> I have 2 partitions on my CF card - Partition1 is DOS FAT16 partition, 
> Partition2 is Linux with ext3 filesystem.
>
>  
> Here is the full log of the serial terminal:
> Linux/PPC load: console=ttyS0,9600 root=/dev/sda2
> Uncompressing Linux...done.
> Now booting the kernel
> [    0.000000] Linux version 2.6.17.1 (psampath@psampath-test 
> <mailto:psampath@psampath-test>) (gcc version 3.4.
> 1) #3 Mon Oct 2 14:43:23 PDT 2006
> [    0.000000] Xilinx ML403 Reference System (Virtex-4 FX)
> [    0.000000] Built 1 zonelists
> [    0.000000] Kernel command line: console=ttyS0,9600 root=/dev/sda2
> [    0.000000] Xilinx INTC #0 at 0xD1000FC0 mapped to 0xFDFFEFC0
> [    0.000000] PID hash table entries: 512 (order: 9, 2048 bytes)
> [    0.000166] Console: colour dummy device 80x25
> [    0.000650] Dentry cache hash table entries: 8192 (order: 3, 32768 
> bytes)
> [    0.001465] Inode-cache hash table entries: 4096 (order: 2, 16384 
> bytes)
> [    0.014853] Memory: 62524k available (1736k kernel code, 552k data, 
> 84k init,
>  0k highmem)
> [    0.104274] Security Framework v1.0.0 initialized
> [    0.104471] Mount-cache hash table entries: 512
> [    0.110096] NET: Registered protocol family 16
> [    0.118276] NET: Registered protocol family 2
> [    0.152515] IP route cache hash table entries: 512 (order: -1, 2048 
> bytes)
> [    0.153502] TCP established hash table entries: 2048 (order: 1, 
> 8192 bytes)
> [    0.153689] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
> [    0.153787] TCP: Hash tables configured (established 2048 bind 1024)
> [    0.153814] TCP reno registered
> [    0.161503] VFS: Disk quotas dquot_6.5.1
> [    0.161747] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> [    0.162380] Initializing Cryptographic API
> [    0.162433] io scheduler noop registered
> [    0.162534] io scheduler anticipatory registered (default)
> [    0.162630] io scheduler deadline registered
> [    0.162764] io scheduler cfq registered
> [    0.773694] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, 
> IRQ sharing
> enabled
> [    0.782331] serial8250.0: ttyS0 at MMIO 0xa0001003 (irq = 9) is a 16450
> [    2.663867] RAMDISK driver initialized: 16 RAM disks of 300000K 
> size 1024 blo
> cksize
> [    2.758159] i8042.c: No controller found.
> [    2.806550] mice: PS/2 mouse device common for all mice
> [    2.869032] TCP bic registered
> [    2.904787] NET: Registered protocol family 8
> [    2.956790] NET: Registered protocol family 20
> [    3.012128] VFS: Cannot open root device "sda2" or unknown-block(0,0)
> [    3.088465] Please append a correct "root=" boot option
> [    3.150933] Kernel panic - not syncing: VFS: Unable to mount root 
> fs on unkno
> wn-block(0,0)
> [    3.249891]  <0>Rebooting in 180 seconds..
>  
> Problem 2:
> - Untar the kernel 2.6.17.1
> - Applied the 5 TEMAC patches
> - Applied Ameet's Sysace patch
which patch did you apply? For TEMAC... apply the following patch: 
http://www.cs.york.ac.uk/rtslab/demos/amos/xupv2pro/patches/linuxppc-2.6.17.1-sysace-1.2-after-TEMAC.patch

cheers,
-Ameet
> - copied the xparameters_ml403.h to the 
> arch/ppc/platforms/4xx/xparameters/xparameters_ml403.h generated by EDK
>  
> - After including the network driver and sysace driver in "make 
> menuconfig" and generating the zImage and booting the board the kernel 
> hangs.
>  
> loaded at:     00400000 0051613C
> board data at: 00514124 0051413C
> relocated to:  004050E8 00405100
> zimage at:     00405881 005137E8
> avail ram:     00517000 10000000
> Linux/PPC load: console=ttyS0,9600 root=/dev/sda2
> Uncompressing Linux...done.
> Now booting the kernel
> I suspect the xparameter addresses are incorrect. Which parameter 
> should i modify in the xparameters_ml403.h?
>  
> Kindly send a reply at your earliest.
> Thanks!
> Pradeep

Re: booting 2.6 kernel on ML403

[Pradeep Sampath]

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

Hi Ameet,
  Thanks for the instant reply. I changed root parameter to xsa as you suggested root=/dev/xsa2. But i still get the same failure.
   
  [    3.093694] TCP bic registered
[    3.129458] NET: Registered protocol family 8
[    3.181412] NET: Registered protocol family 20
[    3.236744] VFS: Cannot open root device "xsa2" or unknown-block(0,0)
[    3.313092] Please append a correct "root=" boot option
[    3.375552] Kernel panic - not syncing: VFS: Unable to mount root fs on unkno
wn-block(0,0)
[    3.474504]  <0>Rebooting in 180 seconds..
  
 
  On the CF i created the following block and character device files
  # mknod -m 660 console c 5 1
# mknod -m 660 xsa b 254 0
# mknod -m 660 xsa1 b 254 1
# mknod -m 660 xsa2 b 254 2
# mknod -m 660 xsa3 b 254 3
mkdir tts
# mknod -m 660 0 c 4 64

> Problem 2:
> - Untar the kernel 2.6.17.1
> - Applied the 5 TEMAC patches
> - Applied Ameet's Sysace patch
which patch did you apply? For TEMAC... apply the following patch: 
http://www.cs.york.ac.uk/rtslab/demos/amos/xupv2pro/patches/linuxppc-2.6.17.1-sysace-1.2-after-TEMAC.patch

  Yes, i have applied *only* after-TEMAC.patch. But looks like it blows away the configuration and results in kernel hang.
   
  Any further suggestions on where i should look at.
   
  regards.
  Pradeep

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

Re: booting 2.6 kernel on ML403

[Ameet Patil]

Pradeep Sampath wrote:
> Hi Ameet,
> Thanks for the instant reply. I changed root parameter to xsa as you 
> suggested root=/dev/xsa2. But i still get the same failure.
>  
> [    3.093694] TCP bic registered
> [    3.129458] NET: Registered protocol family 8
> [    3.181412] NET: Registered protocol family 20
> [    3.236744] VFS: Cannot open root device "xsa2" or unknown-block(0,0)
> [    3.313092] Please append a correct "root=" boot option
> [    3.375552] Kernel panic - not syncing: VFS: Unable to mount root 
> fs on unkno
> wn-block(0,0)
> [    3.474504]  <0>Rebooting in 180 seconds..
>
>  
> On the CF i created the following block and character device files
> # mknod -m 660 console c 5 1
> # mknod -m 660 xsa b 254 0
> # mknod -m 660 xsa1 b 254 1
> # mknod -m 660 xsa2 b 254 2
> # mknod -m 660 xsa3 b 254 3
> mkdir tts
> # mknod -m 660 0 c 4 64
>
> > Problem 2:
> > - Untar the kernel 2.6.17.1
> > - Applied the 5 TEMAC patches
> > - Applied Ameet's Sysace patch
> which patch did you apply? For TEMAC... apply the following patch:
> http://www.cs.york.ac.uk/rtslab/demos/amos/xupv2pro/patches/linuxppc-2.6.17.1-sysace-1.2-after-TEMAC.patch
> Yes, i have applied *only* after-TEMAC.patch. But looks like it blows 
> away the configuration and results in kernel hang.
>  
> Any further suggestions on where i should look at.
>  
> regards.
> Pradeep
Please could send me all the boot messages until the point where it 
stops. This will help me better identify the problem.

Thanks,
-Ameet

Re: booting 2.6 kernel on ML403

[Ming Liu]

Hi,

>   [    3.093694] TCP bic registered
>[    3.129458] NET: Registered protocol family 8
>[    3.181412] NET: Registered protocol family 20
>[    3.236744] VFS: Cannot open root device "xsa2" or unknown-block(0,0)
>[    3.313092] Please append a correct "root=" boot option

It looks that some errors still exist in the parameters you passed to 
"root=". Please double check it, or post it in the maillist for deep 
analysis. 

Regards
Ming

_________________________________________________________________
享用世界上最大的电子邮件系统― MSN Hotmail。  http://www.hotmail.com  

Re: booting 2.6 kernel on ML403

[Ameet Patil]

Ming Liu wrote:
> Hi,
>
>> [ 3.093694] TCP bic registered
>> [ 3.129458] NET: Registered protocol family 8
>> [ 3.181412] NET: Registered protocol family 20
>> [ 3.236744] VFS: Cannot open root device "xsa2" or unknown-block(0,0)
>> [ 3.313092] Please append a correct "root=" boot option
>
> It looks that some errors still exist in the parameters you passed to
> "root=". Please double check it, or post it in the maillist for deep
> analysis.
> Regards
> Ming
>
> _________________________________________________________________
> 享用世界上最大的电子邮件系统― MSN Hotmail。 http://www.hotmail.com
> ------------------------------------------------------------------------
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Hi Ming,
IIRC, you are or were using the TEMAC driver along with my System Ace
driver, isn't it? Does my driver patch ***-after-TEMAC.patch work for
you? I ask this because Pradeep is having some problems using it (see
Problem 2 in his email). Could you please update on this?

Thanks,
-Ameet

Re: booting 2.6 kernel on ML403

[Ming Liu]

Hello Ameet,
I am using that driver very well now. There is only one problem. It seems 
that the driver for TEMAC only support Gigabit Enet, not 10/100/1000M 
adapted. But because I want to use the Gigabit enet, I don't care that. So 
it's OK, at lease for 1Gbit/s.

So I don't think Pradeep's problem is caused by Temac. I still suspect that 
he didn't pass a right parameter to "root=", just like what I posted 
before.

Regards
Ming


>From: Ameet Patil <ammubhai@gmail.com>
>To: Ming Liu <eemingliu@hotmail.com>
>CC: pradeepsampath@yahoo.com,  linuxppc-embedded@ozlabs.org
>Subject: Re: booting 2.6 kernel on ML403
>Date: Wed, 04 Oct 2006 09:35:07 +0100
>
>Ming Liu wrote:
> > Hi,
> >
> >> [ 3.093694] TCP bic registered
> >> [ 3.129458] NET: Registered protocol family 8
> >> [ 3.181412] NET: Registered protocol family 20
> >> [ 3.236744] VFS: Cannot open root device "xsa2" or unknown-block(0,0)
> >> [ 3.313092] Please append a correct "root=" boot option
> >
> > It looks that some errors still exist in the parameters you passed to
> > "root=". Please double check it, or post it in the maillist for deep
> > analysis.
> > Regards
> > Ming
> >
> > _________________________________________________________________
> > 享用世界上最大的电子邮件系统― MSN Hotmail。 http://www.hotmail.com
> > 
------------------------------------------------------------------------
> >
> > _______________________________________________
> > Linuxppc-embedded mailing list
> > Linuxppc-embedded@ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>Hi Ming,
>IIRC, you are or were using the TEMAC driver along with my System Ace
>driver, isn't it? Does my driver patch ***-after-TEMAC.patch work for
>you? I ask this because Pradeep is having some problems using it (see
>Problem 2 in his email). Could you please update on this?
>
>Thanks,
>-Ameet

_________________________________________________________________
与联机的朋友进行交流，请使用 MSN Messenger:  http://messenger.msn.com/cn  

Re: booting 2.6 kernel on ML403

[Pradeep Sampath]

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

Hello Ameet/Ming,
   
  First of all really appreciate your inputs on this... 
  Problem 1 :
  I was using the factory shipped compact flash as is which comes with a DOS FAT16 partition and a linux 83 partition with ext3 filesystem. I tried it on 2 factory shipped CFs and its the same behavior - . When i plug-in the CF card reader to the linux box it always reads it as "sda" and in the linux2.6.17.1/Documentation/devices.txt - sda is the device file for SCSI disk devices. Wonerding how you guys configured the root option as "/dev/xsa".
   
  Now i re-formatted my CF, created a ext2 filesystem using busybox-1.1.0 like the BYU instructions. Created 2 partitions on CF card 1. FAT16 partition & 2. linux partition and then created 1. dos file system using mkdosfs and 2. linux ext2 filesystem using mke2fs.
   
  But the problem still persists and i get "Please append a correct "root=" boot option :"
  :(
   
  Problem 2: After i included the TEMAC driver and sysace drivers, the kernel just hangs. I thought i'll fix problem 1 before i get to problem 2... 
   
  With your help i am getting the confidence that i can make this all work!
  thanks once again.
  -Pradeep



Ming Liu <eemingliu@hotmail.com> wrote:
  Hello Ameet,
I am using that driver very well now. There is only one problem. It seems 
that the driver for TEMAC only support Gigabit Enet, not 10/100/1000M 
adapted. But because I want to use the Gigabit enet, I don't care that. So 
it's OK, at lease for 1Gbit/s.

So I don't think Pradeep's problem is caused by Temac. I still suspect that 
he didn't pass a right parameter to "root=", just like what I posted 
before.

Regards
Ming


>From: Ameet Patil 
>To: Ming Liu 
>CC: pradeepsampath@yahoo.com, linuxppc-embedded@ozlabs.org
>Subject: Re: booting 2.6 kernel on ML403
>Date: Wed, 04 Oct 2006 09:35:07 +0100
>
>Ming Liu wrote:
> > Hi,
> >
> >> [ 3.093694] TCP bic registered
> >> [ 3.129458] NET: Registered protocol family 8
> >> [ 3.181412] NET: Registered protocol family 20
> >> [ 3.236744] VFS: Cannot open root device "xsa2" or unknown-block(0,0)
> >> [ 3.313092] Please append a correct "root=" boot option
> >
> > It looks that some errors still exist in the parameters you passed to
> > "root=". Please double check it, or post it in the maillist for deep
> > analysis.
> > Regards
> > Ming
> >
> > _________________________________________________________________
> > ÏíÓÃÊÀ½çÉÏ×î´óµÄµç×ÓÓʼþϵͳ¡ª MSN Hotmail¡£ http://www.hotmail.com
> > 
------------------------------------------------------------------------
> >
> > _______________________________________________
> > Linuxppc-embedded mailing list
> > Linuxppc-embedded@ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>Hi Ming,
>IIRC, you are or were using the TEMAC driver along with my System Ace
>driver, isn't it? Does my driver patch ***-after-TEMAC.patch work for
>you? I ask this because Pradeep is having some problems using it (see
>Problem 2 in his email). Could you please update on this?
>
>Thanks,
>-Ameet

_________________________________________________________________
ÓëÁª»úµÄÅóÓѽøÐн»Á÷£¬ÇëʹÓà MSN Messenger: http://messenger.msn.com/cn 

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

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

Re: booting 2.6 kernel on ML403

[Pradeep Sampath]

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

Ameet,
   
  loaded at:     00400000 0051513C
board data at: 00513124 0051313C
relocated to:  004050E8 00405100
zimage at:     004057FD 0051230A
avail ram:     00516000 04000000
  Linux/PPC load: console=ttyS0,9600 root=/dev/xsa2
Uncompressing Linux...done.
Now booting the kernel


Please could send me all the boot messages until the point where it 
stops. This will help me better identify the problem.

Thanks,
-Ameet




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

RE: booting 2.6 kernel on ML403

[John Bonesio]

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

Hi Pradeep,

 

If you are using the MontaVista/Xilinx driver for sysace for linux 2.6, the CONFIG_CMDLINE item in .config should have

    root=/dev/xsysace2 rw

in it. From the text below it's not clear what driver you are using. If you are using a different driver, you may be able to search for

    #define MAJOR_NAME

in the source code of the sysace driver. I believe that will indicate which device name you should use in the CONFIG_CMDLINE.

 

As you probably already know, the '2' in '/dev/xsysace2' refers to the partition number it should use - partition 2 in this case.

 

For Problem 2: Do you see any error leds light up on the board? It's possible that the drivers you are using for one or both of those cores is not meant for the version of the cores you are using. The core most likely to be suspect is the TEMAC soft core, as that has changed recently. Even though you are using the hard TEMAC core, there is a soft wrapper around it to connect it up to the bus and what not. This soft wrapper has changed from version 2 to version 3 not too long ago. While the TEMAC driver that MontaVista has (and I believe posted to this mailing list) is for version 2 of the soft TEMAC core.

 

Hope this helps,

 

- John

 

________________________________

From: linuxppc-embedded-bounces+jbonesio=xilinx.com@ozlabs.org [mailto:linuxppc-embedded-bounces+jbonesio=xilinx.com@ozlabs.org] On Behalf Of Pradeep Sampath
Sent: Wednesday, October 04, 2006 10:35 AM
To: Ming Liu; ammubhai@gmail.com
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: booting 2.6 kernel on ML403

 

Hello Ameet/Ming,

 

First of all really appreciate your inputs on this... 

Problem 1 :

I was using the factory shipped compact flash as is which comes with a DOS FAT16 partition and a linux 83 partition with ext3 filesystem. I tried it on 2 factory shipped CFs and its the same behavior - . When i plug-in the CF card reader to the linux box it always reads it as "sda" and in the linux2.6.17.1/Documentation/devices.txt - sda is the device file for SCSI disk devices. Wonerding how you guys configured the root option as "/dev/xsa".

 

Now i re-formatted my CF, created a ext2 filesystem using busybox-1.1.0 like the BYU instructions. Created 2 partitions on CF card 1. FAT16 partition & 2. linux partition and then created 1. dos file system using mkdosfs and 2. linux ext2 filesystem using mke2fs.

 

But the problem still persists and i get "Please append a correct "root=" boot option :"

:(

 

Problem 2: After i included the TEMAC driver and sysace drivers, the kernel just hangs. I thought i'll fix problem 1 before i get to problem 2... 

 

With your help i am getting the confidence that i can make this all work!

thanks once again.

-Pradeep



Ming Liu <eemingliu@hotmail.com> wrote:

	Hello Ameet,
	I am using that driver very well now. There is only one problem. It seems 
	that the driver for TEMAC only support Gigabit Enet, not 10/100/1000M 
	adapted. But because I want to use the Gigabit enet, I don't care that. So 
	it's OK, at lease for 1Gbit/s.
	
	So I don't think Pradeep's problem is caused by Temac. I still suspect that 
	he didn't pass a right parameter to "root=", just like what I posted 
	before.
	
	Regards
	Ming
	
	
	>From: Ameet Patil 
	>To: Ming Liu 
	>CC: pradeepsampath@yahoo.com, linuxppc-embedded@ozlabs.org
	>Subject: Re: booting 2.6 kernel on ML403
	>Date: Wed, 04 Oct 2006 09:35:07 +0100
	>
	>Ming Liu wrote:
	> > Hi,
	> >
	> >> [ 3.093694] TCP bic registered
	> >> [ 3.129458] NET: Registered protocol family 8
	> >> [ 3.181412] NET: Registered protocol family 20
	> >> [ 3.236744] VFS: Cannot open root device "xsa2" or unknown-block(0,0)
	> >> [ 3.313092] Please append a correct "root=" boot option
	> >
	> > It looks that some errors still exist in the parameters you passed to
	> > "root=". Please double check it, or post it in the maillist for deep
	> > analysis.
	> > Regards
	> > Ming
	> >
	> > _________________________________________________________________
	> > ÏíÓÃÊÀ½çÉÏ×î´óµÄµç×ÓÓʼþϵͳ¡ª MSN Hotmail¡£ http://www.hotmail.com
	> > 
	------------------------------------------------------------------------
	> >
	> > _______________________________________________
	> > Linuxppc-embedded mailing list
	> > Linuxppc-embedded@ozlabs.org
	> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
	>Hi Ming,
	>IIRC, you are or were using the TEMAC driver along with my System Ace
	>driver, isn't it? Does my driver patch ***-after-TEMAC.patch work for
	>you? I ask this because Pradeep is having some problems using it (see
	>Problem 2 in his email). Could you please update on this?
	>
	>Thanks,
	>-Ameet
	
	_________________________________________________________________
	ÓëÁª»úµÄÅóÓѽøÐн»Á÷£¬ÇëʹÓà MSN Messenger: http://messenger.msn.com/cn 
	
	_______________________________________________
	Linuxppc-embedded mailing list
	Linuxppc-embedded@ozlabs.org
	https://ozlabs.org/mailman/listinfo/linuxppc-embedded

 


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

RE: booting 2.6 kernel on ML403

[John Bonesio]

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

A quick amendment to my previous email:

The device name you should use in the CONFIG_CMDLINE  "root=..." can be found in the routine call to register_blkdev() in the driver source code. The first parameter to register_blkdev() is the major number of the device. The second parameter is the name of the device, as in /dev/xsda2, or /dev/xsysace2. This second parameter will contain just the 'xsda' or 'xsysace' in it, and it may be a preprocessor constant defined earlier in the file, such as #define MAJOR_NAME "xsda", but it might not be a constant either. It depends on the code.

 

Hopefully this clears things up a bit.

 

- John

 

________________________________

From: linuxppc-embedded-bounces+jbonesio=xilinx.com@ozlabs.org [mailto:linuxppc-embedded-bounces+jbonesio=xilinx.com@ozlabs.org] On Behalf Of Pradeep Sampath
Sent: Wednesday, October 04, 2006 10:35 AM
To: Ming Liu; ammubhai@gmail.com
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: booting 2.6 kernel on ML403

 

Hello Ameet/Ming,

 

First of all really appreciate your inputs on this... 

Problem 1 :

I was using the factory shipped compact flash as is which comes with a DOS FAT16 partition and a linux 83 partition with ext3 filesystem. I tried it on 2 factory shipped CFs and its the same behavior - . When i plug-in the CF card reader to the linux box it always reads it as "sda" and in the linux2.6.17.1/Documentation/devices.txt - sda is the device file for SCSI disk devices. Wonerding how you guys configured the root option as "/dev/xsa".

 

Now i re-formatted my CF, created a ext2 filesystem using busybox-1.1.0 like the BYU instructions. Created 2 partitions on CF card 1. FAT16 partition & 2. linux partition and then created 1. dos file system using mkdosfs and 2. linux ext2 filesystem using mke2fs.

 

But the problem still persists and i get "Please append a correct "root=" boot option :"

:(

 

Problem 2: After i included the TEMAC driver and sysace drivers, the kernel just hangs. I thought i'll fix problem 1 before i get to problem 2... 

 

With your help i am getting the confidence that i can make this all work!

thanks once again.

-Pradeep



Ming Liu <eemingliu@hotmail.com> wrote:

	Hello Ameet,
	I am using that driver very well now. There is only one problem. It seems 
	that the driver for TEMAC only support Gigabit Enet, not 10/100/1000M 
	adapted. But because I want to use the Gigabit enet, I don't care that. So 
	it's OK, at lease for 1Gbit/s.
	
	So I don't think Pradeep's problem is caused by Temac. I still suspect that 
	he didn't pass a right parameter to "root=", just like what I posted 
	before.
	
	Regards
	Ming
	
	
	>From: Ameet Patil 
	>To: Ming Liu 
	>CC: pradeepsampath@yahoo.com, linuxppc-embedded@ozlabs.org
	>Subject: Re: booting 2.6 kernel on ML403
	>Date: Wed, 04 Oct 2006 09:35:07 +0100
	>
	>Ming Liu wrote:
	> > Hi,
	> >
	> >> [ 3.093694] TCP bic registered
	> >> [ 3.129458] NET: Registered protocol family 8
	> >> [ 3.181412] NET: Registered protocol family 20
	> >> [ 3.236744] VFS: Cannot open root device "xsa2" or unknown-block(0,0)
	> >> [ 3.313092] Please append a correct "root=" boot option
	> >
	> > It looks that some errors still exist in the parameters you passed to
	> > "root=". Please double check it, or post it in the maillist for deep
	> > analysis.
	> > Regards
	> > Ming
	> >
	> > _________________________________________________________________
	> > ÏíÓÃÊÀ½çÉÏ×î´óµÄµç×ÓÓʼþϵͳ¡ª MSN Hotmail¡£ http://www.hotmail.com
	> > 
	------------------------------------------------------------------------
	> >
	> > _______________________________________________
	> > Linuxppc-embedded mailing list
	> > Linuxppc-embedded@ozlabs.org
	> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
	>Hi Ming,
	>IIRC, you are or were using the TEMAC driver along with my System Ace
	>driver, isn't it? Does my driver patch ***-after-TEMAC.patch work for
	>you? I ask this because Pradeep is having some problems using it (see
	>Problem 2 in his email). Could you please update on this?
	>
	>Thanks,
	>-Ameet
	
	_________________________________________________________________
	ÓëÁª»úµÄÅóÓѽøÐн»Á÷£¬ÇëʹÓà MSN Messenger: http://messenger.msn.com/cn 
	
	_______________________________________________
	Linuxppc-embedded mailing list
	Linuxppc-embedded@ozlabs.org
	https://ozlabs.org/mailman/listinfo/linuxppc-embedded

 


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

Re: booting 2.6 kernel on ML403

[Ameet Patil]

Hi Pradeep,

Pradeep Sampath wrote:
> Hello Ameet/Ming,
>  
> First of all really appreciate your inputs on this...
> Problem 1 :
> I was using the factory shipped compact flash as is which comes with a 
> DOS FAT16 partition and a linux 83 partition with ext3 filesystem. 
> I tried it on 2 factory shipped CFs and its the same behavior - . When 
> i plug-in the CF card reader to the linux box it always reads it as 
> "sda" and in the linux2.6.17.1/Documentation/devices.txt - sda is the 
> device file for SCSI disk devices. Wonerding how you guys configured 
> the root option as "/dev/xsa".
xsa and sda are nothing but the device name registered by the driver. It 
is not related to whether the device is a SCSI or not. Since I wrote the 
SysAce driver, I decided to name it as xsa (as opposed to the original 
Monta Vista xsysace). Thus, all the partitions on this device will be 
named xsa1 for the first partition, xsa2 for the second and so on.

When you access your CF card in your Linux PC, the driver names the 
device as sda. Thats all... theres no much difference. Hope you got the 
point.

cheers,
-Ameet
>  
> Now i re-formatted my CF, created a ext2 filesystem using 
> busybox-1.1.0 like the BYU instructions. Created 2 partitions on CF 
> card 1. FAT16 partition & 2. linux partition and then created 1. dos 
> file system using mkdosfs and 2. linux ext2 filesystem using mke2fs.
>  
> But the problem still persists and i get "Please append a correct 
> "root=" boot option :"
> :(
>  
> Problem 2: After i included the TEMAC driver and sysace drivers, 
> the kernel just hangs. I thought i'll fix problem 1 before i get to 
> problem 2...
>  
> With your help i am getting the confidence that i can make this all work!
> thanks once again.
> -Pradeep
>
>
>
> */Ming Liu <eemingliu@hotmail.com>/* wrote:
>
>     Hello Ameet,
>     I am using that driver very well now. There is only one problem.
>     It seems
>     that the driver for TEMAC only support Gigabit Enet, not 10/100/1000M
>     adapted. But because I want to use the Gigabit enet, I don't care
>     that. So
>     it's OK, at lease for 1Gbit/s.
>
>     So I don't think Pradeep's problem is caused by Temac. I still
>     suspect that
>     he didn't pass a right parameter to "root=", just like what I posted
>     before.
>
>     Regards
>     Ming
>
>
>     >From: Ameet Patil
>     >To: Ming Liu
>     >CC: pradeepsampath@yahoo.com, linuxppc-embedded@ozlabs.org
>     >Subject: Re: booting 2.6 kernel on ML403
>     >Date: Wed, 04 Oct 2006 09:35:07 +0100
>     >
>     >Ming Liu wrote:
>     > > Hi,
>     > >
>     > >> [ 3.093694] TCP bic registered
>     > >> [ 3.129458] NET: Registered protocol family 8
>     > >> [ 3.181412] NET: Registered protocol family 20
>     > >> [ 3.236744] VFS: Cannot open root device "xsa2" or
>     unknown-block(0,0)
>     > >> [ 3.313092] Please append a correct "root=" boot option
>     > >
>     > > It looks that some errors still exist in the parameters you
>     passed to
>     > > "root=". Please double check it, or post it in the maillist
>     for deep
>     > > analysis.
>     > > Regards
>     > > Ming
>     > >
>     > > _________________________________________________________________
>     > > ÏíÓÃÊÀ½çÉÏ×î´óµÄµç×ÓÓʼþϵͳ¡ª MSN Hotmail¡£
>     http://www.hotmail.com
>     > >
>     ------------------------------------------------------------------------
>     > >
>     > > _______________________________________________
>     > > Linuxppc-embedded mailing list
>     > > Linuxppc-embedded@ozlabs.org
>     > > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>     >Hi Ming,
>     >IIRC, you are or were using the TEMAC driver along with my System Ace
>     >driver, isn't it? Does my driver patch ***-after-TEMAC.patch work for
>     >you? I ask this because Pradeep is having some problems using it (see
>     >Problem 2 in his email). Could you please update on this?
>     >
>     >Thanks,
>     >-Ameet
>
>     _________________________________________________________________
>     ÓëÁª»úµÄÅóÓѽøÐн»Á÷£¬ÇëʹÓà MSN Messenger:
>     http://messenger.msn.com/cn
>
>     _______________________________________________
>     Linuxppc-embedded mailing list
>     Linuxppc-embedded@ozlabs.org
>     https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>

Re: booting 2.6 kernel on ML403

[Ameet Patil]

Pradeep,
   What you have pasted is only part of the messages displayed. I can't 
tell anything from this apart from you 'root=' option. It would be nice 
if you could paste the entire log of the boot messages right from 
'loaded at: xxxxxxx  xxxxxxxx' to 'Kernel Rebooting in 150 seconds'.

-Ameet

Pradeep Sampath wrote:
> Ameet,
>  
> loaded at:     00400000 0051513C
> board data at: 00513124 0051313C
> relocated to:  004050E8 00405100
> zimage at:     004057FD 0051230A
> avail ram:     00516000 04000000
> Linux/PPC load: console=ttyS0,9600 root=/dev/xsa2
> Uncompressing Linux...done.
> Now booting the kernel
>
>
> Please could send me all the boot messages until the point where it
> stops. This will help me better identify the problem.
>
> Thanks,
> -Ameet
>
>

Re: booting 2.6 kernel on ML403

[Pradeep Sampath]

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

Hi Ameet,
   
  As soon as i apply the sysace driver and temac drivers and copy the xparameters_ml300.h (from EDK) to xparameters_ml403.h all i get is this... meaning kernel hangs after displaying "Now booting the kernel".
   
  When i disable sysace and TEMAC drivers, the system goes further till "root=" option and then tries to "Kernel Rebooting in 180 seconds". Yesterday i tried root=/dev/xsysace2 rw and creating block device files in /dev of the CF card. But it ran into the same problem.Is there a sysace driver patch that i can apply without applying the TEMAC driver patch? 
   
  So far i was using the EDK 8.1 SP2 (latest) which has the IP core TEMAC version 3.00. Now i downgraded to EDK 8.1 to get the version 2.00 (please see John Bonesio's post). 
   
  I thought the first step is to get the sysace driver running before applying the TEMAC drivers.

  thanks very much!
  Pradeep

Ameet Patil <ammubhai@gmail.com> wrote:
  Pradeep,
What you have pasted is only part of the messages displayed. I can't 
tell anything from this apart from you 'root=' option. It would be nice 
if you could paste the entire log of the boot messages right from 
'loaded at: xxxxxxx xxxxxxxx' to 'Kernel Rebooting in 150 seconds'.

-Ameet

Pradeep Sampath wrote:
> Ameet,
> 
> loaded at: 00400000 0051513C
> board data at: 00513124 0051313C
> relocated to: 004050E8 00405100
> zimage at: 004057FD 0051230A
> avail ram: 00516000 04000000
> Linux/PPC load: console=ttyS0,9600 root=/dev/xsa2
> Uncompressing Linux...done.
> Now booting the kernel
>
>
> Please could send me all the boot messages until the point where it
> stops. This will help me better identify the problem.
>
> Thanks,
> -Ameet
>
>



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

Re: booting 2.6 kernel on ML403

[Pradeep Sampath]

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

Ameet,
  I was able to get the system to work today with your Sysace driver patch and was able to boot the ML403 with the correct 'root=' option. But the kernel crashes with a "Oops: machine check, sig: 7 [#1]". (I have 'nt applied the TEMAC patches yet)
  It appears that the xparamater definition file genearted using EDK 8.1 does not map correctly with the driver and it looks like i need to further downgrade the EDK to 7.1 and re-generate the BSP. I am attaching the console logs and xparamater file. please ignore my earlier reply.
   
  thanks
  Pradeep
  
Linux/PPC load: console=ttyS0,9600 root=/dev/xsysace2
Uncompressing Linux...done.
Now booting the kernel
[    0.000000] Linux version 2.6.17.1 (psampath@psampath-test) (gcc version 3.4.
1) #3 Thu Oct 5 21:00:20 PDT 2006
[    0.000000] Xilinx ML403 Reference System (Virtex-4 FX)
[    0.000000] Built 1 zonelists
[    0.000000] Kernel command line: console=ttyS0,9600 root=/dev/xsysace2
[    0.000000] Xilinx INTC #0 at 0xD1000FC0 mapped to 0xFDFFEFC0
[    0.000000] PID hash table entries: 2048 (order: 11, 8192 bytes)
[    0.000186] Console: colour dummy device 80x25
[    0.001812] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.004864] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.059900] Memory: 257408k available (1672k kernel code, 584k data, 84k init
, 0k highmem)
[    0.248261] Security Framework v1.0.0 initialized
[    0.248329] SELinux:  Disabled at boot.
[    0.248476] Mount-cache hash table entries: 512
[    0.254185] NET: Registered protocol family 16
[    0.262854] NET: Registered protocol family 2
[    0.316504] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.317597] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.318204] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[    0.318515] TCP: Hash tables configured (established 8192 bind 4096)
[    0.318547] TCP reno registered
[    0.325066] audit: initializing netlink socket (disabled)
[    0.325217] audit(0.324:1): initialized
[    0.326741] VFS: Disk quotas dquot_6.5.1
[    0.326987] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.327684] Initializing Cryptographic API
[    0.327761] io scheduler noop registered
[    0.327854] io scheduler anticipatory registered (default)
[    0.327923] io scheduler deadline registered
[    0.328152] io scheduler cfq registered
[    0.948467] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing
enabled
[    0.957267] serial8250.0: ttyS0 at MMIO 0xa0001003 (irq = 9) is a 16450
[    3.007825] RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 bloc
ksize
[    3.097865] Data machine check in kernel mode.
[    3.150765] Oops: machine check, sig: 7 [#1]
[    3.201802] NIP: C011E58C LR: C011DD00 CTR: C021D308
[    3.261169] REGS: c0224f50 TRAP: 0202   Not tainted  (2.6.17.1)
[    3.331981] MSR: 00029030 <EE,ME,IR,DR>  CR: 95000053  XER: E000007F
[    3.408018] TASK = c0489b40[1] 'swapper' THREAD: c04a0000
[    3.470498] GPR00: 00000001 C04A1D20 C0489B40 D1020000 00000101 000005C7 FDFE
D000 C0484BD8
[    3.570483] GPR08: C05C0C20 C011E014 00000000 C0206AEC 00000000 3BB7E7AD FFFF
FFFF FFFFFFFF
[    3.670467] GPR16: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF 00503FFC FFFF
FFFF FFFFFFFF
[    3.770450] GPR24: FFFFFFFF FFFFFFFF FFFFFFFF 2F646576 00000000 C0220000 0000
0000 C0240C60
[    3.872519] NIP [C011E58C] XSysAce_RegWrite16+0x8/0x1c
[    3.933968] LR [C011DD00] XSysAce_Initialize+0x8c/0xe8
[    3.995416] Call Trace:
[    4.024581] [C04A1D20] [FFFFFFFF] 0xffffffff (unreliable)
[    4.089156] [C04A1D40] [C021D358] xsysace_init+0x50/0x330
[    4.153726] [C04A1F90] [C0002448] init+0xa4/0x27c
[    4.209968] [C04A1FF0] [C000509C] kernel_thread+0x44/0x60
[    4.274536] Instruction dump:
[    4.309949] 5480c63e 98030001 7c0006ac 5480863e 98030002 7c0006ac 5484463e 98
830003
[    4.402641] 7c0006ac 4e800020 5480063e 98030000 <7c0006ac> 5484c23e 98830001
7c0006ac
[    4.498278] Kernel panic - not syncing: Attempted to kill init!
[    4.568293]  <0>Rebooting in 180 seconds..
  

Ameet Patil <ammubhai@gmail.com> wrote:
  Pradeep,
What you have pasted is only part of the messages displayed. I can't 
tell anything from this apart from you 'root=' option. It would be nice 
if you could paste the entire log of the boot messages right from 
'loaded at: xxxxxxx xxxxxxxx' to 'Kernel Rebooting in 150 seconds'.

-Ameet

Pradeep Sampath wrote:
> Ameet,
> 
> loaded at: 00400000 0051513C
> board data at: 00513124 0051313C
> relocated to: 004050E8 00405100
> zimage at: 004057FD 0051230A
> avail ram: 00516000 04000000
> Linux/PPC load: console=ttyS0,9600 root=/dev/xsa2
> Uncompressing Linux...done.
> Now booting the kernel
>
>
> Please could send me all the boot messages until the point where it
> stops. This will help me better identify the problem.
>
> Thanks,
> -Ameet
>
>



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

Re: booting 2.6 kernel on ML403

[Ming Liu]

Hi Pradeep,

>   As soon as i apply the sysace driver and temac drivers and copy the 
xparameters_ml300.h (from EDK) to xparameters_ml403.h all i get is this... 
meaning kernel hangs after displaying "Now booting the kernel".

I have experienced this before. But in my condition, I applied both ACE and 
Temac patches. Ameet said it's a problem of the kernel and the kernel just 
lost the configuration information. So just "make proper" and reconfigure 
your kernel and recompile it. In my condition, it helps. I don't know if it 
is useful to solve your problem. Just try it.

>
>   When i disable sysace and TEMAC drivers, the system goes further till 
"root=" option and then tries to "Kernel Rebooting in 180 seconds". 
Yesterday i tried root=/dev/xsysace2 rw and creating block device files in 
/dev of the CF card. But it ran into the same problem.Is there a sysace 
driver patch that i can apply without applying the TEMAC driver patch?

Don't try root=/dev/xsysace2. In Ameet's driver, he defined as xsa2. So 
just keep consistent with the source code. 

Also, in his website, there are patches which are used without Temac. They 
are not labeled with -after-temac. 

>   So far i was using the EDK 8.1 SP2 (latest) which has the IP core TEMAC 
version 3.00. Now i downgraded to EDK 8.1 to get the version 2.00 (please 
see John Bonesio's post).

I am using TEMAC 1.00. The 3.00 version is totally different with 1.00. So 
I don't know if it is one reason about your problem. 



Regards
Ming

_________________________________________________________________
享用世界上最大的电子邮件系统― MSN Hotmail。  http://www.hotmail.com  

Re: booting 2.6 kernel on ML403

[David H. Lynch Jr.]

Ming Liu wrote:
> Hello Ameet,
> I am using that driver very well now. There is only one problem. It
> seems that the driver for TEMAC only support Gigabit Enet, not
> 10/100/1000M adapted. But because I want to use the Gigabit enet, I
> don't care that. So it's OK, at lease for 1Gbit/s.
It is fairly easy to mangle the TEMAC driver for any fixed rate you
want. I added a spd value to the device data, set it to whatever I want
in the initcode, and
changed the SetSpeed () call to use the device data value instead of a
constant.
That was a 2 min kludge. At some point it needs real autonegotiation -
which should not be too hard.


-- 
Dave Lynch 					  	    DLA Systems
Software Development:  				         Embedded Linux
717.627.3770 	       dhlii@dlasys.net 	  http://www.dlasys.net
fax: 1.253.369.9244 			           Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.

"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein