public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@aitel.hist.no>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>, linux-kernel@vger.kernel.org
Subject: Re: The buggy APIC of the Abit BP6
Date: Fri, 21 Jun 2002 15:02:35 +0200	[thread overview]
Message-ID: <3D1323EB.11BF8DB2@aitel.hist.no> (raw)
In-Reply-To: Pine.GSO.3.96.1020620144211.18164B-100000@delta.ds2.pg.gda.pl

"Maciej W. Rozycki" wrote:
> 
> On Thu, 20 Jun 2002, Helge Hafting wrote:
> 
> > Yes, the hardware is at fault.  I don't have money for
> > other hardware though, so working around it seems a good idea.
> 
>  What's the problem with using a privately patched kernel then?  I do that
> all the time for various stuff.
Nothing wrong with that.  I may be wrong, but I have the impression
that the bp6 was quite popular for a while.  It was the only
cheap smp board for a while (excluding those who re-soldered
their cpu's to enable SMP in other boards) 
and it took some time before people realized that a good
PSU and extra cooling wasn't enough.
> 
> > We could simplify the IDE driver a lot by dropping support for
> > all the broken controllers too. Or tell
> > people to not use DMA on them.
> 
>  It depends on how intrusive and reliable the workarounds are.  If merely
> slowing down or using PIO is sufficient, then they may be OK to include.
> 
My impression is that the IDE driver contains workarounds for many
broken chipsets.  Using DMA is usually
default off but can be turned on for those that know it
won't hurt in their case.

I think a similiar approach is ok with the BP6 fix - put it in
because there are a bunch of these boards, default it OFF because
many more don't need it.

Helge Hafting

  reply	other threads:[~2002-06-21 13:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-12 22:33 The buggy APIC of the Abit BP6 Robbert Kouprie
2002-06-13  9:05 ` Helge Hafting
2002-06-13 13:30   ` Robbert Kouprie
2002-06-14 10:54     ` Helge Hafting
2002-06-18 15:30       ` Robbert Kouprie
2002-06-18 15:17         ` Zwane Mwaikambo
2002-06-19 12:47         ` Maciej W. Rozycki
2002-06-19 13:23           ` Robbert Kouprie
2002-06-19 14:03             ` Keith Owens
2002-06-19 14:35               ` Maciej W. Rozycki
2002-06-20  1:50               ` Robbert Kouprie
2002-06-19 14:22             ` Maciej W. Rozycki
2002-06-20 12:21           ` Helge Hafting
2002-06-20 13:10             ` Maciej W. Rozycki
2002-06-21 13:02               ` Helge Hafting [this message]
2002-06-20 22:29             ` Kevin Krieser
2002-06-14 15:07 ` Raphael Manfredi
  -- strict thread matches above, loose matches on Subject: below --
2002-06-14 16:49 Robbert Kouprie
2002-06-14 18:41 ` Raphael Manfredi
2002-06-18  7:33   ` Helge Hafting
2002-06-18  9:53 Robbert Kouprie

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=3D1323EB.11BF8DB2@aitel.hist.no \
    --to=helgehaf@aitel.hist.no \
    --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