9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: kokamoto@hera.eonet.ne.jp
To: 9fans@9fans.net
Subject: [9fans] etheryuk.c for Marvell 88E8036?
Date: Tue, 31 May 2016 17:53:58 +0900	[thread overview]
Message-ID: <30cfbeff491b3ab16b3789329af30116@hera.eonet.ne.jp> (raw)

I'm now facing a serious problem to use 88E8036 rev 16 chip (11ab/4351)
on Sony VAIO F-type notebook.

Adding the device ID above, I can read data without problem.
However, to transmit a larger (say 2500 bytes) data, it hangs up.

For an example, cat <larger than say, 2500byte file) >test in the
network booted terminal without local disk.

The chips shows pci data as:
11ab/4351 5 0:fc200004 16384 2:00005001 256

The chip c->type is Yukfe, and c->rev=1, c->feat=0.

When I look the linux source, it says the chip is SKY2_HW_RSS_BROKEN,
and intentionally gave up to solve this in the kernel layer...

Have you any suggestion, eric?

Kenji




                 reply	other threads:[~2016-05-31  8:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=30cfbeff491b3ab16b3789329af30116@hera.eonet.ne.jp \
    --to=kokamoto@hera.eonet.ne.jp \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).