public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: sungem driver patch testing..
Date: Sun, 11 Sep 2005 13:03:32 +0100	[thread overview]
Message-ID: <20050911120332.GA7627@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0509102008540.4912@g5.osdl.org>

On Sat, Sep 10, 2005 at 08:11:22PM -0700, Linus Torvalds wrote:
> 
> I've been grepping around for things that do their own PCI ROM mapping and 
> do it badly, and one thing that matches that description is the sungem 
> ethernet driver on PC's.
> 
> If anybody has such a beast, can you please try this patch and report 
> whether it works for you? 
> 
> 		Linus
> 
> ---
> diff --git a/drivers/net/sungem.c b/drivers/net/sungem.c
> --- a/drivers/net/sungem.c
> +++ b/drivers/net/sungem.c
> @@ -2817,7 +2817,7 @@ static int gem_ioctl(struct net_device *
>  
>  #if (!defined(__sparc__) && !defined(CONFIG_PPC_PMAC))
>  /* Fetch MAC address from vital product data of PCI ROM. */
> -static void find_eth_addr_in_vpd(void __iomem *rom_base, int len, unsigned char *dev_addr)
> +static int find_eth_addr_in_vpd(void __iomem *rom_base, int len, unsigned char *dev_addr)

While we're at it the cpp conditioal looks bogus.  We definitly needs this
when plugging a SUN card into a mac.  I'd suggest compiling this
unconditionally and fall back to it when whatever firmware method to get
the mac address fails.


  parent reply	other threads:[~2005-09-11 12:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-11  3:11 sungem driver patch testing Linus Torvalds
2005-09-11  7:04 ` Willy Tarreau
2005-09-11 19:03   ` David S. Miller
2005-09-11 12:03 ` Christoph Hellwig [this message]
2005-09-11 17:07   ` Linus Torvalds
2005-09-11 18:24     ` David S. Miller
2005-09-11 18:52       ` Linus Torvalds
2005-09-11 19:03         ` David S. Miller
2005-09-11 18:48     ` Pascal Schmidt

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=20050911120332.GA7627@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox