[Skyeye-developer] Networking broken in 1.2.1?

Peter Chubb peter at chubb.wattle.id.au
Thu May 17 10:56:50 CST 2007


I'm compiling ucLinux (well, snapgear actually) with the ne2k-skyeye
network adapter enabled.

The kernel seems to see the NIC, but skeyeye says:

	arch: arm
	cpu info: armv3, arm7tdmi, 41007700, fff8ff00, 0 
	mach info: name at91, mach_init addr 0x8056f70
	ethmod num=1, mac addr=0:4:3:2:1:f, hostip=10.0.0.1
>>>>	can't find device module: (null)
	uart_mod:0, desc_in:, desc_out:
	SKYEYE: use arm7100 mmu ops
	Loaded ROM   images/romfs.img
	exec file "images/linux"'s format is elf32-little.

Note the flagged line above.

From reading the source, it seems there should be an undocumented
`type=at91' parameter in the skyeye.conf file.  But when I add that,
skyeye opens /dev/tun OK, but the linux kernel hangs.

Using gdb indicates that the register holding the CPU type is now
invalid and so the kernel loops early in startup.

So,
  * Is networking meant to work in the 1.2.1?
  * If so, how should it be set up?

Relevant line from skyeye.conf

  net: state=on, mac=0:4:3:2:1:f, ethmod=tuntap, hostip=10.0.0.1

OR

  net: state=on, mac=0:4:3:2:1:f, ethmod=tuntap, hostip=10.0.0.1, type=at91


--
Dr Peter Chubb  http://www.gelato.unsw.edu.au  peterc AT gelato.unsw.edu.au
http://www.ertos.nicta.com.au           ERTOS within National ICT Australia



More information about the Skyeye-developer mailing list