public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Alan Cox <laughing@shared-source.org>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.13-ac4
Date: Mon, 29 Oct 2001 21:03:33 +0100	[thread overview]
Message-ID: <20011029210333.A4828@suse.cz> (raw)
In-Reply-To: <20011028204003.A1640@lightning.swansea.linux.org.uk> <Pine.GSO.3.96.1011029170323.3407F-100000@delta.ds2.pg.gda.pl>
In-Reply-To: <Pine.GSO.3.96.1011029170323.3407F-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Mon, Oct 29, 2001 at 05:07:51PM +0100

On Mon, Oct 29, 2001 at 05:07:51PM +0100, Maciej W. Rozycki wrote:
> On Sun, 28 Oct 2001, Alan Cox wrote:
> 
> > o	Handle chipsets that dont get 8254 latches	(Roberto Biancardi)
> > 	right and trigger the VIA warning in error
> 
>  Hmm, has anyone tried using the "read back" 8254 command for latching,
> instead?  Chances are it's less buggy... 

We can try, but I think that it's more likely to be more buggy, because
it isn't widely used by software. And at least according to the 8254
docs they should be equivalent in what they do.

-- 
Vojtech Pavlik
SuSE Labs

  parent reply	other threads:[~2001-10-29 20:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-28 20:40 Linux 2.4.13-ac4 Alan Cox
2001-10-29  7:47 ` Vojtech Pavlik
2001-10-29 10:56   ` Alan Cox
2001-10-29 16:38     ` Vojtech Pavlik
2001-10-29 17:14       ` Henning P. Schmiedehausen
2001-10-29 17:28         ` Maciej W. Rozycki
2001-10-29 17:48     ` Vojtech Pavlik
2001-10-29 16:07 ` Maciej W. Rozycki
2001-10-29 16:19   ` Alan Cox
2001-10-29 20:03   ` Vojtech Pavlik [this message]
2001-10-30 11:23     ` Maciej W. Rozycki
2001-10-30  4:09 ` George Garvey
2001-10-30  4:24   ` Mike Fedyk
     [not found] <E15yFhL-0003ED-00@the-village.bc.nu>
2001-10-29 17:11 ` Maciej W. Rozycki

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=20011029210333.A4828@suse.cz \
    --to=vojtech@suse.cz \
    --cc=laughing@shared-source.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@ds2.pg.gda.pl \
    /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