All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jengelh@computergmbh.de
Cc: toms@wonderland.us.com, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: drivers/net/sunhme.c patch
Date: Mon, 29 Oct 2007 15:10:25 -0700 (PDT)	[thread overview]
Message-ID: <20071029.151025.87460351.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0710291606260.26070@fbirervta.pbzchgretzou.qr>

From: Jan Engelhardt <jengelh@computergmbh.de>
Date: Mon, 29 Oct 2007 16:11:18 +0100 (CET)

> 
> On Oct 29 2007 08:54, Tom Southerland wrote:
> >
> > This patch provides a unique mac address for all interfaces
> > for the Sun QFE card (non-sparc).  It takes the base mac from
> > the first interface and increments the mac address for the
> > other interfaces.
> 
> Where is the difference to a SPARC QFE? PCI is PCI after all, is not it?

This is exactly why I wish this patch had been posted to
netdev@vger.kernel.org, now we have a dialogue going and even if I add
netdev to the CC: now, you can't follow it completely as a netdev
subscriber without going to the lkml archives.

To answer the question, yes it is just a normal PCI device, they put 4
HME chips behind a PCI bridge.  However, the OpenFirmware on the cards
usually creates device node properties for these PCI devices for the
local ethernet addresses.  That's what he's trying to duplicate here.

  reply	other threads:[~2007-10-29 22:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-29 14:54 drivers/net/sunhme.c patch Tom Southerland
2007-10-29 15:11 ` Jan Engelhardt
2007-10-29 22:10   ` David Miller [this message]
2007-10-29 22:12     ` Jan Engelhardt
2007-10-29 22:41       ` David Miller
2007-10-29 22:07 ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2007-10-30  1:53 Tom Southerland
2007-10-30  3:12 ` David Miller

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=20071029.151025.87460351.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=toms@wonderland.us.com \
    /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.