From: Andrew de Quincey <adq_dvb@lidskialf.net>
To: Marcelo Penna Guerra <eu@marcelopenna.org>,
Jeff Garzik <jgarzik@pobox.com>
Cc: Rahul Karnik <rahul@genebrew.com>,
lkml <linux-kernel@vger.kernel.org>, Laurens <masterpe@xs4all.nl>
Subject: Re: [PATCH] nvidia nforce 1.0-261 nvnet for kernel 2.5
Date: Mon, 28 Jul 2003 09:53:34 +0100 [thread overview]
Message-ID: <200307280953.34933.adq_dvb@lidskialf.net> (raw)
In-Reply-To: <200307272011.51631.eu@marcelopenna.org>
On Monday 28 July 2003 00:11, Marcelo Penna Guerra wrote:
> No luck here, Jeff ... if the hardware is really based on AMD8111 as it
> appears to be (i2c and ide are similar), they surelly changed more
> registers. It'll take some time to RE it.
Hmm, If they had licensed it, I don't see why they would have changed the
registers that much; they didn't for the other hardware they licensed.
Judging by the size of nvnetlib.o, there isn't really that much to it (which
is nice from an RE point of view)
next prev parent reply other threads:[~2003-07-28 8:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-26 22:09 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
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 [this message]
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=200307280953.34933.adq_dvb@lidskialf.net \
--to=adq_dvb@lidskialf.net \
--cc=eu@marcelopenna.org \
--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
all inboxes | Powered by JetHome®