From: Alan Cox <alan@redhat.com>
To: skraw@ithnet.com (Stephan von Krawczynski)
Cc: alan@redhat.com (Alan Cox), linux-kernel@vger.kernel.org
Subject: Re: Tighten up serverworks workaround.
Date: Mon, 3 Mar 2003 09:42:37 -0500 (EST) [thread overview]
Message-ID: <200303031442.h23EgbR02502@devserv.devel.redhat.com> (raw)
In-Reply-To: <20030303134650.584c9f11.skraw@ithnet.com> from "Stephan von Krawczynski" at Mar 03, 2003 01:46:50 PM
> We are a bit astonished since we expected serverworks-based hardware to perform
> _better_ than VIA...
My experience is that in general it does.
> The email you commented is only a small hint that within -pre5 there are still
> declared-unknown parts of the chipset. Based on the theory that they are named
> "unknown" because nobody around here knows them, it might have been an adequate
> idea to ask someone from serverworks, or not? This is in no way meant offensive.
Sure, but lets not give senior folks at Serverworks a full blast of l/k.
Its better to sumarise the issues. In some cases vendors do have docs,
so the unknown device ids missing from lspci for example can be dealt with
outside already
prev parent reply other threads:[~2003-03-03 14:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 13:49 Tighten up serverworks workaround davej
2003-02-26 16:27 ` Alan Cox
2003-02-26 16:29 ` Dave Jones
2003-02-26 16:36 ` Alan Cox
2003-02-26 17:27 ` Kimball Brown
2003-02-26 18:03 ` Alan Cox
2003-02-26 18:47 ` Jonathan Lundell
2003-02-27 12:14 ` Ingo Oeser
2003-03-03 9:03 ` Mike A. Harris
2003-03-03 10:45 ` Stephan von Krawczynski
2003-03-03 12:02 ` Alan Cox
2003-03-03 12:46 ` Stephan von Krawczynski
2003-03-03 14:42 ` Alan Cox [this message]
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=200303031442.h23EgbR02502@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=skraw@ithnet.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