netdev - Re: KS8695: problem with ethernet driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1258037066.1931.8.camel@myhost>
Date:	Thu, 12 Nov 2009 22:44:26 +0800
From:	"Figo.zhang" <figo1802@...il.com>
To:	zeal <zealcook@...il.com>
Cc:	netdev@...r.kernel.org, Vincent Sanders <vince@...tec.co.uk>,
	Ben Dooks <ben@...tec.co.uk>
Subject: Re: KS8695: problem with ethernet driver

On Mon, 2009-11-16 at 17:23 +0800, zeal wrote:
> Hi,
> 
> I've two questions on the ks8695.
> 
> 1. We knew recently Figo.zhang has added NAPI support for ks8695 net driver.
> Thanks him. But on our ks8695 board it couldn't work well as i thought.
> We used net-next-git kernel.
> 
> IP layer cannot receive any frame from lan or wan port(s).
> 
> After dig into the driver, I found the rx interrupt occurs,
> but the corresponding status bit is not set. So it won't go into napi
> schedule block.

would like to add debug information at ks8695_rx_irq() to see if the
interrupt function can work and the status value? in line 443, add :
printk(KERN_EMERG "rx status = 0x%x\n", status);

> 
>         if (status & mask_bit) {
>                 if (napi_schedule_prep(&ksp->napi)) {
>                         /*disable rx interrupt*/
>                         status &= ~mask_bit;
>                         writel(status , KS8695_IRQ_VA + KS8695_INTEN);
>                         __napi_schedule(&ksp->napi);
>                 }
>         }
> 
> Does anybody tested this NAPI driver succeeded before? If so it maybe
> hardware issue.
> 
> 2. It's a extend topic about ks8695. Does the cpu port can tell the
> source port (i.e. lan port ID)
> when it receive a frame from LAN ports? I think a smart switch need
> know where the frame come from
> and then decide where it to go. And many switch-chip in this way.
> The manual can't help me at all as i've done according to it.
> 
> Any hint is appreciated.
> 


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html