All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Park <parkw@better.net>
To: Andre Hedrick <andre@linux-ide.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: VIA686B + 2.2.18 (was: VIA686A chipset crash under 2.4.2-ac20)
Date: Fri, 16 Mar 2001 14:50:30 -0500	[thread overview]
Message-ID: <20010316145030.A7907@better.net> (raw)
In-Reply-To: <4219755109.20010316192322@student.luth.se> <Pine.LNX.4.10.10103161041040.14210-100000@master.linux-ide.org>
In-Reply-To: <Pine.LNX.4.10.10103161041040.14210-100000@master.linux-ide.org>; from andre@linux-ide.org on Fri, Mar 16, 2001 at 10:42:26AM -0800

On Fri, Mar 16, 2001 at 10:42:26AM -0800, Andre Hedrick wrote:
> 
> Okay not to worry, I now have a my hands on a VIA 686B and will look
> at the changes that happened to the VIA686A
> 
> Have you run 2.2.18 plus my patches off kernel.org?

Hi Andre, 

I'm running 2.2.18 on VIA686B (ABit VP6).  Some time ago, you mentioned
that you got ~80Mb/s from 'hdparm -t /dev/hda'.  Please tell us how?
Which hdparm/kernel options did you enable?

:wq --William Park, Open Geometry Consulting, Linux/Python, 8 CPUs.

  parent reply	other threads:[~2001-03-16 19:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-15 16:22 VIA686A chipset crash under 2.4.2-ac20 kozkir-8
2001-03-16 18:11 ` Andre Hedrick
2001-03-16 18:23   ` Re[2]: " kozkir-8
2001-03-16 18:42     ` Andre Hedrick
2001-03-16 19:03       ` Kirill Kozmin
2001-03-16 19:38         ` Andre Hedrick
2001-03-16 19:50       ` William Park [this message]
2001-03-20 18:39         ` VIA686B + 2.2.18 (was: VIA686A chipset crash under 2.4.2-ac20) Andre Hedrick
2001-03-21 23:34       ` VIA686A chipset crash under 2.4.2-ac20 Kirill Kozmin
2001-03-26 22:28         ` VIA686b chipset and dma_intr errors, and 3c905B errors Nicholas Petreley
2001-03-27  4:19           ` Nicholas Petreley

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=20010316145030.A7907@better.net \
    --to=parkw@better.net \
    --cc=andre@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.