From: Steve Poulsen <spoulsen@css-design.us>
To: Budhee Jamaich <budheej@gmail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: OMAP2430: networking errors
Date: Thu, 17 May 2007 13:20:28 -0500 [thread overview]
Message-ID: <464C9CEC.5070806@css-design.us> (raw)
In-Reply-To: <57314e840705170935u4791b98cs29504cf57523cbc2@mail.gmail.com>
Budhee,
If you are building your own kernel, I would just open smc91x.c and
change the
#define SMC_DEBUG 0
to
#define SMC_DEBUG 4
I think that is enough to cause it to print out the packets it
receives. When you boot, you should get some printing when it tries to
DHCP. It is kind of a one-shot process since you can't mount a
filesystem via NFS until the network is working.
I cannot help you with that specific board. Richard may help more
there. I can just give you some ideas as to what I have done to track
these down...the hard way.
Also, I would suggest checking your cables and hubs. One thing I have
noticed is that if you mess around changing MAC addresses, the ARP
tables of various devices will end up wrong. Unplugging and plugging
your cable into a new slot of your hub (or power cycling your hub),
should correct that. The reason I bring this up is that you said U-boot
sometimes will not reply to the ARP packet. This is more disturbing
than a simple case where a driver always fails.
Finally, I noticed my smc91x.h is patched for OMAP. Around line 191 it
looks like this:
#define SMC_IRQ_FLAGS (( \
machine_is_omap_h2() \
|| machine_is_omap_h3() \
|| machine_is_omap_h4() \
|| (machine_is_omap_innovator() && !cpu_is_omap1510()) \
) ? SA_TRIGGER_FALLING : SA_TRIGGER_RISING)
The patch added the machine_is_omap_h4() line. This was the only thing
patched in the driver that seemed relevant. To be honest, I am not sure
what is considered omap_h4 (h2, h3 show up in menuconfig and have a
descriptions as to what they cover), but I would make sure yours looks
like above, to confirm the proper patching.
I am using 2.6.16 patched for omap:
http://ftp.kernel.org/pub/linux/kernel/v2.6/
http://www.muru.com/linux/omap/patches/old/
Good luck!
Steve
Budhee Jamaich wrote:
> On 5/17/07, Woodruff, Richard <r-woodruff2@ti.com> wrote:
>>
>> > it's a development board. how do I know which ethernet chip is on it ?
>>
>> Ok. Is it the TI-SDP2430 development board?
> yes. ethernet chip: SMC 91C96.
>
>>
>> If so, what images are you using? Did you build them or use pre-built
>> ones.
> I built it. used TI's BSP. it is based on kernel 2.6.10.
> I am now cloning myself a copy of Tony's git tree.
> I will try to build it, maybe that will help.
>
> otherwise I guess I would have no choice but debug smc91x.c ?
>
>>
>> Why do you report your MAC address as yy:yy:yy:yy:yy:yy. Is that what
>> the driver said or did you remove it for some reason.
> oh, you will have to forgive me here.
> I usually remove personal data from posts to public mailing lists.
>
>>
>> If it works sometimes and not other times that is odd. Are you using
>> the same MAC address on multiple board or something?
> hmm, the MAC address is the real hardware one. AFAIK it is
> unique for that specific board.
>
> Thank You !
> Budhee
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
>
next prev parent reply other threads:[~2007-05-17 18:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 13:39 OMAP2430: networking errors Budhee Jamaich
2007-05-17 13:44 ` Woodruff, Richard
2007-05-17 14:01 ` Budhee Jamaich
2007-05-17 16:10 ` Woodruff, Richard
2007-05-17 16:35 ` Budhee Jamaich
2007-05-17 18:20 ` Steve Poulsen [this message]
2007-05-17 19:55 ` Budhee Jamaich
2007-05-17 20:03 ` Syed Mohammed, Khasim
2007-05-17 21:28 ` Steve Poulsen
2007-05-18 7:05 ` Budhee Jamaich
2007-05-17 14:48 ` Budhee Jamaich
2007-05-17 14:10 ` Steve Poulsen
2007-05-17 14:28 ` Budhee Jamaich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=464C9CEC.5070806@css-design.us \
--to=spoulsen@css-design.us \
--cc=budheej@gmail.com \
--cc=linux-omap-open-source@linux.omap.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.