mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jeongdo Son" <sohn9086@gmail.com>
To: "Will Newton" <will.newton@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Linux-SH <linux-sh@vger.kernel.org>
Subject: Re: [BUG REPORT] smc911x: Auto negotiation NOT supported
Date: Mon, 10 Mar 2008 10:45:36 +0900	[thread overview]
Message-ID: <59fd4ce80803091845g2979c23ayfa1e53ce221ef846@mail.gmail.com> (raw)
In-Reply-To: <87a5b0800803070354x391ff718u3af9664804526da1@mail.gmail.com>

Hi, Will

Thanks for your reply.

On Fri, Mar 7, 2008 at 8:54 PM, Will Newton <will.newton@gmail.com> wrote:
>  Are you getting interrupts from the chip? Sounds like it could be you
>  have missed and interrupt somewhere - check where your interrupt
>  polarities and where you are acking/clearing them down.
>

I think there's no problem with getting interrupts.
Because the driver works well while eth0 is configured for DHCP mode.
Only static IP allocation occurs the problem.

Here is the /proc/interrupts.
(The interrupt for eth0 is recognized as IRQ 9)
~ $ cat /proc/interrupts
           CPU0
  3:         46  sh7780-irl3210-level     rtc-62423a period
  6:         67  sh7780-irl3210-level     r8a66597_hcd:usb1
  9:         96  sh7780-irl3210-level     eth0
 12:          0  sh7780-irl3210-level     fb0
 13:          0  sh7780-irl3210-level     fb0
 28:      11366          sh7780-level     periodic timer
 38:          0          sh7780-level     DMAC Address Error
 40:          0          sh7780-level     SCI Receive Error
 41:         62          sh7780-level     SCI Receive Data Full
 42:          0          sh7780-level     SCI Break
 43:       1901          sh7780-level     SCI Transmit Data Empty
 68:          1          sh7780-level     yenta
Err:          0

Regards,
Jeongdo Son

      reply	other threads:[~2008-03-10  1:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-07  6:00 Jeongdo Son
2008-03-07 11:54 ` Will Newton
2008-03-10  1:45   ` Jeongdo Son [this message]

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=59fd4ce80803091845g2979c23ayfa1e53ce221ef846@mail.gmail.com \
    --to=sohn9086@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=will.newton@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®