public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: neroden@fastmail.fm (Nathanael Nerode)
Cc: linux-kernel@vger.kernel.org
Subject: Re: TG3(Tigoon) & Kernel 2.4.27
Date: Mon, 30 Aug 2004 15:31:24 -0700	[thread overview]
Message-ID: <20040830153124.03aa84be.davem@redhat.com> (raw)
In-Reply-To: <20040830221638.GA3596@fastmail.fm>

On Mon, 30 Aug 2004 18:16:38 -0400
neroden@fastmail.fm (Nathanael Nerode) wrote:

> >I guess if I ran objdump --disassemble on the image and
> >used the output of that in the tg3 driver and "compiled
> >that source" they'd be happy.  And this makes the situation
> >even more ludicrious.
> 
> Before you blithely made this claim, you should have actually tried running
> objdump --disassemble on the image.

I was speaking abstractly.  It is well definted which parts of
the hex arrays are the data, bss, and text sections.  It doesn't
take a rocket scientist to reconstruct things.

  parent reply	other threads:[~2004-08-30 22:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-30 22:16 TG3(Tigoon) & Kernel 2.4.27 Nathanael Nerode
2004-08-30 22:23 ` Jeff Garzik
2004-08-30 22:31 ` David S. Miller [this message]
2004-08-30 22:32 ` Andreas Schwab
  -- strict thread matches above, loose matches on Subject: below --
2004-08-24 15:13 Laurent CARON
2004-08-24 16:25 ` Randy.Dunlap
2004-08-24 18:34   ` David S. Miller
2004-08-25  1:37     ` Joshua Kwan
2004-08-25  3:17       ` Randy.Dunlap
2004-08-25  4:02         ` Joshua Kwan
2004-08-25  4:45     ` Willy Tarreau
2004-08-25  6:36       ` David S. Miller
2004-08-25  7:47         ` Joshua Kwan
2004-08-25  8:34           ` Oliver Neukum
2004-08-25 19:03             ` David S. Miller
2004-08-31  1:14         ` Ryan Cumming
2004-08-31  1:33           ` David S. Miller
2004-08-31  5:05           ` Willy Tarreau
2004-08-25  7:40     ` Laurent CARON

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=20040830153124.03aa84be.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neroden@fastmail.fm \
    /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