linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
To: Jesse Allen <the3dfxdude@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.1-mm1
Date: Mon, 12 Jan 2004 19:37:52 +0100	[thread overview]
Message-ID: <4002E980.3030401@gmx.de> (raw)
In-Reply-To: <20040112175443.GA870@tesore.local>

Jesse Allen wrote:
> I didn't think these patches would make it into a kernel tree, except experimental ones.  For one, I don't think we know what's wrong with the nforce2's apic timer.  And second, I don't need the disconnect patch, because I have verfied a BIOS update has fixed C1 disconnect completely for my board. (works on and off)

Isn't is possbile to find out which registers were altered with the new 
bios? Ie. read out registers with out bios and then with new bios adn 
then compare? Then we (well someone smarter than me :)) could make a 
real fix for the nforce2-apic issue.

Prakash

  reply	other threads:[~2004-01-12 18:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-12 17:54 2.6.1-mm1 Jesse Allen
2004-01-12 18:37 ` Prakash K. Cheemplavam [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-09  9:40 2.6.1-mm1 Andrew Morton
2004-01-09 14:47 ` 2.6.1-mm1 Christoph Hellwig
2004-01-09 14:53 ` 2.6.1-mm1 Wojciech 'Sas' Cieciwa
2004-01-09 14:21   ` 2.6.1-mm1 Bartlomiej Zolnierkiewicz
2004-01-09 16:30 ` 2.6.1-mm1 Prakash K. Cheemplavam
2004-01-09 21:20   ` 2.6.1-mm1 Andrew Morton
2004-01-09 21:24     ` 2.6.1-mm1 Prakash K. Cheemplavam

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=4002E980.3030401@gmx.de \
    --to=prakashkc@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=the3dfxdude@hotmail.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).