From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: ralf@linux-mips.org, jeff@garzik.org,
michal.k.k.piotrowski@gmail.com, pg@cs.stanford.edu,
ahennessy@mvista.com, netdev@vger.kernel.org,
linux-mips@linux-mips.org
Subject: Re: possible bug in net/tc35815.c in linux-2.6.19
Date: Mon, 26 Feb 2007 23:07:47 +0300 [thread overview]
Message-ID: <45E33E13.7010007@ru.mvista.com> (raw)
In-Reply-To: <20070226.200554.125898248.nemoto@toshiba-tops.co.jp>
Hello.
Atsushi Nemoto wrote:
> I know both MontaVista and CELF have new driver for the chip. If
> anybody in MontaVista did not complain I can send CELF's one available
> at http://tree.celinuxforum.org/pubwiki/moin.cgi/PatchArchive. (it
Yeah, tc35815_1.c in our looks like the one in the CELF archive (what I
didn't get is why they decided to keep both drivers around?)
> needs some changes for recent kernel, for example pt_regs removal, but
> it would be easy).
> Sergei?
I think everybody would be just thankful. :-)
There's quite a lot of other TX4938 patches that need pushing into
Linux/MIPS -- unfortunetely, this hasn't been done by MV... :-<
> ---
> Atsushi Nemoto
BTW, does RBTX4938 boot the recent kernels for you? If so, what .config
are you using -- I'm afraid something's up with rbhma4500_defconfig?
WBR, Sergei
next prev parent reply other threads:[~2007-02-26 20:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45DFEC09.3020801@cs.stanford.edu>
2007-02-24 12:37 ` possible bug in net/tc35815.c in linux-2.6.19 Michal Piotrowski
2007-02-24 22:04 ` Jeff Garzik
2007-02-26 10:26 ` Ralf Baechle
2007-02-26 11:05 ` Atsushi Nemoto
2007-02-26 20:07 ` Sergei Shtylyov [this message]
2007-02-27 14:55 ` Atsushi Nemoto
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=45E33E13.7010007@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=ahennessy@mvista.com \
--cc=anemo@mba.ocn.ne.jp \
--cc=jeff@garzik.org \
--cc=linux-mips@linux-mips.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pg@cs.stanford.edu \
--cc=ralf@linux-mips.org \
/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).