public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: "Dale Farnsworth" <dale@farnsworth•org>
To: Sven Luther <sven.luther@wanadoo•fr>
Cc: Nicolas DET <det.nicolas@free•fr>, linuxppc-embedded@ozlabs•org
Subject: Re: [PATCH][PPC32] mv64x60 updates
Date: Sun, 6 Mar 2005 03:29:24 -0700	[thread overview]
Message-ID: <20050306102924.GA32386@xyzzy> (raw)
In-Reply-To: <20050306070248.GA6673@pegasos>

On Sun, Mar 06, 2005 at 08:02:48AM +0100, Sven Luther wrote:
> On Sat, Mar 05, 2005 at 03:51:28PM -0700, Dale Farnsworth wrote:
> > By all means, try it.  Several people are using it without complaints, but
> > I'd appreciate your feedback.  There isn't anything dangerous in there.
> > Gigabit works for me.  I'm not sure what Kconfig parts would be needed
> > specifically for gigabit support.
> 
> I added just a PPC_CHRP dependency on the MV64XXX_ETH entry, and i was able to
> build it, and even insmod it, but the module doesn't do a thing, and not even
> a single line shows up in dmesg. I guess i am either missing a part of the
> patch or there is something wrong with the probe code.
> 
> I have gotten the diff against : 
> 
> include/linux/mv643xx.h drivers/net/mv643xx_eth.[ch] and drivers/net/Kconfig,
> adding :
> 
>  config MV643XX_ETH
>         tristate "MV-643XX Ethernet support"
> -       depends on MOMENCO_OCELOT_C || MOMENCO_JAGUAR_ATX
> +       depends on MOMENCO_OCELOT_C || MOMENCO_JAGUAR_ATX || MV64360 || PPC_CHRP
>         help
>           This driver supports the gigabit Ethernet on the Marvell MV643XX
> -         chipset which is used in the Momenco Ocelot C and Jaguar ATX.
> +         chipset which is used in the Momenco Ocelot C and Jaguar ATX and
> +         Pegasos II, amongst other PPC and MIPS boards.
> 
> I have no idea where your MV64360 comes from, it seems to be not existent in
> any other Kconfig, ... oh well, maybe i am wrong, i wasn't able to do a
> recursive bk co, so maybe i missed a bunch of Kconfig files with my grep/find
> combo :/ Will have to look more.

MV64360 is in arch/ppc/Kconfig, and is currently defined for KATANA and
CHESTNUT.  If I understand correctly, it should be defined for any
board using the MV64360.  I don't think we want the PPC_CHRP dependency.

> Anyway, how do you probe for the chip ? On the pegasos we used to map on the
> marvell pci id :
> 
>   0000:00:00.0 Host bridge: Marvell Technology Group Ltd. MV64360/64361/64362
>   System Controller (rev 03)
> 
> too bad Marvell didn't do the logical thing and made the ethernet port appear
> as separated devices on a third internal pci bus.

The mv643xx_eth probe is dependent on having the appropriate
platform device entry.  See eth0_device and mv64x60_add_pds() in
arch/ppc/syslib/mv643x60.c .

-Dale

  reply	other threads:[~2005-03-06 10:29 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-26  0:14 [PATCH][PPC32] mv64x60 updates Mark A. Greer
2005-02-24  8:25 ` Sven Luther
2005-02-24 15:28   ` Mark A. Greer
2005-02-24 16:04     ` Sven Luther
2005-02-24 17:08       ` Mark A. Greer
2005-02-24 17:05         ` Sven Luther
2005-02-24 17:24       ` Dale Farnsworth
2005-03-05 19:27         ` Sven Luther
2005-03-05 20:32           ` Sven Luther
2005-03-05 22:51             ` Dale Farnsworth
2005-03-06  7:02               ` Sven Luther
2005-03-06 10:29                 ` Dale Farnsworth [this message]
2005-03-06 19:10                   ` Sven Luther
2005-03-06 19:48                     ` Nicolas DET
2005-03-07  1:00                     ` [PATCH][PPC32] " Dale Farnsworth
2005-03-07  6:52                       ` Sven Luther
2005-03-07 10:56                         ` Nicolas DET
2005-03-07 10:58                         ` Nicolas DET
2005-03-07 12:30                           ` James Chapman
2005-03-07 12:46                             ` Sven Luther
2005-03-07 12:57                             ` Nicolas DET
2005-03-07 13:20                               ` Sven Luther
2005-03-07 17:24                                 ` Mark A. Greer
2005-03-07 13:23                               ` Linwoes
2005-03-07 22:54                               ` mv643xx_eth SA_SHIRQ support patch Dale Farnsworth
2005-03-08  6:49                                 ` Sven Luther
2005-03-08  7:27                                   ` Benjamin Herrenschmidt
2005-03-08 12:20                                     ` Dale Farnsworth
2005-03-08 12:15                                       ` Sven Luther
2005-03-08 12:42                                         ` Sven Luther
     [not found]                                           ` <20050308164310.GA9891@pegasos>
2005-03-08 22:31                                             ` Benjamin Herrenschmidt
2005-03-09  7:17                                               ` Sven Luther
2005-03-09  7:39                                                 ` Benjamin Herrenschmidt
2005-03-09  7:40                                                   ` Sven Luther
2005-03-08 18:19                                         ` Mark A. Greer
2005-03-08 18:19                                           ` Sven Luther
2005-03-08 19:28                                     ` [PATCH] final mv643xx_eth pegasos patch set Sven Luther
2005-03-08 19:52                                       ` Sven Luther
2005-03-08 23:18                                         ` Nicolas DET
2005-03-09  2:03                               ` mv64x60 updates Benjamin Herrenschmidt
2005-03-09  2:01                             ` Benjamin Herrenschmidt
2005-03-09 15:59                               ` Chris Friesen
2005-03-05 21:58           ` [PATCH][PPC32] " Dale Farnsworth

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=20050306102924.GA32386@xyzzy \
    --to=dale@farnsworth$(echo .)org \
    --cc=det.nicolas@free$(echo .)fr \
    --cc=linuxppc-embedded@ozlabs$(echo .)org \
    --cc=sven.luther@wanadoo$(echo .)fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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