From: Alex Deucher <alexdeucher@gmail.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@oss.sgi.com, linux-kernel@vger.kernel.org, jgarzik@pobox.com
Subject: Re: Marvell 88W8310 and 88E8050 PCI Express support
Date: Thu, 24 Feb 2005 18:08:50 -0500 [thread overview]
Message-ID: <a728f9f905022415084f82f769@mail.gmail.com> (raw)
In-Reply-To: <20050224143509.4fe2a6a8@dxpl.pdx.osdl.net>
On Thu, 24 Feb 2005 14:35:09 -0800, Stephen Hemminger
<shemminger@osdl.org> wrote:
> On Thu, 24 Feb 2005 16:46:34 -0500
> Alex Deucher <alexdeucher@gmail.com> wrote:
>
> > I've noticed most of the new AMD64 chipsets now include integrated
> > marvell GigE and wifi chips onboard. I haven't been able to find much
> > on the status of linux support for these chips. Apparently the PCIE
> > GigE chip only works with sk98lin
>
> You need to use the version from SysKonnect. If you look at the source
> for that, you will see why I started on the skge driver.
>
>
> > http://www.ussg.iu.edu/hypermail/linux/kernel/0502.1/0010.html
> > Does anyone know if support for the chip is being added to skge?
>
> As soon as I get the hardware (on order), or a donation of a new system.
> Then I will report the interface from sk98lin.
>
> > The
> > 88W8310 doesn't seem to be supported at all, at least not that I can
> > see. Does anyone know the status of the 88W8310? Are there any
> > experimental drivers? Is Marvell friendly to opensource? Are the
> > databooks available?
>
> If you find databook for Yukon 2 chipset let me know. I found the original
> Yukon and Genesis manuals, but nothing newer.
>
Thanks for the info. If I get a board with a yukon 2, I'd be happy to
help. I don't suppose you know anything about the wifi chip
(88W8310)? Jeff?
Thanks,
Alex
prev parent reply other threads:[~2005-02-24 23:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 21:46 Marvell 88W8310 and 88E8050 PCI Express support Alex Deucher
2005-02-24 22:35 ` Stephen Hemminger
2005-02-24 23:08 ` Alex Deucher [this message]
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=a728f9f905022415084f82f769@mail.gmail.com \
--to=alexdeucher@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.