Re: 2.4.19, don't "hdparm -I /dev/hde" if hde is on a Asus A7V133 Promise ctrlr, or...

[Tomas Szepe]

> > > > > > 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" <[e-mail]>, 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.
> 
> I would not say this is the case.  What is going on is people are wanting
> to migrate to more of an internal hidden operation.
> 
> Think about it from their side.
> They want to make it easier to program the card.

The result of their attempts has seemed to be the exact opposite
so far, so I'd say they're either hiding a bit too much or the
hardware doesn't cut it.

Anyway, what are the chances of the 2.4.21-pre PDC driver getting
fixed up so it works like it did in 2.4.18?

> Linux is an OS that like to know what is going on all the time,
> and the two clash.

Are you suggesting something to the point of Windows not having
to cope with the same issues?  There has to be some kind of fundamental
difference given Promise themselves successfully hosed the Linux driver
the instant they touched it, while the Windows one just works. :)

-- 
Tomas Szepe <[e-mail]>