From: Sven Luther <sl@bplan-gmbh.de>
To: Dale Farnsworth <dale@farnsworth.org>
Cc: linuxppc-dev@ozlabs.org, Sven Luther <sl@bplan-gmbh.de>
Subject: Re: [PATCH 2.6.14-rc5 1/1] : mv643xx_eth_pcidev - implements hotplug for the marvell gige functionality by probing the northbridge pci id.
Date: Tue, 25 Oct 2005 22:20:04 +0200 [thread overview]
Message-ID: <20051025202004.GA25348@localhost.localdomain> (raw)
In-Reply-To: <20051025182434.GA13982@xyzzy.farnsworth.org>
On Tue, Oct 25, 2005 at 11:24:34AM -0700, Dale Farnsworth wrote:
> On Tue, Oct 25, 2005 at 07:51:59AM +0000, Sven Luther wrote:
> > Add Marvell gigabit ethernet hotplug through the northbridge pci id support
> > for the Pegasos machines.
> >
> > Signed-off-by: Nicolas DET <det.nicolas@free.fr>
> > Signed-off-by: Sven Luther <sl@bplan-gmbh.de>
> >
> > ---
> > This patch is not optimal, as the proper way to handling this is to bring full
> > hotplug support to the platform drivers, but this would be much more invasive
> > and far reaching a project. This approach matches the marvell discovery
> > northbridge pci id to load the driver for the builtin gigabit ethernet
> > function, and is similar of what is done already using the discover module
> > loading technique. With more and more distributions moving to using hotplug
> > only to probe for modules to load, this patch becomes necessary.
> >
> > Friendly,
> >
> > Sven Luther
>
> > diff -Naur a/drivers/net/mv643xx_eth.c b/drivers/net/mv643xx_eth.c
> > --- a/drivers/net/mv643xx_eth.c 2005-10-25 09:20:50.604386000 +0200
> > +++ b/drivers/net/mv643xx_eth.c 2005-10-25 09:20:14.596386000 +0200
> > @@ -36,6 +36,10 @@
> > #include <linux/udp.h>
> > #include <linux/etherdevice.h>
> >
> > +#ifdef CONFIG_PPC_MULTIPLATFORM
> > +#include <linux/pci.h>
> > +#endif
> > +
> > #include <linux/bitops.h>
> > #include <linux/delay.h>
> > #include <linux/ethtool.h>
> > @@ -1640,6 +1644,16 @@
> > " and Dale Farnsworth");
> > MODULE_DESCRIPTION("Ethernet driver for Marvell MV643XX");
> >
> > +#ifdef CONFIG_PPC_MULTIPLATFORM
> > +static struct pci_device_id pci_marvell_mv64360[] = {
> > + { PCI_DEVICE(PCI_VENDOR_ID_MARVELL, PCI_DEVICE_ID_MARVELL_MV64360) },
> > + { }
> > +};
> > +
> > +MODULE_DEVICE_TABLE(pci, pci_marvell_mv64360);
> > +#endif
> > +
> > +
> > /*
> > * The second part is the low level driver of the gigE ethernet ports.
> > */
>
> I don't think this is really dependent on PPC_MULTIPLATFORM,
> and the driver also supports 64460.
Ah, well, the PPC_MULTIPLATFORM was in order to not break potentially other
plateforms i know nothing about, and yes, the below patch would be perfect
too.
Friendly,
Sven Luther
next prev parent reply other threads:[~2005-10-25 20:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 7:51 [PATCH 2.6.14-rc5 1/1] : mv643xx_eth_pcidev - implements hotplug for the marvell gige functionality by probing the northbridge pci id Sven Luther
2005-10-25 18:24 ` Dale Farnsworth
2005-10-25 20:20 ` Sven Luther [this message]
2005-10-27 19:26 ` Christoph Hellwig
2005-10-27 19:57 ` Sven Luther
2005-10-27 21:14 ` Nicolas DET
2005-10-29 4:56 ` Paul Mackerras
2005-10-29 5:37 ` Sven Luther
2005-10-31 19:05 ` Mark A. Greer
2005-10-31 21:21 ` Sven Luther
2005-11-01 9:25 ` Paul Mackerras
2005-11-01 16:57 ` Mark A. Greer
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=20051025202004.GA25348@localhost.localdomain \
--to=sl@bplan-gmbh.de \
--cc=dale@farnsworth.org \
--cc=linuxppc-dev@ozlabs.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).