From: Tomas Szepe <szepe@pinerecords.com>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.19, don't "hdparm -I /dev/hde" if hde is on a Asus A7V133 Promise ctrlr, or...
Date: Thu, 19 Dec 2002 12:14:50 +0100 [thread overview]
Message-ID: <20021219111450.GD17201@louise.pinerecords.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10212190217240.8350-100000@master.linux-ide.org>
> > > > So. I /think/ that somehow the Promise controller isn't being
> > > > initialized properly by the Linux kernel, UNLESS the mobo's BIOS
> > > > inits it first?
> > >
> > > In some situations yes. The BIOS does stuff including fixups we mere
> > > mortals arent permitted to know about.
> >
> > OTOH mere mortals are allowed to make full dump of PCI config ;)
> >
> > "D.A.M. Revok" <marvin@synapse.net>, can you send lspci -vvvxxx
> > outputs when you boot with BIOS enabled and BIOS disabled?
>
> Promise knows this point.
> Thus they moved the setting to a push/pull in the vendor space in the
> dma_base+1 and dma_base+3 respectively.
>
> lspci -vvvxxx fails when the content is located in bar4 io space.
Clearly Promise is the one storage vendor whose products are best avoided.
Andre, could you give a recommendation on what add-on IDE controllers are
not junk hardware and will work nicely with Linux? 'Cos I can't seem to
remember seeing anything in the shelves other than Promise or CMD64X/68X.
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2002-12-19 11:07 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <233C89823A37714D95B1A891DE3BCE5202AB1B35@xch-a.win.zambeel.com>
2002-12-18 10:38 ` 2.4.19, don't "hdparm -I /dev/hde" if hde is on a Asus A7V133 Promise ctrlr, or D.A.M. Revok
2002-12-18 10:44 ` Andre Hedrick
2002-12-18 21:35 ` D.A.M. Revok
2002-12-18 22:01 ` Andre Hedrick
2002-12-18 22:38 ` Alan Cox
2002-12-18 21:58 ` Andre Hedrick
2002-12-18 22:03 ` D.A.M. Revok
2002-12-19 1:11 ` Alan Cox
2002-12-19 14:40 ` Denis Vlasenko
2002-12-19 10:19 ` Andre Hedrick
2002-12-19 11:14 ` Tomas Szepe [this message]
2002-12-19 11:45 ` Andre Hedrick
2002-12-19 12:03 ` Tomas Szepe
2002-12-19 12:41 ` Andre Hedrick
2003-01-16 18:54 ` Ookhoi
2002-12-19 15:14 ` Denis Vlasenko
2002-12-19 10:33 ` Andre Hedrick
2002-12-19 18:12 ` Ross Biro
2002-12-19 6:47 ` Ross Vandegrift
[not found] ` <Pine.LNX.4.10.10212181359350.8350-100000@master.linux-ide. org>
2002-12-19 13:26 ` Stephen Satchell
2002-12-21 23:22 Jason Radford
2003-01-17 16:47 ` Paul Jakma
[not found] <200212182204.gBIM48uD000332@darkstar.example.net>
2002-12-18 22:18 ` D.A.M. Revok
2002-12-19 2:02 ` Mike Dresser
-- strict thread matches above, loose matches on Subject: below --
2002-12-15 20:49 D.A.M. Revok
2002-12-15 21:39 ` John Bradford
2002-12-15 22:25 ` D.A.M. Revok
2002-12-15 23:37 ` John Bradford
2002-12-18 18:19 ` Ross Biro
2002-12-18 18:17 ` Ross Biro
2002-12-18 21:10 ` Andre Hedrick
2002-12-18 21:19 ` Ross Biro
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=20021219111450.GD17201@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--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.