From: Vincent Bernat <bernat@free.fr>
To: Tom Eastep <teastep@shorewall.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VIA Northbridge Workaround in 2.4.18 Causing Video Problems
Date: Tue, 26 Feb 2002 21:42:23 +0100 [thread overview]
Message-ID: <m3u1s4asb4.fsf@neo.loria> (raw)
In-Reply-To: <20020226195730.BD7691B93C@mail.shorewall.net>
In-Reply-To: <20020226195730.BD7691B93C@mail.shorewall.net> (Tom Eastep's message of "Tue, 26 Feb 2002 11:57:30 -0800")
OoO Pendant le journal télévisé du mardi 26 février 2002, vers 20:57,
Tom Eastep <teastep@shorewall.net> disait:
> I'm currently getting around the problem with the following hack:
You may use the "setpci" command instead to fix this in "userland".
next prev parent reply other threads:[~2002-02-26 20:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 19:57 VIA Northbridge Workaround in 2.4.18 Causing Video Problems Tom Eastep
2002-02-26 20:42 ` Vincent Bernat [this message]
2002-02-26 21:19 ` Mark Cooke
2002-02-27 15:12 ` Tom Eastep
2002-02-27 16:29 ` Vincent Bernat
2002-02-27 2:27 ` Steven Walter
2002-02-27 22:33 ` James Cassidy
2002-02-27 22:45 ` Tom Eastep
-- strict thread matches above, loose matches on Subject: below --
2002-02-27 18:01 Alex Davis
2002-02-27 21:26 ` Mark Cooke
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=m3u1s4asb4.fsf@neo.loria \
--to=bernat@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=teastep@shorewall.net \
/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