Hello!
On Fri, Jan 7, 2011 at 10:24 AM, Russell King - ARM Linux <[email protected]> wrote: > On Fri, Jan 07, 2011 at 07:56:34PM +0530, Santosh Shilimkar wrote: >> > -----Original Message----- >> > From: Russell King - ARM Linux [mailto:[email protected]] >> > Sent: Friday, January 07, 2011 7:55 PM >> > To: Santosh Shilimkar >> > Cc: [email protected]; Tony Lindgren >> > Subject: Re: 4430SDP boot failure >> > >> > On Fri, Jan 07, 2011 at 06:39:06PM +0530, Santosh Shilimkar wrote: >> > > Have sent you latest bootloaders and full bootlog on my ES1.0 >> > > OMAP4430SDP. 2.6.37 just boots fine for me. >> > > >> > > Low level debug as you reported seems to be broken though. >> > >> > Many thanks, the new mlo and uboot gets dhcp/tftp working nicely on >> > the board - which should ease the debugging problem as it no longer >> > requires anything but the reset button pressed to test a new kernel. >> >> Glad to hear that. > > Right, next couple of problems. > > udev isn't creating the ttyO* nodes for whatever reason on my fs - does > anyone know what device major/minor numbers these end up with? It seems > they're dynamically assigned. This is what I have: mazi-gentoo ~ # ls -l /dev/ttyO? crw-rw---- 1 root uucp 247, 0 Dec 31 1999 /dev/ttyO0 crw-rw---- 1 root uucp 247, 1 Dec 31 1999 /dev/ttyO1 crw------- 1 ddiaz tty 247, 2 Jan 7 11:02 /dev/ttyO2 crw-rw---- 1 root uucp 247, 3 Dec 31 1999 /dev/ttyO3 Greetings! Daniel Díaz [email protected] > There's also something fishy going on with networking (if I configure > PNP IP, I get an IP: > > ks8851 spi1.0: message enable is 0 > ks8851 spi1.0: eth0: revision 0, MAC 1a:6a:b1:02:1d:90, IRQ 194 > IP-Config: Got DHCP answer from 0.0.0.0, my address is 192.168.0.144 > IP-Config: Complete: > device=eth0, addr=192.168.0.144, mask=255.255.255.0, gw=192.168.0.1, > host=192.168.0.144, domain=arm.linux.org.uk, nis-domain=(none), > bootserver=0.0.0.0, rootserver=0.0.0.0, rootpath= > > but the board doesn't respond to that IP address. Meanwhile the DHCP > server shows: > > DHCPDISCOVER from 1a:6a:b1:02:1d:90 via eth0 > > in its log, and the ethernet address appears to be random for each boot. > Obviously, as I can't log into the board via any means, it's nigh on > impossible to work out what's actually going on. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
