From: "Roman Mashak" <mrv@corecom.co.kr>
To: "Raj Palani" <Rajesh_Palani@pmc-sierra.com>,
"Ralf Baechle" <ralf@linux-mips.org>
Cc: <linux-mips@linux-mips.org>
Subject: Re: Ethernet bridging on 2.6.12-rc3 (PMC-sierra patched)
Date: Wed, 21 Jun 2006 09:34:52 +0900 [thread overview]
Message-ID: <001401c694ca$8cb8e530$9d0ba8c0@mrv> (raw)
In-Reply-To: 478F19F21671F04298A2116393EEC3D531D2D4@sjc1exm08.pmc_nt.nt.pmc-sierra.bc.ca
Hello, Raj!
You wrote to "Ralf Baechle" <ralf@linux-mips.org>; "Roman Mashak"
<mrv@corecom.co.kr> on Tue, 20 Jun 2006 09:15:56 -0700:
RP> I would request that you take a look at our current GE driver
RP> (msp85x0_ge.c) for the Sequoia platform and send us your feedback.
RP> This is currently available on our ftp site ftp.pmc-sierra.com under
RP> /pub/linux/2.6.12/linux-2.6.12-rc3_L002.tar.gz. The driver has been
RP> completely re-written and we welcome any feedback on the same.
As you could notice in my first message in this thread I reffered to
2.6.12-rc3_L002 from PMC ftp site. And Ethernet bridging behavior I
described is occurring at that particular kernel.
RP> The patches that have been generated for fixes that were made after
RP> this release are available under
RP> /pub/linux/2.6.12/patches-2.6.12-rc3_L002.
With best regards, Roman Mashak. E-mail: mrv@corecom.co.kr
WARNING: multiple messages have this Message-ID (diff)
From: "Roman Mashak" <mrv@corecom.co.kr>
To: Raj Palani <Rajesh_Palani@pmc-sierra.com>,
Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: Ethernet bridging on 2.6.12-rc3 (PMC-sierra patched)
Date: Wed, 21 Jun 2006 09:34:52 +0900 [thread overview]
Message-ID: <001401c694ca$8cb8e530$9d0ba8c0@mrv> (raw)
Message-ID: <20060621003452.4Mk8RasL8T4602b8eWJ_AVxE3T3Bux-6D-Sjj8rXlzA@z> (raw)
In-Reply-To: 478F19F21671F04298A2116393EEC3D531D2D4@sjc1exm08.pmc_nt.nt.pmc-sierra.bc.ca
Hello, Raj!
You wrote to "Ralf Baechle" <ralf@linux-mips.org>; "Roman Mashak"
<mrv@corecom.co.kr> on Tue, 20 Jun 2006 09:15:56 -0700:
RP> I would request that you take a look at our current GE driver
RP> (msp85x0_ge.c) for the Sequoia platform and send us your feedback.
RP> This is currently available on our ftp site ftp.pmc-sierra.com under
RP> /pub/linux/2.6.12/linux-2.6.12-rc3_L002.tar.gz. The driver has been
RP> completely re-written and we welcome any feedback on the same.
As you could notice in my first message in this thread I reffered to
2.6.12-rc3_L002 from PMC ftp site. And Ethernet bridging behavior I
described is occurring at that particular kernel.
RP> The patches that have been generated for fixes that were made after
RP> this release are available under
RP> /pub/linux/2.6.12/patches-2.6.12-rc3_L002.
With best regards, Roman Mashak. E-mail: mrv@corecom.co.kr
next prev parent reply other threads:[~2006-06-21 0:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 16:15 Ethernet bridging on 2.6.12-rc3 (PMC-sierra patched) Raj Palani
2006-06-20 16:45 ` Ralf Baechle
2006-06-21 0:34 ` Roman Mashak [this message]
2006-06-21 0:34 ` Roman Mashak
-- strict thread matches above, loose matches on Subject: below --
2006-06-21 7:01 Raj Palani
2006-06-20 17:07 Raj Palani
2006-06-19 9:02 Roman Mashak
2006-06-19 9:02 ` Roman Mashak
2006-06-19 13:51 ` Ralf Baechle
2006-06-20 0:36 ` Roman Mashak
2006-06-20 0:36 ` Roman Mashak
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='001401c694ca$8cb8e530$9d0ba8c0@mrv' \
--to=mrv@corecom.co.kr \
--cc=Rajesh_Palani@pmc-sierra.com \
--cc=linux-mips@linux-mips.org \
--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