* KS8695: problem with ethernet driver
@ 2009-11-16 9:23 zeal
2009-11-12 14:44 ` Figo.zhang
0 siblings, 1 reply; 2+ messages in thread
From: zeal @ 2009-11-16 9:23 UTC (permalink / raw)
To: netdev; +Cc: Figo.zhang, Vincent Sanders, Ben Dooks
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.
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.
--
Thanks & Regards
zeal
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: KS8695: problem with ethernet driver
2009-11-16 9:23 KS8695: problem with ethernet driver zeal
@ 2009-11-12 14:44 ` Figo.zhang
0 siblings, 0 replies; 2+ messages in thread
From: Figo.zhang @ 2009-11-12 14:44 UTC (permalink / raw)
To: zeal; +Cc: netdev, Vincent Sanders, Ben Dooks
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.
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-11-16 13:32 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-11-16 9:23 KS8695: problem with ethernet driver zeal
2009-11-12 14:44 ` Figo.zhang
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).