linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Penna Guerra <eu@marcelopenna.org>
To: Rahul Karnik <rahul@genebrew.com>,
	Andrew de Quincey <adq_dvb@lidskialf.net>
Cc: lkml <linux-kernel@vger.kernel.org>, Laurens <masterpe@xs4all.nl>,
	Jeff Garzik <jgarzik@pobox.com>
Subject: Re: [PATCH] nvidia nforce 1.0-261 nvnet for kernel 2.5
Date: Sat, 26 Jul 2003 23:26:49 -0300	[thread overview]
Message-ID: <200307262326.49638.eu@marcelopenna.org> (raw)
In-Reply-To: <3F235B73.70701@genebrew.com>

Hi,

>From nvnet.c:

   /* 
     * Mac address is loaded at boot time into h/w reg, but it's loaded 
backwards
     * we get the address, save it, and reverse it. The saved value is loaded
     * back into address at close time.
     */

PRINTK(DEBUG_INIT, "nvnet_init - get mac address\n");
    priv->hwapi->pfnGetNodeAddress(priv->hwapi->pADCX, priv-
>original_mac_addr);

But I don't think the only thing missing is the MAC address. You could try to 
manually set it in the source itself and see if anything works.

Marcelo Penna Guerra

On Sunday 27 July 2003 01:56, Rahul Karnik wrote:
> Andrew de Quincey wrote:
> > Small patch for the latest nvidia nforce 1.0-261 nvnet drivers with
> > kernel 2.5.
>
> Further nvnet musings (cc:ing Jeff as net driver maintainer and
> knowledgeable person).
>
> As I reported here a few days earlier, I tried using the AMD8111 driver
> with my NForce2 ethernet a few days ago, with the result that no MAC
> address was being assigned to the card. I suspect that the MAC address
> is being assigned by the Nvidia driver. Does that make sense?
>
> If so, then using the option in the BIOS to manually set the MAC address
> might make the AMD driver work. Unfortunately, I have no idea what I
> should set it to without stomping on the MAC address for other devices.
>
> Any ideas? I hate to rely on a binary only module for something as
> "simple" as a 10/100 ethernet card.
>
> Thanks,
> Rahul
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2003-07-27  5:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-26 22:09 [PATCH] nvidia nforce 1.0-261 nvnet for kernel 2.5 Andrew de Quincey
2003-07-27  4:50 ` Rahul Karnik
2003-07-27  4:56 ` Rahul Karnik
2003-07-27  2:26   ` Marcelo Penna Guerra [this message]
2003-07-27  5:59     ` Rahul Karnik
2003-07-27  9:16       ` Laurens
2003-07-27 10:37         ` Rahul Karnik
2003-07-27 11:19       ` Andrew de Quincey
2003-07-27 11:22       ` Andrew de Quincey
2003-07-27 11:48         ` Rahul Karnik
2003-07-27 11:46           ` Andrew de Quincey
2003-07-27 12:02           ` Andrew de Quincey
2003-07-27 13:36             ` Rahul Karnik
2003-07-27 14:01             ` Rahul Karnik
2003-07-27 14:14               ` Andrew de Quincey
2003-07-27 14:44                 ` Rahul Karnik
2003-07-27 15:46                   ` Alan Cox
2003-07-27 16:28                     ` Rahul Karnik
2003-07-27 19:51                       ` Laurens
2003-07-28  1:09             ` Jeff Garzik
2003-07-27 23:11               ` Marcelo Penna Guerra
2003-07-28  8:53                 ` Andrew de Quincey
2003-07-27  5:53   ` Brian Jackson
2003-07-29  8:44 Eric

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=200307262326.49638.eu@marcelopenna.org \
    --to=eu@marcelopenna.org \
    --cc=adq_dvb@lidskialf.net \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masterpe@xs4all.nl \
    --cc=rahul@genebrew.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 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).